RFC 3953: Telephone Number Mapping (ENUM) Service Registration for Presence Services
In plain English — editorial summary, not part of the RFC
This document registers a Telephone Number Mapping (ENUM) service for presence. Specifically, this document focuses on provisioning pres URIs in ENUM. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3953
- Published
- January 2005
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 7
- 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 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 4002IANA Registration for Enumservice 'web' and 'ft'Updated
February 2005
- RFC 3762Telephone Number Mapping (ENUM) Service Registration for H.323Updated
April 2004
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
- 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 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
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?