RFC 3105 (rfc3105) - Page 1 of 11
Finding an RSIP Server with SLP
Alternative Format: Original Text Document
Network Working Group J. Kempf
Request for Comments: 3105 NTT DoCoMo USA Labs
Category: Experimental G. Montenegro
Sun Microsystems
October 2001
Finding an RSIP Server with SLP
Status of this Memo
This memo defines an Experimental Protocol for the Internet
community. It does not specify an Internet standard of any kind.
Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved.
IESG Note
The IESG notes that the set of documents describing the RSIP
technology imply significant host and gateway changes for a complete
implementation. In addition, the floating of port numbers can cause
problems for some applications, preventing an RSIP-enabled host from
interoperating transparently with existing applications in some cases
(e.g., IPsec). Finally, there may be significant operational
complexities associated with using RSIP. Some of these and other
complications are outlined in section 6 of the RFC 3102, as well as
in the Appendices of RFC 3104. Accordingly, the costs and benefits
of using RSIP should be carefully weighed against other means of
relieving address shortage.
Abstract
This document contains an SLP service type template that describes
the advertisements made by RSIP servers for their services. Service
Location Protocol (SLP) is an IETF standards track protocol
specifically designed to allow clients to find servers offering
particular services. Since RSIP (Realm Specific IP) clients require
a mechanism to discover RSIP servers, SLP is a natural match for a
solution. The service type template is the basis for an Internet
Assigned Numbers Authority (IANA) standard definition of the
advertisements offered by RSIP servers, an important step toward
interoperability.
Kempf & Montenegro Experimental