Functional Groupings and Block Allocation (TSAG-R30, Annex 2, 3)

Total Page:16

File Type:pdf, Size:1020Kb

Functional Groupings and Block Allocation (TSAG-R30, Annex 2, 3)

INTERNATIONAL TELECOMMUNICATION UNION COM 16 – ILS 19 – E TELECOMMUNICATION STANDARDIZATION SECTOR English only STUDY PERIOD 2001-2004 Original: English Question(s): ALL/16; 1-20/15 Geneva, 16-26 November 2004 Ref.: COM 15 – LS 3 – E Source: ITU-T SG 15 Title: Response to TSAG LS on “ToR and Action Plan for continued ITU-T SGs Restructuring Group”

To: TSAG (cc All ITU-T SGs) Approval: Agreed to at SG 15 meeting (Geneva, 19-30 April 2004) For: Information/Action Deadline: N/A Contact: Peter Wery Tel: +1 613 828 5691 Nortel Networks (Canada) Fax: +1 819 671 3731 Canada Email: [email protected]

In response to TSAG’s liaison statement (Nov. 2003) on ‘ToR and action plan for continued ITU-T SGs Restructuring Group’ (TD 7R1/GEN, SG 15, April 2004), SG 15 has prepared this liaison statement at its recent meeting, 19-30 April 2004.

This liaison statement takes into account the functional grouping and block allocation for ‘Optical and other Transport Network Infrastructures’ (13C, 13D, 15A, 15B, 17B) as developed at the November 2003 meeting of TSAG, as well as subsequent liaison statements to TSAG from SG 13 (TD 322/TSAG) and SG 17 (TD 335, 338/TSAG), and the report of the 5-7 April 2004 Ottawa meeting of the TSAG Restructuring Group of ITU-T (TD 340R1/TSAG).

SG 15 continues to support the notion that any new ITU-T SG structure will retain a SG with a strong focus on optical and other transport network infrastructure. SG 15 welcomes the efforts of TSAGs Correspondence Group on Restructuring and views this as a much needed exercise to keep ITU-T at the forefront as a global telecommunication standards developing organization.

Functional groupings and block allocation (TSAG-R30, Annex 2, 3) Overall, Study Group 15 supports the block allocation as given in TSAG-R30, Annex 2 and 3, i.e. - Optical and other Transport Network Infrastructures 13C, 13D, 15A, 15B, 17B Taking into account the developments on restructuring since the TSAG meeting of November 2003, Study Group 15 would like to provide some additional clarification with regard to Blocks 13C, 13D, 15B and 17B, as they relate to the scope of the work that belongs with the functional grouping of ‘Optical and Other Transport Network Infrastructures’ (successor of SG 15).

Attention: Some or all of the material attached to this liaison statement may be subject to ITU copyright. In such a case this will be indicated in the individual document. Such a copyright does not prevent the use of the material for its intended purpose, but it prevents the reproduction of all or part of it in a publication without the authorization of ITU. - 2 - COM 16 – ILS 19 – E

Study Group 15 has also prepared a set of revised/new Questions for study in the 2005-2008 ITU-T Study Period (TD /TSAG). The allocation of these Questions to functional Blocks 15A, 15B and 15C is shown in Attachment 1.

