RFC 6075 ACAP Vendor Subtrees Registry December 2010 3.2. Tokens (the ABNF production in Section 3.2). Processors to accept other non-ASCII Unicode codepoints in Vendor With IANA, so the new restriction is not believed to introduce anyįinally, note that this document does not change the requirement on required all Vendor Tokens to be registered Registrations violate the new restricted syntax on characters allowed Hyphen, and space to be used in registrations (the Īt the time of publication of this document, no existing Therefore, this document allows only ASCII letters, digits, the Whitespace, and quotes are likely to be confusing and have been Specification restricts the current registrations to the ASCII subsetįurthermore, characters such as ASCII control characters, most Handling and comparison of full Unicode strings therefore, this Publication of, however, concerns have been raised on the Vendor Tokens are able to contain any valid Unicode codepoint,Įncoded as, except the special characters. Period, which need not be registered, thus forming a complete Vendor NOT contain any slash character, period, or the percent and asteriskįollowing this may be names, separated from the Vendor Token by a Is followed by the name of the company or product. Where a formal syntax and the prose are in conflict,Ī Vendor Token is a UTF-8 string that begins with "vendor." and that The formal syntax is to be considered normative and is specified "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in thisĭocument are to be interpreted as described in. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", It replaces Section 7.4 and portions of Section 4, particularly Section 4.3, of. In all but name, allowing easier referencing. Original specification and dissociates it from the original document This document merely updates the registry to reduce ambiguity in the Exposure of vendorĪttributes directly in end-user user interfaces was not an intended As such, engineers and operatorsĪlready have to be familiar with international technical English toĭiagnose textual protocol problems, the restriction to ASCII may helpĪnd is not believed to harm that intended use. Vendor attribute without having to look it up in a registry (although The use of textual rather than numeric identifiers for vendorsīenefits engineers and operators who are diagnosing protocol problemsīy allowing them some possibility of identifying the origin of a Various names to within a specific vendor's scope. , and is proving to be a useful mechanism for namespacing Reused by several specifications, including both and The ACAP Vendor Registry, and this registry has subsequently been The specification includes the specification and creation of RFC 6075 ACAP Vendor Subtrees Registry December 2010ġ. The Trust Legal Provisions and are provided without warranty as Include Simplified BSD License text as described in Section 4.e of Code Components extracted from this document must Please review these documentsĬarefully, as they describe your rights and restrictions with respect This document is subject to BCP 78 and the IETF Trust's Legal Information about the current status of this document, any errata,Īnd how to provide feedback on it may be obtained atĬopyright (c) 2010 IETF Trust and the persons identified as the Internet Standards is available in Section 2 of RFC 5741. Internet Engineering Steering Group (IESG). Received public review and has been approved for publication by the It represents the consensus of the IETF community. This document is a product of the Internet Engineering Task Force This is an Internet Standards Track document. Need for a direct normative reference to ACAP and removing ambiguity. This document updates the description of this registry, removing the Specification included a vendor registry now used in other protocols. The original Application Configuration Access Protocol (ACAP) The Internet Assigned Number Authority (IANA) Application ConfigurationĪccess Protocol (ACAP) Vendor Subtrees Registry Internet Engineering Task Force (IETF) D. RFC 6075: The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry
0 Comments
Leave a Reply. |