Network Working Group M. Tuexen
Request for Comments: 5133 Muenster Univ. of Applied Sciences
Updates: 4233 K. Morneault
Category: Standards Track Cisco Systems, Inc.
December 2007
Network Working Group M. Tuexen
Request for Comments: 5133 Muenster Univ. of Applied Sciences
Updates: 4233 K. Morneault
Category: Standards Track Cisco Systems, Inc.
December 2007
Terminal Endpoint Identifier (TEI) Query Request Number Change
终端端点标识符（TEI）查询请求编号更改
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）。本备忘录的分发不受限制。
Abstract
摘要
The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) Protocol, described in RFC 4233, defines the message type of Terminal Endpoint Identifier (TEI) Query Request messages as 5. However, this number is already being used by the Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol described in RFC 4129. This document updates RFC 4233 such that the message type of TEI Query Request messages is 8.
RFC 4233中描述的综合业务数字网（ISDN）Q.921-用户适配层（IUA）协议将终端端点标识符（TEI）查询请求消息的消息类型定义为5。然而，数字专用网信令系统（DPNSS）/数字接入信令系统2（DASS 2）扩展（DUA）已经在使用该号码，以实现RFC 4129中描述的IUA协议。本文档更新RFC 4233，使TEI查询请求消息的消息类型为8。
Table of Contents
目录
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . . 2
3. New Message Type of the TEI Query Message . . . . . . . . . . . 2
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 2
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 2
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 2
7. Normative References . . . . . . . . . . . . . . . . . . . . . 3
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . . 2
3. New Message Type of the TEI Query Message . . . . . . . . . . . 2
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 2
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 2
6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 2
7. Normative References . . . . . . . . . . . . . . . . . . . . . 3
The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) protocol, described in [RFC3057], does not define a Terminal Endpoint Identifier (TEI) Query Request message. The Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol, described in [RFC4129], introduces Data Link Connection (DLC) Status messages of type 5, 6, and 7. Then, [RFC4233] was published, which updates [RFC3057]. [RFC4233] also introduces the TEI Query Request message and uses the message type of 5 for it. This makes it impossible to differentiate the DLC Status request from a TEI Query Request.
[RFC3057]中描述的综合业务数字网（ISDN）Q.921-用户适配层（IUA）协议未定义终端端点标识符（TEI）查询请求消息。[RFC4129]中描述的IUA协议的数字专用网络信令系统（DPNSS）/数字接入信令系统2（DASS 2）扩展（DUA）引入了类型为5、6和7的数据链路连接（DLC）状态消息。然后发布了[RFC4233]，更新了[RFC3057]。[RFC4233]还引入了TEI查询请求消息，并使用消息类型5。这使得无法区分DLC状态请求和TEI查询请求。
This document updates [RFC4233].
本文件更新了[RFC4233]。
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
This document updates [RFC4233] by introducing the following change:
本文件通过引入以下变更对[RFC4233]进行了更新：
Terminal Endpoint Identifier (TEI) Query messages MUST be encoded with a message type of 8 instead of 5 as described in [RFC4233].
终端端点标识符（TEI）查询消息必须按照[RFC4233]中所述的消息类型8而不是5进行编码。
In the "Message Types" section of the "Signaling User Adaptation Layer Assignments" registry, IANA has reserved the message type 8 of Management Messages for Terminal Endpoint Identifier (TEI) Query Request messages.
在“信令用户适配层分配”注册表的“消息类型”部分，IANA为终端端点标识符（TEI）查询请求消息保留了管理消息的消息类型8。
This document does not require any security considerations in addition to the ones given in [RFC4233].
除[RFC4233]中给出的安全注意事项外，本文件不需要任何安全注意事项。
The authors wish to thank Jon Peterson and Christian Vogt for their invaluable comments.
作者希望感谢乔恩·彼得森和克里斯蒂安·沃格特的宝贵评论。
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3057] Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom, "ISDN Q.921-User Adaptation Layer", RFC 3057, February 2001.
[RFC3057]Morneault，K.，Rengasami，S.，Kalla，M.，和G.Sidebottom，“ISDN Q.921-用户适配层”，RFC 3057，2001年2月。
[RFC4129] Mukundan, R., Morneault, K., and N. Mangalpally, "Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA Protocol", RFC 4129, September 2005.
[RFC4129]Mukundan，R.，Morneault，K.，和N.Mangalpally，“数字专用网络信令系统（DPNSS）/数字接入信令系统2（DASS 2）对IUA协议的扩展”，RFC 41292005年9月。
[RFC4233] Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom, "Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer", RFC 4233, January 2006.
[RFC4233]Morneault，K.，Rengasami，S.，Kalla，M.，和G.Sidebottom，“综合业务数字网（ISDN）Q.921-用户适配层”，RFC 4233，2006年1月。
Authors' Addresses
作者地址
Michael Tuexen Muenster Univ. of Applied Sciences Stegerwaldstr. 39 48565 Steinfurt Germany
Michael Tuexen Muenster应用科学大学Stegerwaldstr。39 48565德国斯坦福德
EMail: tuexen@fh-muenster.de
EMail: tuexen@fh-muenster.de
Ken Morneault Cisco Systems, Inc. 13615 Dulles Technology Drive Herndon, VA 20171 US
Ken Morneault Cisco Systems，Inc.美国弗吉尼亚州赫恩登市杜勒斯技术大道13615号，邮编20171
Phone: +1-703-484-3323
EMail: kmorneau@cisco.com
Phone: +1-703-484-3323
EMail: kmorneau@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The IETF Trust (2007).
版权所有（C）IETF信托基金（2007年）。
This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息以“原样”为基础提供，贡献者、他/她所代表或赞助的组织（如有）、互联网协会、IETF信托基金和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.