Ethernet related standardization activities (Block 13C) Subsequent to the functional grouping and block allocation of the November 2003 TSAG meeting (TSAG-R30, Annex 2, 3), Study Group 13 at its final meeting in February 2004 developed a set of draft revised/new Questions for study in the 2005-2008 ITU-T Study Period (TD 322/TSAG). In the final paragraph of clause 3 of this document, Study Group 13 argues that Ethernet OAM is inextricably related to NGN OAM strategies, and therefore should remain with the continuing work of Study Group 13. Certain participants in Study Group 15 are sympathetic to this argument, with the result being that Study Group 15 will no longer strongly advocate that the Ethernet OAM work be grouped with the related Ethernet work from Study Group 15 for the next study period. However, Study Group 15 also notes that Question E/13 (OAM and network management for NGN) addresses several transport technology specific survivability mechanisms, including protection switching for Ethernet, MPLS, and ATM based transport networks. Related Recommendations include I.630 (ATM protection) and Y.1720 (MPLS protection), and draft new Recommendation Y.17ethps (Ethernet protection switching) . Under Question 9/15, Study Group 15 over the years has addressed and continues to address network protection and other survivability mechanisms for specific transport technologies. It has developed and continues to develop a number of Recommendations on generic and technology specific protection switching, such as the G.808 series on generic protection switching, the G.840 series on SDH protection switching, and the G.873 series on OTN protection switching. It is therefore proposed that the study of transport technology specific survivability mechanisms (including protection) be carried out in a transport network oriented Study Group (successor of Study Group 15). This includes responsibility for current Recommendations I.630 and Y.1720, as well as responsibility for completion of new draft Recommendation Y.17ethps. Study Group 15 has prepared a proposed division of the work of Q.E/13 into two Questions, Q.E1/13 (OAM and network management for NGN) to be addressed in a NGN oriented Study Group (see Attachment 2), and Q.E2/13 (Technology Specific Transport Plane Protection Switching and survivability) to be addressed under the functional grouping of ‘Optical and Other Transport Network Infrastructures’ (successor of SG 15) (see Attachment 3). Transport Network Architecture (Block 13D) Draft Question P/13 (Core network architecture) corresponds to Block 13D, and the transfer of this Question and related Recommendations G.805, G.807 and G.809 to the functional grouping of ‘Optical and Other Transport Network Infrastructures’ (successor of SG 15) is appropriate, fully supported by Study Group 15 and is in line with the November 2003 conclusions of TSAG (TSAG- R30, Annex 2, 3). Network Signal Processing (Block 15C) Participants of WP 2/15 represent a close group of experts which for the most part participate in all of WP 2/15’s Questions (Q.5, 6, 7, 8/15). It is therefore most important that a transfer of these activities keep these activities together as one group. Other important considerations for participants in Block 15C are that any SG that would become the new ‘home’ for Block 15C would have to:

ITU-T\COM-T\COM16\LS\19E.DOC - 3 - COM 16 – ILS 19 – E i) provide for at least 8 working days during a SG meeting for discussions at the WP and Question level, consistent with the current 2 week duration of SG 15 meetings; ii) maintain essentially serial sessions for all Questions of Block C so that all participants can attend the meetings. IP related lower layer issue (Block 17B) On a number of occasions during the current Study Period work under Q.7/17 (currently evolved to Q.C/17) and Q.9/15 and 11/15 have produced competing solutions to the same issues (packet adaptation into TDM and WDM transport, network protection). This does not serve industry well. As a result of a Study Group 15 initiative, a lot of interaction, including joint meetings, between these Questions of two Study Groups was necessary in the areas of LAPS and Multiple Service Rings (MSR). While this proposal did not initiate from our Study Group, Study Group 15 sees an advantage if the work of Q.C/17 relating to packet adaptation into transport and network protection was allocated to transport network oriented Study Group (successor of Study Group 15) that already covers these topics. Study Group 15 has prepared a proposed division of the work of Q.C/17 into a Q.C1/17 (Protocols and service mechanisms for Multi-service Data Networks (MSDN)) to be addressed in a Data oriented Study Group (see Attachment 4), and a Q.C2/17 (Data transport protocols) to be addressed under the functional grouping of ‘Optical and Other Transport Network Infrastructures’ (successor of SG 15) (see Attachment 5).

ITU-T\COM-T\COM16\LS\19E.DOC - 4 - COM 16 – ILS 19 – E

Attachment 1

ITU-T Study Group 15 Optical and other transport networks List of Questions ITU-T Study Period 2005-2008

Question Title Continuation of Restr. Question Block A1/15 Optical systems for fiber access networks 2/15 15A A2/15 Transceivers for customer access and in-premises phone line 4/15 15A networking systems on metallic pairs B1/15 Circuit multiplication equipment and systems 5/15 15C B2/15 Speech enhancement in signal processing network equipment 6/15 15C B3/15 Voice gateway equipment 7/15 15C B4/15 Interaction aspects of signal processing network equipment 8/15 15C C1/15 Transport equipment and network protection/restoration 9/15 15B C2/15 Signal structures, interfaces and interworking for transport 11/15 15B networks C3/15 Technology specific transport network architectures 12/15 15B C4/15 Network synchronization and time distribution performance 13/15 15B C5/15 Management and control of transport systems and equipment 14/15 15B D1/15 Characteristics and test methods of optical fibres and cables 15/15 15B D2/15 Characteristics of optical systems for terrestrial transport networks 16/15 15B D3/15 Characteristics of optical components and subsystems 17/15 15B D4/15 Characteristics of optical fibre submarine cable systems 18/15 15B D5/15 Optical fibres and cables for the access network to and in 20/15 15B buildings and homes E1/15 Coordination of Access Network Transport standards 1/15 15A E2/15 General characteristics of optical transport networks 19/15 15B

ITU-T\COM-T\COM16\LS\19E.DOC - 5 - COM 16 – ILS 19 – E

Attachment 2

