The Internet Assigned Number Authority Application Configuration Access Protocol Vendor Subtrees Registry
RFC 6075, “The Internet Assigned Number Authority Application Configuration Access Protocol Vendor Subtrees Registry”, is a Proposed Standard document published in December 2010 by D. Cridland. It updates RFC 2244. The canonical text is published by the RFC Editor.
Abstract
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]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6075 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6069 Making TCP More Robust to Long Connectivity Disruptions
- RFC 6068 The 'mailto' URI Scheme
- RFC 6082 Deprecating Unicode Language Tag Characters: RFC 2482 is Historic
- RFC 6067 BCP 47 Extension U
- RFC 6065 Using Authentication, Authorization, and Accounting Services to Dynamically Provision View-Based Access Control Model User-to-Group Mappings
- RFC 6063 Dynamic Symmetric Key Provisioning Protocol
- RFC 6062 Traversal Using Relays around NAT Extensions for TCP Allocations
- RFC 6059 Simple Procedures for Detecting Network Attachment in IPv6