RFC 3224: Vendor Extensions for Service Location Protocol, Version 2
In plain English — editorial summary, not part of the RFC
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." [STANDARDS-TRACK]
Document record
- Document ID
- RFC3224
- Published
- January 2002
- Authors
- E. Guttman
- Status
- PROPOSED STANDARD
- Stream
- Legacy
- Area
- —
- Pages
- 10
- Also known as
- —
- Updates:
- RFC 2608
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3082Notification and Subscription for SLPCurrent
March 2001
- RFC 3111Service Location Protocol Modifications for IPv6Current
May 2001
- RFC 3105Finding an RSIP Server with SLPCurrent
October 2001
- RFC 3049TN3270E Service Location and Session BalancingCurrent
January 2001
- RFC 3421Select and Sort Extensions for the Service Location Protocol (SLP)Current
November 2002
- RFC 3822Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)Updated
July 2004
- RFC 3832Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRVUpdated
July 2004
- RFC 2610DHCP Options for Service Location ProtocolCurrent
June 1999
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?