draft-ietf-mpls-git-uus-04.txt   rfc3033.txt 
Network Working Group Muneyoshi Suzuki
INTERNET DRAFT NTT Network Working Group M. Suzuki
Expires July 11, 2000 January 11, 2000 Request for Comments: 3033 NTT
Category: Standards Track January 2001
The Assignment of the Information Field and Protocol Identifier The Assignment of the Information Field and Protocol Identifier
in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling
for the Internet Protocol for the Internet Protocol
<draft-ietf-mpls-git-uus-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document specifies an Internet standards track protocol for the
all provisions of Section 10 of RFC2026. Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Internet-Drafts are working documents of the Internet Engineering Official Protocol Standards" (STD 1) for the standardization state
Task Force (IETF), its areas, and its working groups. Note that and status of this protocol. Distribution of this memo is unlimited.
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."
The list of current Internet-Drafts can be accessed at Copyright Notice
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at Copyright (C) The Internet Society (2001). All Rights Reserved.
http://www.ietf.org/shadow.html.
Abstract Abstract
The purpose of this document is to specify the assignment of the The purpose of this document is to specify the assignment of the
information field and protocol identifier in the Q.2941 Generic information field and protocol identifier in the Q.2941 Generic
Identifier and Q.2957 User-to-user Signaling for the Internet Identifier and Q.2957 User-to-user Signaling for the Internet
protocol. protocol.
The assignment, that is specified in section 4 of this document, is The assignment, that is specified in section 4 of this document, is
designed for advanced B-ISDN signaling support of the Internet designed for advanced B-ISDN signaling support of the Internet
skipping to change at page 3, line 14 skipping to change at page 3, line 10
This section clarifies B-ISDN signaling functions that are required This section clarifies B-ISDN signaling functions that are required
when the session is supported by the VC, for advanced B-ISDN when the session is supported by the VC, for advanced B-ISDN
signaling support of the Internet protocol. signaling support of the Internet protocol.
2.1 Long-lived Session Signaling 2.1 Long-lived Session Signaling
An example scenario for establishing a VC for a long-lived session is An example scenario for establishing a VC for a long-lived session is
shown in Fig. 2.1. shown in Fig. 2.1.
IP Router ATM SW ATM SW IP Router IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+ +----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS | | WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+ +--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....| |.....|__/ |===||==| X |========| X |==||===| \__|.....|
| | | / \ | | / \ | | | | | | / \ | | / \ | | |
+------+ +-----+ +-----+ +------+ +------+ +-----+ +-----+ +------+
A. New session initially forwarded over a default VC. A. New session initially forwarded over a default VC.
IP Router ATM SW ATM SW IP Router IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+ +----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS | | WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+ +--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....| |.....|__/ |===||==| X |========| X |==||===| \__|.....|
| |<------+-/-\-+--------+-/-\-+------>| | | |<------+-/-\-+--------+-/-\-+------>| |
+------+ +-----+ +-----+ +------+ +------+ +-----+ +-----+ +------+
New VC is set up New VC is set up
B. New VC is set up for the long-lived session. B. New VC is set up for the long-lived session.
IP Router ATM SW ATM SW IP Router IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+ +----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS | | WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | |<------+-\-/-+--------+-\-/-+------>| | +-+--+ +--+-+ | |<------+-\-/-+--------+-\-/-+------>| | +-+--+
|.....|__ |===||==| X |========| X |==||===| __|.....| |.....|__ |===||==| X |========| X |==||===| __|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ | | \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ +-----+ +------+ +------+ +-----+ +-----+ +------+
New VC New VC
C. Transfer of the long-lived session to a new VC. C. Transfer of the long-lived session to a new VC.
Fig. 2.1: Example scenario for establishing a VC for a long-lived session. Fig. 2.1: Example scenario for establishing a VC for a long-lived
session.
First, a session is multiplexed into the default VC connecting the First, a session is multiplexed into the default VC connecting the
routers. Then, if a router detects that it is a long-lived session, routers. Then, if a router detects that it is a long-lived session,
it sets up a new VC for the session. If the new VC is established it sets up a new VC for the session. If the new VC is established
successfully, the long-lived session is moved to the new VC. successfully, the long-lived session is moved to the new VC.
In this procedure involving an ATM VC setup, the B-ISDN signaling In this procedure involving an ATM VC setup, the B-ISDN signaling
entity in the called side router must detect that the incoming call entity in the called side router must detect that the incoming call
corresponds to a session of the Internet protocol and notify that corresponds to a session of the Internet protocol and notify that
fact to the IP layer entity. Based on this information, the IP layer fact to the IP layer entity. Based on this information, the IP layer
skipping to change at page 5, line 15 skipping to change at page 5, line 8
o If the setup protocol supports negotiation, then an ATM VC whose o If the setup protocol supports negotiation, then an ATM VC whose
QoS is based on the result of negotiation can be established. QoS is based on the result of negotiation can be established.
However, the latter scheme, at least, cannot support a case where a However, the latter scheme, at least, cannot support a case where a
PVC is used to support a QoS-sensitive session. Therefore, both PVC is used to support a QoS-sensitive session. Therefore, both
procedures should be taken into account. procedures should be taken into account.
An example of a message sequence that simultaneously establishes a An example of a message sequence that simultaneously establishes a
QoS-sensitive session and an ATM VC is shown in Fig. 2.2. QoS-sensitive session and an ATM VC is shown in Fig. 2.2.
IP Router ATM SW ATM SW IP Router IP Router ATM SW ATM SW IP Router
+----+ B-ISDN Signaling +----+ +----+ B-ISDN Signaling +----+
| WS | +------+ UNI +-----+ Setup +-----+ UNI +------+ | WS | | WS | +------+ UNI +-----+ Setup +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/--Protocol--\-/-+------>|<-\ | +-+--+ +--+-+ | /->|<------+-\-/--Protocol--\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....| |.....|__/ |===||==| X |========| X |==||===| \__|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ | | \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ Data +-----+ +------+ +------+ +-----+ Data +-----+ +------+
QoS VC QoS VC
N-CONNECT | | N-CONNECT | |
---------->| | | | | | ---------->| | | | | |
|->| SETUP | | | | |->| SETUP | | | |
| |------------>| | | | | |------------>| | | |
| |<------------| | | | | |<------------| | | |
| | CALL PROC |----------->| SETUP | | | | CALL PROC |----------->| SETUP | |
| | | |------------>| | | | | |------------>| |
| | | | |->| N-CONNECT | | | | |->| N-CONNECT
| | | | | |----------> | | | | | |---------->
| | | | | |<---------- | | | | | |<----------
| | | | CONN |<-| N-CONNECT-ACK | | | | CONN |<-| N-CONNECT-ACK
| | | |<------------| | | | | |<------------| |
| | | |------------>| | | | | |------------>| |
| | CONN |<-----------| CONN ACK |->| | | CONN |<-----------| CONN ACK |->|
| |<------------| | | | | |<------------| | | |
| |------------>| | | | | |------------>| | | |
|<-| CONN ACK | | | | |<-| CONN ACK | | | |
<----------| | | | | | <----------| | | | | |
N-CONNECT | | N-CONNECT | |
-ACK -ACK
Fig. 2.2: Example procedure for simultaneous QoS-sensitive session and Fig. 2.2: Example procedure for simultaneous QoS-sensitive session
ATM VC establishment. and ATM VC establishment.
RSVP is currently proposed for the setup protocol and new setup RSVP is currently proposed for the setup protocol and new setup
protocols are likely to be developed in the future. Therefore, to protocols are likely to be developed in the future. Therefore, to
generalize the discussion, the procedure for the setup protocol in generalize the discussion, the procedure for the setup protocol in
this example is the general connection setup procedure using this example is the general connection setup procedure using
confirmed service. confirmed service.
To implement this signaling procedure, the B-ISDN signaling must To implement this signaling procedure, the B-ISDN signaling must
include the User-user information element that the capacity is include the User-user information element that the capacity is
sufficient to forward the setup protocol. sufficient to forward the setup protocol.
skipping to change at page 7, line 45 skipping to change at page 7, line 42
= = = =
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 3.1: Format of the Generic Identifier information element. Fig. 3.1: Format of the Generic Identifier information element.
The usage of the first 4 octets of fields is specified in section 4 The usage of the first 4 octets of fields is specified in section 4
of the Q.2931. of the Q.2931.
The Identifier related standard/application field identifies the The Identifier related standard/application field identifies the
standard or application that uses the identifier. Assignment of the standard or application that uses the identifier. Assignment of the
Identifier related standard/application field for the Intenet Identifier related standard/application field for the Internet
protocol is as follows. A leading 0x means hexadecimal. protocol is as follows. A leading 0x means hexadecimal.
0x03: IPv4. 0x03: IPv4.
0x04: ST2+. 0x04: ST2+.
0x05: IPv6. 0x05: IPv6.
0x06: MPLS. 0x06: MPLS.
Note: DSM-CC, H.310/H.321, MPOA, ATM VCC Trunking, AAL2, and Note: DSM-CC, H.310/H.321, MPOA, ATM VCC Trunking, AAL2, and
H.323/H.245 are also supported. H.323/H.245 are also supported.
A transferred identifier is given by the combination of the A transferred identifier is given by the combination of the
Identifier type, length and value fields, and a Generic Identifier Identifier type, length and value fields, and a Generic Identifier
information element may contain multiple identifiers. information element may contain multiple identifiers.
Assignment of the Identifier type field for the Intenet protocol is Assignment of the Identifier type field for the Internet protocol is
as follows. A leading 0x means hexadecimal. as follows. A leading 0x means hexadecimal.
0x01: Session. 0x01: Session.
0x02: Resource. 0x02: Resource.
0x10-0xFD: Reserved for IANA assignment. 0x10-0xFD: Reserved for IANA assignment.
0xFE: Experiment/Organization specific. 0xFE: Experiment/Organization specific.
skipping to change at page 9, line 29 skipping to change at page 9, line 29
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Length of contents of information element | 3-4 | Length of contents of information element | 3-4
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol discriminator | 5 | Protocol discriminator | 5
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| User information | 6- | User information | 6-
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 3.2: Format of the User-user information element. Fig. 3.2: Format of the User-user information element.
The usage of the first 4 octets of fields is specified in section 4 The usage of the first 4 octets of fields is specified in section 4
of the Q.2931. of the Q.2931.
The Protocol discriminator field identifies the upper layer protocol The Protocol discriminator field identifies the upper layer protocol
that uses the user-user information. that uses the user-user information.
The User information field contains the user-user information to be The User information field contains the user-user information to be
transferred. transferred.
skipping to change at page 10, line 48 skipping to change at page 10, line 48
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type | | Identifier type |
| = Session, Resource, or Experiment | | = Session, Resource, or Experiment |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | | Identifier length |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value | | Identifier value |
= = = =
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.1: Principle of assignment in the Generic Identifier Fig. 4.1: Principle of assignment in the Generic Identifier
information element. information element.
The Identifier related standard/application field is the IPv4, ST2+, The Identifier related standard/application field is the IPv4, ST2+,
IPv6, or MPLS. IPv6, or MPLS.
The Identifier type field is the Session, Resource, or The Identifier type field is the Session, Resource, or
Experiment/Organization specific. Experiment/Organization specific.
The Identifier value field is assigned to Internet protocol related The Identifier value field is assigned to Internet protocol related
information which is identified by the Identifier related information which is identified by the Identifier related
standard/application field and Identifier type field. The following standard/application field and Identifier type field. The following
skipping to change at page 12, line 35 skipping to change at page 12, line 33
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv4 address | 4 | Destination IPv4 address | 4
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1 | Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2 | Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2 | Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.2: IPv4 session identifier. Fig. 4.2: IPv4 session identifier.
The Identifier type field is the Session (0x01). The Identifier type field is the Session (0x01).
The Identifier length is 13 octets. The Identifier length is 13 octets.
The Source IPv4 address, Destination IPv4 address, Protocol, Source The Source IPv4 address, Destination IPv4 address, Protocol, Source
Port, and Destination Port [7, 9, 10] are assigned in that order to Port, and Destination Port [7, 9, 10] are assigned in that order to
the Identifier value field. the Identifier value field.
Note: This specific session identifier is intended for use only with Note: This specific session identifier is intended for use only with
the explicit reservation. If wild card associations are needed at a the explicit reservation. If wild card associations are needed at a
later date, another identifier type will be used. later date, another identifier type will be used.
4.1.3 IPv6 session identifier 4.1.3 IPv6 session identifier
If the Identifier related standard/application field in the Generic If the Identifier related standard/application field in the Generic
Identifier information element is the IPv6, and the Identifier type Identifier information element is the IPv6, and the Identifier type
field in the identifier is the Session, the identifier is the IPv6 field in the identifier is the Session, the identifier is the IPv6
session identifier. The format of the IPv6 session identifier is session identifier. The format of the IPv6 session identifier is
shown in Fig. 4.3. shown in Fig. 4.3.
skipping to change at page 13, line 33 skipping to change at page 13, line 26
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv6 address | 16 | Destination IPv6 address | 16
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1 | Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2 | Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2 | Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.3: IPv6 session identifier. Fig. 4.3: IPv6 session identifier.
The Identifier type field is the Session (0x01). The Identifier type field is the Session (0x01).
The Identifier length is 37 octets. The Identifier length is 37 octets.
The Source IPv6 address, Destination IPv6 address, Protocol, Source The Source IPv6 address, Destination IPv6 address, Protocol, Source
Port, and Destination Port [8, 9, 10] are assigned in that order to Port, and Destination Port [8, 9, 10] are assigned in that order to
the Identifier value field. the Identifier value field.
Note: This specific session identifier is intended for use only with Note: This specific session identifier is intended for use only with
the explicit reservation. If wild card associations are needed at a the explicit reservation. If wild card associations are needed at a
later date, another identifier type will be used. later date, another identifier type will be used.
4.1.4 MPLS VCID 4.1.4 MPLS VCID
If the Identifier related standard/application field in the Generic If the Identifier related standard/application field in the Generic
Identifier information element is the MPLS, and the Identifier type Identifier information element is the MPLS, and the Identifier type
field in the identifier is the Resource, the identifier is the MPLS 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. VCID. The format of the MPLS VCID is shown in Fig. 4.4.
Bits Octet Bits Octet
skipping to change at page 14, line 24 skipping to change at page 14, line 24
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type | | Identifier type |
| = Resource (0x02) | 1 | = Resource (0x02) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | | Identifier length |
| = 4 octets (0x04) | 1 | = 4 octets (0x04) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| MPLS VCID | 4 | MPLS VCID | 4
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.4: MPLS VCID. Fig. 4.4: MPLS VCID.
The Identifier type field is the Resource (0x02). The Identifier type field is the Resource (0x02).
The Identifier length is 4 octets. The Identifier length is 4 octets.
The MPLS VCID [13] is assigned to the Identifier value field. The MPLS VCID [13] is assigned to the Identifier value field.
4.1.5 Experiment/Organization specific 4.1.5 Experiment/Organization specific
If the Identifier related standard/application field in the Generic If the Identifier related standard/application field in the Generic
skipping to change at page 15, line 29 skipping to change at page 15, line 20
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | 1 | Identifier length | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Organizationally unique identifier (OUI) | 3 | Organizationally unique identifier (OUI) | 3
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Experiment/Organization specific info. | | Experiment/Organization specific info. |
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.5: Experiment/Organization specific. Fig. 4.5: Experiment/Organization specific.
The Identifier type field is the Experiment/Organization specific The Identifier type field is the Experiment/Organization specific
(0xFE). (0xFE).
The first 3 octets in the Identifier value field must contain the The first 3 octets in the Identifier value field must contain the
Organizationally unique identifier (OUI) (as specified in IEEE Organizationally unique identifier (OUI) (as specified in IEEE 802-
802-1990; section 5.1). 1990; section 5.1).
4.2 Assignment in the User-user Information Element 4.2 Assignment in the User-user Information Element
4.2.1 Use of User-to-user Signaling 4.2.1 Use of User-to-user Signaling
The information field and protocol identifier assignment principle The information field and protocol identifier assignment principle
for the Internet protocol in the User-user information element is for the Internet protocol in the User-user information element is
shown in Fig. 4.6. shown in Fig. 4.6.
Bits Bits
skipping to change at page 16, line 34 skipping to change at page 16, line 26
| Protocol discriminator | | Protocol discriminator |
| = Internet protocol/application (0x06) | 5 | = Internet protocol/application (0x06) | 5
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Internet protocol/application identifier | 6 | Internet protocol/application identifier | 6
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Internet protocol/application related info. | 7- | Internet protocol/application related info. | 7-
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.6: Principle of assignment in the User-user information element. Fig. 4.6: Principle of assignment in the User-user information
element.
The Protocol discriminator field is the Internet protocol/application The Protocol discriminator field is the Internet protocol/application
(0x06). In this case, the first 1 octet in the User information (0x06). In this case, the first 1 octet in the User information
field is the Internet protocol/application identifier field. field is the Internet protocol/application identifier field.
Assignment of the Internet protocol/application identifier field is Assignment of the Internet protocol/application identifier field is
as follows. A leading 0x means hexadecimal. as follows. A leading 0x means hexadecimal.
0x00: Reserved. 0x00: Reserved.
skipping to change at page 18, line 31 skipping to change at page 17, line 48
| = Internet protocol/application (0x06) | 5 | = Internet protocol/application (0x06) | 5
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Internet protocol/application identifier | | Internet protocol/application identifier |
| = RSVP message (0x02) | 6 | = RSVP message (0x02) | 6
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| RSVP message | 7- | RSVP message | 7-
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.7: RSVP message. Fig. 4.7: RSVP message.
The Internet protocol/application identifier field is the RSVP The Internet protocol/application identifier field is the RSVP
message (0x02). message (0x02).
The RSVP message [12] is assigned to the Internet The RSVP message [12] is assigned to the Internet
protocol/application related information field. The SETUP message protocol/application related information field. The SETUP message
may contain the RSVP Resv message. The CONNECT message may contain may contain the RSVP Resv message. The CONNECT message may contain
the RSVP ResvConf message. The RELEASE message may contain the RSVP the RSVP ResvConf message. The RELEASE message may contain the RSVP
ResvErr or ResvTear message. ResvErr or ResvTear message.
skipping to change at page 19, line 34 skipping to change at page 18, line 40
| Internet protocol/application identifier | | Internet protocol/application identifier |
| = Experiment/Organization specific (0xFE) | 6 | = Experiment/Organization specific (0xFE) | 6
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Organizationally unique identifier (OUI) | 7-9 | Organizationally unique identifier (OUI) | 7-9
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Experiment/Organization specific info. | 10- | Experiment/Organization specific info. | 10-
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.8: Experiment/Organization specific. Fig. 4.8: Experiment/Organization specific.
The Internet protocol/application identifier field is the The Internet protocol/application identifier field is the
Experiment/Organization specific (0xFE). Experiment/Organization specific (0xFE).
The first 3 octets in the Internet protocol/application related The first 3 octets in the Internet protocol/application related
information field must contain the Organizationally unique identifier information field must contain the Organizationally unique identifier
(OUI) (as specified in IEEE 802-1990; section 5.1). (OUI) (as specified in IEEE 802-1990; section 5.1).
5. Open Issues 5. Open Issues
The following issues are still remain in this document. The following issues are still remain in this document.
o Generic Identifier support for session aggregation. o Generic Identifier support for session aggregation.
Session aggregation support may be needed in a backbone Session aggregation support may be needed in a backbone
environment. Wild card style aggregated session identifier may be environment. Wild card style aggregated session identifier may be
feasible. However, before specifying Generic Identifier support feasible. However, before specifying Generic Identifier support
for it, session aggregation model in ATM VCs should be clarified. for it, session aggregation model in ATM VCs should be clarified.
o Generic Identifier support for the IPv6 flow label and traffic o Generic Identifier support for the IPv6 flow label and traffic
classes. classes.
The IPv6 flow label and traffic classes support may be needed in The IPv6 flow label and traffic classes support may be needed in
future. However, currently their semantics are not clear. future. However, currently their semantics are not clear.
6. IANA Considerations 6. IANA Considerations
When the Identifier related standard/application field in the When the Identifier related standard/application field in the
Q.2941.2 Generic Identifier information element is the IPv4, ST2+, Q.2941.2 Generic Identifier information element is the IPv4, ST2+,
IPv6, or MPLS, numbers between 0x10-0xFD in the Identifier type field IPv6, or MPLS, numbers between 0x10-0xFD in the Identifier type field
are reserved for IANA assignment. (See section 3.1). Following the are reserved for IANA assignment. (See section 3.1.) Following the
policies outlined in [14], these numbers are allocated through an policies outlined in [14], these numbers are allocated through an
IETF Consensus action. IETF Consensus action.
When the Protocol discriminator field in the Q.2957 User-user When the Protocol discriminator field in the Q.2957 User-user
information element is the Internet protocol/application, numbers information element is the Internet protocol/application, numbers
between 0x03-0xFD in the Internet protocol/application identifier between 0x03-0xFD in the Internet protocol/application identifier
field are reserved for IANA assignment. (See section 4.2.1). field are reserved for IANA assignment. (See section 4.2.1.)
Following the policies outlined in [14], these numbers are allocated Following the policies outlined in [14], these numbers are allocated
through an IETF Consensus action. through an IETF Consensus action.
7. Security Considerations 7. Security Considerations
This document specifies the information field and protocol identifier This document specifies the information field and protocol identifier
assignment in the Q.2941 Generic Identifier and Q.2957 User-to-user assignment in the Q.2941 Generic Identifier and Q.2957 User-to-user
Signaling for the Internet protocol, so these do not weaken the Signaling for the Internet protocol, so these do not weaken the
security of the B-ISDN signaling. security of the B-ISDN signaling.
skipping to change at page 21, line 31 skipping to change at page 20, line 31
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type | | Identifier type |
| = Session (0x01) | 1 | = Session (0x01) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | | Identifier length |
| = 6 octets (0x06) | 1 | = 6 octets (0x06) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Stream ID (SID) | 6 | Stream ID (SID) | 6
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. A.1: ST2+ session identifier. Fig. A.1: ST2+ session identifier.
The Identifier type field is the Session (0x01). The Identifier type field is the Session (0x01).
The Identifier length is 6 octets. The Identifier length is 6 octets.
The Stream ID (SID) [11] is assigned to the Identifier value field. The Stream ID (SID) [11] is assigned to the Identifier value field.
A.2 ST2+ SCMP A.2 ST2+ SCMP
The format of the User-user information element for the ST2+ SCMP is The format of the User-user information element for the ST2+ SCMP is
skipping to change at page 22, line 32 skipping to change at page 21, line 32
| = Internet protocol/application (0x06) | 5 | = Internet protocol/application (0x06) | 5
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| Internet protocol/application identifier | | Internet protocol/application identifier |
| = ST2+ SCMP (0x01) | 6 | = ST2+ SCMP (0x01) | 6
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
| ST2+ SCMP | 7- | ST2+ SCMP | 7-
= = = =
| | | |
+-----+-----+-----+-----+-----+-----+-----+-----+ +-----+-----+-----+-----+-----+-----+-----+-----+
Fig. A.2: ST2+ SCMP. Fig. A.2: ST2+ SCMP.
The Internet protocol/application identifier field is the ST2+ SCMP The Internet protocol/application identifier field is the ST2+ SCMP
(0x01). (0x01).
The ST2+ SCMP [11] is assigned to the Internet protocol/application The ST2+ SCMP [11] is assigned to the Internet protocol/application
related information field. The SETUP and ADD PARTY messages may related information field. The SETUP and ADD PARTY messages may
contain the ST2+ SCMP CONNECT message. The CONNECT and ADD PARTY ACK contain the ST2+ SCMP CONNECT message. The CONNECT and ADD PARTY ACK
messages may contain the ST2+ SCMP ACCEPT message. The RELEASE and messages may contain the ST2+ SCMP ACCEPT message. The RELEASE and
DROP PARTY messages may contain the ST2+ SCMP DISCONNECT message. DROP PARTY messages may contain the ST2+ SCMP DISCONNECT message.
The RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and DROP PARTY The RELEASE, RELEASE COMPLETE, ADD PARTY REJECT, and DROP PARTY
messages may contain the ST2+ SCMP REFUSE message. messages may contain the ST2+ SCMP REFUSE message.
References References
[1] ITU-T, "Broadband Integrated Services Digital Network (B- [1] ITU-T, "Broadband Integrated Services Digital Network (B-
ISDN)-Digital Subscriber Signaling System No. 2 (DSS 2)-User- ISDN)-Digital Subscriber Signaling System No. 2 (DSS 2)-User-
Network Interface (UNI) Layer 3 Specification for Basic Network Interface (UNI) Layer 3 Specification for Basic
Call/Connection Control," ITU-T Recommendation Q.2931, September Call/Connection Control," ITU-T Recommendation Q.2931, September
1995. 1995.
[2] ITU-T, "Broadband Integrated Services Digital Network (B- [2] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)-
ISDN)-Digital Subscriber Signaling System No. 2 (DSS 2)-User- Digital Subscriber Signaling System No. 2 (DSS 2)-User-Network
Network Interface Layer 3 Specification for Point-to-Multipoint Interface Layer 3 Specification for Point-to-Multipoint
Call/Connection Control," ITU-T Recommendation Q.2971, October Call/Connection Control," ITU-T Recommendation Q.2971, October
1995. 1995.
[3] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) [3] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)
Digital Subscriber Signaling System No. 2 (DSS 2): Generic Digital Subscriber Signaling System No. 2 (DSS 2): Generic
Identifier Transport," Draft ITU-T New Recommendation Q.2941.1, Identifier Transport," ITU-T New Recommendation Q.2941.1,
September 1997. September 1997.
[4] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN) [4] ITU-T, "Broadband Integrated Services Digital Network (B-ISDN)
Digital Subscriber Signaling System No. 2 (DSS 2): Generic Digital Subscriber Signaling System No. 2 (DSS 2): Generic
Identifier Transport Extensions," Draft ITU-T New Recommendation Identifier Transport Extensions," ITU-T New Recommendation
Q.2941.2, July 1999. Q.2941.2, December 1999.
[5] ITU-T, "Stage 3 Description for Additional Information [5] ITU-T, "Stage 3 Description for Additional Information Transfer
Transfer Supplementary Service Using B-ISDN Digital Subscriber Supplementary Service Using B-ISDN Digital Subscriber Signaling
Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User Signalling
Signalling (UUS)," ITU-T Recommendation Q.2957, February 1995. (UUS)," ITU-T Recommendation Q.2957, February 1995.
[6] ITU-T, "Stage 3 Description for Additional Information [6] ITU-T, "Stage 3 Description for Additional Information Transfer
Transfer Supplementary Service Using B-ISDN Digital Subscriber Supplementary Service Using B-ISDN Digital Subscriber Signaling
Signaling System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User System No. 2 (DSS 2)-Basic Call Clause 1-User-to-User Signalling
Signalling (UUS)," Draft ITU-T Recommendation Q.2957 Amendment 1, (UUS)," ITU-T Recommendation Q.2957 Amendment 1, December 1999.
July 1999.
[7] J. Postel Ed., "Internet Protocol," RFC 791, September 1981. [7] Postel, J., Ed., "Internet Protocol", STD 5, RFC 791, September
1981.
[8] S. Deering and R. Hinden, "Internet Protocol, Version 6 (IPv6) [8] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)
Specification," RFC 2460, December 1998. Specification", RFC 2460, December 1998.
[9] J. Postel, "User Datagram Protocol," RFC 768, August 1980. [9] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August
1980.
[10] J. Postel Ed., "Transmission Control Protocol," RFC 793, [10] Postel, J., Ed., "Transmission Control Protocol", STD 7, RFC
September 1981. 793, September 1981.
[11] L. Delgrossi and L. Berger, Ed., "Internet Stream Protocol [11] Delgrossi, L. and L. Berger, Ed., "Internet Stream Protocol
Version 2 (ST2) Protocol Specification - Version ST2+," RFC 1819, Version 2 (ST2) Protocol Specification - Version ST2+", RFC
August 1995. 1819, August 1995.
[12] R. Braden Ed., "Resource ReSerVation Protocol (RSVP)-Version [12] Braden, R., Ed., "Resource ReSerVation Protocol (RSVP) - Version
1 Functional Specification," RFC 2205, September 1997. 1 Functional Specification", RFC 2205, September 1997.
[13] K. Nagami, N. Demizu, H. Esaki, Y. Katsube, and P. Doolan, [13] Nagami, K., Demizu, N., Esaki, H., Katsube, Y. and P. Doolan,
"VCID Notification over ATM link for LDP," Work in Progress. "VCID Notification over ATM link for LDP", RFC 3038, January
2001.
[14] T. Narten and H. Alvestrand, "Guidelines for Writing an IANA [14] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA
Considerations Section in RFCs," RFC 2434, October 1998. Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[15] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A [15] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A
Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996. Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996.
[16] S. Damaskos and A. Gavras, "Connection Oriented Protocols [16] S. Damaskos and A. Gavras, "Connection Oriented Protocols over
over ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, February
February 1994. 1994.
[17] ITU-T, "Integrated Services Digital Network (ISDN) Overall [17] ITU-T, "Integrated Services Digital Network (ISDN) Overall
Network Aspects and Functions ISDN Protocol Reference Model," ITU- Network Aspects and Functions ISDN Protocol Reference Model,"
T Recommendation I.320, November 1993. ITU-T Recommendation I.320, November 1993.
[18] ITU-T, "Digital Subscriber Signaling System No. 1 (DSS 1) [18] ITU-T, "Digital Subscriber Signaling System No. 1 (DSS 1)
Specification of a Synchronization and Coordination Function for Specification of a Synchronization and Coordination Function for
the Provision of the OSI Connection-mode Network Service in an the Provision of the OSI Connection-mode Network Service in an
ISDN Environment," ITU-T Recommendation Q.923, February 1995. ISDN Environment," ITU-T Recommendation Q.923, February 1995.
Acknowledgments Acknowledgments
I would like to thank Kenichi Kitami of the NTT Information I would like to thank Kenichi Kitami of the NTT Information Sharing
Sharing Lab. Group, who is also the chair of ITU-T SG11 WP1, Lab. Group, who is also the chair of ITU-T SG11 WP1, Shinichi
Shinichi Kuribayashi of the NTT Information Sharing Platform Kuribayashi of the NTT Information Sharing Platform Labs., Hiroshi
Labs., Hiroshi Yao and Takumi Ohba of the NTT Network Service Yao and Takumi Ohba of the NTT Network Service Systems Labs., and
Systems Labs., and Noriyuki Takahashi of the NTT Information Noriyuki Takahashi of the NTT Information Sharing Platform Labs., for
Sharing Platform Labs., for their valuable comments and their valuable comments and discussions.
discussions.
And I would also like to thank the active members of IETF, ITU-T, And I would also like to thank the active members of IETF, ITU-T, and
and ATM Forum, especially Joel Halpern of Newbridge Networks, ATM Forum, especially Joel Halpern of Newbridge Networks, Andrew
Andrew Malis of Ascend Communications, George Swallow and Bruce Malis of Ascend Communications, George Swallow and Bruce Davie of
Davie of Cisco Systems, Rao Cherukuri of IBM, Rajiv Kapoor of Cisco Systems, Rao Cherukuri of IBM, Rajiv Kapoor of AT&T, Greg Ratta
AT&T, Greg Ratta of Lucent, Kaoru Kenyoshi of NEC, Hiroto Uno of of Lucent, Kaoru Kenyoshi of NEC, Hiroto Uno of Hitachi, Hiroshi
Hitachi, Hiroshi Esaki and Kenichi Nagami of Toshiba, and Esaki and Kenichi Nagami of Toshiba, and Noritoshi Demizu of NAIST
Noritoshi Demizu of NAIST for their valuable comments and for their valuable comments and suggestions.
suggestions.
Also this specification is based on various discussions during the Also, this specification is based on various discussions during the
ST2+ over ATM project at the NTT Multimedia Joint Project with ST2+ over ATM project at the NTT Multimedia Joint Project with
NACSIS. I would like to thank Professor Shoichiro Asano of the NACSIS. I would like to thank Professor Shoichiro Asano of the
National Center for Science Information Systems for his invaluable National Center for Science Information Systems for his invaluable
advice in this area. advice in this area.
Author's Address Author's Address
Muneyoshi Suzuki Muneyoshi Suzuki
NTT Information Sharing Platform Laboratories NTT Information Sharing Platform Laboratories
3-9-11, Midori-cho 3-9-11, Midori-cho
Musashino-shi, Tokyo 180-8585, Japan Musashino-shi, Tokyo 180-8585, Japan
Phone: +81-422-59-2119 Phone: +81-422-59-2119
Fax: +81-422-59-3203 Fax: +81-422-37-7691
EMail: suzuki@nal.ecl.net EMail: suzuki.muneyoshi@lab.ntt.co.jp
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.
 End of changes. 58 change blocks. 
182 lines changed or deleted 175 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/