TRIP IANA Postal Rule: Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses
IANA no longer collects postal addresses for TRIP registry entries, for a privacy benefit.
Arkko, J. and T. Hardie, "Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses", RFC 8602, DOI 10.17487/RFC8602, July 2019, <https://www.rfc-editor.org/info/rfc8602>.
@misc{rfc8602,
series = {Request for Comments},
number = 8602,
howpublished = {RFC 8602},
publisher = {RFC Editor},
doi = {10.17487/RFC8602},
url = {https://www.rfc-editor.org/info/rfc8602},
author = {J. Arkko and T. Hardie},
title = {{Update to the Telephony Routing over IP (TRIP) IANA Registry Rules regarding Postal Addresses}},
pagetotal = 3,
year = 2019,
month = jul,
} RFC text
Contents
Internet Engineering Task Force (IETF) J. Arkko
Request for Comments: 8602 Ericsson
Updates: 3219 T. Hardie
Category: Standards Track July 2019
ISSN: 2070-1721
Update to the Telephony Routing over IP (TRIP) IANA Registry Rules
regarding Postal Addresses
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 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 Section 2 of RFC 7841.
Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
https://www.rfc-editor.org/info/rfc8602.
Copyright Notice
Copyright (c) 2019 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
(https://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
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. Normative References . . . . . . . . . . . . . . . . . . . . 2
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 3
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 IP Telephony
Administrative Domain (ITAD) Numbers ([RFC3219], Section 13.5) 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.
3. Security Considerations
No security impacts of this change have been identified.
4. 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>.
[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>.
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: jari.arkko@piuha.net
Ted Hardie
Email: ted.ietf@gmail.com
AI ELI5
On this page
§1Introduction
RFC 8602 updates the IANA registry rules for the Telephony Routing over IP (TRIP) protocol. It stops requiring that postal addresses be included in contact information.
The reason given is short: no use for the addresses is identified, and leaving them out provides a privacy benefit. The memo updates RFC 3219.
If nobody uses the home addresses, it is safer not to keep them.
§2What Changes in the Registries
The update applies to the registration rules for TRIP Attributes (RFC 3219, Section 13.2) and TRIP IP Telephony Administrative Domain (ITAD) Numbers (Section 13.5), following RFC 8126.
The IETF no longer requires IANA to collect postal address information when adding TRIP registry entries. IANA has also removed previously collected postal addresses from the registries.
The two lists stop asking for addresses, and the addresses already on them were wiped.
§3Security Considerations
No security impacts of this change have been identified.
The only stated benefit is for privacy, since less personal contact data is kept in the registries.
Nothing gets riskier, and people's addresses are better protected.