Service Location Protocol Modifications for IPv6
RFC 3111
|
| Document |
Type |
|
RFC - Proposed Standard
(May 2001; No errata)
|
|
Last updated |
|
2013-03-02
|
|
Stream |
|
IETF
|
|
Formats |
|
plain text
html
pdf
htmlized
bibtex
|
| Stream |
WG state
|
|
(None)
|
|
Document shepherd |
|
No shepherd assigned
|
| IESG |
IESG state |
|
RFC 3111 (Proposed Standard)
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group E. Guttman
Request for Comments: 3111 Sun Microsystems
Category: Standards Track May 2001
Service Location Protocol Modifications for IPv6
Status of this Memo
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.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
Abstract
This document defines the Service Location Protocol Version 2's
(SLPv2) use over IPv6 networks. Since this protocol relies on UDP
and TCP, the changes to support its use over IPv6 are minor.
This document does not describe how to use SLPv1 over IPv6 networks.
There is at the time of this publication no implementation or
deployment of SLPv1 over IPv6. It is RECOMMENDED that SLPv2 be used
in general, and specifically on networks which support IPv6.
Guttman Standards Track [Page 1]
RFC 3111 Service Location Protocol Modifications for IPv6 May 2001
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . 2
2. Eliminating support for broadcast SLP requests . . . . . 3
3. Address Specification for IPv6 Addresses in URLs . . . . 3
4. SLP multicast behavior over IPv6 . . . . . . . . . . . . 4
4.1. SLPv2 Multicast Group-IDs for IPv6 . . . . . . . . . . 4
4.2. SLPv2 Scoping Rules for IPv6 . . . . . . . . . . . . . 5
4.2.1 Joining SLPv2 Multicast Groups . . . . . . . . . . . . 5
4.2.2 Sending SLPv2 Multicast Messages . . . . . . . . . . . 6
4.2.3 Rules for Message Processing . . . . . . . . . . . . . 6
4.2.4 SLPv2 Agents with multiple interfaces . . . . . . . . 7
4.2.4.1 General Rules . . . . . . . . . . . . . . . . . . . . 7
4.2.4.2 Multihomed UA . . . . . . . . . . . . . . . . . . . . 8
4.2.4.3 Multihomed SA . . . . . . . . . . . . . . . . . . . . 8
4.2.4.4 Multihomed DA . . . . . . . . . . . . . . . . . . . . 9
5. IANA Considerations . . . . . . . . . . . . . . . . . . . 10
6. Security Considerations . . . . . . . . . . . . . . . . . 10
Acknowledgments . . . . . . . . . . . . . . . . . . . . . 10
References . . . . . . . . . . . . . . . . . . . . . . . 11
Author's Address . . . . . . . . . . . . . . . . . . . . 12
Full Copyright Statement . . . . . . . . . . . . . . . . 13
1. Introduction
The Service Location Protocol (SLP) provides a scalable framework for
the discovery and selection of network services. Using this
protocol, computers using IP based networks no longer need so much
static configuration of network services for network based
applications. This is especially important as computers become more
portable, and users less tolerant of or less able to fulfill the
demands of network administration.
The following are changes required to have the Service Location
Protocol work over IPv6. These changes include:
- Eliminating support for broadcast SLP requests
- Address Specification for IPv6 Addresses in URLs
- Use of IPv6 multicast addresses and IPv6 address scopes
- Restricted Propagation of Service Advertisements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [4].
Guttman Standards Track [Page 2]
RFC 3111 Service Location Protocol Modifications for IPv6 May 2001
2. Eliminating support for broadcast SLP requests
Service Location over IPv4 allows broadcasts to send Service Location
request messages. IPv6 makes use of link-local multicast in place of
broadcast. Broadcast-only configuration for SLP is not supported
under IPv6. If a User Agent wishes to make a request to discover
Directory Agents or make a request of multiple Service Agents, the
User Agent must multicast the request to the appropriate multicast
address.
This change modifies the requirements described in Section 6.1 (Use
of Ports, UDP and Multicast) of the Service Location Protocol [2].
3. Address Specification for IPv6 Addresses in URLs
Whenever possible the DNS [5] name of the service should be used
rather than the numerical representation described in this section.
Service Location allows the use of the protocol without the benefit
of DNS. This is relevant when a group of systems is connected to
build a network without any previous configuration of servers to
Show full document text