1. CCAMP - 69th IETF1 Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G.8011 User-Network Interface (UNI) draft-berger-ccamp-gmpls-mef-uni-00.txt Lou Berger Don Fedyk

2. CCAMP - 69th IETF2 Background Multiple liaisons From OIF/ITU Initial focus on traffic parameters (G.8011/MEF10.1) More recent included label format for VLAN lists Original draft objective Provide a label format for VLAN lists based on label sets  Found that implications weren’t “just a label format” Current draft objective Define GMPLS based support for MEF/G.8011 UNI Based on GMPLS UNI (RFC4208)

3. CCAMP - 69th IETF3 Draft Highlights Leverages GMPLS UNI (RFC4208) and GMPLS Calls Uses MEF Traffic parameters See draft-ietf-ccamp-ethernet-traffic-parameters- Majority of document focus on Ethernet Service support – not UNI specifics Draft to be split 1.Draft covering new switching type and new services 2.Draft covering UNI specific topics

4. CCAMP - 69th IETF4 Draft Scope Limited to UNI-C to UNI-N Service provider / Transport network is out of scope Two service types EPL – Ethernet Private Line (port-to-port service) EVPL – Ethernet Virtual Private Line (VLAN based service) Source: ITU G.8011

5. CCAMP - 69th IETF5 GMPLS UNI (RFC4208) and Calls GMPLS UNI (RFC4208) and GMPLS Calls used unmodified GMPLS UNI (RFC4208) provides Reference model Addressing approach GMPLS Calls provides Connection identification Foundation for Ethernet Endpoint (UNI) identification Avoiding large messages via multiple LSPs

6. CCAMP - 69th IETF6 Ethernet Endpoint (UNI) Identification Ethernet endpoint (UNI) ID is character based Need to carry ID in signaling Carried via new LSP_ATTRIBUTES Endpoint ID TLV Required during call establishment (notifies) Optional in LSP messages May need to resolve ID to IP address When remote UNI-C’s IP address isn’t know Handled with specific procedures during call establishment

7. CCAMP - 69th IETF7 EPL Service EPL: Ethernet Private Line Supports a single port-to-port connection (EVC) EPL Type 1: Frame based connection All MAC Frames transported by provider across connection EPL Type 2: Character based connection All 8B/10B encoded information transported across connection Port to port Service

8. CCAMP - 69th IETF8 EPL Specifics EPL is a port-to-port connection service Doesn’t match current switching types Similar 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 interface Must use port labels Encoding based on EPL service type Type 1/MEF Ethernet Type 2 8B/10B*

9. CCAMP - 69th IETF9 EVPL Service EPL: Ethernet Virtual Private Line Multiplexed service – Based on Ethernet VLAN tags/IDs Multiple connections per port Each connection can support multiple VLAN IDs (up to 4K) EVC 1 EVC 2

10. CCAMP - 69th IETF10 EVPL Specifics EVPL service implies MAC layer (VLAN ID) switching Switching type: L2SC LSP Encoding:Type Ethernet G-PID:Ethernet Need to represent up to 4K VLAN IDs New label: Generalized Channel_Set Label EVPL Generalized Label New C-types for all label related objects LABEL_REQUEST, LABEL, SUGGESTED_LABEL, LABEL_SET, ACCEPTABLE_LABEL_SET, UPSTREAM_LABEL, RECOVERY_LABEL

11. CCAMP - 69th IETF11 EVPL Related Label Formats +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | 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 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Rsvd | VLAN ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Generalized Channel_Set LABEL Channel_Set Sub-Object EVPL Generalized Label (subchannel) Format Action (from RFC3471): 0 – Inclusive List 1 – Exclusive List 2 – Inclusive Range 3 – Exclusive Range

12. CCAMP - 69th IETF12 EVPL - Symmetric labels Use same label values in both directions Optimization to save message size Allows network to select label (VLAN IDs) for both direction Signaled by setting Num Subchannels to 0 In either LABEL or UPSTREAM_LABEL Draft to be updated to allow for use in either Actual labels carried in other label object

13. CCAMP - 69th IETF13 EVPL - Multiple LSPs Single EVPL connection may use many VLAN IDs May result in large label object  fragmentation Multiple LSPs used to avoid fragmentation All LSPs signaled within a single GMPLS Call Single LSP SHOULD be used when possible Make-before-break (MBB) used to modify label or service parameters When using multiple LSPs All LSPs must use same service related objects All SHOULD share resources VLAN ID modification via LSP add/drop or MBB Service parameter changes require MBB for all LSPs

14. CCAMP - 69th IETF14 Next Steps Resolve open issues Will use generic term “line” rather than "8B/10B" LSP Encoding Type Document assumes that [MEF-TRAFFIC] supports signaling of desired L2 control protocol processing, but this is not yet included in [MEF-TRAFFIC]. Document will be divided into two documents: one that defines generic GMPLS support for Ethernet Services and the new DCSC Switching Type, and one that covers UNI specific topics. Other comments?