ACAP NUMBERS Registration Procedures ACAP's usefulness comes from providing a structured storage model for all sorts of configuration data. However, for its potential to be achieved, it is important that the Internet community strives for the following goals: (1) Standardization. It is very important to standardize dataset classes. The authors hope that ACAP achieves the success that SNMP has seen with the definition of numerous standards track MIBs. (2) Community Review. In the absence of standardization, it is important to get community review on a proposal to improve its engineering quality. Community review is strongly recommended prior to registration. The ACAP implementors mailing list should be used for this purpose. (3) Registration. Registration serves a two-fold purpose. First it prevents use of the same name for different purposes, and second it provides a one-stop list which can be used to locate existing extensions or dataset classes to prevent duplicate work. The following registration templates may be used to register ACAP protocol elements with the Internet Assigned Numbers Authority (IANA). 7.1. ACAP Capabilities New ACAP capabilities MUST be registered prior to use. Careful consideration should be made before extending the protocol, as it can lead to complexity or interoperability problems. Review of proposals on the acap implementors mailing list is strongly encouraged prior toregistration. To: iana@iana.org Subject: Registration of ACAP capability Capability name: Capability keyword: Capability arguments: Published Specification(s): (Optional, but strongly encouraged) Person and email address to contact for further information: 7.2. ACAP Response Codes ACAP response codes are registered on a first come, first served basis. Review of proposals on the acap implementors mailing list is strongly encouraged prior to registration. To: iana@iana.org Subject: Registration of ACAP response code Response Code: Arguments (use ABNF to specify syntax): Purpose: Published Specification(s): (Optional, but strongly encouraged) Person and email address to contact for further information: 7.3. Dataset Classes A dataset class provides a core set of attributes for use in a specified hierarchy. It may also define rules for the dataset hierarchy underneath that class. Dataset class specifications must be standards track or IESG approved experimental RFCs. To: iana@iana.org Subject: Registration of ACAP dataset class Dataset class name/attribute prefix: Purpose: Published Specification(s): (Standards track or IESG approved experimental RFC) Person and email address to contact for further information: 7.4. Vendor Subtree Vendors may reserve a portion of the ACAP namespace for private use. Dataset class names beginning with "vendor.." are reserved for use by that company or product. In addition, all attribute names beginning with "vendor.." are reserved for use by that company or product once registered. Registration is on a first come, first served basis. Whenever possible, private attributes and dataset classes should be avoided in favor of improving interoperable dataset class definitions. To: iana@iana.org Subject: Registration of ACAP vendor subtree Private Prefix: vendor.. Person and email address to contact for further information: (company names and addresses should be included when appropriate) REGISTRATIONS -------------------------------------------------------------------- ACAP Capabilities Name Reference ---- --------- STARTTLS [RFC2595] -------------------------------------------------------------------- ACAP Response Codes Name Reference ---- --------- -------------------------------------------------------------------- Dataset Classes Name Reference ---- --------- -------------------------------------------------------------------- Vendor Subtrees Name Reference ---- --------- vendor.Qualcomm/Eudora [Gellens] vendor.Eudora [Gellens] vendor.ruslan [Shibayev] vendor.Cyrusoft/Mulberry [Daboo] vendor.Cyrusoft/SilkyMail [Daboo] REFERENCES [RFC2595] Newman, C., "Using TLS with IMAP, POP3 and ACAP", RFC 2595, Innosoft, June 1999. PEOPLE [Daboo] Cyrus Daboo , June 2000. [Gellens] Randall Gellens , June 1998. [Shibayev] Dmitry Shibayev , April 1999. []