Presentation on theme: "3/12/2008CCAMP IETF 71 Philadelphia1 GMPLS Ethernet Label Switching Architecture and Framework draft-ietf-ccamp-gmpls-ethernet-arch-01.txt Design Team."— Presentation transcript:
3/12/2008CCAMP IETF 71 Philadelphia1 GMPLS Ethernet Label Switching Architecture and Framework draft-ietf-ccamp-gmpls-ethernet-arch-01.txt Design Team Don Fedyk Lou Berger Loa Andersson George Swallow
3/12/2008draft-ietf-ccamp-gmpls-ethernet-arch-012 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
3/12/2008draft-ietf-ccamp-gmpls-ethernet-arch-013 PBBN Switching Types S-tagged bundled all-to-one transparent PBBN Customer Service Interfaces I-taggedPort (MAC) based one-to-one many-to-one
3/12/2008draft-ietf-ccamp-gmpls-ethernet-arch-014 Control Plane and GMPLS Signaling Scope Core Edge Ethernet Services EthernetCore Framework Single and Multi Domain Control plane Transport Ethernet Service Signaling Services Model Edge UNI NNI Edge Services Ethernet Services Core Peer
3/12/2008draft-ietf-ccamp-gmpls-ethernet-arch-015 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.
3/12/2008draft-ietf-ccamp-gmpls-ethernet-arch-016 Next Steps Update draft: Based on discussion Other comments to WG/list/authors