CCAMP - 71th IETF 1

Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 Ethernet Service

Switching

draft-berger-ccamp-gmpls-ether-svcs-01.txt

Lou Berger <lberger@labn.net>Dimitri Papadimitriou<dimitri.papadimitriou@alcatel-lucent.be>Don Fedyk <dwfedyk@nortel.com>

CCAMP - 71th IETF 2

RecapObjective of draft:

Define GMPLS signaling support for MEF/G.8011 service switchingBased on GMPLS and GMPLS Calls (RFC4974)Support UNI draft-berger-ccamp-gmpls-mef-uni

Draft provides:New switching services• EPL: Ethernet Private Line

– Supports a single port-to-port Ethernet connection (EVC)

• EVPL: Ethernet Virtual Private Line– Multiplexed service – Based on Ethernet VLAN tags/IDs

– Uses new label format

Other service specifics

CCAMP - 71th IETF 3

Changes from previous versionAddress Dimitri’s points from last meeting:Better align terminology with other GMPLS documents •e.g., switching vs. services

Consolidate generic GMPLS extensions•Now in section 5•May be moved into standalone document

Switching Type for EVPL•Pending outcome of broader discussion

Some text cleanupNo other technical changesStill have some open issues

CCAMP - 71th IETF 4

Generic GMPLS ExtensionsMotivated by EPL/EVPL but generally applicable:

Notify message format• Allow LSP_ATTRIBUTES object in notifies

Data channel switching• Digital switching of a single channel supporting port

Channel set label • Allows a single label object to represent multiple data channels(Label_set for label)

Open question:Separate or leave in tech. specific draft?

If WG agrees generally useful SeparateIf not Leave as is

CCAMP - 71th IETF 5

EVPL Switching Type

EVPL: Ethernet Virtual Private Line Multiplexed service – Based on Ethernet VLAN tags/IDsMultiple connections per port Each connection can support multiple VLAN IDs (up to 4K)

Open question: Which switching type?RFC3945 defines L2SC• Interfaces that recognize frame/cell boundaries and can switch data based on the content of the frame/cell header (e.g., Ethernet bridges and ATM)

Use of L2SC TBD• As discussed earlier

CCAMP - 71th IETF 6

Next steps

WG document?

Other comments?

CCAMP - 71th IETF 7

Some additional details

CCAMP - 71th IETF 8

Data Channel SwitchingMotivated by EPL service

Port-to-port switching on a digital levelDoesn’t match current switching typesSimilar to an opaque OXC that handles a single wavelength• Which is Lambda-Switch Capable (LSC) per Section 3.5 of RFC4202

New switching type: Data-Channel Switch Capable

DCSC interfaces are able to support switching of the whole digital channel presented on single channel interfaceMust use port labels

Can support multiple encodingsE.g., Ethernet or Line (8B/10B)

CCAMP - 71th IETF 9

Channel Set Label+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Length | Class-Num (16)| C-Type (TBA) |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Channel_Set Sub-Object 1 |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+: : :+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Channel_Set Sub-Object N |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Action | Num Subchannels | Label Type |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Subchannel 1 || +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| ... | :+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ :: : :: : :+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| Subchannel N || +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+| ... | Padding |+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Generalized Channel_Set LABEL

Channel_Set Sub-Object

Action (from RFC3471):0 – Inclusive List1 – Exclusive List2 – Inclusive Range3 – Exclusive Range