[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits] [IPR]

Versions: (draft-tuexen-sigtran-rfc4233update) 00 01 02 RFC 5133

Network Working Group                                          M. Tuexen
Internet-Draft                        Muenster Univ. of Applied Sciences
Expires: December 28, 2006                                  K. Morneault
                                                     Cisco Systems, Inc.
                                                           June 26, 2006


                    TEI Query Request Number Change
                draft-ietf-sigtran-rfc4233update-00.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 December 28, 2006.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   The IUA protocol described in RFC4233 defines the messages type of
   TEI Query Request messages as 5.  But this number is already used by
   the IUA extension DUA described in RFC4129.  This document updates
   IUA such that the message type of TEI Query Request messages is 8.






Tuexen & Morneault      Expires December 28, 2006               [Page 1]


Internet-Draft       TEI Query Request Number Change           June 2006


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.  Normative References  . . . . . . . . . . . . . . . . . . . . . 3
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 5
   Intellectual Property and Copyright Statements  . . . . . . . . . . 6









































Tuexen & Morneault      Expires December 28, 2006               [Page 2]


Internet-Draft       TEI Query Request Number Change           June 2006


1.  Introduction

   The IUA protocol described in RFC3057 [2] does not define a TEI Query
   Request message.  The IUA extension DUA described in RFC4129 [3]
   introduces DLC Status messages of type 5, 6, and 7.  After that
   RFC4233 [4] was published, which updates RFC3057 [2].  This document
   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 [4]


2.  Conventions

   The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD,
   SHOULD NOT, RECOMMENDED, NOT RECOMMENDED, MAY, and OPTIONAL, when
   they appear in this document, are to be interpreted as described in
   RFC2119 [1].


3.  New Message Type of the TEI Query Message

   This document updates RFC4233 [4] by introducing the following
   change.

   TEI Query messages MUST be encoded with a message type of 8 instead
   of 5 as described in RFC4233 [4].


4.  IANA Considerations

   IANA should reserve the message type 8 of Management Messages for TEI
   Query Request messages.


5.  Security Considerations

   This document does not require any security considerations in
   addition to the one given in RFC4233 [4].

6.  Normative References

   [1]  Bradner, S., "Key words for use in RFCs to Indicate Requirement
        Levels", BCP 14, RFC 2119, March 1997.

   [2]  Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom,
        "ISDN Q.921-User Adaptation Layer", RFC 3057, February 2001.



Tuexen & Morneault      Expires December 28, 2006               [Page 3]


Internet-Draft       TEI Query Request Number Change           June 2006


   [3]  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.

   [4]  Morneault, K., Rengasami, S., Kalla, M., and G. Sidebottom,
        "Integrated Services Digital Network (ISDN) Q.921-User
        Adaptation Layer", RFC 4233, January 2006.











































Tuexen & Morneault      Expires December 28, 2006               [Page 4]


Internet-Draft       TEI Query Request Number Change           June 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 December 28, 2006               [Page 5]


Internet-Draft       TEI Query Request Number Change           June 2006


Intellectual Property Statement

   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.


Disclaimer of Validity

   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 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.


Copyright Statement

   Copyright (C) The Internet Society (2006).  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.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Tuexen & Morneault      Expires December 28, 2006               [Page 6]


Html markup produced by rfcmarkup 1.129d, available from https://tools.ietf.org/tools/rfcmarkup/