Skip to main content

Attribute List Extension for the Service Location Protocol

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 3059.
Author Erik Guttman
Last updated 2013-03-02 (Latest revision 2001-01-04)
RFC stream Legacy stream
Stream Legacy state (None)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3059 (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 3059

        Title:      Attribute List Extension for the Service Location
        Author(s):  E. Guttman
        Status:     Standards Track
        Date:       February 2001
        Pages:      6
        Characters: 11208
        Updates/Obsoletes/SeeAlso:    None        

        I-D Tag:    draft-guttman-svrloc-attrlist-ext-05.txt


The Service Location Protocol, Version 2 (SLPv2) provides a mechanism
for a service to be discovered in a single exchange of messages.  This
exchange of messages does not presently include any of the service's
attributes.  This document specifies a SLPv2 extension which allows
a User Agent (UA) to request a service's attributes be included as an
extension to Service Reply messages.  This will eliminate the need
for multiple round trip messages for a UA to acquire all service

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.