rfc3033.txt

最新的RFC

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

   The Identifier length is 37 octets.

   The Source IPv6 address, Destination IPv6 address, Protocol, Source
   Port, and Destination Port [8, 9, 10] are assigned in that order to
   the Identifier value field.

   Note: This specific session identifier is intended for use only with
   the explicit reservation.  If wild card associations are needed at a
   later date, another identifier type will be used.
















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


4.1.4 MPLS VCID

   If the Identifier related standard/application field in the Generic
   Identifier information element is the MPLS, and the Identifier type
   field in the identifier is the Resource, the identifier is the MPLS
   VCID.  The format of the MPLS VCID is shown in Fig. 4.4.

                                 Bits                         Octet
              8     7     6     5     4     3     2     1     length
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |                Identifier type                |
           |               = Resource (0x02)               |  1
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |               Identifier length               |
           |               = 4 octets (0x04)               |  1
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |                   MPLS VCID                   |  4
           +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. 4.4: MPLS VCID.

   The Identifier type field is the Resource (0x02).

   The Identifier length is 4 octets.

   The MPLS VCID [13] is assigned to the Identifier value field.

4.1.5 Experiment/Organization specific

   If the Identifier related standard/application field in the Generic
   Identifier information element is the IPv4, ST2+, IPv6, or MPLS, and
   the Identifier type field in the identifier is the
   Experiment/Organization specific, the identifier is the
   Experiment/Organization specific.  The format of the
   Experiment/Organization specific is shown in Fig. 4.5.
















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


                              Bits                         Octet
           8     7     6     5     4     3     2     1     length
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |                Identifier type                |
        |   =  Experiment/Organization specific (0xFE)  |  1
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |               Identifier length               |  1
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |    Organizationally unique identifier (OUI)   |  3
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |     Experiment/Organization specific info.    |
        =                                               =
        |                                               |
        +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. 4.5: Experiment/Organization specific.

   The Identifier type field is the Experiment/Organization specific
   (0xFE).

   The first 3 octets in the Identifier value field must contain the
   Organizationally unique identifier (OUI) (as specified in IEEE 802-
   1990; section 5.1).

4.2 Assignment in the User-user Information Element

4.2.1 Use of User-to-user Signaling

   The information field and protocol identifier assignment principle
   for the Internet protocol in the User-user information element is
   shown in Fig. 4.6.




















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


                              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   |  6
        +-----+-----+-----+-----+-----+-----+-----+-----+
        |   Internet protocol/application related info. |  7-
        =                                               =
        |                                               |
        +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. 4.6: Principle of assignment in the User-user information
                element.

   The Protocol discriminator field is the Internet protocol/application
   (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: Reserved for ST2+.

     0x02: RSVP message.

     0x03-0xFD: Reserved for IANA assignment.

     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.




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


   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.  This rule
   enables negotiation; this document does not specify the detailed
   procedure of this negotiation.

4.2.2 RSVP message

   The format of the RSVP message is shown in Fig. 4.7.

                                 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   |
           |              = RSVP message (0x02)            |  6
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |                  RSVP message                 |  7-
           =                                               =
           |                                               |
           +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. 4.7: RSVP message.

   The Internet protocol/application identifier field is the RSVP
   message (0x02).




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


   The RSVP message [12] is assigned to the Internet
   protocol/application related information field.  The SETUP message
   may contain the RSVP Resv message.  The CONNECT message may contain
   the RSVP ResvConf message.  The RELEASE message may contain the RSVP
   ResvErr or ResvTear message.

4.2.3 Experiment/Organization specific

   The format of the Experiment/Organization specific 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 (0x06)    |  5
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |    Internet protocol/application identifier   |
           |  =  Experiment/Organization specific (0xFE)   |  6
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |    Organizationally unique identifier (OUI)   |  7-9
           +-----+-----+-----+-----+-----+-----+-----+-----+
           |     Experiment/Organization specific info.    |  10-
           =                                               =
           |                                               |
           +-----+-----+-----+-----+-----+-----+-----+-----+

      Fig. 4.8: Experiment/Organization specific.

   The Internet protocol/application identifier field is the
   Experiment/Organization specific (0xFE).

   The first 3 octets in the Internet protocol/application related
   information field must contain the Organizationally unique identifier
   (OUI) (as specified in IEEE 802-1990; section 5.1).

5. Open Issues

   The following issues are still remain in this document.




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


   o Generic Identifier support for session aggregation.

      Session aggregation support may be needed in a backbone
      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. IANA Considerations

   When the Identifier related standard/application field in the
   Q.2941.2 Generic Identifier information element is the IPv4, ST2+,
   IPv6, or MPLS, numbers between 0x10-0xFD in the Identifier type field
   are reserved for IANA assignment.  (See section 3.1.)  Following the
   policies outlined in [14], these numbers are allocated through an
   IETF Consensus action.

   When the Protocol discriminator field in the Q.2957 User-user
   information element is the Internet protocol/application, numbers
   between 0x03-0xFD in the Internet protocol/application identifier
   field are reserved for IANA assignment.  (See section 4.2.1.)
   Following the policies outlined in [14], these numbers are allocated
   through an IETF Consensus action.

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