rfc-8602

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

J. Arkko, T. Hardie

date2019-07 streamIETF wgnon working group statusPROPOSED STANDARD pages3 canonicalhttps://www.rfc-editor.org/rfc/rfc8602 doi10.17487/RFC8602

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.

updates

rfc-3219 — Telephony Routing over IP (TRIP)

Extracted elements (5)

design-rationale §1

Postal addresses are no longer required in TRIP registry contact information because no use for the addresses was identified, and omitting this information provides a privacy benefit.

privacy, registry, realtime

privacy-consideration §1

Removing the requirement to collect postal addresses in TRIP registry entries provides a privacy benefit. Previously collected postal addresses have been removed from the registries retroactively.

privacy, registry

registry §2

The TRIP Attributes registry (RFC 3219, Section 13.2) is updated to no longer require postal address information in registration entries. IANA has also removed previously collected postal addresses from this registry.

registry, realtime, voip

registry §2

The TRIP IP Telephony Administrative Domain (ITAD) Numbers registry (RFC 3219, Section 13.5) is updated to no longer require postal address information in registration entries. IANA has also removed previously collected postal addresses from this registry.

registry, realtime, voip

security-consideration §3

No security impacts have been identified from removing the postal address collection requirement from TRIP registry entries.

security, registry