Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses

Internet Engineering Task Force (IETF)                          J. Arkko
Request for Comments: 8602                                      Ericsson
Updates: <a href="./rfc3219">3219</a>                                                  T. Hardie
Category: Standards Track                                      July 2019
ISSN: 2070-1721


   <span class="h1">Update to the Telephony Routing over IP (TRIP) IANA Registry Rules</span>
                       <span class="h1">regarding Postal Addresses</span>

Abstract

   This memo updates the IANA registry rules for the Telephony Routing
   over IP (TRIP) protocol, by no longer requiring that postal addresses
   be included in contact information.

   This memo updates <a href="./rfc3219">RFC 3219</a>.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in <a href="./rfc7841#section-2">Section 2 of RFC 7841</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="https://www.rfc-editor.org/info/rfc8602">https://www.rfc-editor.org/info/rfc8602</a>.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="https://trustee.ietf.org/license-info">https://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.





<span class="grey">Arkko & Hardie               Standards Track                    [Page 1]</span>

<span id="page-2" ></span>
<span class="grey"><a href="./rfc8602">RFC 8602</a>                  TRIP Registry Update                 July 2019</span>


Table of Contents

   <a href="#section-1">1</a>.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-2">2</a>.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-3">3</a>.  Security Considerations . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   <a href="#section-4">4</a>.  Normative References  . . . . . . . . . . . . . . . . . . . .   <a href="#page-2">2</a>
   Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   <a href="#page-3">3</a>

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

   This memo updates the IANA registry rules for the Telephony Routing
   over IP (TRIP) protocol, by no longer requiring that postal addresses
   be included in contact information.  No use for the addresses is
   identified, and omitting this information provides a privacy benefit.

   This memo updates <a href="./rfc3219">RFC 3219</a>.

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

   This memo updates the registration rules [<a href="./rfc8126" title="">RFC8126</a>] for TRIP
   Attributes (<a href="./rfc3219#section-13.2">[RFC3219], Section 13.2</a>) and TRIP IP Telephony
   Administrative Domain (ITAD) Numbers (<a href="./rfc3219#section-13.5">[RFC3219], Section 13.5</a>) as
   follows.

   The IETF no longer requires IANA to collect postal address
   information when adding TRIP registry entries.  Additionally, IANA
   has removed previously collected postal addresses from the
   registries.

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

   No security impacts of this change have been identified.

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

   [<a id="ref-RFC3219">RFC3219</a>]  Rosenberg, J., Salama, H., and M. Squire, "Telephony
              Routing over IP (TRIP)", <a href="./rfc3219">RFC 3219</a>, DOI 10.17487/RFC3219,
              January 2002, <<a href="https://www.rfc-editor.org/info/rfc3219">https://www.rfc-editor.org/info/rfc3219</a>>.

   [<a id="ref-RFC8126">RFC8126</a>]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
              Writing an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>,
              <a href="./rfc8126">RFC 8126</a>, DOI 10.17487/RFC8126, June 2017,
              <<a href="https://www.rfc-editor.org/info/rfc8126">https://www.rfc-editor.org/info/rfc8126</a>>.







<span class="grey">Arkko & Hardie               Standards Track                    [Page 2]</span>

<span id="page-3" ></span>
<span class="grey"><a href="./rfc8602">RFC 8602</a>                  TRIP Registry Update                 July 2019</span>


Acknowledgements

   The authors would like to thank Michelle Cotton, Alissa Cooper, and
   Jonathan Rosenberg for interesting discussions in this problem space.
   The authors would also like to thank Carlos Pignataro, Russ Housley,
   Abdussalam Baryun, and Paul Wouters for feedback.

Authors' Addresses

   Jari Arkko
   Ericsson
   Kauniainen  02700
   Finland

   Email: [email protected]


   Ted Hardie

   Email: [email protected]































Arkko & Hardie               Standards Track                    [Page 3]