Internet DRAFT - draft-ietf-svrloc-ipv6
draft-ietf-svrloc-ipv6
A new Request for Comments is now available in online RFC libraries.
RFC 3111
Title: Service Location Protocol Modifications for IPv6
Author(s): E. Guttman
Status: Standards Track
Date: May 2001
Mailbox: Erik.Guttman@germany.sun.com
Pages: 13
Characters: 25543
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-svrloc-ipv6-12.txt
URL: ftp://ftp.rfc-editor.org/in-notes/rfc3111.txt
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.
This document is a product of the Service Location Protocol
Working Group of the IETF.
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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
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.