RFC 6118: Update of Legacy IANA Registrations of Enumservices
In plain English — editorial summary, not part of the RFC
This document revises all Enumservices that were IANA registered under the now obsolete specification of the Enumservice registry defined in RFC 3761. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6118
- Published
- March 2011
- Authors
- B. Hoeneisen; A. Mayrhofer
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- rai
- Pages
- 68
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6117IANA Registration of Enumservices: Guide, Template, and IANA ConsiderationsCurrent
March 2011
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 2916E.164 number and DNSObsoleted
September 2000
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 5864DNS SRV Resource Records for AFSUpdated
April 2010
- RFC 6594Use of the SHA-256 Algorithm with RSA, Digital Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) in SSHFP Resource RecordsCurrent
April 2012
- RFC 6891Extension Mechanisms for DNS (EDNS(0))Current
April 2013
- RFC 5205Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionsObsoleted
April 2008
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?