Framework and Requirements for Layer 1 Virtual Private Networks draft-takeda-l1vpn-framework-04.txt Raymond Aubin (Nortel) Marco Carugi (Nortel) Ichiro Inoue (NTT) Hamid Ould-Brahim (Nortel) Tomonori Takeda (NTT) 63rd IETF Paris August 2005

Summary Describe the scope and overview of L1VPNs Mode/Models Requirements Motivations, Reference model, Terminologies NOTE: Focus on GMPLS related aspects only Based on ITU-T documents (Y.1312 and Y.1313) Updated from the last IETF Intensive review during WG creation Alignment with charter 63rd IETF Paris August 2005

Mode/Models Management mode: Basic mode (signaling-based): Soft Permanent Connection type Basic mode (signaling-based): Switched Connection type CE-PE functionality is limited to signaling only Enhanced mode (signaling and routing): CE-PE functionality provides signaling, plus limited reachability/TE information exchange Four sub-service models Various levels of reachability/TE information exchanged between CE-PE 63rd IETF Paris August 2005

Basic Mode Signaling, (Routing) + May distribute VPN membership/reachability Signaling Only CE TE link PE P PE TE link CE May be assigned private addresses Limits LSPs to be between CEs in the same VPN MUST support LSPs between CEs, and MAY support LSPs between devices behind CEs. 63rd IETF Paris August 2005

Enhanced Mode Signaling, (Routing) + involved in VPN reachability/TE information distribution Signaling plus limited reachability/TE information exchange CE TE link PE P PE TE link CE May be assigned private addresses Limits LSPs to be between CEs in the same VPN MUST support LSPs between CEs, and MAY support LSPs between devices behind CEs. Detailed sub-models depending on level of reachability/TE information exchanged between CE-PE. 63rd IETF Paris August 2005

Summary of Requirements Basic mode Enhanced mode CE-PE signaling YES CE-PE TE/reachability info exchange (VPN scoped) NO Private address support OPTIONAL VPN membership/reachability/TE info distribution in the provider network (membership/reachability info only) Connectivity restriction 63rd IETF Paris August 2005

Next Steps First item on the list of milestones We believe the I-D is stable Some changes for alignment may be necessary as work progresses Further liaisons with ITU-T SG13 Alignment with solution works Any comment/suggestion? Is this I-D ready for a WG document? 63rd IETF Paris August 2005