--- 1/draft-ietf-mpls-git-uus-00.txt 2006-02-05 00:39:19.000000000 +0100 +++ 2/draft-ietf-mpls-git-uus-01.txt 2006-02-05 00:39:19.000000000 +0100 @@ -1,95 +1,84 @@ Network Working Group Muneyoshi Suzuki INTERNET DRAFT NTT -Expires December 29, 1998 June 29, 1998 +Expires June 15, 1999 December 15, 1998 The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet Protocol - + Status of this Memo This document is an Internet-Draft. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress". - To view the entire list of current Internet-Drafts, please check - the "1id-abstracts.txt" listing contained in the Internet-Drafts - Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net - (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au - (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu - (US West Coast). + To view the entire list of current Internet-Drafts, please check the + "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow + Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern + Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific + Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast). Abstract The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. The assignment, that is specified in section 4 of this document, is designed for advanced B-ISDN signaling support of the Internet protocol, especially the B-ISDN signaling support for the connection that corresponds to the session in the Internet protocol which is clarified in section 2. This specification provides an indispensable framework for the implementation of long-lived session and QoS- sensitive session transfers over ATM. 0. Background - In the ITU-T SG11 WP1 Kochi meeting held in January 1998, SG11 WP1, - which has responsibility for the B-ISDN signaling protocol - recommendation, decided to discuss B-ISDN signalling support for the - Internet protocol based on draft-suzuki-git-uus-assignment-00.txt. - - In the ITU-T SG11 Geneva meeting held in May 1998, WP1 decided to - enhance the Q.2941 Generic Identifier Transport based on draft- - suzuki-git-uus-assignment-02.txt and developed the Awaiting-review - text (initial draft) [4]. WP1 also decided to continue discussion on - the User-to-user signaling support for the Internet protocol. - Expected standard development process (fastest case) for the - enhancement of the Generic Identifier is: + In the ITU-T SG11 Geneva meeting held in May 1998, SG11 WP1, which + has responsibility for the B-ISDN signaling protocol recommendation, + decided to enhance the Q.2941 Generic Identifier Transport based on + this document and developed the Awaiting-review text. WP1 also + decided to continue discussion on the User-to-user Signaling support + for the Internet protocol. - November 1998: Enhance the Awaiting-review text based on inputs and - develop the Cooling text (Draft Recommendations to be frozen in the + In the ITU-T SG11 WP1 Oostend meeting held in November 1998, WP1 + developed the Cooling text (Draft Recommendations to be frozen in the next meeting, if no significant technical changes are proposed in - that meeting). + that meeting) of Q.2941.2 GIT [4]. WP1 also decided to enhance the + Q.2957 User-to-user Signaling based on this document and developed + the Awaiting-review text [5]. + + Expected standard development process (fastest case) for the + enhancement of the Generic Identifier and User-to-user Signaling is: March 1999: Freeze the Draft Recommendations and letter ballot is requested. February 2000: The Draft Recommendations are decided (final approval). The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet - protocol. To enable this specification, section 6 of this document - clarifies amendments to the current User-to-user Signaling. ITU-T - SG11 will enhance the current User-to-user Signaling based on this - clarification. - - Note that the assignment rule for Generic Identifer described in this - document may be subject to change. - - Note that the assignment rule for the User-to-user Signaling - described in this document may be subject to change, so it should not - be implemented until ITU-T SG11 WP1 decides to enhance the User-to- - user Signaling based on this request. + protocol. Note that the assignment rule for Generic Identifier and + User-to-user Signaling described in this document may be subject to + change. 1. Purpose of Document The purpose of this document is to specify the assignment of the information field and protocol identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol. The assignment, that is specified in section 4 of this document, is designed for advanced B-ISDN signaling support of the Internet @@ -329,39 +318,39 @@ protocol is as follows. A leading 0x means hexadecimal. 0x03: IPv4. 0x04: ST2+. 0x05: IPv6. 0x06: MPLS. - Note: DSM-CC, H.310/H.321, and AAL2 application are also supported. + Note: DSM-CC, H.310/H.321, Trunking, and MPOA are also supported. A transferred identifier is given by the combination of the Identifier type, length and value fields, and a Generic Identifier information element may contain multiple identifiers. Assignment of the Identifier type field for the Intenet protocol is as follows. A leading 0x means hexadecimal. 0x01: Session. 0x02: Resource. 0x03-0xFD: Reserved for IANA assignment. 0xFE: Experiment/Organization specific. The maximum length of the Generic Identifier information element is - 63 octets. (See Draft Q.2941.2.) + 63 octets. See the Q.2941.1 and Draft Q.2941.2 for detailed protocol specifications of the Generic Identifier. 3.2 Overview of the User-to-user Signaling The User-to-user Signaling enables the transfer of information between end-to-end users in the ATM network, and it is defined in Q.2957 and in Q.2971 annex D as an optional information element for the Q.2931 and Q.2971 UNI signaling protocol. The SETUP, ALERTING, @@ -409,25 +398,25 @@ The usage of the first 4 octets of fields is specified in section 4 of the Q.2931. The Protocol discriminator field identifies the upper layer protocol that uses the user-user information. The User information field contains the user-user information to be transferred. - The maximum length of the User-user information element is currently - 133 octets. + The maximum length of the User-user information element is 133 + octets. - See Q.2957 and Q.2971 annex D for detailed protocol specifications of - the User-to-user Signaling. + See Draft Q.2957 and Q.2971 annex D for detailed protocol + specifications of the User-to-user Signaling. 4. Information Field and Protocol Identifier Assignment 4.1 Assignment in the Generic Identifier Information Element 4.1.1 Use of Generic Identifier The information field and protocol identifier assignment principle for the Internet protocol in the Generic Identifier information element is shown in Fig. 4.1. @@ -563,21 +552,21 @@ 4.1.3 ST2+ session identifier If the Identifier related standard/application field in the Generic Identifier information element is the ST2+, and the Identifier type field in the identifier is the Session, the identifier is the ST2+ session identifier. The format of the ST2+ session identifier is shown in Fig. 4.3. Bits Octet - 8 7 6 5 4 3 2 1 Length + 8 7 6 5 4 3 2 1 length +-----+-----+-----+-----+-----+-----+-----+-----+ | Identifier type | | = Session (0x01) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | Identifier length | | = 6 octets (0x06) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | Stream ID (SID) | 6 +-----+-----+-----+-----+-----+-----+-----+-----+ @@ -704,34 +693,34 @@ +-----+-----+-----+-----+-----+-----+-----+-----+ | Information element identifier | | = User-user information element (0x7E) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | 1 | Coding | IE instruction field | | Ext | standard |Flag |Res. | IE action ind. | 2 +-----+-----+-----+-----+-----+-----+-----+-----+ | Length of contents of information element | 3-4 +-----+-----+-----+-----+-----+-----+-----+-----+ | Protocol discriminator | - | = Internet protocol/application (TBD) | 5 + | = Internet protocol/application (0x06) | 5 +-----+-----+-----+-----+-----+-----+-----+-----+ | Internet protocol/application identifier | 6 +-----+-----+-----+-----+-----+-----+-----+-----+ | Internet protocol/application related info. | 7- = = | | +-----+-----+-----+-----+-----+-----+-----+-----+ Fig. 4.7: Principle of assignment in the User-user information element. The Protocol discriminator field is the Internet protocol/application - (TBD). In this case, the first 1 octet in the User information field - is the Internet protocol/application identifier field. + (0x06). In this case, the first 1 octet in the User information + field is the Internet protocol/application identifier field. Assignment of the Internet protocol/application identifier field is as follows. A leading 0x means hexadecimal. 0x00: Reserved. 0x01: ST2+ SCMP. 0x02: RSVP message. @@ -739,37 +728,52 @@ 0xFE: Experiment/Organization specific. 0xFF: Reserved. The field that follows the Internet protocol/application identifier field is assigned to Internet protocol/application related information that is identified by the Internet protocol/application identifier field. + When a B-ISDN signaling message containing a User-user information + element enters an ATM network that does not support the User-to-user + Signaling, the network clears the call, discards the information + element, or discards the signaling message. (See sections 4.5.1 and + 5.6.8.1 of Q.2931, section 1.9 of Q.2957, and Q.2971 annex D for + details.) + + To enable reliable User-user information element transfer, when the + calling party sends a SETUP or ADD PARTY message with a User-user + information element, the CONNECT or ADD PARTY ACK message returned by + the called party must contain a User-user information element. The + called party may not respond with the same user information received + from the calling party. The calling party should confirm that the + response message contains a User-user information element. + 4.2.2 ST2+ SCMP The format of the ST2+ SCMP is shown in Fig. 4.8. Bits 8 7 6 5 4 3 2 1 Octets +-----+-----+-----+-----+-----+-----+-----+-----+ | Information element identifier | | = User-user information element (0x7E) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | 1 | Coding | IE instruction field | | Ext | standard |Flag |Res. | IE action ind. | 2 +-----+-----+-----+-----+-----+-----+-----+-----+ | Length of contents of information element | 3-4 +-----+-----+-----+-----+-----+-----+-----+-----+ | Protocol discriminator | - | = Internet protocol/application (TBD) | 5 + | = Internet protocol/application (0x06) | 5 +-----+-----+-----+-----+-----+-----+-----+-----+ | Internet protocol/application identifier | | = ST2+ SCMP (0x01) | 6 +-----+-----+-----+-----+-----+-----+-----+-----+ | ST2+ SCMP | 7- = = | | +-----+-----+-----+-----+-----+-----+-----+-----+ Fig. 4.8: ST2+ SCMP. @@ -794,21 +798,21 @@ +-----+-----+-----+-----+-----+-----+-----+-----+ | Information element identifier | | = User-user information element (0x7E) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | 1 | Coding | IE instruction field | | Ext | standard |Flag |Res. | IE action ind. | 2 +-----+-----+-----+-----+-----+-----+-----+-----+ | Length of contents of information element | 3-4 +-----+-----+-----+-----+-----+-----+-----+-----+ | Protocol discriminator | - | = Internet protocol/application (TBD) | 5 + | = Internet protocol/application (0x06) | 5 +-----+-----+-----+-----+-----+-----+-----+-----+ | Internet protocol/application identifier | | = RSVP message (0x02) | 6 +-----+-----+-----+-----+-----+-----+-----+-----+ | RSVP message | 7- = = | | +-----+-----+-----+-----+-----+-----+-----+-----+ Fig. 4.9: RSVP message. @@ -832,21 +836,21 @@ +-----+-----+-----+-----+-----+-----+-----+-----+ | Information element identifier | | = User-user information element (0x7E) | 1 +-----+-----+-----+-----+-----+-----+-----+-----+ | 1 | Coding | IE instruction field | | Ext | standard |Flag |Res. | IE action ind. | 2 +-----+-----+-----+-----+-----+-----+-----+-----+ | Length of contents of information element | 3-4 +-----+-----+-----+-----+-----+-----+-----+-----+ | Protocol discriminator | - | = Internet protocol/application (TBD) | 5 + | = Internet protocol/application (0x06) | 5 +-----+-----+-----+-----+-----+-----+-----+-----+ | Internet protocol/application identifier | | = Experiment/Organization specific (0xFE) | 6 +-----+-----+-----+-----+-----+-----+-----+-----+ | Organizationally unique identifier (OUI) | 7-9 +-----+-----+-----+-----+-----+-----+-----+-----+ | Experiment/Organization specific info. | 10- = = | | +-----+-----+-----+-----+-----+-----+-----+-----+ @@ -870,41 +874,21 @@ environment. Wild card style aggregated session identifier may be feasible. However, before specifying Generic Identifier support for it, session aggregation model in ATM VCs should be clarified. o Generic Identifier support for the IPv6 flow label and traffic classes. The IPv6 flow label and traffic classes support may be needed in future. However, currently their semantics are not clear. -6. Required Amendments to the User-to-user Signaling - - The information field and protocol identifier assignment in the - Generic Identifier information element and User-user information - element, which are described in section 4, are required for advanced - B-ISDN signaling support of the Internet protocol. - - To enable advanced B-ISDN signaling support for the Internet - protocol, the following amendments should be applied to the Q.2957 - and Q.2971 annex D User-to-user Signaling. - - o Add the Internet protocol/application to the Protocol - discriminator. - - o Increase the maximum length of the User-user information element to - sufficiently long, e.g. 262 octets, to forward the setup protocol - such as ST2+ and RSVP. This amendment is not applied and remains - 133 octets when the User-user information element interworks with - the N-ISDN user-user information element. - -7. Security Considerations +6. Security Considerations This document specifies the information field and protocol identifier assignment in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet protocol, so these do not weaken the security of the B-ISDN signaling. In a called party of the B-ISDN signaling, if the incoming SETUP message contains the calling party number and if it is verified and passed by the ATM network or it is provided by the network, then it is feasible to use the calling party number for part of the calling @@ -925,49 +909,50 @@ 1995. [3] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) Digital Subscriber Signaling System No. 2 (DSS 2): Generic Identifier Transport," Draft ITU-T New Recommendation Q.2941.1, September 1997. [4] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) Digital Subscriber Signaling System No. 2 (DSS 2): Generic Identifier Transport," Draft ITU-T New Recommendation Q.2941.2, - May 1998. (http://www.nal.ecl.net/SG11WP1/itu-t-sg11-tmp-doc- - td55r2.ps) + November 1998. (http://www.nal.ecl.net/SG11WP1/itu-t-sg11-tmp- + doc-td87r2.ps) [5] ITU-T, "Stage 3 Description for Additional Information Transfer Supplementary Service Using B-ISDN Digital Subscriber Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User - Signalling (UUS)," ITU-T Recommendation Q.2957, February 1995. + Signalling (UUS)," Draft ITU-T New Recommendation Q.2957, November + 1998. (http://www.nal.ecl.net/SG11WP1/itu-t-sg11-tmp-doc- + td103.ps) [6] J. Postel Ed., "Internet Protocol," RFC 791, September 1981. [7] S. Deering and R. Hinden, "Internet Protocol, Version 6 (IPv6) - Specification," Internet Draft, July 1997, . + Specification," RFC 2460, December 1998. [8] J. Postel, "User Datagram Protocol," RFC 768, August 1980. [9] J. Postel Ed., "Transmission Control Protocol," RFC 793, September 1981. [10] L. Delgrossi and L. Berger, Ed., "Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+," RFC 1819, August 1995. [11] R. Braden Ed., "Resource ReSerVation Protocol (RSVP)-Version 1 Functional Specification," RFC 2205, September 1997. - [12] K. Nagami, N. Demizu, H. Esaki, and P. Doolan, "VCID - Notification over ATM link," Internet Draft, March 1998, . + [12] K. Nagami, N. Demizu, H. Esaki, Y. Katsube, and P. Doolan, + "VCID Notification over ATM link," Internet Draft, November 1998, + . [13] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996. [14] S. Damaskos and A. Gavras, "Connection Oriented Protocols over ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, February 1994. [15] ITU-T, "Integrated Services Digital Network (ISDN) Overall Network Aspects and Functions ISDN Protocol Reference Model," @@ -979,32 +964,32 @@ ISDN Environment," ITU-T Recommendation Q.923, February 1995. [17] K. Kitami, "Proposed Direction for B-ISDN & Multimedia Signaling," ITU-T SG11 Delayed Contribution D.647, January 1998, (http://www.nal.ecl.net/SG11WP1/itu-t-sg11-del-contrib-d647.ps). Acknowledgments I would like to thank Kenichi Kitami of the NTT Network Innovation Planning and Promotion Dept., who is also the chair of ITU-T SG11 - WP1, Shinichi Kuribayashi of the NTT Business Communications Hqs., - Hiroshi Yao and Takumi Ohba of the NTT Network Service Systems - Labs., and Noriyuki Takahashi of the NTT Multimedia Networks Labs. - for their valuable comments and discussions. + WP1, Shinichi Kuribayashi, Hiroshi Yao, and Takumi Ohba of the NTT + Network Service Systems Labs., and Noriyuki Takahashi of the NTT + Multimedia Networks Labs. for their valuable comments and + discussions. And I would also like to thank the active members of IETF, ITU-T, and ATM Forum, especially Joel Halpern of Newbridge Networks, Andrew Malis of Ascend Communications, George Swallow and Bruce Davie of Cisco Systems, Rao Cherukuri of IBM, Rajiv Kapoor of - AT&T, Greg Ratta of Lucent, Hiroshi Esaki and Kenichi Nagami of - Toshiba, and Noritoshi Demizu of NAIST for their valuable comments - and suggestions. + AT&T, Greg Ratta of Lucent, Kaoru Kenyoshi of NEC, Hiroshi Esaki + and Kenichi Nagami of Toshiba, and Noritoshi Demizu of NAIST for + their valuable comments and suggestions. Also this specification is based on various discussions during the ST2+ over ATM project at the NTT Multimedia Joint Project with NACSIS. I would like to thank Professor Shoichiro Asano of the National Center for Science Information Systems for his invaluable advice in this area. Author's Address Muneyoshi Suzuki