60 likes | 157 Views
GMPLS Ethernet Label Switching Architecture and Framework draft-ietf-ccamp-gmpls-ethernet-arch-01.txt. Design Team Don Fedyk dwfedyk@nortel.com Lou Berger lberger@labn.net Loa Andersson loa@pi.se George Swallow swallow@cisco.com. WG ID Details updated in Feb/08.
E N D
GMPLS Ethernet Label Switching Architecture and Frameworkdraft-ietf-ccamp-gmpls-ethernet-arch-01.txt Design Team Don Fedyk dwfedyk@nortel.com Lou Berger lberger@labn.net Loa Andersson loa@pi.se George Swallow swallow@cisco.com CCAMP IETF 71 Philadelphia
WG ID Details updated in Feb/08 • Preserve Existing GMPLS Model • Addressing and Routing is IP • Extensions only where needed • Switching type under discussion • L2SC removed for discussion • May define new ones for specific technology • Extensions for service identifiers (I-SID) • New label formats for STD data planes • Requires use of Ethernet Traffic parameters • Minor text changes from 00 draft • “Transport” Ethernet • P2P Signaling • Ethernet Service Model draft-ietf-ccamp-gmpls-ethernet-arch-01
PBBN Switching Types PBBN Customer Service Interfaces Port (MAC) based S-tagged I-tagged one-to-one bundled all-to-one many-to-one transparent draft-ietf-ccamp-gmpls-ethernet-arch-01
Control Plane and GMPLS Signaling Scope Framework NNI Services Services Core Edge Ethernet UNI Services Ethernet Edge Core Services Core Edge Ethernet Peer Service Signaling Services Model Single and Multi Domain Control plane “Transport” Ethernet draft-ietf-ccamp-gmpls-ethernet-arch-01
Switching Types • We see the requirement for multiple switching types • Not L2SC because it is has been defined, may be used for ATM, Ethernet, and others. • We will need new ones for the technology specific documents • Not clear that Ethernet Switching has a true hierarchy. Even between technologies there is ambiguity. draft-ietf-ccamp-gmpls-ethernet-arch-01
Next Steps • Update draft: • Based on discussion • Other comments to WG/list/authors draft-ietf-ccamp-gmpls-ethernet-arch-01