Question E1/13 - OAM and network management for NGN (Continuation of part of Question 3/13) 1 Motivation OAM and network management capabilities are essential for any network technology when developing a carrier-class network. It is particular true when developing an NGN because NGN is expected to provide wide variety of services in terms of reliability and performance including highly reliable and high quality services, which require effective network management. Recommendations related to such capabilities for ATM, MPLS and Ethernet were developed by Q.3/13 in previous study periods. I.610 specifies OAM for ATM. Y.1710, Y.1711 and Y.1712 specify OAM requirements, OAM mechanisms and OAM interworking, respectively. Y.1730 specifies OAM requirements for Ethernet. Several other Recommendations related to MPLS OAM and Ethernet OAM are under development. Under the responsibility of this Question, Recommendations will be developed to provide the specifications for OAM requirements, OAM mechanisms, and OAM interworking for realizing NGN and other networks. This activity will be conducted with close cooperation with related Study Groups, IETF, IEEE, Metro Ethernet Forum and other standardization bodies as necessary. 2 Question Study items to be considered include, but are not limited to:  Clarification of requirements and mechanisms of OAM for next generation networks (NGN). This includes study on end-to-end OAM support for packet based ubiquitous networks. The OAM functions include defect detection, defect localization, topology management and performance management.  OAM and survivability functions for IP-based networks on end-to-end and segment basis. This includes study on service OAM and transport OAM for NGN. This also includes study on coordination between OAM functions indifferent layers to allow optimisation in case where the IP-based network is built on a multi-layer network.  OAM functions for MPLS-based networks including defect localization functions, performance measurement functions, OAM for multipoint-to-point LSPs.  Clarification of generic OAM principles for connection-oriented circuit switched, connection-oriented packet switched and connectionless packet switched networks.  Clarification of generic OAM principles under interworking of different network technologies. This includes network interworking and service interworking scenarios.  Clarification of requirements and mechanisms of OAM functions for VPNs realized by various technologies (e.g., Layer 3, Layer 2 or Layer 1).  OAM functions for Ethernet-based networks. This includes defect detection, defect localization and performance measurement functions. OAM functions should be able to be applied to both point-to-point and multipoint-to-multipoint networks. 3 Tasks Tasks include, but are not limited to:  Preparation of Recommendation on OAM requirements and framework for NGN.

ITU-T\COM-T\COM16\LS\19E.DOC - 6 - COM 16 – ILS 19 – E

 Preparation of Recommendation on OAM mechanisms for NGN.  Preparation of Recommendations on MPLS OAM mechanisms including defect localization functions, performance management functions (if necessary) and support of multipoint-to- point LSPs.  Preparation of Recommendation on OAM functions for networks under interworking of different network technologies.  Preparation of Recommendation on OAM functions for VPNs realized by various technologies.  Recommendation on OAM functions for Ethernet-based networks including support of multipoint-to-multipoint networks. 4 Relationships Recommendations: I and Y series Questions: Q.B, C and I/13 Study Groups: ITU-T Study Groups on network architecture including MPLS and Ethernet. ITU-T Study Groups on TMN and network management principles and specifications ITU-T Study Groups on SDH and ATM TMN architecture and on transport systems and equipment. Standardisation bodies fora and consortia: IETF working groups related to network management and OAM IEEE 802.1 and 802.3 working groups MEF MPLS and Frame Relay Alliance

ITU-T\COM-T\COM16\LS\19E.DOC - 7 - COM 16 – ILS 19 – E

Attachment 3

Question E2/13 – Technology specific transport plane protection switching and survivability (Continuation of part of Q.3/13)

1 Motivation Protection switching and survivability capabilities are essential for any network technology when developing a carrier-class network. Recommendations related to such capabilities for ATM and MPLS are I.630 protection switching function for ATM, and Y.1720 protection switching for MPLS, respectively. Under the responsibility of this Question Recommendations will be developed to provide the survivability mechanisms including protection switching and rerouting for networks based on specific transport plane technologies. This activity will be conducted with close cooperation with related Study Groups, IETF, IEEE, Metro Ethernet Forum and other standardization bodies as necessary. The following major Recommendations, in force at the time of approval of this Question, fall under its responsibility: I.630, Y.1720. 3 Question Study items to be considered include, but are not limited to:  Clarification of requirements and mechanisms of survivability functions for networks based on specific transport plane technologies. This includes study on end-to-end OAM support for packet based ubiquitous networks. The survivability functions include protection switching and other survivability techniques such as rerouting.  Survivability functions for transport layer networks on end-to-end and segment basis. This also includes study on coordination between OAM functions in different layers to allow optimization for multi-layer networks.  Survivability functions for MPLS-based networks including shared mesh MPLS protection, fast MPLS protection and rerouting.  Survivability functions for Ethernet-based networks. This includes protection switching and other recovery techniques.

