Question 2/2 - Routing and interworking plans for fixed and mobile networks

The study should be continued. With the rapid growth of IP-based networks, it will become increasingly important to ensure that integration of various voice, data and multimedia services on such networks can route and interwork with networks based on other technologies, particularly TDM-based PSTN networks, ISDN, ATM, IMT-2000 and mobile network technologies. Routing methods are currently standardized for IP- and ATM-based network technologies, which are being widely extended beyond data services to include voice, multimedia and other services integrated on a shared network. Existing routing methods are not adequate to address all the QoS and performance issues that arise with the extended applications. These issues and others are critical to be addressed by Q.2/2 in its ongoing work.

The attached Annex provides the topics that are expected to be considered in this proposed Question.

The anticipated results and associated target dates for approved text are provided in the attached Annex.

The ongoing study of routing and interworking issues will require close liaison as follows:

1) Within Study Group 2 with Questions focusing on a) numbering and addressing plans; b) network management; c) network performance; d) traffic engineering.

2) Within ITU-T Study Groups 3, 4, 7, 11 and 13. Additionally, close liaison will need to be maintained with the IETF and ATM Forum.

Annex (to Question 2/2)
Project Number	Topic and rationale	Target completion date
1	Maintenance of existing E-series Recommendations Rationale: It is essential to provide required evolution in existing recommendations.	Ongoing
2	Routing of calls when using international network routing addresses Rationale: This project will continue work on Recommendation E.353, which has been undertaken to identify and recommend guidelines and options for routing calls when using international routing addresses. It addresses issues of both portable and non-portable numbers, as well as services which use E.164 numbering. Implementation of a new international routing addressing plan will be developed in collaboration with SG 11. Leader(s): Tommy Petersen	2000
3	Interworking of routing addresses and IP names/addresses Rationale: When a call is routed via an IP network at the international interface, translation from an international routing address (INRA), as specified in E.353, to IP names/addresses may be necessary. Since the INRA is a non-E.164 number, this approach consequently needs to use "non-number" signalling information to map to IP names/addresses. This work will be done in collaboration with Q.1/2. Leader(s): Tommy Petersen	2001
4	Support for differentiated QoS services for new network applications and technologies Rationale: IP- and ATM-based network technologies are being widely extended beyond data services to include voice, multimedia, and other services integrated on a shared network. Existing methods are not adequate to address all the QoS resource management and performance issues that arise with the extended applications. This project will lead to new recommendations on needed QoS extensions arising from the new applications and technologies. Leader(s): Jerry Ash	2001
5	Routing methods for new network applications and technologies Rationale: L3 routing methods currently standardized for IP- and ATM-based network technologies are not adequate to address all the call and connection routing needs that arise with extended applications, such as voice, multimedia, and other services integrated on a shared network. The implications of inter-domain routing across multiple service providers will be considered. Also, L2 optical transport network (OTN) routing issues arising from wavelength division multiplexing (WDM) technology will be included. This project will lead to new recommendations on needed L2 and L3 routing extensions arising from the new applications and technologies. Leader(s): Jerry Ash	2001
6	Open routing application programming interface Rationale: Application-programming interfaces (APIs) are being developed to allow control of network elements through open interfaces available to individual applications. APIs allow applications to access and control network functions including routing policy, as necessary, according to the specific application functions. The API parameters under application control, such as those specified for example in PARLAY, are independent of the individual protocols supported within the network, and therefore can provide a common language and framework across various network technologies, such as TDM-, ATM-, and IP-based technologies. This recommendation will address the connection management routing parameters as well as the routing policy parameters, which need to be controlled through an applications interface. Leader(s):	2002
7	IN routing methods Rationale: This project will address the need to provide IN-based routing methods across IP- and TDM-based networks. Currently, extension of TDM-based IN capabilities for interworking with IP networks is being addressed by SG 11 (IP-IN project) and by IETF (PINT and SPIRITS working groups). However, access to IN routing capabilities from within an all-IP-technology network, such as with an extension to the SIP protocol, for example, have not been defined. This project will address such needed extensions. Leader(s): Jerry Ash	2001
8	Address translation and routing for mobile and portable terminals Rationale: This Recommendation will consider means to translate between E.164 and IP routing addresses, and the associated routing procedures involved. The scope will include interworking of fixed, wireless, and portable terminals across various technologies, including TDM-, ATM- and IP-based networks. A new recommendation will reflect new technologies, such as IP-based network capabilities, and reflect issues such as tracking the routing address mapping of E.164 numbers and/or names to IP addresses. The intent is to complement existing protocols, including DNS, Recommendation E.174 on UPT, and Recommendations E.212/E.214 on mobile station identity and global title derivation. Leader(s):	2002
9	Routing of calls across TDM-, ATM- and IP-based networks Rationale: This project will continue work on Recommendation E.351, which has been undertaken to identify and recommend information exchange (IE) needs for routing across TDM-, ATM- and IP-based networks. These IE needs include support for INRA and IP-address parameters, route selection parameters, QoS resource management parameters, and routing table management parameters. Implementation of these capabilities will be developed in collaboration with SG 11, IETF, and ATMF. Leader(s): Jerry Ash	2001
10	Other projects Rationale: New and/or modified projects will be introduced as needed, as has always been the experience.	Ongoing