Service Provider Requirements for Ethernet Control with GMPLS draft-ietf-ccamp-ethernet-gmpls-provider-reqs-00.txt Wataru Imajuku (Ed.) NTT Nabil Bitar (Ed.) Verizon Tomohiro Otani (Ed.) KDDI R&D Labs. 72nd IETF Dublin July 2008

Scope of ID Clarify service provider requirements for basic B-VLAN control over IEEE802.1Qay networks Scope of IEEE802.1Qay is Traffic Engineering over IEEE802.1ah (B-VLAN) based Ethernet This ID does not exclude S/C-VLAN control over IEEE802.1ad or .1Q networks, because IEEE802.1ah networks can include IEEE802.1ad based Ethernet Switches as Backbone Core Bridges (BCBs) IEEE802.1Qay like implementation is possible even for these IEEE802.1ad based Ethernet Switches IEEE802.1ah based Ethernet Switch Equipment is expected to support S-tagged IF/C-tagged IF as well as I-tagged IF. 72nd IETF Dublin July 2008

Status of This Document Original document draft-imajuku-ccamp-ethernet-gmpls-req-01.txt Submitted to IETF70 (Vancouber) meeting Adopted as WG document in April draft-ietf-ccamp-ethernet-gmpls-provider-reqs-00.txt Change from Original Document Deleted “4.1.3 Hybrid operation with legacy Ethernet” Based on comment from Niel (Thank you, Niel) 72nd IETF Dublin July 2008

Next Step Update requirements based on the discussion amongst SPs, especially Addressing Asymmetric bandwidth QoS control P&R requirements Layer 2 control specific OAM requirements Security requirements P2MP requirements Change Editor from NTT Wataru Imajuku has been transferred to NTT Communications Yoshiaki Sone takes over his mission 72nd IETF Dublin July 2008

Appendix: Requirements (Single Layer) Control plane architecture and functionalities Support for in-band control plane channel Support for automatic neighbor discovery mechanism Assume hybrid operation with legacy Ethernet Ethernet Label Switched Path (Eth-LSP) control Prevention of loops Service control Support for control mechanisms of service type at egress port OA&M Should capitalize on existing OA&M functionalities Such as IEEE802.3ag/ITU-T Y.1731 Link Aggregation Assume Eth-LSP control over Bandwidth Flexible Links, i.e., Link Aggregation Group (LAG) Links Support for priority control of Eth-LSPs Support for re-routing mechanism following change of “Link Bandwidth” Inter-domain Support for inter-domain Eth-LSP traversing over various kinds of demarcation points (Facing I-tagged, S-tagged, or C-tagged interfaces). 72nd IETF Dublin July 2008

Appendix: Requirements (Multiple Layers) Support for dynamic formation of Link Aggregation Group Layer 2 GMPLS and Layer 1 GMPLS inter-working Similar requirements to MPLS-GMPLS inter-work. End-to-end signaling of Eth-LSPs Triggered establishment of L1 LSPs Selective advertisement of FA into L2 domain Etc. Scalability Number of service ports Number of bundled S-VLANs mapped to I-SID and Eth-LSPs (Need control of mapping at egress node). 72nd IETF Dublin July 2008