Presentation is loading. Please wait.

Presentation is loading. Please wait.

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

Similar presentations


Presentation on theme: "Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G"— Presentation transcript:

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

2 Recap Objective of drafts: Drafts provide:
Define GMPLS based support for MEF/G.8011 UNI Based on GMPLS UNI (RFC4208) and GMPLS Calls (RFC4974) Drafts provide: 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 and UNI specifics CCAMP - 70th IETF

3 Changes from previous version
Document split: -gmpls-mef-uni-00.txt -gmpls-ether-svcs-00.txt covers new switching type and services Alignment with Ethernet Traffic parameters (draft-ietf-ccamp-ethernet-traffic-parameters-) General cleanup No significant technical changes -gmpls-mef-uni-01.txt covers UNI specifics CCAMP - 70th IETF

4 Technical Changes Draft-berger-ccamp-gmpls-mef-uni-01.txt – None
Contains only UNI specifics UNI Addressing (GMPLS UNI and CALLS) Ethernet  IP address resolution Connection Identification Draft-berger-ccamp-gmpls-ether-svcs-00.txt (Deltas from draft-berger-ccamp-gmpls-mef-uni-00.txt) Renamed encoding 8B/10B line New MEF-TRAFFIC TLV: L2 Control Protocol TLV To align with [MEF-TRAFFIC] Provides for handling of L2 control traffic at ingress and egress Per MEF10.1, G and G General text cleanup and references update CCAMP - 70th IETF

5 L2 Control Protocol (L2CP) TLV
Carried in MEF Traffic Parameters (SENDER_TSPEC) L2CP TLV Format: | Type= | Length= | | IL2CP | EL2CP | Reserved | IL2CP – Ingress Layer 2 Control Processing Value Description Reference 0 Reserved 1 Discard/Block [MEF10.1], [8011.1] and [8011.2] 2 Peer/Process [MEF10.1], [8011.1] and [8011.2] 3 Pass to EVC/Pass [MEF10.1], [8011.1] and [8011.2] 4 Peer and Pass to EVC [MEF10.1] EL2CP – Egress Layer 2 Control Processing Value Description Reference 1 Based on IL2CP Value [MEF10.1] 2 Generate [8011.1] and [8011.2] 3 None [8011.1] and [8011.2] 4 Reserved CCAMP - 70th IETF

6 Open Issue Further draft split? Proposal from Dimitri:
Split service document to match current RFC documents: Protocol generic vs. Technology specific Extensions to RFC 3471/RFC (label format and data channel switching) Extensions to RFC 4974 (call related) Extensions to Ethernet Traffic Parameters (for L2CP TLV) Continue to have UNI specific document Extensions to RFC 4208 CCAMP - 70th IETF

7 Next steps Identify and resolve open issues
Solicit feedback from MEF/OIF Do we need a liaison? Other comments? CCAMP - 70th IETF


Download ppt "Generalized MPLS (GMPLS) Support For Metro Ethernet Forum and G"

Similar presentations


Ads by Google