Motivation

As a result of the development of NGN, and the need to support of new services such as IPTV, VPN, new requirements for the public data network have emerged, such as better scalability, throughput, reliability, multipoint to multipoint communication, etc. Various new or enhanced data communication technologies have been developed and deployed in the global market, with the intent of satisfying these new requirements. During the last study period new Recommendations that provide the general requirements (Y.2601) and a high level architecture (Y.2611, technology independent), were developed. These Recommendations will be used to evolve the PDN which provides the topmost part of NGN transport stratum, to meet the industry requirements for enhanced data communications.

This Question will continue the studies on data networks and data transmission related to the PDNs, especially the FPBN (based on Y.2601, Y.2611), to provide further details of the key elements of PDN technologies, such as "middle" level architecture (maybe technology dependent), general requirements and methods for naming, routing and addressing from the technical aspect (e.g. format, types), reliability requirements and methods, etc. The objective of this work is to develop a PDN that can efficiently support the NGN packet based services over the transport network that provides connectivity using technologies such as Ethernet, T-MPLS, GFP mapping over SDH/OTN.

Work on the Recommendations for data networks has been completed and the Recommendations are currently mature. This set of Recommendations includes much of the work on the leased circuit, circuit-switched, and the X.25 packet-switched public data networks. Systems based on these data network Recommendations have been implemented over a relatively long period of time. Operational experiences in the implementation of those systems may lead to the discovery of technical errors or desirable enhancements to the related Recommendations. Therefore, there is a need for the ongoing maintenance of X-series data network Recommendations.

Recommendations under responsibility of this Question include:

F.600, X.1, X.2, X.3, X.5, X.6, X.7, X.8, X.20, X.20bis, X.21, X.21bis, X.22, X.24, X.25, X.28, X.29, X.30, X.31, X.32, X.33, X.34, X.35, X.37, X.38, X.39, X.4, X.42, X.45, X.46, X.48, X.49, X.60, X.70, X.71, X.75, X.77, X.78, X.80, X.81, X.82, X.92, X.96, X.110, X.111, X.115, X.116, X.121, X.122, X.123, X.124, X.125, X.130, X.131, X.134, X.135, X.136, X.137, X.138, X.139, X.140, X.141, X.150, X.180, X.181, X.300, X.301, X.302, X.305, X.320, X.321, X.322, X.323, X.324, X.325, X.326, X.327, X.328, X.329, X.340, X.350, X.351, X.352, X.353, X.361, X.371, Y.2601, Y.2611

Questions

• • How can the various aspects of the NGN services including, IPTV, IMS etc. (such QoS, reliability, addressing, routing, naming, security/privacy) be accommodated in the PDN, and how can the PDN best utilize the capabilities provided by the current and evolving transport network to support these NGN services?
• How can the various aspects of the NGN services including, IPTV, IMS etc. (such QoS, reliability, addressing, routing, naming, security/privacy) be accommodated in a dedicated data network, and how can that dedicated data network best utilize the capabilities provided by the current and evolving transport network to support these NGN services?
• What administrative procedures are needed for the allocation of resources for telecommunications in the disaster relief?
• What corrections or enhancements are needed in the X-series data network Recommendations?
• What enhancements to existing Recommendations are required to provide energy savings directly or indirectly in information and communication technologies (ICTs) or in other industries? What enhancements to developing or new Recommendations are required to provide such energy savings?

Tasks

Develop revised or new X or Y series data network Recommendations, as needed, based on received contributions.

There is a need for ongoing maintenance of the following F-series and X-series data network Recommendations:

• Service and operational principles – F.600
• User classes of service and optional user facilities – X.1, X.2
• DTE/DCE interfaces and access – X.3, X.5, X.8, X.20, X.20bis, X.21, X.21bis, X.22, X.25, X.28, X.29, X.30, X.31, X.32, X.33, X.34, X.35, X.37, X.38, X.39, X.42, X.45, X.46
• Structure of signals – X.4
• Technical characteristics of data transmission services – X.7
• Interchange circuits – X.24
• Signalling interfaces – X.60, X.70, X.71, X.75, X.77, X.78, X.80, X.81, X.82
• Multicast – X.6, X.48, X.49
• Hypothetical reference connections – X.92
• Call progress signals – X.96
• Routing – X.110, X.111, X.115, X.116
• Numbering and numbering plan interworking – X.121, X.122, X.123, X.124, X.125
• Quality of Service – X.130, X.131, X.134, X.135, X.136, X.137, X.138, X.139, X.140, X.141
• Maintenance testing – X.150
• Administrative arrangements – X.180, X.181
• Interworking – X.300, X.301, X.302, X.305, X.320, X.321, X.322, X.323, X.324, X.325, X.326, X.327, X.328, X.329, X.340, X.350, X.351, X.352, X.353, X.361, X.371

NOTE 1 – Recommendations X.26 (V.10) and X.27 (V.11) are under the responsibility of Study Group 16.

NOTE 2 – Recommendations X.50, X.50bis, X.51, X.51bis, X.52, X.53, X.54, X.55, X.56, X.57 and X.58 are under the responsibility of Study Group 15.

NOTE 3 – Recommendations X.160, X.161, X.162, X.163, X.170, X.171 are under the responsibility of Study Group 2.

Relationships

Recommendations: Y.2601, Y.2611, Q.933, Q.933bis, X.36, X.76, X.84, X.142, X.144-X.149, X.151, X.272; E-series numbering Recommendations

Questions: Qs 12/13, 17/13; Q.12/15

Study groups: ITU-T Study Groups 2, 11, 12, 15 and 16

Standardization bodies: ISO/IEC JTC 1/SC 6