| CARVIEW |
Select Language
HTTP/2 200
date: Mon, 14 Jul 2025 04:40:22 GMT
content-type: text/html; charset=UTF-8
content-encoding: gzip
vary: Accept-Encoding
strict-transport-security: max-age=31536000; includeSubDomains
x-frame-options: SAMEORIGIN
x-xss-protection: 1; mode=block
x-content-type-options: nosniff
cf-cache-status: DYNAMIC
server: cloudflare
cf-ray: 95ee576c6ee5c183-BLR
alt-svc: h3=":443"; ma=86400
Information on RFC 6118 » RFC Editor
Search RFCs
RFC 6118
Update of Legacy IANA Registrations of Enumservices, March 2011
- File formats:
- Status:
- PROPOSED STANDARD
- Updates:
- RFC 3762, RFC 3764, RFC 3953, RFC 4143, RFC 4002, RFC 4238, RFC 4355, RFC 4415, RFC 4769, RFC 4969, RFC 4979, RFC 5028, RFC 5278, RFC 5333
- Authors:
- B. Hoeneisen
A. Mayrhofer - Stream:
- IETF
- Source:
- enum (rai)
Cite this RFC: TXT | XML | BibTeX
DOI: https://doi.org/10.17487/RFC6118
Discuss this RFC: Send questions or comments to the mailing list enum@ietf.org
Other actions: Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 6118
Abstract
This document revises all Enumservices that were IANA registered under the now obsolete specification of the Enumservice registry defined in RFC 3761. [STANDARDS-TRACK]
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.
IAB • IANA • IETF • IRTF • ISE • ISOC • IETF Trust
Reports • Privacy Statement • Site Map • Contact Us