rfc3033.txt

RFC 的详细文档！

   is feasible to use the calling party number for part of the calling
   party authentication to strengthen security.










Suzuki                      Standards Track                    [Page 19]

RFC 3033             GIT and UUS Assignment for IP          January 2001


Appendix. Information Field and Protocol Identifier Assignment for ST2+

   This appendix specifies information field and protocol identifier
   assignment in the Generic Identifier and User-to-user Signaling for
   ST2+.  Note that this appendix is NOT part of the standard.

A.1 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. A.1.

                              Bits                         Octet
           8     7     6     5     4     3     2     1     length
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |                Identifier type                |
        |                = Session (0x01)               |  1
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |               Identifier length               |
        |               = 6 octets (0x06)               |  1
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |                Stream ID (SID)                |  6
        +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. A.1: ST2+ session identifier.

   The Identifier type field is the Session (0x01).

   The Identifier length is 6 octets.

   The Stream ID (SID) [11] is assigned to the Identifier value field.


















Suzuki                      Standards Track                    [Page 20]

RFC 3033             GIT and UUS Assignment for IP          January 2001


A.2 ST2+ SCMP

   The format of the User-user information element for the ST2+ SCMP is
   shown in Fig. A.2.

                                 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 (0x06)    |  5
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |    Internet protocol/application identifier   |
           |               = ST2+ SCMP (0x01)              |  6
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |                   ST2+ SCMP                   |  7-
           =                                               =
           |                                               |
           +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. A.2: ST2+ SCMP.

   The Internet protocol/application identifier field is the ST2+ SCMP
   (0x01).

   The ST2+ SCMP [11] is assigned to the Internet protocol/application
   related information field.  The SETUP and ADD PARTY messages may
   contain the ST2+ SCMP CONNECT message.  The CONNECT and ADD PARTY ACK
   messages may contain the ST2+ SCMP ACCEPT message.  The RELEASE and
   DROP PARTY messages may contain the ST2+ SCMP DISCONNECT message.
   The RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and DROP PARTY
   messages may contain the ST2+ SCMP REFUSE message.












Suzuki                      Standards Track                    [Page 21]

RFC 3033             GIT and UUS Assignment for IP          January 2001


References

   [1]  ITU-T, "Broadband Integrated Services Digital Network (B-
        ISDN)-Digital Subscriber Signaling System No. 2 (DSS 2)-User-
        Network Interface (UNI) Layer 3 Specification for Basic
        Call/Connection Control," ITU-T Recommendation Q.2931, September
        1995.

   [2]  ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)-
        Digital Subscriber Signaling System No. 2 (DSS 2)-User-Network
        Interface Layer 3 Specification for Point-to-Multipoint
        Call/Connection Control," ITU-T Recommendation Q.2971, October
        1995.

   [3]  ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)
        Digital Subscriber Signaling System No. 2 (DSS 2): Generic
        Identifier Transport," 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 Extensions," ITU-T New Recommendation
        Q.2941.2, December 1999.

   [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.

   [6]  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 Amendment 1, December 1999.

   [7]  Postel, J., Ed., "Internet Protocol", STD 5, RFC 791, September
        1981.

   [8]  Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
        Specification", RFC 2460, December 1998.

   [9]  Postel, J., "User Datagram Protocol", STD 6, RFC 768, August
        1980.

   [10] Postel, J., Ed., "Transmission Control Protocol", STD 7, RFC
        793, September 1981.






Suzuki                      Standards Track                    [Page 22]

RFC 3033             GIT and UUS Assignment for IP          January 2001


   [11] Delgrossi, L. and L. Berger, Ed., "Internet Stream Protocol
        Version 2 (ST2) Protocol Specification - Version ST2+", RFC
        1819, August 1995.

   [12] Braden, R., Ed., "Resource ReSerVation Protocol (RSVP) - Version
        1 Functional Specification", RFC 2205, September 1997.

   [13] Nagami, K., Demizu, N., Esaki, H., Katsube, Y. and P. Doolan,
        "VCID Notification over ATM link for LDP", RFC 3038, January
        2001.

   [14] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA
        Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.

   [15] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A
        Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996.

   [16] S. Damaskos and A. Gavras, "Connection Oriented Protocols over
        ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, February
        1994.

   [17] ITU-T, "Integrated Services Digital Network (ISDN) Overall
        Network Aspects and Functions ISDN Protocol Reference Model,"
        ITU-T Recommendation I.320, November 1993.

   [18] ITU-T, "Digital Subscriber Signaling System No. 1 (DSS 1)
        Specification of a Synchronization and Coordination Function for
        the Provision of the OSI Connection-mode Network Service in an
        ISDN Environment," ITU-T Recommendation Q.923, February 1995.






















Suzuki                      Standards Track                    [Page 23]

RFC 3033             GIT and UUS Assignment for IP          January 2001


Acknowledgments

   I would like to thank Kenichi Kitami of the NTT Information Sharing
   Lab. Group, who is also the chair of ITU-T SG11 WP1, Shinichi
   Kuribayashi of the NTT Information Sharing Platform Labs., Hiroshi
   Yao and Takumi Ohba of the NTT Network Service Systems Labs., and
   Noriyuki Takahashi of the NTT Information Sharing Platform 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, Kaoru Kenyoshi of NEC, Hiroto Uno of Hitachi, 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
   NTT Information Sharing Platform Laboratories
   3-9-11, Midori-cho
   Musashino-shi, Tokyo 180-8585, Japan

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


















Suzuki                      Standards Track                    [Page 24]

RFC 3033             GIT and UUS Assignment for IP          January 2001


Full Copyright Statement

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Suzuki                      Standards Track                    [Page 25]