Network Working Group M. Suzuki
Request for Comments: 3033 NTT
Category: Standards Track January 2001
Network Working Group M. Suzuki
Request for Comments: 3033 NTT
Category: Standards Track January 2001
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
互联网协议的Q.2941通用标识符和Q.2957用户对用户信令中信息字段和协议标识符的分配
Status of this Memo
本备忘录的状况
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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.
本文件的目的是在互联网协议的Q.2941通用标识符和Q.2957用户对用户信令中规定信息字段和协议标识符的分配。
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.
本文件第4节中规定的分配设计用于互联网协议的高级B-ISDN信令支持，尤其是第2节中阐明的互联网协议会话对应连接的B-ISDN信令支持。该规范为在ATM上实现长寿命会话和对QoS敏感的会话传输提供了不可或缺的框架。
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.
本文件的目的是在互联网协议的Q.2941通用标识符和Q.2957用户对用户信令中规定信息字段和协议标识符的分配。
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
本文件第4节中规定的分配设计用于互联网协议的高级B-ISDN信令支持，尤其是与互联网协议中的会话对应的连接的B-ISDN信令支持
clarified in section 2. Needless to say, the purpose of this specification is not limited to this support, and it should also be applicable to other purposes.
在第2节中阐明。不用说，本规范的目的不仅限于此支持，还应适用于其他目的。
This specification provides an indispensable framework for the implementation of long-lived session and QoS-sensitive session transfers over ATM. Note that this document only specifies the assignment of the information field and protocol identifier, and that it may not specify complete protocol that enables interoperable implementation. This is because it is beyond the scope of this document and will be specified in a separate document.
该规范为在ATM上实现长寿命会话和对QoS敏感的会话传输提供了不可或缺的框架。请注意，本文档仅指定信息字段和协议标识符的分配，并且可能未指定支持互操作实现的完整协议。这是因为它超出了本文件的范围，将在单独的文件中指定。
With the development of new multimedia applications on the current Internet, the demands for multimedia support are increasing in the IP network, which currently supports best effort communications. In particular, demands to support QoS guaranteed communications are increasing with the development of voice, audio, and video communications applications. And it may also be necessary to introduce the mechanism that can efficiently transfer the huge volume of traffic expected with these applications.
随着当前Internet上新的多媒体应用的发展，支持尽力而为通信的IP网络对多媒体支持的需求不断增加。特别是，随着语音、音频和视频通信应用的发展，支持QoS保证通信的需求正在增加。此外，可能还需要引入能够有效传输这些应用程序所需的巨大流量的机制。
The major features of B-ISDN are high speed, logical multiplexing with the VP/VC, and flexible QoS management per VC, so it is quite natural to use these distinctive functions of B-ISDN to implement a multimedia support mechanism in the IP network. The flexible QoS management and logical multiplexing functions in B-ISDN are the expected method of implementing the QoS guaranteed communications in the Internet. And when a long-lived session is supported by a particular VC, efficient packet forwarding may be possible using the high speed and logical multiplexing of B-ISDN.
B-ISDN的主要特点是高速、与VP/VC的逻辑多路复用以及每个VC的灵活QoS管理，因此使用B-ISDN的这些独特功能在IP网络中实现多媒体支持机制是很自然的。B-ISDN中灵活的QoS管理和逻辑复用功能是在Internet上实现QoS保证通信的预期方法。并且，当特定VC支持长寿命会话时，可以使用B-ISDN的高速和逻辑多路复用来实现高效分组转发。
This section clarifies B-ISDN signaling functions that are required when the session is supported by the VC, for advanced B-ISDN signaling support of the Internet protocol.
本节阐明了VC支持会话时所需的B-ISDN信令功能，以支持Internet协议的高级B-ISDN信令。
An example scenario for establishing a VC for a long-lived session is shown in Fig. 2.1.
图2.1显示了为长期会话建立VC的示例场景。
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| | | / \ | | / \ | | |
+------+ +-----+ +-----+ +------+
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| | | / \ | | / \ | | |
+------+ +-----+ +-----+ +------+
A. New session initially forwarded over a default VC.
A.新会话最初通过默认VC转发。
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| |<------+-/-\-+--------+-/-\-+------>| |
+------+ +-----+ +-----+ +------+
New VC is set up
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/-+--------+-\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| |<------+-/-\-+--------+-/-\-+------>| |
+------+ +-----+ +-----+ +------+
New VC is set up
B. New VC is set up for the long-lived session.
B.为长期会话设置新VC。
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | |<------+-\-/-+--------+-\-/-+------>| | +-+--+
|.....|__ |===||==| X |========| X |==||===| __|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ +-----+ +------+
New VC
IP Router ATM SW ATM SW IP Router
+----+ Default VC +----+
| WS | +------+ UNI +-----+ +-----+ UNI +------+ | WS |
+--+-+ | |<------+-\-/-+--------+-\-/-+------>| | +-+--+
|.....|__ |===||==| X |========| X |==||===| __|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ +-----+ +------+
New VC
C. Transfer of the long-lived session to a new VC.
C.将长期会话转移到新VC。
Fig. 2.1: Example scenario for establishing a VC for a long-lived session.
图2.1：为长期会话建立VC的示例场景。
First, a session is multiplexed into the default VC connecting the 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 successfully, the long-lived session is moved to the new VC.
首先，会话被多路复用到连接路由器的默认VC中。然后，如果路由器检测到它是一个长期会话，它会为该会话设置一个新的VC。如果新VC成功建立，则长时间会话将移动到新VC。
In this procedure involving an ATM VC setup, the B-ISDN signaling entity in the called side router must detect that the incoming call corresponds to a session of the Internet protocol and notify that fact to the IP layer entity. Based on this information, the IP layer entity moves the session to the new VC.
在这个涉及ATM VC设置的过程中，被叫方路由器中的B-ISDN信令实体必须检测到传入呼叫对应于因特网协议的会话，并将该事实通知IP层实体。基于此信息，IP层实体将会话移动到新VC。
Therefore, to implement this signaling procedure, the B-ISDN signaling must include an session identifier as an information element. The B-LLI, B-HLI, User-user, and Generic Identifier information elements are all capable of transferring this information. Considering the original purposes of these information elements, the most appropriate one to use is the Generic Identifier information element.
因此，为了实现该信令过程，B-ISDN信令必须包括会话标识符作为信息元素。B-LLI、B-HLI、用户和通用标识符信息元素都能够传输此信息。考虑到这些信息元素的原始用途，最适合使用的是通用标识符信息元素。
The major difference between QoS-sensitive session signaling and long-lived session signaling is that call setup is not initiated by the detection of a long-lived session, but is explicitly initiated by the setup protocol such as RSVP. To implement QoS-sensitive session signaling using ATM, the ATM network between the routers must forward not only the session identifier but also the setup protocol.
QoS敏感会话信令和长寿命会话信令之间的主要区别在于，呼叫设置不是通过检测长寿命会话来启动的，而是通过设置协议（如RSVP）显式启动的。为了使用ATM实现对QoS敏感的会话信令，路由器之间的ATM网络不仅必须转发会话标识符，还必须转发设置协议。
There are two schemes for forwarding the setup protocol. One is to multiplex the protocol into a default VC connecting the routers, or to forward the protocol through a particular VC. In this case, the QoS-sensitive session and the ATM VC are established sequentially. The second scheme is to forward the setup protocol as an information element in the B-ISDN signaling. In this case, the QoS-sensitive session and the ATM VC are established simultaneously. The latter scheme has the following advantages compared with the former one.
有两种转发设置协议的方案。一种是将协议复用到连接路由器的默认VC中，或者通过特定VC转发协议。在这种情况下，按顺序建立QoS敏感会话和ATM VC。第二种方案是将设置协议作为B-ISDN信令中的信息元素转发。在这种情况下，QoS敏感会话和ATM VC同时建立。与前者相比，后者具有以下优点。
o Easier to implement.
o 更容易实现。
- Admission control is simplified, because admission control for the IP and ATM layers can be done simultaneously.
- 由于IP层和ATM层的准入控制可以同时进行，因此准入控制被简化。
- Watchdog timer processing is simplified, because there is no need to watch the IP layer establishment and ATM layer establishment sequentially.
- 看门狗定时器处理被简化，因为不需要依次监视IP层建立和ATM层建立。
o If the setup protocol supports negotiation, then an ATM VC whose QoS is based on the result of negotiation can be established.
o 如果设置协议支持协商，则可以建立基于协商结果的QoS的ATM-VC。
However, the latter scheme, at least, cannot support a case where a PVC is used to support a QoS-sensitive session. Therefore, both procedures should be taken into account.
然而，后一种方案至少不能支持使用PVC支持QoS敏感会话的情况。因此，这两种程序都应考虑在内。
An example of a message sequence that simultaneously establishes a QoS-sensitive session and an ATM VC is shown in Fig. 2.2.
同时建立QoS敏感会话和ATM VC的消息序列示例如图2.2所示。
IP Router ATM SW ATM SW IP Router
+----+ B-ISDN Signaling +----+
| WS | +------+ UNI +-----+ Setup +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/--Protocol--\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ Data +-----+ +------+
QoS VC
N-CONNECT | |
---------->| | | | | |
|->| SETUP | | | |
| |------------>| | | |
| |<------------| | | |
| | CALL PROC |----------->| SETUP | |
| | | |------------>| |
| | | | |->| N-CONNECT
| | | | | |---------->
| | | | | |<----------
| | | | CONN |<-| N-CONNECT-ACK
| | | |<------------| |
| | | |------------>| |
| | CONN |<-----------| CONN ACK |->|
| |<------------| | | |
| |------------>| | | |
|<-| CONN ACK | | | |
<----------| | | | | |
N-CONNECT | |
-ACK
IP Router ATM SW ATM SW IP Router
+----+ B-ISDN Signaling +----+
| WS | +------+ UNI +-----+ Setup +-----+ UNI +------+ | WS |
+--+-+ | /->|<------+-\-/--Protocol--\-/-+------>|<-\ | +-+--+
|.....|__/ |===||==| X |========| X |==||===| \__|.....|
| \-->|<------+-/-\-+--------+-/-\-+------>|<--/ |
+------+ +-----+ Data +-----+ +------+
QoS VC
N-CONNECT | |
---------->| | | | | |
|->| SETUP | | | |
| |------------>| | | |
| |<------------| | | |
| | CALL PROC |----------->| SETUP | |
| | | |------------>| |
| | | | |->| N-CONNECT
| | | | | |---------->
| | | | | |<----------
| | | | CONN |<-| N-CONNECT-ACK
| | | |<------------| |
| | | |------------>| |
| | CONN |<-----------| CONN ACK |->|
| |<------------| | | |
| |------------>| | | |
|<-| CONN ACK | | | |
<----------| | | | | |
N-CONNECT | |
-ACK
Fig. 2.2: Example procedure for simultaneous QoS-sensitive session and ATM VC establishment.
图2.2：同时建立QoS敏感会话和ATM VC的示例过程。
RSVP is currently proposed for the setup protocol and new setup protocols are likely to be developed in the future. Therefore, to generalize the discussion, the procedure for the setup protocol in this example is the general connection setup procedure using confirmed service.
RSVP目前建议用于设置协议，未来可能会开发新的设置协议。因此，为了概括讨论，本例中设置协议的过程是使用确认服务的一般连接设置过程。
To implement this signaling procedure, the B-ISDN signaling must include the User-user information element that the capacity is sufficient to forward the setup protocol.
为了实现该信令过程，B-ISDN信令必须包括用户信息元素，即容量足以转发设置协议。
The Generic Identifier enables the transfer of identifiers between end-to-end users in the ATM network, and it is defined in the Q.2941 Part 1 (Q.2941.1) [3] and Part 2 (Q.2941.2) [4] as an optional information element for the Q.2931 [1] and Q.2971 [2] UNI signaling protocol. The SETUP, ALERTING, CONNECT, RELEASE, RELEASE COMPLETE, ADD PARTY, PARTY ALERTING, ADD PARTY ACK, ADD PARTY REJECT, DROP PARTY, and DROP PARTY ACK messages that are transferred between end-to-end users in the ATM network may contain up to three Generic Identifier information elements. The ATM network transfers the Generic Identifier information element transparently if it contains no coding rule errors.
通用标识符支持ATM网络中端到端用户之间的标识符传输，并且在Q.2941第1部分（Q.2941.1）[3]和第2部分（Q.2941.2）[4]中定义为Q.2931[1]和Q.2971[2]UNI信令协议的可选信息元素。ATM网络中端到端用户之间传输的设置、警报、连接、释放、释放完成、添加方、添加方警报、添加方确认、添加方拒绝、删除方和删除方确认消息最多可包含三个通用标识符信息元素。如果ATM网络不包含编码规则错误，则它将透明地传输通用标识符信息元素。
The format of the Generic Identifier information element specified in the Q.2941 is shown in Fig. 3.1.
Q.2941中规定的通用标识符信息元素的格式如图3.1所示。
Bits
8 7 6 5 4 3 2 1 Octets
+-----+-----+-----+-----+-----+-----+-----+-----+
| Information element identifier |
| = Generic identifier transport IE (0x7F) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 | Coding | IE instruction field |
| Ext | standard |Flag |Res. | IE action ind. | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Length of contents of information element | 3-4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier related standard/application | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type | 6
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value | 8-
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value |
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
Bits
8 7 6 5 4 3 2 1 Octets
+-----+-----+-----+-----+-----+-----+-----+-----+
| Information element identifier |
| = Generic identifier transport IE (0x7F) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 | Coding | IE instruction field |
| Ext | standard |Flag |Res. | IE action ind. | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Length of contents of information element | 3-4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier related standard/application | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type | 6
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value | 8-
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value |
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 3.1: Format of the Generic Identifier information element.
图3.1：通用标识符信息元素的格式。
The usage of the first 4 octets of fields is specified in section 4 of the Q.2931.
Q.2931第4节规定了字段前4个八位字节的用法。
The Identifier related standard/application field identifies the standard or application that uses the identifier. Assignment of the Identifier related standard/application field for the Internet protocol is as follows. A leading 0x means hexadecimal.
与标识符相关的标准/应用程序字段标识使用标识符的标准或应用程序。互联网协议标识符相关标准/应用字段的分配如下所示。前导0x表示十六进制。
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 H.323/H.245 are also supported.
注：还支持DSM-CC、H.310/H.321、MPOA、ATM VCC中继、AAL2和H.323/H.245。
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 Internet protocol is as follows. A leading 0x means hexadecimal.
Internet协议的标识符类型字段的分配如下所示。前导0x表示十六进制。
0x01: Session.
0x01:会话。
0x02: Resource.
0x02:资源。
0x10-0xFD: Reserved for IANA assignment.
0x10-0xFD：为IANA分配保留。
0xFE: Experiment/Organization specific.
0xFE：特定于实验/组织。
The maximum length of the Generic Identifier information element is 63 octets.
通用标识符信息元素的最大长度为63个八位字节。
See the Q.2941.1 and Draft Q.2941.2 for detailed protocol specifications of the Generic Identifier.
有关通用标识符的详细协议规范，请参见Q.2941.1和草案Q.2941.2。
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 [5, 6] and in Q.2971 annex D [2] as an optional information element for the Q.2931 [1] and Q.2971 [2] UNI signaling protocol. The SETUP, ALERTING, CONNECT, RELEASE, RELEASE COMPLETE, PROGRESS, ADD PARTY, PARTY ALERTING, ADD PARTY ACK, ADD PARTY REJECT, DROP PARTY, and DROP PARTY ACK messages that are transferred between end-to-end users in the ATM network may contain a User-user information element. The ATM network transfers the User-user information element transparently if it contains no coding rule errors.
用户到用户信令支持ATM网络中端到端用户之间的信息传输，Q.2957[5,6]和Q.2971附录D[2]将其定义为Q.2931[1]和Q.2971[2]UNI信令协议的可选信息元素。ATM网络中端到端用户之间传输的设置、警报、连接、释放、释放完成、进度、添加方、方警报、添加方确认、添加方拒绝、删除方和删除方确认消息可能包含用户信息元素。如果ATM网络不包含编码规则错误，则它可以透明地传输用户信息元素。
From the viewpoint of B-ISDN signaling applications, it seems the Generic Identifier and User-to-user Signaling are similar functions. But their rules for processing exceptions are not completely the same, because their purposes are different. The Generic Identifier is designed for the transfer of identifiers between the c-planes, while the User-to-user Signaling is designed for the transfer of user data via the c-planes. Another difference is that the latter supports interworking with the user-user information element in the
从B-ISDN信令应用的角度来看，通用标识符和用户对用户信令似乎是类似的功能。但它们处理异常的规则并不完全相同，因为它们的目的不同。通用标识符设计用于在c平面之间传输标识符，而用户到用户信令设计用于通过c平面传输用户数据。另一个区别是后者支持与
Q.931 N-ISDN signaling, but the Generic Identifier does not. Note that the ATM network may check the contents of the Generic Identifier information element, but does not check the contents of the User-to-user information element.
Q.931 N-ISDN信令，但通用标识符没有。注意，ATM网络可以检查通用标识符信息元素的内容，但不检查用户对用户信息元素的内容。
The format of the User-user information element is shown in Fig. 3.2.
用户信息元素的格式如图3.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 | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| User information | 6-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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 | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| User information | 6-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 3.2: Format of the User-user information element.
图3.2：用户信息元素的格式。
The usage of the first 4 octets of fields is specified in section 4 of the Q.2931.
Q.2931第4节规定了字段前4个八位字节的用法。
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 133 octets.
用户信息元素的最大长度为133个八位字节。
See Q.2957, Draft Q.2957 amendment 1, and Q.2971 annex D for detailed protocol specifications of the User-to-user Signaling.
有关用户对用户信令的详细协议规范，请参见Q.2957、Q.2957修正案草案1和Q.2971附录D。
The information field and protocol identifier assignment principle for the Internet protocol in the Generic Identifier information element is shown in Fig. 4.1.
通用标识符信息元素中互联网协议的信息字段和协议标识符分配原则如图4.1所示。
Bits
8 7 6 5 4 3 2 1 Octets
+-----+-----+-----+-----+-----+-----+-----+-----+
| Information element identifier |
| = Generic identifier transport IE (0x7F) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 | Coding | IE instruction field |
| Ext | standard |Flag |Res. | IE action ind. | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Length of contents of information element | 3-4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier related standard/application |
| = IPv4, ST2+, IPv6, or MPLS | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session, Resource, or Experiment | 6
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value | 8-
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session, Resource, or Experiment |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value |
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
Bits
8 7 6 5 4 3 2 1 Octets
+-----+-----+-----+-----+-----+-----+-----+-----+
| Information element identifier |
| = Generic identifier transport IE (0x7F) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| 1 | Coding | IE instruction field |
| Ext | standard |Flag |Res. | IE action ind. | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Length of contents of information element | 3-4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier related standard/application |
| = IPv4, ST2+, IPv6, or MPLS | 5
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session, Resource, or Experiment | 6
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length | 7
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value | 8-
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session, Resource, or Experiment |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier value |
= =
+-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.1: Principle of assignment in the Generic Identifier information element.
图4.1：通用标识符信息元素中的赋值原理。
The Identifier related standard/application field is the IPv4, ST2+, IPv6, or MPLS.
与标识符相关的标准/应用程序字段是IPv4、ST2+、IPv6或MPLS。
The Identifier type field is the Session, Resource, or Experiment/Organization specific.
标识符类型字段是特定于会话、资源或实验/组织的。
The Identifier value field is assigned to Internet protocol related information which is identified by the Identifier related standard/application field and Identifier type field. The following identifiers are specified.
标识符值字段分配给互联网协议相关信息，该信息由标识符相关标准/应用字段和标识符类型字段标识。指定了以下标识符。
Std./app. Id type
标准/应用。Id类型
IPv4 session identifier IPv4 Session
IPv4会话标识符IPv4会话
IPv6 session identifier IPv6 Session
IPv6会话标识符IPv6会话
MPLS VCID MPLS Resource
MPLS VCID MPLS资源
Exp./Org. specific IPv4/ST2+/IPv6/MPLS Experiment
Exp./Org. specific IPv4/ST2+/IPv6/MPLS Experiment
As described in section 3.1, the B-ISDN signaling message transferred between end-to-end users may contain up to three Generic Identifier information elements. These elements may contain multiple identifiers. This document does not specify the order of identifiers when multiple identifiers appear in a signaling message.
如第3.1节所述，端到端用户之间传输的B-ISDN信令消息最多可包含三个通用标识符信息元素。这些元素可能包含多个标识符。当一条信令消息中出现多个标识符时，本文档未指定标识符的顺序。
This document also does not specify the semantics when multiple identifiers having the same Identifier type appear in a signaling message, or when a signaling message contains a Generic Identifier information element that does not contain identifiers.
当具有相同标识符类型的多个标识符出现在信令消息中时，或者当信令消息包含不包含标识符的通用标识符信息元素时，本文档也没有指定语义。
When a B-ISDN signaling message containing a Generic Identifier information element enters an ATM network that does not support the Generic Identifier, 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 and section 9.3 of Q.2941.1 for details.)
当包含通用标识符信息元素的B-ISDN信令消息进入不支持通用标识符的ATM网络时，该网络清除呼叫、丢弃信息元素或丢弃信令消息。（详见Q.2931第4.5.1节和第5.6.8.1节以及Q.2941.1第9.3节。）
To enable reliable Generic Identifier information element transfer, when the calling party sends a SETUP or ADD PARTY message with up to three Generic Identifier information elements, the CONNECT or ADD PARTY ACK message returned by the called party must contain at least one Generic Identifier information element. The called party may not respond with the same identifiers received from the calling party. The calling party should confirm that the response message contains at least one Generic Identifier information element. This rule enables identifier negotiation; this document does not specify the detailed procedure of this negotiation.
为了实现可靠的通用标识符信息元素传输，当主叫方发送包含最多三个通用标识符信息元素的设置方或添加方消息时，被叫方返回的连接方或添加方确认消息必须至少包含一个通用标识符信息元素。被叫方可能不会使用从主叫方接收到的相同标识符进行响应。呼叫方应确认响应消息至少包含一个通用标识符信息元素。该规则支持标识符协商；本文件未规定本次谈判的详细程序。
If the Identifier related standard/application field in the Generic Identifier information element is the IPv4, and the Identifier type field in the identifier is the Session, the identifier is the IPv4 session identifier. The format of the IPv4 session identifier is shown in Fig. 4.2.
如果通用标识符信息元素中与标识符相关的标准/应用程序字段为IPv4，且标识符中的标识符类型字段为会话，则标识符为IPv4会话标识符。IPv4会话标识符的格式如图4.2所示。
Bits Octet
8 7 6 5 4 3 2 1 length
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session (0x01) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
| = 13 octets (0x0D) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source IPv4 address | 4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv4 address | 4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
Bits Octet
8 7 6 5 4 3 2 1 length
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session (0x01) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
| = 13 octets (0x0D) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source IPv4 address | 4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv4 address | 4
+-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.2: IPv4 session identifier.
图4.2:IPv4会话标识符。
The Identifier type field is the Session (0x01).
标识符类型字段是会话（0x01）。
The Identifier length is 13 octets.
标识符长度为13个八位字节。
The Source IPv4 address, Destination IPv4 address, Protocol, Source Port, and Destination Port [7, 9, 10] are assigned in that order to the Identifier value field.
源IPv4地址、目标IPv4地址、协议、源端口和目标端口[7、9、10]按该顺序分配给标识符值字段。
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.
注意：此特定会话标识符仅用于显式保留。如果以后需要通配符关联，将使用另一种标识符类型。
If the Identifier related standard/application field in the Generic Identifier information element is the IPv6, and the Identifier type field in the identifier is the Session, the identifier is the IPv6 session identifier. The format of the IPv6 session identifier is
如果通用标识符信息元素中与标识符相关的标准/应用程序字段为IPv6，且标识符中的标识符类型字段为会话，则标识符为IPv6会话标识符。IPv6会话标识符的格式为
shown in Fig. 4.3.
如图4.3所示。
Bits Octet
8 7 6 5 4 3 2 1 length
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session (0x01) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
| = 37 octets (0x25) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source IPv6 address | 16
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv6 address | 16
+-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
Bits Octet
8 7 6 5 4 3 2 1 length
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier type |
| = Session (0x01) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Identifier length |
| = 37 octets (0x25) | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source IPv6 address | 16
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination IPv6 address | 16
+-----+-----+-----+-----+-----+-----+-----+-----+
| Protocol | 1
+-----+-----+-----+-----+-----+-----+-----+-----+
| Source Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
| Destination Port | 2
+-----+-----+-----+-----+-----+-----+-----+-----+
Fig. 4.3: IPv6 session identifier.
图4.3:IPv6会话标识符。
The Identifier type field is the Session (0x01).
标识符类型字段是会话（0x01）。
The Identifier length is 37 octets.
标识符长度为37个八位字节。
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.
源IPv6地址、目标IPv6地址、协议、源端口和目标端口[8、9、10]按该顺序分配给标识符值字段。
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.
注意：此特定会话标识符仅用于显式保留。如果以后需要通配符关联，将使用另一种标识符类型。
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.
如果通用标识符信息元素中与标识符相关的标准/应用程序字段是MPLS，并且标识符中的标识符类型字段是资源，则标识符是MPLS VCID。MPLS VCID的格式如图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
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图4.4:MPLS VCID。
The Identifier type field is the Resource (0x02).
标识符类型字段是资源（0x02）。
The Identifier length is 4 octets.
标识符长度为4个八位字节。
The MPLS VCID [13] is assigned to the Identifier value field.
MPLS VCID[13]被分配给标识符值字段。
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.
如果通用标识符信息元素中与标识符相关的标准/应用程序字段是IPv4、ST2+、IPv6或MPLS，并且标识符中的标识符类型字段是特定于实验/组织的，则标识符是特定于实验/组织的。具体实验/组织的格式如图4.5所示。
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. |
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图4.5：特定实验/组织。
The Identifier type field is the Experiment/Organization specific (0xFE).
标识符类型字段是特定于实验/组织的（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).
标识符值字段中的前3个八位字节必须包含组织唯一标识符（OUI）（如IEEE 802-1990；第5.1节所述）。
The information field and protocol identifier assignment principle for the Internet protocol in the User-user information element is shown in Fig. 4.6.
用户信息元素中互联网协议的信息字段和协议标识符分配原则如图4.6所示。
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-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图4.6：用户信息元素中的分配原则。
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.
协议鉴别器字段是Internet协议/应用程序（0x06）。在这种情况下，用户信息字段中的前1个八位组是互联网协议/应用程序标识符字段。
Assignment of the Internet protocol/application identifier field is as follows. A leading 0x means hexadecimal.
Internet协议/应用程序标识符字段的分配如下所示。前导0x表示十六进制。
0x00: Reserved.
0x00：保留。
0x01: Reserved for ST2+.
0x01:为ST2+保留。
0x02: RSVP message.
0x02:RSVP消息。
0x03-0xFD: Reserved for IANA assignment.
0x03-0xFD：为IANA分配保留。
0xFE: Experiment/Organization specific.
0xFE：特定于实验/组织。
0xFF: Reserved.
0xFF：保留。
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.
Internet协议/应用程序标识符字段后面的字段被分配给由Internet协议/应用程序标识符字段标识的Internet协议/应用程序相关信息。
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.)
当包含用户信息元素的B-ISDN信令消息进入不支持用户对用户信令的ATM网络时，该网络清除呼叫、丢弃信息元素或丢弃信令消息。（详见Q.2931第4.5.1节和第5.6.8.1节、Q.2957第1.9节和Q.2971附录D。）
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.
为了实现可靠的用户信息元素传输，当主叫方发送带有用户信息元素的设置方或添加方消息时，被叫方返回的连接方或添加方确认消息必须包含用户信息元素。被叫方可能不会使用从主叫方接收到的相同用户信息进行响应。呼叫方应确认响应消息包含用户信息元素。这一规则允许谈判；本文件未规定本次谈判的详细程序。
The format of the RSVP message is shown in Fig. 4.7.
RSVP消息的格式如图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-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图4.7:RSVP消息。
The Internet protocol/application identifier field is the RSVP message (0x02).
Internet协议/应用程序标识符字段是RSVP消息（0x02）。
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.
RSVP消息[12]被分配到互联网协议/应用程序相关信息字段。设置消息可能包含RSVP Resv消息。CONNECT消息可能包含RSVP ResvConf消息。释放消息可能包含RSVP ResvErr或ResvTear消息。
The format of the Experiment/Organization specific is shown in Fig. 4.8.
具体实验/组织的格式如图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-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图4.8：特定实验/组织。
The Internet protocol/application identifier field is the Experiment/Organization specific (0xFE).
Internet协议/应用程序标识符字段是特定于实验/组织的（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).
互联网协议/应用程序相关信息字段中的前3个八位字节必须包含组织唯一标识符（OUI）（如IEEE 802-1990；第5.1节所规定）。
The following issues are still remain in this document.
以下问题仍保留在本文件中。
o Generic Identifier support for session aggregation.
o 会话聚合的通用标识符支持。
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.
主干网环境中可能需要会话聚合支持。通配符样式的聚合会话标识符可能是可行的。然而，在为其指定通用标识符支持之前，应澄清ATM VCs中的会话聚合模型。
o Generic Identifier support for the IPv6 flow label and traffic classes.
o IPv6流标签和流量类的通用标识符支持。
The IPv6 flow label and traffic classes support may be needed in future. However, currently their semantics are not clear.
未来可能需要IPv6流标签和流量类支持。然而，目前它们的语义还不清楚。
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.
当Q.2941.2通用标识符信息元素中与标识符相关的标准/应用程序字段为IPv4、ST2+、IPv6或MPLS时，标识符类型字段中0x10-0xFD之间的数字保留用于IANA分配。（见第3.1节）按照[14]中概述的政策，通过IETF共识行动分配这些数字。
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.
当Q.2957用户信息元素中的协议鉴别器字段是Internet协议/应用程序时，Internet协议/应用程序标识符字段中0x03-0xFD之间的数字保留用于IANA分配。（见第4.2.1节）按照[14]中概述的政策，通过IETF共识行动分配这些数字。
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.
本文件规定了互联网协议的Q.2941通用标识符和Q.2957用户对用户信令中的信息字段和协议标识符分配，因此不会削弱B-ISDN信令的安全性。
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 party authentication to strengthen security.
在B-ISDN信令的被叫方中，如果传入的设置消息包含主叫方号码，并且如果它是由ATM网络验证和传递的，或者它是由网络提供的，那么使用主叫方号码作为主叫方身份验证的一部分以加强安全性是可行的。
Appendix. Information Field and Protocol Identifier Assignment for ST2+
附录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.
本附录规定了ST2+通用标识符和用户对用户信令中的信息字段和协议标识符分配。请注意，本附录不是本标准的一部分。
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.
如果通用标识符信息元素中与标识符相关的标准/应用程序字段为ST2+，标识符中的标识符类型字段为会话，则标识符为ST2+会话标识符。ST2+会话标识符的格式如图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
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图A.1:ST2+会话标识符。
The Identifier type field is the Session (0x01).
标识符类型字段是会话（0x01）。
The Identifier length is 6 octets.
标识符长度为6个八位字节。
The Stream ID (SID) [11] is assigned to the Identifier value field.
流ID（SID）[11]被分配给标识符值字段。
The format of the User-user information element for the ST2+ SCMP is shown in Fig. A.2.
ST2+SCMP的用户信息元素的格式如图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-
= =
| |
+-----+-----+-----+-----+-----+-----+-----+-----+
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.
图A.2:ST2+SCMP。
The Internet protocol/application identifier field is the ST2+ SCMP (0x01).
Internet协议/应用程序标识符字段是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.
ST2+SCMP[11]被分配到互联网协议/应用程序相关信息字段。设置和添加方消息可能包含ST2+SCMP CONNECT消息。CONNECT和ADD PARY ACK消息可能包含ST2+SCMP ACCEPT消息。释放方和丢弃方消息可能包含ST2+SCMP断开连接消息。发布、发布完成、添加方拒绝和删除方消息可能包含ST2+SCMP拒绝消息。
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.
[1] ITU-T，“宽带综合业务数字网（B-ISDN）-第2号数字用户信令系统（DSS2）-基本呼叫/连接控制的用户网络接口（UNI）第3层规范”，ITU-T建议Q.2931995年9月。
[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.
[2] ITU-T，“宽带综合业务数字网（B-ISDN）-第2号数字用户信令系统（DSS 2）-点对多点呼叫/连接控制的用户网络接口层3规范”，ITU-T建议Q.2971，1995年10月。
[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.
[3] ITU-T，“宽带综合业务数字网（B-ISDN）数字用户信令系统第2号（DSS 2）：通用标识符传输”，ITU-T新建议Q.2941.11997年9月。
[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.
[4] ITU-T，“宽带综合业务数字网（B-ISDN）数字用户信令系统第2号（DSS 2）：通用标识符传输扩展”，ITU-T新建议Q.2941.2，1999年12月。
[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.
[5] ITU-T，“使用第2号B-ISDN数字用户信令系统（DSS 2）的附加信息传输补充业务的第3阶段说明-基本呼叫条款1-用户对用户信令（UUS）”，ITU-T建议Q.2957，1995年2月。
[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.
[6] ITU-T，“使用B-ISDN数字用户信令系统第2号（DSS 2）的附加信息传输补充业务的第3阶段说明-基本呼叫条款1-用户对用户信令（UUS）”，ITU-T建议Q.2957修订件1，1999年12月。
[7] Postel, J., Ed., "Internet Protocol", STD 5, RFC 791, September 1981.
[7] Postel，J.，Ed.，“互联网协议”，STD 5，RFC 7911981年9月。
[8] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6) Specification", RFC 2460, December 1998.
[8] Deering，S.和R.Hinden，“互联网协议，第6版（IPv6）规范”，RFC 2460，1998年12月。
[9] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.
[9] Postel，J.，“用户数据报协议”，STD 6，RFC 768，1980年8月。
[10] Postel, J., Ed., "Transmission Control Protocol", STD 7, RFC 793, September 1981.
[10] Postel，J.，Ed.，“传输控制协议”，标准7，RFC 793，1981年9月。
[11] Delgrossi, L. and L. Berger, Ed., "Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+", RFC 1819, August 1995.
[11] Delgrossi，L.和L.Berger，编辑，“互联网流协议版本2（ST2）协议规范-版本ST2+”，RFC 18191995年8月。
[12] Braden, R., Ed., "Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification", RFC 2205, September 1997.
[12] Braden，R.，Ed.，“资源预留协议（RSVP）-第1版功能规范”，RFC 22052997年9月。
[13] Nagami, K., Demizu, N., Esaki, H., Katsube, Y. and P. Doolan, "VCID Notification over ATM link for LDP", RFC 3038, January 2001.
[13] Nagami，K.，Demizu，N.，Esaki，H.，Katsube，Y.和P.Doolan，“LDP ATM链路上的VCID通知”，RFC 3038，2001年1月。
[14] Narten, T., and H. Alvestrand, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
[14] Narten，T.和H.Alvestrand，“在RFCs中编写IANA注意事项部分的指南”，BCP 26，RFC 2434，1998年10月。
[15] P. Newman, T. Lyon, and G. Minshall, "Flow Labelled IP: A Connectionless Approach to ATM," Proc. IEEE Infocom, March 1996.
[15] P.Newman，T.Lyon和G.Minshall，“流标记IP：ATM的无连接方法”，Proc。IEEE信息网，1996年3月。
[16] S. Damaskos and A. Gavras, "Connection Oriented Protocols over ATM: A case study," Proc. SPIE, Vol. 2188, pp.226-278, February 1994.
[16] S.Damaskos和A.Gavras，“ATM上面向连接的协议：案例研究”，Proc。SPIE，第2188卷，第226-278页，1994年2月。
[17] ITU-T, "Integrated Services Digital Network (ISDN) Overall Network Aspects and Functions ISDN Protocol Reference Model," ITU-T Recommendation I.320, November 1993.
[17] ITU-T，“综合业务数字网（ISDN）整体网络方面和功能ISDN协议参考模型”，ITU-T建议I.320，1993年11月。
[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.
[18] ITU-T，“在ISDN环境中提供OSI连接模式网络服务的第1号数字用户信令系统（DSS 1）同步和协调功能规范”，ITU-T建议Q.923，1995年2月。
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.
我要感谢NTT信息共享实验室组的Kenichi Kitami，他也是ITU-T SG11 WP1的主席，NTT信息共享平台实验室的Shinici Kuribayashi，NTT网络服务系统实验室的Hiroshi Yao和Takumi Ohba，以及NTT信息共享平台实验室的Noriyuki Takahashi。，感谢他们的宝贵意见和讨论。
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.
我还要感谢IETF、ITU-T和ATM论坛的积极成员，特别是新桥网络的Joel Halpern、Ascend Communications的Andrew Malis、Cisco Systems的George Swallow和Bruce Davie、IBM的Rao Cherukuri、AT&T的Rajiv Kapoor、朗讯的Greg Ratta、NEC的Kaoru Kenyoshi、日立的Hiroto Uno、，东芝的Hiroshi Esaki和Kenichi Nagami以及NAIST的Noritoshi Demizu感谢他们的宝贵意见和建议。
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.
此外，本规范基于NTT多媒体与NACSIS联合项目中ST2+over ATM项目期间的各种讨论。我要感谢国家科学信息系统中心的浅野昭一教授在这方面提出的宝贵建议。
Author's Address
作者地址
Muneyoshi Suzuki NTT Information Sharing Platform Laboratories 3-9-11, Midori-cho Musashino-shi, Tokyo 180-8585, Japan
Muneyoshi Suzuki NTT信息共享平台实验室3-9-11，Midori cho Musashino shi，东京180-8585
Phone: +81-422-59-2119
Fax: +81-422-37-7691
EMail: suzuki.muneyoshi@lab.ntt.co.jp
Phone: +81-422-59-2119
Fax: +81-422-37-7691
EMail: suzuki.muneyoshi@lab.ntt.co.jp
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
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.
RFC编辑功能的资金目前由互联网协会提供。