Network Working Group J. Kempf
Request for Comments: 3105 NTT DoCoMo USA Labs
Category: Experimental G. Montenegro
Sun Microsystems
October 2001
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
使用SLP查找RSIP服务器
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.
版权所有（C）互联网协会（2001年）。版权所有。
IESG Note
IESG注释
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.
IESG指出，描述RSIP技术的一组文档意味着主机和网关的重大更改，以实现完整的实现。此外，端口号的浮动可能会导致某些应用程序出现问题，从而在某些情况下（例如，IPsec）阻止启用RSIP的主机与现有应用程序进行透明的互操作。最后，使用RSIP可能会带来巨大的操作复杂性。RFC 3102第6节以及RFC 3104附录概述了其中一些并发症和其他并发症。因此，使用RSIP的成本和收益应与其他缓解地址短缺的方法仔细权衡。
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.
本文档包含一个SLP服务类型模板，该模板描述RSIP服务器为其服务所做的广告。服务位置协议（SLP）是一种IETF标准跟踪协议，专门设计用于允许客户端查找提供特定服务的服务器。由于RSIP（领域特定IP）客户端需要一种机制来发现RSIP服务器，因此SLP是解决方案的自然匹配。服务类型模板是RSIP服务器提供的广告的Internet Assigned Numbers Authority（IANA）标准定义的基础，这是实现互操作性的重要一步。
Table of Contents
目录
1. Introduction ............................................... 2
2. Notation Conventions ....................................... 2
3. Terminology ................................................ 2
4. Using SLP for RSIP Service Discovery ....................... 3
5. Using Scopes for Server Provisioning ....................... 4
6. Load Balancing ............................................. 6
7. The RSIP Service Type Template ............................. 7
8. Security Considerations .................................... 9
9. Summary .................................................... 9
References ..................................................... 9
Authors' Addresses ............................................. 10
Full Copyright Statement ....................................... 11
1. Introduction ............................................... 2
2. Notation Conventions ....................................... 2
3. Terminology ................................................ 2
4. Using SLP for RSIP Service Discovery ....................... 3
5. Using Scopes for Server Provisioning ....................... 4
6. Load Balancing ............................................. 6
7. The RSIP Service Type Template ............................. 7
8. Security Considerations .................................... 9
9. Summary .................................................... 9
References ..................................................... 9
Authors' Addresses ............................................. 10
Full Copyright Statement ....................................... 11
Realm Specific IP (RSIP) [7] enables an RSIP client in one realm to borrow addresses and other resources from another realm. It does so by engaging in an RSIP protocol [1] exchange with an RSIP server. The RSIP protocol requires the RSIP server to have a permanent presence on both realms.
领域特定IP（RSIP）[7]允许一个领域中的RSIP客户端从另一个领域借用地址和其他资源。它通过与RSIP服务器进行RSIP协议[1]交换来实现这一点。RSIP协议要求RSIP服务器在两个领域都有永久存在。
There are a variety of traditional ways an RSIP client could go about locating the appropriate RSIP server. However, Service Location Protocol (SLP) [2][11] is an IETF standards track protocol specifically designed to facilitate location of services and their servers by clients. SLP provides a number of features that simplify locating RSIP servers. In this document, we describe how RSIP clients can use SLP to discover RSIP servers.
RSIP客户机可以通过多种传统方式查找适当的RSIP服务器。然而，服务定位协议（SLP）[2][11]是一种IETF标准跟踪协议，专门设计用于方便客户端定位服务及其服务器。SLP提供了许多简化RSIP服务器定位的功能。在本文档中，我们描述了RSIP客户端如何使用SLP发现RSIP服务器。
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].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[4]中所述进行解释。
We reproduce here some SLP terminology from [2] for readers unfamiliar with SLP.
这里我们为不熟悉SLP的读者重现了[2]中的一些SLP术语。
User Agent (UA)
用户代理（UA）
A process working on the user's behalf to establish contact with some service. The UA retrieves service information from the Service Agents or Directory Agents.
代表用户与某些服务建立联系的过程。UA从服务代理或目录代理检索服务信息。
Service Agent (SA)
服务代理（SA）
A process working on behalf of one or more services to advertise the services and their capabilities.
代表一个或多个服务宣传服务及其功能的过程。
Directory Agent (DA)
目录代理（DA）
A process which collects service advertisements. There can only be one DA present per given host.
收集服务广告的过程。每个给定主机只能有一个DA。
Scope
范围
A set of services, typically making up a logical administrative group.
一组服务，通常构成一个逻辑管理组。
Service Advertisement
服务广告
A URL, attributes, and a lifetime (indicating how long the advertisement is valid), providing service access information and capabilities description for a particular service.
URL、属性和生存期（指示广告有效的时间），提供特定服务的服务访问信息和功能描述。
SLP provides the framework in which RSIP clients and servers make contact. Here is a description of how an RSIP server and client find each other using SLP:
SLP提供了RSIP客户端和服务器进行联系的框架。以下是RSIP服务器和客户端如何使用SLP找到彼此的描述：
1. The RSIP server implements a SLP SA while the RSIP client implements an SLP UA.
1. RSIP服务器实现SLP SA，而RSIP客户端实现SLP UA。
2. The RSIP SA constructs a service advertisement consisting of a service URL, attributes and a lifetime. The URL has service type "service:rsip", and attributes defined according to the template in Section 7.
2. RSIP SA构造一个服务广告，由服务URL、属性和生存期组成。URL具有服务类型“service:rsip”和根据第7节中的模板定义的属性。
3. If an SLP DA is found, the SA contacts the DA and registers the advertisement. If no DA is found, the SA maintains the advertisement itself, answering multicast UA queries directly.
3. 如果找到SLP DA，SA将联系DA并注册广告。如果未找到DA，SA将维护播发本身，直接回答多播UA查询。
4. When the RSIP client requires contact information for an RSIP server, the UA either contacts the DA using unicast or the SA using multicast. The UA includes a query based on the attributes to indicate the characteristics of the server it requires.
4. 当RSIP客户端需要RSIP服务器的联系信息时，UA或者使用单播与DA联系，或者使用多播与SA联系。UA包括一个基于属性的查询，以指示其所需服务器的特征。
5. Once the UA has the host name or address of the RSIP server as well as the port number, it can begin negotiation using the RSIP protocol.
5. 一旦UA获得RSIP服务器的主机名或地址以及端口号，它就可以使用RSIP协议开始协商。
This procedure is exactly the same for any client/server pair implementing SLP and is not specific to RSIP.
此过程对于实现SLP的任何客户机/服务器对都完全相同，并且不特定于RSIP。
Many protocols use a variety of traditional methods for service discovery. These methods include static configuration, purpose-build protocols for discovery, special features in the protocol itself, DNS SRV RRs [5], or DHCP [6]. SLP provides a number of advantages over these traditional methods:
许多协议使用各种传统方法进行服务发现。这些方法包括静态配置、用于发现的专用构建协议、协议本身的特殊功能、DNS SRV RRs[5]或DHCP[6]。与这些传统方法相比，SLP具有许多优势：
1. Discovery of services using SLP is dynamic, whereas many of the traditional methods only allow static or weakly dynamic (i.e., difficult to update) discovery. Clients only discover services that are actually active with SLP. Furthermore, if subsequent to initial discovery a server goes down, the client can reissue an SLP query and obtain a new server. On the server side, no databases must be updated to provide dynamic discovery, the servers advertise themselves.
1. 使用SLP发现服务是动态的，而许多传统方法只允许静态或弱动态（即难以更新）发现。客户端仅发现使用SLP实际处于活动状态的服务。此外，如果在初始发现之后服务器停机，客户端可以重新发出SLP查询并获得新服务器。在服务器端，不必更新任何数据库来提供动态发现，服务器会自行发布。
2. SLP requires no third party configuration. Only the server offering the service and the client seeking it are required to know the details for the particular service type.
2. SLP不需要第三方配置。只有提供服务的服务器和寻求服务的客户端才需要知道特定服务类型的详细信息。
3. SLP allows clients to specify the attributes describing the desired server. A client discovers servers that meet a set of specific requirements. This reduces the amount of network traffic involved in selecting a server when many possible choices are available.
3. SLP允许客户端指定描述所需服务器的属性。客户机发现满足一组特定需求的服务器。当有许多可能的选择可用时，这将减少选择服务器所涉及的网络流量。
4. SLP contains a number of scaling mechanisms (DAs, scopes, multicast convergence algorithm), that facilitate deployment in large enterprise networks as well as in smaller networks.
4. SLP包含许多扩展机制（DAs、作用域、多播聚合算法），可促进在大型企业网络和小型网络中的部署。
One particular design feature of SLP that is useful for RSIP is scopes. Scopes in SLP are a mechanism for provisioning access to particular service advertisements. An administrator assigns UAs and SAs to particular scopes to assure that UAs only find SAs in those scopes. Scopes are not an access control mechanism for the service itself, however. UAs from outside the scope can still access services in a particular scope (unless the service itself provides for access control), they just won't be able to find the services using SLP.
SLP对RSIP有用的一个特殊设计特性是作用域。SLP中的作用域是一种机制，用于提供对特定服务广告的访问。管理员将UAs和SAs分配给特定的作用域，以确保UAs只在这些作用域中找到SAs。但是，作用域不是服务本身的访问控制机制。范围外的UAs仍然可以访问特定范围内的服务（除非服务本身提供访问控制），他们只是无法使用SLP找到服务。
Scopes are useful for RSIP service advertisement provisioning because they allow a system administrator to tie particular RSIP clients to specific RSIP servers. For example, consider the network architecture described in Section 4.2.1 of [7]. RSIP clients are
作用域对于RSIP服务广告配置非常有用，因为它们允许系统管理员将特定的RSIP客户端绑定到特定的RSIP服务器。例如，考虑在[4.2]第4.2.1节中描述的网络体系结构。RSIP客户是
recommended to find "the nearest" RSIP server, but exactly how that should be arranged is left unspecified. SLP provides a way for system administrators to precisely specify which realm an RSIP client resides in, by tying the realm to an SLP scope. The diagram from Section 14.1 is reproduced here, with SLP scopes included to illustrate how clients could be directed to the right RSIP servers.
建议查找“最近的”RSIP服务器，但具体如何安排还未确定。SLP通过将领域绑定到SLP作用域，为系统管理员提供了一种精确指定RSIP客户端驻留在哪个领域的方法。这里复制了第14.1节中的图表，其中包括SLP范围，以说明如何将客户端定向到正确的RSIP服务器。
+-----------+
| |
| RSIP |
| server +---- 10.0.0.0/8
| B | SLP Scope: B
| |
+-----+-----+
|
| 10.0.1.0/24
+-----------+ | (149.112.240.0/25)
| | |
149.112.240.0/24| RSIP +--+
----------------+ server | SLP Scope: A
| A +--+
| | |
+-----------+ | 10.0.2.0/24
| (149.112.240.128/25)
|
+-----+-----+
| |
| RSIP |
| server +---- 10.0.0.0/8
| C | SLP Scope: C
| |
+-----------+
+-----------+
| |
| RSIP |
| server +---- 10.0.0.0/8
| B | SLP Scope: B
| |
+-----+-----+
|
| 10.0.1.0/24
+-----------+ | (149.112.240.0/25)
| | |
149.112.240.0/24| RSIP +--+
----------------+ server | SLP Scope: A
| A +--+
| | |
+-----------+ | 10.0.2.0/24
| (149.112.240.128/25)
|
+-----+-----+
| |
| RSIP |
| server +---- 10.0.0.0/8
| C | SLP Scope: C
| |
+-----------+
Clients on the upper 10.0.0.0/8 network are configured to use SLP scope B, while clients on the lower 10.0.0.0/8 network are configured to use SLP scope C. RSIP servers B and C (as clients of server A) use SLP to locate RSIP server A, as do other RSIP clients on the 10.0.1.0/24 and 10.0.2.0/24 subnets. Within these two subnets, all clients have their scopes configured to be A.
上层10.0.0.0/8网络上的客户端配置为使用SLP作用域B，而下层10.0.0.0/8网络上的客户端配置为使用SLP作用域C。RSIP服务器B和C（作为服务器A的客户端）使用SLP定位RSIP服务器A，10.0.1.0/24和10.0.2.0/24子网上的其他RSIP客户端也是如此。在这两个子网中，所有客户端都将其作用域配置为A。
Note that specifying a particular SLP scope for RSIP clients does not restrict the SLP scope for other services advertised by SLP. SLP UAs can be configured for multiple scopes, so the scope configured for printing may be different from the scope configured for RSIP service.
请注意，为RSIP客户端指定特定SLP作用域并不限制SLP播发的其他服务的SLP作用域。SLP UAs可以配置为多个作用域，因此为打印配置的作用域可能不同于为RSIP服务配置的作用域。
Since SLP scopes are configured through a DHCP option [8], along with the IP address, system administrators can easily switch a cluster of machines from one realm to another by simply changing the scope and
由于SLP作用域是通过DHCP选项[8]以及IP地址配置的，因此系统管理员只需更改作用域和IP地址，就可以轻松地将计算机集群从一个领域切换到另一个领域
IP address assignments on the DHCP server. For example, in the above architecture, suppose a system administrator wanted to remove RSIP server B so that clients on the upper 10.0.0.0/8 subnet were directly on subnet 10.0.1.0/24. These clients now communicate with RSIP server A. By simply changing the address assignments and scope configuration of these clients on the DHCP server, the realm can be effectively switched.
DHCP服务器上的IP地址分配。例如，在上述体系结构中，假设系统管理员希望删除RSIP服务器B，以便上层10.0.0.0/8子网上的客户端直接位于子网10.0.1.0/24上。这些客户端现在与RSIP服务器A通信。只需在DHCP服务器上更改这些客户端的地址分配和作用域配置，就可以有效地切换领域。
While SLP itself contains no specific provision for load balancing, load balancing can easily be implemented using SLP. The only requirement is that the service type template specify an attribute indicating server load. In the case of RSIP, the service type template in Section 7 contains such an attribute. The attribute indicates the number of RSIP client sessions currently being supported by the server.
虽然SLP本身不包含负载平衡的具体规定，但可以使用SLP轻松实现负载平衡。唯一的要求是服务类型模板指定一个指示服务器负载的属性。在RSIP的情况下，第7节中的服务类型模板包含这样一个属性。该属性表示服务器当前支持的RSIP客户端会话数。
In order to perform load balancing, the RSIP server must update its service advertisement periodically as new connections are accepted. An RSIP client seeking to find the server having the lightest load performs the following series of SLP operations.
为了执行负载平衡，RSIP服务器必须在接受新连接时定期更新其服务公告。RSIP客户端试图找到负载最轻的服务器，执行以下一系列SLP操作。
1. As in Section 4, the client issues an SLP service request and collects all the returned service URLs.
1. 与第4节一样，客户端发出SLP服务请求并收集所有返回的服务URL。
2. For each service URL, the client performs an SLP attribute request for the attribute LOAD. The integer load figures are returned.
2. 对于每个服务URL，客户端对属性加载执行SLP属性请求。返回整数负载数字。
3. The client sorts through the returned load figures and selects the URL having the least number of connections. The client establishes its RSIP session with that server.
3. 客户端对返回的负载数据进行排序，并选择连接数最少的URL。客户端与该服务器建立RSIP会话。
Because of network delays, this procedure does not guarantee that a client will always obtain a connection with the lightest loaded server, but it does provide a high probability that the selected server is more lightly loaded.
由于网络延迟，此过程不能保证客户端始终与负载最轻的服务器建立连接，但它确实提供了所选服务器负载较轻的高概率。
A similar procedure is used in [9] to load balance access to TN3270E telnet servers.
[9]中使用了类似的过程来平衡对TN3270E telnet服务器的负载访问。
Name of submitters: James Kempf <james@docomolabs-usa.com>
Gabriel Montenegro <gab@sun.com>
Name of submitters: James Kempf <james@docomolabs-usa.com>
Gabriel Montenegro <gab@sun.com>
Language of service template: en
服务模板语言：en
Security Considerations: RSIP clients can use Service Location Protocol to find RSIP servers having particular security characteristics. If secure access to such information is required, SLP security should be used.
安全注意事项：RSIP客户端可以使用服务位置协议查找具有特定安全特性的RSIP服务器。如果需要安全访问此类信息，则应使用SLP安全。
Template text:
----------------------template begins here -------------------------
template-type = rsip
Template text:
----------------------template begins here -------------------------
template-type = rsip
template-version = 0.0
模板版本=0.0
template-description= The service:rsip type provides advertisements for clients seeing realm-specific IP (RSIP) servers. RSIP servers use the Realm Specific IP protocol to manage addresses and other resources from one realm on behalf of a client in another realm.
template description=服务：rsip类型为看到特定领域IP（rsip）服务器的客户端提供播发。RSIP服务器使用领域特定的IP协议代表另一领域中的客户机管理来自一个领域的地址和其他资源。
template-url-syntax=
;No additional URL path information required. An example service
;URL for an RSIP server is: service:rsip://gateway.mydomain:4455
template-url-syntax=
;No additional URL path information required. An example service
;URL for an RSIP server is: service:rsip://gateway.mydomain:4455
ipsec-support = BOOLEAN O #True if the server supports IPSEC as per [10]
ipsec支持=布尔O#如果服务器根据[10]支持ipsec，则为True
ike-support = BOOLEAN O #True if the server supports IKE as per [10]
ike支持=布尔O#如果服务器根据[10]支持ike，则为True
tunnel-type = STRING L M O IP-IP #The tunneling methods supported by the RSIP server. Clients #should include this attribute in a query so that they obtain a #server offering a tunneling method for which they have #support. Default is IP-IP. The values are currently #restricted to IP-IP, L2TP, GRE and NONE. A server can support #multiple tunnel types. IP-IP,L2TP,GRE,NONE
隧道类型=字符串L M O IP-IP#RSIP服务器支持的隧道方法。客户机应在查询中包含此属性，以便获得一个服务器，该服务器提供他们支持的隧道方法。默认值为IP-IP。这些值目前仅限于IP-IP、L2TP、GRE和NONE。服务器可以支持#多种隧道类型。IP-IP，L2TP，GRE，无
transport = STRING L M O TCP #Transport used by the RSIP protocol itself. TCP,UDP
transport=字符串L M O TCP#RSIP协议本身使用的传输。TCP，UDP
load = INTEGER O
#If the server supports load balancing, this attribute should be
#set to an integer from 0 to 100. 0 is the lowest indication of
#load and 100 the highest. Clients can query for this attribute
#and obtain load information, from which they can make an
#intelligent decision about which server to use.
----------------------template ends here ---------------------------
load = INTEGER O
#If the server supports load balancing, this attribute should be
#set to an integer from 0 to 100. 0 is the lowest indication of
#load and 100 the highest. Clients can query for this attribute
#and obtain load information, from which they can make an
#intelligent decision about which server to use.
----------------------template ends here ---------------------------
Service type templates provide information that is used to interpret information obtained by clients through SLP. If the RSIP template is modified or if a false template is distributed, RSIP servers may not correctly register themselves, or RSIP clients may not be able to interpret service information.
服务类型模板提供用于解释客户端通过SLP获得的信息的信息。如果修改了RSIP模板或分发了错误的模板，则RSIP服务器可能无法正确注册自己，或者RSIP客户端可能无法解释服务信息。
SLP provides an authentication mechanism for UAs to assure that service advertisements only come from trusted SAs [2]. If trust is an issue, particularly with respect to the information sought by the client about IPSEC and IKE support, then SLP authentication should be enabled in the network.
SLP为UAs提供了一种身份验证机制，以确保服务广告仅来自受信任的SA[2]。如果信任是一个问题，特别是关于客户端寻求的有关IPSEC和IKE支持的信息，则应在网络中启用SLP身份验证。
This document describes how SLP can be used by RSIP clients to find RSIP servers. A service type template for an RSIP SLP service type is presented. In addition, a few techniques for provisioning access to service advertisements for particular gateway servers, and for load balancing using SLP were provided. The result should allow RSIP service provisioning that is considerably more dynamic and robust than when traditional service discovery mechanisms are used.
本文档描述RSIP客户端如何使用SLP查找RSIP服务器。介绍了RSIP SLP服务类型的服务类型模板。此外，还提供了一些技术，用于为特定网关服务器提供对服务广告的访问，以及使用SLP进行负载平衡。其结果应该允许RSIP服务提供比使用传统服务发现机制时更具动态性和健壮性。
References
工具书类
[1] Borella, M., Grabelsky, D., Lo, J. and K. Taniguchi, "Realm Specific IP: Protocol Specification", RFC 3103, April 2001.
[1] Borella，M.，Grabelsky，D.，Lo，J.和K.Taniguchi，“领域特定IP：协议规范”，RFC 3103，2001年4月。
[2] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service Location Protocol, version 2", RFC 2608, July 1999.
[2] Guttman，E.，Perkins，C.，Veizades，J.和M.Day，“服务位置协议，版本2”，RFC 26081999年7月。
[3] Guttman, E, Perkins, C. and J. Kempf, "Service Templates and service: Schemes", RFC 2609, July 1999.
[3] Guttman，E，Perkins，C.和J.Kempf，“服务模板和服务：方案”，RFC 26091999年7月。
[4] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[4] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[5] Gulbrandsen, A. and P. Vixie, "A DNS RR for specifying the location of services (DNS SRV)", RFC 2052, October 1996.
[5] Gulbrandsen，A.和P.Vixie，“用于指定服务位置（DNS SRV）的DNS RR”，RFC 2052，1996年10月。
[6] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, March 1997.
[6] Droms，R.，“动态主机配置协议”，RFC 2131，1997年3月。
[7] Borella, M., Lo, J., Grabelsky, D. and G. Montenegro, "Realm Specific IP: Framework", RFC 3102, October 2001.
[7] Borella，M.，Lo，J.，Grabelsky，D.和G.黑山，“特定领域知识产权：框架”，RFC 3102，2001年10月。
[8] Perkins, C. and E. Guttman, "DHCP Options for Service Location Protocol", RFC 2610, July 1999.
[8] Perkins，C.和E.Guttman，“服务位置协议的DHCP选项”，RFC 2610，1999年7月。
[9] Naugle, J., Kasthurirangan, K. and G. Ledford, "TN3270E Service Location and Session Balancing", RFC 3049, January 2001.
[9] Naugle，J.，Kasturirangan，K.和G.Ledford，“TN3270E服务位置和会话平衡”，RFC 3049，2001年1月。
[10] Montenegro, G. and M. Borella, "RSIP Support for End-to-end IPSEC", RFC 3104, October 2001.
[10] 黑山G.和M.Borella，“RSIP对端到端IPSEC的支持”，RFC 3104，2001年10月。
[11] E. Guttman, "Service Location Protocol: Automatic Discovery of
IP Network Services," IEEE Internet Computing, July/August 1999.
Available at: http://computer.org/internet/ic1999/w4toc.htm
[11] E. Guttman, "Service Location Protocol: Automatic Discovery of
IP Network Services," IEEE Internet Computing, July/August 1999.
Available at: http://computer.org/internet/ic1999/w4toc.htm
Authors' Addresses
作者地址
Questions about this document may be directed to:
有关本文件的问题，请联系：
James Kempf NTT DoCoMo USA Labs 181 Metro Drive, Suite 300 San Jose, CA 95110
詹姆斯·肯普夫NTT DoCoMo美国实验室加利福尼亚州圣何塞市地铁路181号300室95110
Phone: 408-451-4711 Email: james@docomolabs-usa.com
电话：408-451-4711电子邮件：james@docomolabs-美国网
Gabriel E. Montenegro Sun Microsystems Laboratories, Europe 29, chemin du Vieux Chene 38240 Meylan FRANCE
加布里埃尔E.黑山太阳微系统实验室，欧洲29号，法国墨西哥chemin du Vieux Chene 38240
Phone: +33 476 18 80 45
EMail: gab@sun.com
Phone: +33 476 18 80 45
EMail: gab@sun.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English.
本文件及其译本可复制并提供给他人，对其进行评论或解释或协助其实施的衍生作品可全部或部分编制、复制、出版和分发，不受任何限制，前提是上述版权声明和本段包含在所有此类副本和衍生作品中。但是，不得以任何方式修改本文件本身，例如删除版权通知或对互联网协会或其他互联网组织的引用，除非出于制定互联网标准的需要，在这种情况下，必须遵循互联网标准过程中定义的版权程序，或根据需要将其翻译成英语以外的其他语言。
The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns.
上述授予的有限许可是永久性的，互联网协会或其继承人或受让人不会撤销。
This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
本文件和其中包含的信息是按“原样”提供的，互联网协会和互联网工程任务组否认所有明示或暗示的保证，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。