Terminal Endpoint Identifier (TEI) Query Request Number Change
draft-ietf-sigtran-rfc4233update-02
The information below is for an old version of the document that is already published as an RFC.
Document | Type |
This is an older version of an Internet-Draft that was ultimately published as RFC 5133.
|
|
---|---|---|---|
Authors | Ken Morneault , Michael Tüxen | ||
Last updated | 2015-10-14 (Latest revision 2007-11-03) | ||
Replaces | draft-tuexen-sigtran-rfc4233update | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Became RFC 5133 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | Jon Peterson | ||
Send notices to | (None) |
draft-ietf-sigtran-rfc4233update-02
Network Working Group M. Tuexen Internet-Draft Muenster Univ. of Applied Sciences Updates: 4233 (if approved) K. Morneault Intended status: Standards Track Cisco Systems, Inc. Expires: May 6, 2008 November 3, 2007 TEI Query Request Number Change draft-ietf-sigtran-rfc4233update-02.txt Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that 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 http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on May 6, 2008. Copyright Notice Copyright (C) The IETF Trust (2007). Abstract The Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer (IUA) protocol described in RFC4233 defines the messages type of Terminal Endpoint Identifier (TEI) Query Request messages as 5. But this number is already used by the Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions (DUA) to the IUA Protocol described in RFC4129. This document updates RFC4233 such that the message type of TEI Query Tuexen & Morneault Expires May 6, 2008 [Page 1] Internet-Draft TEI Query Request Number Change November 2007 Request messages is 8. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. New Message Type of the TEI Query Message . . . . . . . . . . . 3 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 3 6. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 3 7. Normative References . . . . . . . . . . . . . . . . . . . . . 4 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 4 Intellectual Property and Copyright Statements . . . . . . . . . . 5 Tuexen & Morneault Expires May 6, 2008 [Page 2] Internet-Draft TEI Query Request Number Change November 2007 1. Introduction 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. This document updates [RFC4233]. 2. Conventions 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]. 3. New Message Type of the TEI Query Message This document updates [RFC4233] by introducing the following change. Terminal Endpoint Identifier (TEI) Query messages MUST be encoded with a message type of 8 instead of 5 as described in [RFC4233]. 4. IANA Considerations IANA should reserve the message type 8 of Management Messages for Terminal Endpoint Identifier (TEI) Query Request messages. 5. Security Considerations This document does not require any security considerations in addition to the ones given in [RFC4233]. 6. Acknowledgments The authors wish to thank Jon Peterson and Christian Vogel for their invaluable comments. Tuexen & Morneault Expires May 6, 2008 [Page 3] Internet-Draft TEI Query Request Number Change November 2007 7. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3057] Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom, "ISDN Q.921-User Adaptation Layer", RFC 3057, February 2001. [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. [RFC4233] Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom, "Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer", RFC 4233, January 2006. Authors' Addresses Michael Tuexen Muenster Univ. of Applied Sciences Stegerwaldstr. 39 48565 Steinfurt Germany Email: tuexen@fh-muenster.de Ken Morneault Cisco Systems, Inc. 13615 Dulles Technology Drive Herndon, VA 20171 US Phone: +1-703-484-3323 Email: kmorneau@cisco.com Tuexen & Morneault Expires May 6, 2008 [Page 4] Internet-Draft TEI Query Request Number Change November 2007 Full Copyright Statement Copyright (C) The IETF Trust (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. 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. 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. 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. 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. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Tuexen & Morneault Expires May 6, 2008 [Page 5]