RFC 3764: enumservice registration for Session Initiation Protocol (SIP) Addresses-of-Record
In plain English — editorial summary, not part of the RFC
This document registers an Electronic Number (ENUM) service for the Session Initiation Protocol (SIP), pursuant to the guidelines in RFC 3761. Specifically, this document focuses on provisioning SIP addresses-of-record in ENUM. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3764
- Published
- April 2004
- Authors
- J. Peterson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 8
- 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 3725Best Current Practices for Third Party Call Control (3pcc) in the Session Initiation Protocol (SIP)Current
April 2004
- RFC 3840Indicating User Agent Capabilities in the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3841Caller Preferences for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3842A Message Summary and Message Waiting Indication Event Package for the Session Initiation Protocol (SIP)Current
August 2004
- RFC 3680A Session Initiation Protocol (SIP) Event Package for RegistrationsUpdated
March 2004
- RFC 3853S/MIME Advanced Encryption Standard (AES) Requirement for the Session Initiation Protocol (SIP)Current
July 2004
- RFC 3891The Session Initiation Protocol (SIP) "Replaces" HeaderCurrent
September 2004
- RFC 3892The Session Initiation Protocol (SIP) Referred-By MechanismUpdated
September 2004
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?