RFC 8602

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

📅 published July 2019, from ietf

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

Okay bestie, let's get into this one. 🦋 It's an RFC from July 2019, written by J. Arkko (Ericsson) and T. Hardie. It's a Standards Track doc, and it updates RFC 3219 (the TRIP spec). It doesn't obsolete anything. The ISSN is 2070-1721. 📄✨

Abstract ✨

Okay so this memo updates the IANA registry rules for the Telephony Routing over IP (TRIP) protocol. 🌸 The big change? It no longer requires postal addresses in contact information. 🙈

This memo updates RFC 3219. 💜

Status of This Memo 🧚

This is an Internet Standards Track document. 🔥

It's a product of the Internet Engineering Task Force (IETF), so it represents the consensus of the IETF community. 👑 It got public review and was approved for publication by the Internet Engineering Steering Group (IESG). If you want more on Internet Standards, check out Section 2 of RFC 7841. 💖

Current status, errata, and feedback info live at https://www.rfc-editor.org/info/rfc8602. 🫶

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) as in effect on the date of publication. Please read these carefully, because they spell out your rights and restrictions. 🎀 Code Components pulled out of this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License. 💅

1. Introduction 🦋

Okay so this memo updates the IANA registry rules for TRIP, and it stops requiring postal addresses in contact info. 🙈 Nobody has identified a use for the addresses, and leaving them out is a privacy win. 🔒💖

This memo updates RFC 3219. 💜

2. IANA Considerations 🌸

This memo updates the registration rules [RFC8126] for two things from RFC 3219 🫶:

  • TRIP Attributes ([RFC3219], Section 13.2)
  • TRIP IP Telephony Administrative Domain (ITAD) Numbers ([RFC3219], Section 13.5)

Here's the deal: the IETF no longer requires IANA to collect postal address information when adding TRIP registry entries. 🙅‍♀️ Plus, IANA has removed the postal addresses it had already collected from the registries. 🧹✨

3. Security Considerations 🔐

No security impacts of this change have been identified. 💅 Periodt.

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 want to give a shoutout to Michelle Cotton, Alissa Cooper, and Jonathan Rosenberg for the interesting discussions in this problem space. 💖 They also thank Carlos Pignataro, Russ Housley, Abdussalam Baryun, and Paul Wouters for their feedback. 🌈

Authors' Addresses 💌

Jari Arkko Ericsson Kauniainen 02700 Finland

Email: jari.arkko@piuha.net

Ted Hardie

Email: ted.ietf@gmail.com

📦 where this page comes from