Transcript PPT Version
ITU-T Study Group 13 Communications to IETF CCAMP Working Group Marco Carugi ITU-T SG13 Liaison Officer to IETF CCAMP [email protected] and Tomonori Takeda Editor of ITU-T SG13 L1 VPN documents [email protected] What is ITU-T SG13? What areas does it work in? – Multi-protocol and IP-based networks and their internetworking – Lead Study Group for IP related matters, B-ISDN, Global Information Infrastructure and satellite matters What are its main topics? – services on IP/MPLS-based networks, architecture, interworking and adaptation, OAM and network management, performances and resource management, end-to-end considerations (such as QoS) What new study areas is it looking at? – Next Generation Networks (NGN) : a key area of interest for the whole ITU in next period • Requirements and architectures are the main current work areas – Continuation/extension of current studies • Ex. Ethernet OAM, Generic VPN architectures, services over MPLS (Voice, Mobile IP) What are the timescales? – NGN project milestones are under work – New study period (4Q04-08) will imply new structure of ITU-T Study Groups • SG13 has just formulated his future study plan (new Questions) NGN project Some key objectives of the Next Generation Network Project – Service Convergence – Flexibility for easy service creation – Full Mobility – Multi-layering – Security, manageability, QoS support Current status – SG13 has setup a task force to speed up the initial phase : JRG-NGN – Set of foundational deliverables is under work (plan for consent in 2004) – Growing involvement of other Study Groups – Cooperation with other standard organisations, including IETF, will be certainly required (but we are not yet there) If interested in this work, please contact SG13 Liaison COM13–LS23: info on L1 VPN work From SG13 (Question 11) to IETF CCAMP / L2VPN / L3VPN WGs Main Liaison objective : info on status of ITU L1 VPN Recs (attached) – Y.1312 (L1 VPN Generic Requirements and Architecture elements) : approved in Sept 03 – Y.1313 (L1 VPN service and network architectures) : consented in Feb 04 L1 VPN Questionnaire (attached) – details in liaison – Evaluation of community interest, input for assessment of priorities and direction of future work – To be filled by interested parties, summary of collected feedback will be made public L1 VPN framework Internet draft (attached) – Objective : improve understanding of ITU work inside IETF and for further cooperation – Co-authored by individual people who have all participated into the ITU L1 VPN work – Content basically summarizes the above two Recommendations Next SG13 steps in the L1 VPN area – Picture under completion in next months – Cooperation with other standard efforts seems essential and beneficial on both sides – Possible areas of cooperation with IETF require further discussion • This liaison is a way to move on our dialogue Draft overview • Title: Framework for Layer 1 Virtual Private Networks <draft-takeda-l1vpn-framework-00.txt> • Authors : • Raymond Aubin (Nortel) • Marco Carugi (Nortel) • Ichiro Inoue (NTT) • Hamid Ould-brahim (Nortel) • Tomonori Takeda (NTT) • Summary • ITU-T SG13 has been researching and specifying both the requirements and the architecture of L1VPNs for some time. • The ID provides a framework for L1VPNs and the realization of the framework by those networks being controlled by GMPLS protocols. • Possible deployment scenarios are described : Carrier’s carrier, Multi service backbone Concept of L1VPN • Customers are provided with a virtual optical network using dedicated or shared resources. • Connectivity restriction: Layer 1 connectivity is provided to a limited set of CE's physical interfaces. (This set forms the L1VPN membership.) • Per VPN control and management: Some level of control and management capability is provided to the customer. L1VPN customer interfaces (or service interfaces) for customer#1 VPN#1 CE CE PE CE Provider network PE CE PE P CE PE CE VPN#2 L1VPN customer interfaces (or service interfaces) for customer#2 L1VPN Service Models Type of the customer interface Management based service model Control based service model Type of information exchanged Signaling based service model (Overlay service model) Signaling and routing service model UNI (Overlay) type of interface NNI (Peer) type of interface Type of routing information exchanged Virtual Per VPN link model peer model