Terminal Endpoint Identifier (TEI) Query Request Number Change

Network Working Group                                          M. Tuexen
Request for Comments: 5133            Muenster Univ. of Applied Sciences
Updates: <a href="./rfc4233">4233</a>                                               K. Morneault
Category: Standards Track                            Cisco Systems, Inc.
                                                           December 2007


     <span class="h1">Terminal Endpoint Identifier (TEI) Query Request Number Change</span>

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.

Abstract

   The Integrated Services Digital Network (ISDN) Q.921-User Adaptation
   Layer (IUA) Protocol, described in <a href="./rfc4233">RFC 4233</a>, 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 <a href="./rfc4129">RFC 4129</a>.
   This document updates <a href="./rfc4233">RFC 4233</a> such that the message type of TEI
   Query Request messages is 8.

Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  Conventions Used in This Document . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-3">3</a>.  New Message Type of the TEI Query Message . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-4">4</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-5">5</a>.  Security Considerations . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-6">6</a>.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a>
   <a href="#section-7">7</a>.  Normative References  . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>














<span class="grey">Tuexen & Morneault          Standards Track                     [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc5133">RFC 5133</a>            TEI Query Request Number Change        December 2007</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The Integrated Services Digital Network (ISDN) Q.921-User Adaptation
   Layer (IUA) protocol, described in [<a href="./rfc3057" title=""ISDN Q.921-User Adaptation Layer"">RFC3057</a>], 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 [<a href="./rfc4129" title=""Digital Private Network Signaling System (DPNSS)/Digital Access Signaling System 2 (DASS 2) Extensions to the IUA Protocol"">RFC4129</a>], introduces Data Link Connection (DLC) Status
   messages of type 5, 6, and 7.  Then, [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>] was published, which
   updates [<a href="./rfc3057" title=""ISDN Q.921-User Adaptation Layer"">RFC3057</a>].  [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>] 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 [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>].

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Conventions Used in This Document</span>

   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 [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>].

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  New Message Type of the TEI Query Message</span>

   This document updates [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>] 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 [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>].

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  IANA Considerations</span>

   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.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   This document does not require any security considerations in
   addition to the ones given in [<a href="./rfc4233" title=""Integrated Services Digital Network (ISDN) Q.921-User Adaptation Layer"">RFC4233</a>].

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  Acknowledgments</span>

   The authors wish to thank Jon Peterson and Christian Vogt for their
   invaluable comments.






<span class="grey">Tuexen & Morneault          Standards Track                     [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc5133">RFC 5133</a>            TEI Query Request Number Change        December 2007</span>


<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Normative References</span>

   [<a id="ref-RFC2119">RFC2119</a>]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC3057">RFC3057</a>]  Morneault, K., Rengasami, S., Kalla, M., and G.
              Sidebottom, "ISDN Q.921-User Adaptation Layer", <a href="./rfc3057">RFC 3057</a>,
              February 2001.

   [<a id="ref-RFC4129">RFC4129</a>]  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", <a href="./rfc4129">RFC 4129</a>, September 2005.

   [<a id="ref-RFC4233">RFC4233</a>]  Morneault, K., Rengasami, S., Kalla, M., and G.
              Sidebottom, "Integrated Services Digital Network (ISDN)
              Q.921-User Adaptation Layer", <a href="./rfc4233">RFC 4233</a>, January 2006.

Authors' Addresses

   Michael Tuexen
   Muenster Univ. of Applied Sciences
   Stegerwaldstr. 39
   48565 Steinfurt
   Germany

   EMail: [email protected]


   Ken Morneault
   Cisco Systems, Inc.
   13615 Dulles Technology Drive
   Herndon, VA  20171
   US

   Phone: +1-703-484-3323
   EMail: [email protected]














<span class="grey">Tuexen & Morneault          Standards Track                     [Page 3]</span>

<span id="page-4" ></span>
<span class="grey"><a href="./rfc5133">RFC 5133</a>            TEI Query Request Number Change        December 2007</span>


Full Copyright Statement

   Copyright (C) The IETF Trust (2007).

   This document is subject to the rights, licenses and restrictions
   contained in <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a>, 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 <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and <a href="https://www.rfc-editor.org/bcp/bcp79">BCP 79</a>.

   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
   <a href="http://www.ietf.org/ipr">http://www.ietf.org/ipr</a>.

   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
   [email protected].












Tuexen & Morneault          Standards Track                     [Page 4]