RFC 5067: Infrastructure ENUM Requirements
In plain English — editorial summary, not part of the RFC
This document provides requirements for "infrastructure" or "carrier" ENUM (E.164 Number Mapping), defined as the use of RFC 3761 technology to facilitate interconnection of networks for E.164 number addressed services, in particular but not restricted to VoIP (Voice over IP.) This memo provides information for the Internet community.
Document record
- Document ID
- RFC5067
- Published
- November 2007
- Authors
- S. Lind; P. Pfautz
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rai
- Pages
- 7
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5076ENUM Validation Information Mapping for the Extensible Provisioning ProtocolCurrent
December 2007
- RFC 5057Multiple Dialog Usages in the Session Initiation ProtocolCurrent
November 2007
- RFC 5079Rejecting Anonymous Requests in the Session Initiation Protocol (SIP)Current
December 2007
- RFC 5039The Session Initiation Protocol (SIP) and SpamCurrent
January 2008
- RFC 5104Codec Control Messages in the RTP Audio-Visual Profile with Feedback (AVPF)Updated
February 2008
- RFC 5105ENUM Validation Token Format DefinitionCurrent
December 2007
- RFC 5028A Telephone Number Mapping (ENUM) Service Registration for Instant Messaging (IM) ServicesUpdated
October 2007
- RFC 5025Presence Authorization RulesCurrent
December 2007
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?