RFC 3059: Attribute List Extension for the Service Location Protocol
In plain English — editorial summary, not part of the RFC
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 information. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3059
- Published
- February 2001
- Authors
- E. Guttman
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 6
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 3082Notification and Subscription for SLPCurrent
March 2001
- RFC 3224Vendor Extensions for Service Location Protocol, Version 2Current
January 2002
- RFC 2193IMAP4 Mailbox ReferralsCurrent
September 1997
- RFC 3049TN3270E Service Location and Session BalancingCurrent
January 2001
- RFC 3080The Blocks Extensible Exchange Protocol CoreCurrent
March 2001
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?