RFC 3224 (rfc3224) - Page 3 of 10
Vendor Extensions for Service Location Protocol, Version 2
Alternative Format: Original Text Document
RFC 3224 Vendor Extensions for Service January 2002 2.0 Enterprise Number Enterprise Numbers are used to distinguish different vendors in IETF protocols. Vendor Extensions to SLPv2 SHOULD use these values to avoid any possibility of a name space collision. Each vendor is responsible for ensuring that vendor extensions under their own authority are non-conflicting. IANA maintains a repository of all 'SMI Network Management Private Enterprise Codes,' whose prefix is iso.org.dod.internet.private.enterprise (1.3.6.1.4.1). The number which follows is unique and may be registered by an on-line form [3]. The complete up-to-date list of Enterprise Numbers is maintained by IANA [3]. 3.0 Naming Authorities Naming Authorities are defined by SLPv2 [1] as an agency or group which catalogues Service Types and attributes. A Service Type is a string representing a service which can be discovered by SLPv2. Attributes may be associated with a particular Service Type which is advertised by SLPv2. Service Type strings and service attributes may be registered with IANA by creating a Service Template [4]. The template is included in an internet draft and an email message is sent to srvloc- list@iana.org requesting that the template be included in the Service Template registry. In this case, the naming authority for the service type is IANA. It is also possible for a Vendor to create their own naming authority. In this case, any service type or attribute may be used. SLPv2 allows arbitrary naming authorities to coexist. To use an explicit naming authority, a vendor simply employs their Enterprise Number as a naming authority. For example, for the following (fictitious) Enterprise Number 9999 Acme, Inc. Erik Guttman femur@example.com the Naming Authority string to use would be "9999". A service: URL which used this Naming Authority to advertise a Roadrunner Detector service could look like service:roadrunner-detector.9999://example.com:9341 Guttman Standards Track
