draft-arkko-trip-registry-update-00.txt   draft-arkko-trip-registry-update.txt 
Internet Engineering Task Force J. Arkko Internet Engineering Task Force J. Arkko
Internet-Draft Ericsson Internet-Draft Ericsson
Updates: 3219 (if approved) T. Hardie Updates: 3219 (if approved) T. Hardie
Intended status: Informational July 16, 2018 Intended status: Standards Track December 4, 2018
Expires: January 17, 2019 Expires: June 7, 2019
Update to the TRIP IANA Registry Rules Regarding Postal Addresses Update to the TRIP IANA Registry Rules Regarding Postal Addresses
draft-arkko-trip-registry-update-00 draft-arkko-trip-registry-update-01
Abstract Abstract
This memo updates the IANA registry rules for the Telephony Routing This memo updates the IANA registry rules for the Telephony Routing
over IP (TRIP) protocol, by no longer requiring that postal addresses over IP (TRIP) protocol, by no longer requiring that postal addresses
be included in contact information. be included in contact information.
This memo updates RFC 3219. This memo updates RFC 3219.
Status of This Memo Status of This Memo
skipping to change at page 1, line 35 skipping to change at page 1, line 35
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 17, 2019. This Internet-Draft will expire on June 7, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
This memo updates the IANA registry rules for the Telephony Routing This memo updates the IANA registry rules for the Telephony Routing
over IP (TRIP) protocol, by no longer requiring that postal addresses over IP (TRIP) protocol, by no longer requiring that postal addresses
be included in contact information. No use for the addresses is be included in contact information. No use for the addresses is
identified, and omitting this information provides a privacy benefit. identified, and omitting this information provides a privacy benefit.
This memo updates RFC 3219. This memo updates RFC 3219.
2. IANA Considerations 2. IANA Considerations
This memo updates the registration rules for TRIP Attributes This memo updates the registration rules [RFC8126] for TRIP
([RFC3219], Section 13.2) and TRIP ITAD Numbers ([RFC3219], Attributes ([RFC3219], Section 13.2) and TRIP ITAD Numbers
Section 13.5) as follows. ([RFC3219], Section 13.5) as follows.
IANA will no longer collect postal address information when adding IANA will no longer collect postal address information when adding
TRIP registry entries. Additionally, IANA should no longer publish TRIP registry entries. Additionally, IANA should no longer publish
previously collected postal addresses. previously collected postal addresses.
3. Security Considerations 3. Security Considerations
No security impacts of this change have been identified. No security impacts of this change have been identified.
4. Acknowledgements 4. Acknowledgements
The authors would like to thank Michelle Cotton, Alissa Cooper, and The authors would like to thank Michelle Cotton, Alissa Cooper, and
Jonathan Rosenberg for interesting discussions in this problem space. 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 5. Normative References
[RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony [RFC3219] Rosenberg, J., Salama, H., and M. Squire, "Telephony
Routing over IP (TRIP)", RFC 3219, DOI 10.17487/RFC3219, Routing over IP (TRIP)", RFC 3219, DOI 10.17487/RFC3219,
January 2002, <https://www.rfc-editor.org/info/rfc3219>. January 2002, <https://www.rfc-editor.org/info/rfc3219>.
[RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for [RFC8126] Cotton, M., Leiba, B., and T. Narten, "Guidelines for
Writing an IANA Considerations Section in RFCs", BCP 26, Writing an IANA Considerations Section in RFCs", BCP 26,
RFC 8126, DOI 10.17487/RFC8126, June 2017, RFC 8126, DOI 10.17487/RFC8126, June 2017,
 End of changes. 5 change blocks. 
7 lines changed or deleted 9 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/