RFC 4769: IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information
In plain English — editorial summary, not part of the RFC
This document registers the Enumservice type "pstn" and subtype "tel" using the URI scheme 'tel', as well as the subtype "sip" using the URI scheme 'sip' as per the IANA registration process defined in the ENUM specification, RFC 3761. This Enumservice is used to facilitate the routing of telephone calls in those countries where number portability exists. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4769
- Published
- November 2006
- Authors
- J. Livingood; R. Shockey
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 13
- Also known as
- —
- Updated by:
- RFC 6118
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5278IANA Registration of Enumservices for Voice and Video MessagingUpdated
July 2008
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 4825The Extensible Markup Language (XML) Configuration Access Protocol (XCAP)Current
May 2007
- RFC 4826Extensible Markup Language (XML) Formats for Representing Resource ListsCurrent
May 2007
- RFC 4575A Session Initiation Protocol (SIP) Event Package for Conference StateCurrent
August 2006
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
- RFC 4479A Data Model for PresenceCurrent
July 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?