3 Tasks Tasks include, but are not limited to: - Preparation of Recommendation on MPLS survivability functions including shared mesh protection, fast protection and rerouting. Relationships between protection switching and rerouting should be clarified. - Recommendation on Ethernet protection switching and other survivability techniques.

4 Relationships Recommendations: G, I and Y series Questions: Q.E1/13, Q.C1/15 Study Groups: ITU-T Study Groups on network architecture including MPLS and Ethernet. ITU-T Study Groups on TMN and network management principles and specifications ITU-T Study Groups on SDH and ATM TMN architecture and on transport systems and equipment. Standardisation bodies, forums and consortia: IETF working groups related to network management and OAM IEEE 802.1 and 802.3 working groups MEF MPLS and Frame Relay Alliance Study Group 13 on NGN aspects

ITU-T\COM-T\COM16\LS\19E.DOC - 8 - COM 16 – ILS 19 – E

Attachment 4

Question C1/17: Protocols and service mechanisms for Multi-service Data Networks (MSDN) (continuation of part of Q.7/17)

1 Motivation This Question is intended to provide protocols and service mechanisms for support of multi-service data networks (MSDN). Ethernet MAC, RPR MAC and other telecommunication channels have been deployed already and are continuing to develop all over the world. Multiple Service Ring based on RPR, is a multi-service Metro network technology that can also be used in various topologies. This Question addresses how to make use of these existing broadband resources effectively to provide multi-service data network applications. This Question provides the protocols and service mechanisms for MSDN. The new Recommendations will be suited for the existing multi-service data networks and various MAC (Ethernet, Gigabit Ethernet, RPR) engineering applications. 2 Question This Question develops Recommendations with respect to protocols and service mechanisms for MSDN. The associated work will be handled and progressed in co-operation with other study groups, the IETF, IEEE 802, MEF, etc. The scope includes: (i) Develop Requirements for MSDN, areas of study and development include: o Identification of market needs o architectural considerations, for L2 data networks; o multi-service multicast aspects; o Ethernet UNI and NNI aspects. (ii) Enhance existing packet protocols or, if required, develop new packet protocols to support the developed MSDN requirements, including service mechanisms; (iii) Develop associated MIBs (Management Information Base) to support item (iv). 3 Tasks Develop new Recommendations according to the items under study. 4 Relationships Recommendations: Questions: Study Groups: ITU-T SGs 4, 11, 13 and 15 Standardization bodies: ISO/IEC JTC 1/SC 6; IETF; IEEE 802 Committee; and Metro Ethernet Forum (MEF)

ITU-T\COM-T\COM16\LS\19E.DOC - 9 - COM 16 – ILS 19 – E

Attachment 5

Question C2/17: Data transport protocols (continuation of part of Q.7/17)

1 Motivation This Question is intended to develop protocols for the transport of data packets. Ethernet MAC, RPR MAC and other telecommunication channels have been deployed already and are continuing to develop all over the world. Multiple Service Ring based on RPR, is a multi-service Metro network technology that can also be used in various topologies. This Question addresses how to make use of these existing broadband resources effectively in order to provide multi-service data network applications. The following major Recommendations, in force at the time of approval of this Question, fall under its responsibility: X.85/Y.1321, X.86/Y.1323, X.87/Y.1324

2 Question Study items to be considered include, but are not limited to:  What enhancements are necessary for the specifications of IP and Ethernet Services over LAPS (Link Access Procedure - SDH)?  What enhancements are needed to the specifications of Multiple Services Rings based on RPR (Resilient Packet Rings as per IEEE 802.17)?  How can associated Ethernet/Gigabit Ethernet/10G Ethernet aspects be addressed in multiple services rings?

3 Tasks Tasks include, but are not limited to: - Maintenance and/or extension of current Recommendations

4 Relationships Recommendations: G.7041/Y.1303, G.7042/Y.1305, G.841, G.842, G.808.1, G.8040/Y.1340 Questions: C1/15, C2/15, C3/15, C1/17 Study Groups: SG 4 on networks maintenance SG 13 on network performance Standardisation bodies, forums and consortia: IETF Working Group pppext on IP transport IEEE 802.3 on Ethernet transport MEF on Ethernet services Issues IEEE 802.17 on Resilient Packet Rings IEEE 802.1 on Ethernet Bridges

______

ITU-T\COM-T\COM16\LS\19E.DOC

Recommended publications