RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry
In plain English — editorial summary, not part of the RFC
The original Application Configuration Access Protocol (ACAP) specification included a vendor registry now used in other protocols. This document updates the description of this registry, removing the need for a direct normative reference to ACAP and removing ambiguity. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6075
- Published
- December 2010
- Authors
- D. Cridland
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 2244
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6249Metalink/HTTP: Mirrors and HashesCurrent
June 2011
- RFC 5854The Metalink Download Description FormatCurrent
June 2010
- RFC 5791RFC 2731 ("Encoding Dublin Core Metadata in HTML") Is ObsoleteCurrent
February 2010
- RFC 5464The IMAP METADATA ExtensionCurrent
February 2009
- RFC 5328A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB)Updated
September 2008
- RFC 5174A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)Current
May 2008
- RFC 4287The Atom Syndication FormatUpdated
December 2005
- RFC 4195A Uniform Resource Name (URN) Namespace for the TV-Anytime ForumCurrent
October 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?