Skip to main content

Vendor Extensions for Service Location Protocol, Version 2

The information below is for an old version of the document that is already published as an RFC.
Document Type
This is an older version of an Internet-Draft that was ultimately published as RFC 3224.
Author Erik Guttman
Last updated 2013-03-02 (Latest revision 2001-10-08)
RFC stream Legacy stream
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3224 (Proposed Standard)
Telechat date (None)
Responsible AD (None)
Send notices to (None)
A new Request for Comments is now available in online RFC libraries.

        RFC 3224

        Title:      Vendor Extensions for Service Location Protocol,
                    Version 2
        Author(s):  E. Guttman
        Status:     Standards Track
        Date:       January 2002
        Pages:      10
        Characters: 19618
        Updates:    2608

        I-D Tag:    draft-guttman-svrloc-vendor-ext-07.txt


This document specifies how the features of the Service Location
Protocol, Version 2 allow for vendor extensibility safely, with
no possibility of collisions.  The specification introduces a new
SLPv2 extension:  The Vendor Opaque Extension.  While proprietary
protocol extensions are not encouraged by IETF standards, it is
important that they not hinder interoperability of compliant
implementations when they are undertaken.  This document udpates RFC
2608, "The Service Location Protocol."

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo 
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.