idnits 2.17.1 draft-arkko-trip-registry-update-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year (Using the creation date from RFC3219, updated by this document, for RFC5378 checks: 1999-10-22) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (December 4, 2018) is 1969 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 0 errors (**), 0 flaws (~~), 1 warning (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force J. Arkko 3 Internet-Draft Ericsson 4 Updates: 3219 (if approved) T. Hardie 5 Intended status: Standards Track December 4, 2018 6 Expires: June 7, 2019 8 Update to the TRIP IANA Registry Rules Regarding Postal Addresses 9 draft-arkko-trip-registry-update-01 11 Abstract 13 This memo updates the IANA registry rules for the Telephony Routing 14 over IP (TRIP) protocol, by no longer requiring that postal addresses 15 be included in contact information. 17 This memo updates RFC 3219. 19 Status of This Memo 21 This Internet-Draft is submitted in full conformance with the 22 provisions of BCP 78 and BCP 79. 24 Internet-Drafts are working documents of the Internet Engineering 25 Task Force (IETF). Note that other groups may also distribute 26 working documents as Internet-Drafts. The list of current Internet- 27 Drafts is at http://datatracker.ietf.org/drafts/current/. 29 Internet-Drafts are draft documents valid for a maximum of six months 30 and may be updated, replaced, or obsoleted by other documents at any 31 time. It is inappropriate to use Internet-Drafts as reference 32 material or to cite them other than as "work in progress." 34 This Internet-Draft will expire on June 7, 2019. 36 Copyright Notice 38 Copyright (c) 2018 IETF Trust and the persons identified as the 39 document authors. All rights reserved. 41 This document is subject to BCP 78 and the IETF Trust's Legal 42 Provisions Relating to IETF Documents 43 (http://trustee.ietf.org/license-info) in effect on the date of 44 publication of this document. Please review these documents 45 carefully, as they describe your rights and restrictions with respect 46 to this document. Code Components extracted from this document must 47 include Simplified BSD License text as described in Section 4.e of 48 the Trust Legal Provisions and are provided without warranty as 49 described in the Simplified BSD License. 51 Table of Contents 53 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 54 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 2 55 3. Security Considerations . . . . . . . . . . . . . . . . . . . 2 56 4. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 2 57 5. Normative References . . . . . . . . . . . . . . . . . . . . 2 58 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 3 60 1. Introduction 62 This memo updates the IANA registry rules for the Telephony Routing 63 over IP (TRIP) protocol, by no longer requiring that postal addresses 64 be included in contact information. No use for the addresses is 65 identified, and omitting this information provides a privacy benefit. 67 This memo updates RFC 3219. 69 2. IANA Considerations 71 This memo updates the registration rules [RFC8126] for TRIP 72 Attributes ([RFC3219], Section 13.2) and TRIP ITAD Numbers 73 ([RFC3219], Section 13.5) as follows. 75 IANA will no longer collect postal address information when adding 76 TRIP registry entries. Additionally, IANA should no longer publish 77 previously collected postal addresses. 79 3. Security Considerations 81 No security impacts of this change have been identified. 83 4. Acknowledgements 85 The authors would like to thank Michelle Cotton, Alissa Cooper, and 86 Jonathan Rosenberg for interesting discussions in this problem space. 87 The authors would also like to thank Carlos Pignataro, Russ Housley, 88 Abdussalam Baryun, and Paul Wouters for feedback. 90 5. Normative References 92 [RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony 93 Routing over IP (TRIP)", RFC 3219, DOI 10.17487/RFC3219, 94 January 2002, . 96 [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for 97 Writing an IANA Considerations Section in RFCs", BCP 26, 98 RFC 8126, DOI 10.17487/RFC8126, June 2017, 99 . 101 Authors' Addresses 103 Jari Arkko 104 Ericsson 105 Kauniainen 02700 106 Finland 108 Email: jari.arkko@piuha.net 110 Ted Hardie 112 Email: ted.ietf@gmail.com