Browse Prior Art Database

The Internet Assigned Number Authority (IANA) Application Configuration Access Protocol (ACAP) Vendor Subtrees Registry (RFC6075)

IP.com Disclosure Number: IPCOM000202356D
Original Publication Date: 2010-Dec-01
Included in the Prior Art Database: 2010-Dec-14
Document File: 14 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

D. Cridland: AUTHOR

Abstract

The [ACAP] specification includes the specification and creation of the ACAP Vendor Registry, and this registry has subsequently been reused by several specifications, including both [ANNOTATE] and [METADATA], and is proving to be a useful mechanism for namespacing various names to within a specific vendor's scope.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 21% of the total text.

Internet Engineering Task Force (IETF)                       D. Cridland Request for Comments: 6075                                 Isode Limited Updates: 2244                                              December 2010 Category: Standards Track ISSN: 2070-1721

 The Internet Assigned Number Authority (IANA) Application Configuration             Access Protocol (ACAP) Vendor Subtrees Registry

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.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6075.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the    document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal    Provisions Relating to IETF Documents    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Cridland                     Standards Track                    [Page 1]
 RFC 6075              ACAP Vendor Subtrees Registry        December 2010

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2

   2.  Conventions Used in This Document . . . . . . . . . . . . . . . 2

   3.  The Vendor Subtree Registry . . . . . . . . . . . . . . . . . . 3

     3.1.  Internationalization  . . . . . . . . . . . . . . . . . . . 3

     3.2.  Formal Syntax . . . . . . . . . . . . . . . . . . . . . . . 4

     3.3.  Examples  . . . . . . . . . . . . . . . . . . . . . . . . . 4

     3.4.  Changes from RFC 2244 . . . . . . . . . . . . . . . . . . . 5

   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5

    ...