Internet Engineering Task Force J. Arkko Internet-Draft Ericsson Updates: 3219 (if approved) T. Hardie Intended status: Standards Track December 4, 2018 Expires: June 7, 2019 Update to the TRIP IANA Registry Rules Regarding Postal Addresses draft-arkko-trip-registry-update-01 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 RFC 3219. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on June 7, 2019. Copyright Notice Copyright (c) 2018 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) 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 Arkko & Hardie Expires June 7, 2019 [Page 1]
Internet-Draft TRIP Registry Update December 2018 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 2 5. Normative References . . . . . . . . . . . . . . . . . . . . 2 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction 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 RFC 3219. 2. IANA Considerations This memo updates the registration rules [RFC8126] for TRIP Attributes ([RFC3219], Section 13.2) and TRIP ITAD Numbers ([RFC3219], Section 13.5) as follows. IANA will no longer collect postal address information when adding TRIP registry entries. Additionally, IANA should no longer publish previously collected postal addresses. 3. Security Considerations No security impacts of this change have been identified. 4. 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. 5. Normative References [RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony Routing over IP (TRIP)", RFC 3219, DOI 10.17487/RFC3219, January 2002, <https://www.rfc-editor.org/info/rfc3219>. Arkko & Hardie Expires June 7, 2019 [Page 2]
Internet-Draft TRIP Registry Update December 2018 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for Writing an IANA Considerations Section in RFCs", BCP 26, RFC 8126, DOI 10.17487/RFC8126, June 2017, <https://www.rfc-editor.org/info/rfc8126>. Authors' Addresses Jari Arkko Ericsson Kauniainen 02700 Finland Email: jari.arkko@piuha.net Ted Hardie Email: ted.ietf@gmail.com Arkko & Hardie Expires June 7, 2019 [Page 3]
