Network Working Group J. Naugle
Request for Comments: 3049 K. Kasthurirangan
Category: Standards Track IBM
G. Ledford
Zephyr Development
January 2001
Network Working Group J. Naugle
Request for Comments: 3049 K. Kasthurirangan
Category: Standards Track IBM
G. Ledford
Zephyr Development
January 2001
TN3270E Service Location and Session Balancing
TN3270E服务位置和会话平衡
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.
本文件规定了互联网社区的互联网标准跟踪协议，并要求进行讨论和提出改进建议。有关本协议的标准化状态和状态，请参考当前版本的“互联网官方协议标准”（STD 1）。本备忘录的分发不受限制。
Copyright Notice
版权公告
Copyright (C) The Internet Society (2001). All Rights Reserved.
版权所有（C）互联网协会（2001年）。版权所有。
Abstract
摘要
This document discusses the implementation of Service Location Protocol (SLP) and session balancing with a TN3270E emulator in a client server implementation with a TN3270E server.
本文档讨论在使用TN3270E服务器的客户机-服务器实现中使用TN3270E仿真器实现服务位置协议（SLP）和会话平衡。
Application program developer's can locate TN3270E services and load balance among those services (3270 host sessions), by using this SLP support.
通过使用此SLP支持，应用程序开发人员可以找到TN3270E服务以及这些服务之间的负载平衡（3270主机会话）。
Table of Contents
目录
1. Introduction and Terminology ................................. 2
1.1 Terminology .............................................. 2
2. An Overview of RFC 2165 ...................................... 3
2.1 SLP Agents ............................................... 3
2.2 Service Agents ........................................... 3
2.3 User Agents .............................................. 4
3. TN3270E Server Environment and Load .......................... 4
3.1 TnN3270E Server Load ..................................... 4
4. TN3270E Client Configuration ................................. 6
4.1 SLP Scope ................................................ 6
4.2 DA-Discovery Time-Out .................................... 6
4.3 SA-Discovery Time-Out .................................... 7
5. TN3270E Client Implementation Information .................... 7
5.1 Overview ................................................. 7
1. Introduction and Terminology ................................. 2
1.1 Terminology .............................................. 2
2. An Overview of RFC 2165 ...................................... 3
2.1 SLP Agents ............................................... 3
2.2 Service Agents ........................................... 3
2.3 User Agents .............................................. 4
3. TN3270E Server Environment and Load .......................... 4
3.1 TnN3270E Server Load ..................................... 4
4. TN3270E Client Configuration ................................. 6
4.1 SLP Scope ................................................ 6
4.2 DA-Discovery Time-Out .................................... 6
4.3 SA-Discovery Time-Out .................................... 7
5. TN3270E Client Implementation Information .................... 7
5.1 Overview ................................................. 7
5.2 How to Obtain List of TN3270E Servers Supporting SLP ..... 8
5.3 TN3270E Sample Client Flow ............................... 9
5.3.1 Open the SLP connection ............................. 9
5.3.2 Query the list of TN3270E servers ................... 9
5.3.3 Forward Looking Example using SLPv2 ................. 10
5.3.4 Determine loading of each TN3270E server ............ 10
5.4 Recommendations .......................................... 11
6. Sample Trace Flow of SLP and Session Balancing ............... 11
7. Service Templates and Service Registration ................... 12
7.1 The TN3270E Service Type Template ........................ 12
7.2 The Server Service Template .............................. 16
7.3 Template Contact Information ............................. 17
7.4 Security Considerations .................................. 17
7.5 Sample TN3270 Service Registration Message ............... 18
7.6 Sample Server Service Registration Message ............... 19
8. References ................................................... 19
9. Authors' Addresses ........................................... 20
10. Full Copyright Statement .................................... 21
5.2 How to Obtain List of TN3270E Servers Supporting SLP ..... 8
5.3 TN3270E Sample Client Flow ............................... 9
5.3.1 Open the SLP connection ............................. 9
5.3.2 Query the list of TN3270E servers ................... 9
5.3.3 Forward Looking Example using SLPv2 ................. 10
5.3.4 Determine loading of each TN3270E server ............ 10
5.4 Recommendations .......................................... 11
6. Sample Trace Flow of SLP and Session Balancing ............... 11
7. Service Templates and Service Registration ................... 12
7.1 The TN3270E Service Type Template ........................ 12
7.2 The Server Service Template .............................. 16
7.3 Template Contact Information ............................. 17
7.4 Security Considerations .................................. 17
7.5 Sample TN3270 Service Registration Message ............... 18
7.6 Sample Server Service Registration Message ............... 19
8. References ................................................... 19
9. Authors' Addresses ........................................... 20
10. Full Copyright Statement .................................... 21
This document will provide information on Service Location Protocol implementation to discover TN3270E servers in a network and session balance among those servers. This implementation follows the standards track RFC 2165, Service Location Protocol [1] but also provides some examples when using Service Location Protocol version 2 to be forward looking. Service Location Protocol version 2 is documented in RFC 2608 [4] and RFC 2609 [2].
本文档将提供有关服务位置协议实施的信息，以发现网络中的TN3270E服务器以及这些服务器之间的会话平衡。此实现遵循RFC 2165标准轨道，服务位置协议[1]，但也提供了一些示例，用于前瞻性地使用服务位置协议版本2。服务位置协议版本2记录在RFC 2608[4]和RFC 2609[2]中。
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 RFC 2119 [1].
本文件中的关键词“必须”、“不得”、“要求”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照RFC 2119[1]中所述进行解释。
Session Balance - This refers to the ability of TN3270E client to use server load information to establish a TN3270E connection to the TN3270E server with the least load at that time. The purpose is to distribute the connection of TN3270E sessions among more than one TN3270E server, and one server will not be excessively loaded. The term "load balance" is a more general term, with respect to server load, and in this document we are focusing on the TN3270E session connections to least loaded servers.
会话平衡-这是指TN3270E客户端能够使用服务器负载信息建立到当时负载最低的TN3270E服务器的TN3270E连接。目的是将TN3270E会话的连接分布在多个TN3270E服务器之间，并且一个服务器不会过度加载。术语“负载平衡”是关于服务器负载的一个更一般的术语，在本文档中，我们将重点介绍到负载最少的服务器的TN3270E会话连接。
SNA Gateway - A Systems Network Architecture (SNA) gateway allows multiple LAN-attached workstations to access SNA hosts through one or more physical connections to one or more hosts. A SNA gateway acts as a protocol converter between workstations attached to a LAN and a
SNA网关-系统网络体系结构（SNA）网关允许多个局域网连接工作站通过一个或多个物理连接访问SNA主机。SNA网关充当连接到LAN的工作站和网络之间的协议转换器
WAN host line. It typically would support the SNA protocols LU 0, 1, 2, 3, and dependent LU 6.2 (APPC). SNA gateways typically include a TN3270E server capability.
广域网主机线。它通常支持SNA协议LU 0、1、2、3和从属LU 6.2（APPC）。SNA网关通常包括TN3270E服务器功能。
LU Pool - The Logical Units (LUs) defined in the gateway can be dedicated to a particular workstation or pooled among multiple workstations. Pooling allows workstations to share common Logical Units (LUs), which increases the efficiency of the LUs and reduces the configuration and startup requirements at the host. When a client connects to the gateway, the gateway retrieves an LU from the pool to establish a session. The LU is returned to the pool for access by other workstations when the session is ended.
LU池-网关中定义的逻辑单元（LU）可以专用于特定工作站，也可以在多个工作站之间进行池。池允许工作站共享公共逻辑单元（LU），这提高了LU的效率，并降低了主机上的配置和启动要求。当客户端连接到网关时，网关从池中检索LU以建立会话。会话结束时，LU返回到池中，供其他工作站访问。
Commserver Service Type Template - Commserver service type is defined as an SNA Gateway server as previously defined above in this terminology section. A template describing the attributes for this service type is in section 7.2.
Commserver服务类型模板-Commserver服务类型定义为SNA网关服务器，如上文本术语部分所述。描述此服务类型属性的模板见第7.2节。
RFC 2165, Service Location Protocol (SLP) [1], provides an automatic way for clients to discover services within an administrative domain.
RFC 2165，服务位置协议（SLP）[1]，为客户端提供了一种自动方式来发现管理域内的服务。
These services have various attributes associated with them from which a client can base a service selection. The basic design involves the use of three agent types. These are: User Agents (UA's), Service Agents (SA's) and Directory Agents (DA's).
这些服务具有与之关联的各种属性，客户机可以根据这些属性选择服务。基本设计涉及使用三种代理类型。这些是：用户代理（UA）、服务代理（SA）和目录代理（DA）。
User Agents are used to query Service Agents or Directory Agents. They acquire/request service information based upon the desired attributes and service needed for the user application.
用户代理用于查询服务代理或目录代理。它们根据用户应用程序所需的期望属性和服务来获取/请求服务信息。
Service Agents represent a specific service and advertise service information.
服务代理表示特定的服务并公布服务信息。
Directory Agents act as a central collection point for service registration information by Service Agents which is later requested by "user agents" in "intranets".
目录代理充当服务代理的服务注册信息的中心收集点，服务代理稍后会在“内部网”中请求“用户代理”。
The service registers itself with the service agent so that the SA can start advertising this information over the network. The process of registration consists of the service giving the SA all relevant configuration information and attribute tag/value list pairs specific to this service. The Service template is an abstract schema that
服务向服务代理注册，以便SA可以开始在网络上发布此信息。注册过程包括向SA提供所有相关配置信息和特定于此服务的属性标记/值列表对的服务。服务模板是一个抽象模式，它
applies to the service type. The service template for TN3270E is shown later, contains the URL which is the address of the server with the port, which should be used to connect to it. The URL also contains the service type which in this case is TN3270. The template also contains all the other attributes associated with this service.
应用于服务类型。稍后将显示TN3270E的服务模板，其中包含URL，该URL是带有端口的服务器的地址，该端口应用于连接到它。URL还包含服务类型，在本例中为TN3270。该模板还包含与此服务关联的所有其他属性。
The User Agent working on the TN3270E client's behalf retrieves service information from the Service Agent(s) or a Directory Agent. Based on the gathered information and required attributes the TN3270E client or user can decide whether or not to connect with a particular server. Based on the service advertisements from various TN3270E servers, the client looks at the load attribute and can decide to connect to the least loaded server. If by the time it connects to that particular TN3270E server, the server becomes unavailable it can try connecting to the next server in its list (ie: the second least loaded server whose advertisement was retrieved by the client/user agent).
代表TN3270E客户端工作的用户代理从服务代理或目录代理检索服务信息。根据收集的信息和所需的属性，TN3270E客户端或用户可以决定是否与特定服务器连接。根据来自各种TN3270E服务器的服务广告，客户机查看load属性，并可以决定连接到负载最少的服务器。如果在连接到该特定TN3270E服务器时，该服务器变得不可用，则它可以尝试连接到其列表中的下一个服务器（即：第二个负载最少的服务器，其广告由客户端/用户代理检索）。
TN3270E Servers are pervasive in today's networked environment. SLP provides emulator clients with a way to discover TN3270E servers in the network and session balance among the servers. The TN3270E servers could be distributed across different SNA gateways with different connection methods to hosts. The use of LU pools provides an easy way for administrators to provide users access to hosts. Administrators can add users to LU pools that have pre-configured LU's with specific attributes, like LU types and model types.
TN3270E服务器在当今的网络环境中无处不在。SLP为emulator客户端提供了一种在网络中发现TN3270E服务器以及服务器间会话平衡的方法。TN3270E服务器可以通过不同的主机连接方法分布在不同的SNA网关上。LU池的使用为管理员提供了一种方便的方式，让用户能够访问主机。管理员可以将用户添加到具有特定属性（如LU类型和模型类型）的预配置LU的LU池中。
These LU pools would typically have LUs from several different gateways assigned, and as members of the LU pool make TN3270E session connections, they would be making connections to different TN3270E servers, with different load factors, so that session balancing could be accomplished. The use of LU pools is not a requirement for SLP and session balancing. A TN3270E client could obtain a session by using SLP and session balancing to locate the least loaded server in the network. On a service request a wild card "*" could be used when asking for LUPOOL if the emulator doesn't care which device types are supported in given pools or if it can assume given pools support only certain device types.
这些LU池通常会分配来自多个不同网关的LU，并且当LU池的成员进行TN3270E会话连接时，他们将使用不同的负载系数连接到不同的TN3270E服务器，以便实现会话平衡。SLP和会话平衡不要求使用LU池。TN3270E客户端可以通过使用SLP和会话平衡来定位网络中负载最少的服务器，从而获得会话。如果emulator不关心给定池中支持哪些设备类型，或者假设给定池仅支持某些设备类型，则在服务请求时，可以使用通配符“*”。
TN3270E servers providing load information, SHOULD include number of sessions available, not in current use, as part of the calculation in determining the total load for the server. There can be other
提供负载信息的TN3270E服务器应包括当前未使用的可用会话数，作为确定服务器总负载计算的一部分。可能还有其他原因
factors that might have an effect on server load. An example would be if a server is not dedicated to only SNA traffic, and is handling other processes, like file services and print services, etc. It is beyond the scope of this document to standardize the method of individual server load calculations. Different vendors server's may calculate load information based upon factors they consider important, and methods for calculating load may change over time.
可能影响服务器负载的因素。一个例子是，如果一台服务器不仅专用于SNA流量，而且正在处理其他流程，如文件服务和打印服务等。标准化单个服务器负载计算的方法超出了本文档的范围。不同的供应商服务器可以根据他们认为重要的因素来计算负载信息，并且计算负载的方法可以随着时间而改变。
If the TN3270E server coexists in a network with other TN server implementations using SLP for session balancing, TN3270E server load could be adjusted to compensate for differences in load calculations.
如果TN3270E服务器与使用SLP进行会话平衡的其他TN服务器实现共存于网络中，则可以调整TN3270E服务器负载以补偿负载计算中的差异。
One way to allow TN3270E server administrators to compensate for differences in implementations of calculating server load measurement is to provide the ability to modify the load calculation on the TN3270E server. An element of control can be provided by allowing the administrator to modify the load measurement, by using an integral number between 0 and 100 (100 being the highest) to change the load. This load measurement acts as an additional factor on the server's actual load calculation, so that the administrator could bias up or down, the likelihood of that server being selected by a TN3270E client.
允许TN3270E服务器管理员补偿计算服务器负载测量实现差异的一种方法是提供修改TN3270E服务器上的负载计算的能力。可以通过允许管理员修改负载测量来提供控制元素，方法是使用0到100之间的整数（100为最大值）来更改负载。此负载测量作为服务器实际负载计算的一个附加因素，因此管理员可以向上或向下偏移该服务器被TN3270E客户端选择的可能性。
Load MUST be defined as one of the attributes for the TN3270E server. The Load attribute provided at the server will allow clients to determine which server to make a connection. If a UA provides only a Service Type, in an Attribute Request, then the reply includes all attributes and all values for that Service Type, and Load would be included. Attribute Requests MAY include a select clause, so you could be returned just load information. For more information on Attribute Requests refer to Service Location Protocol [1].
必须将Load定义为TN3270E服务器的属性之一。服务器上提供的Load属性将允许客户端确定要建立连接的服务器。如果UA在属性请求中仅提供服务类型，则应答将包括该服务类型的所有属性和所有值，并且将包括负载。属性请求可能包含一个select子句，因此您可以只返回加载信息。有关属性请求的更多信息，请参阅服务位置协议[1]。
An application could issue a Service Request to locate a TN3270E server. Then an application designed to perform least-load location of a TN3270E service, could issue a series of Attribute Requests to obtain the load measurement of each server specified with a URL. It would specify a select clause similar to the one below to receive only load information.
应用程序可以发出服务请求以定位TN3270E服务器。然后，设计用于执行TN3270E服务的最小负载定位的应用程序可以发出一系列属性请求，以获取使用URL指定的每个服务器的负载度量。它将指定一个类似于下面的select子句，以仅接收加载信息。
URL = service:tn3270://9.37.51.254:23 Attribute filter = LOAD
URL = service:tn3270://9.37.51.254:23 Attribute filter = LOAD
The attribute LOAD would be returned along with its value. The application could then issue other Attribute Request calls for each URL.
属性加载将与其值一起返回。然后，应用程序可以为每个URL发出其他属性请求调用。
The application would then select the least loaded server as a connection target. If it tries to connect to a server and that connection fails, it could then try to connect to the next least-loaded server.
然后，应用程序将选择负载最少的服务器作为连接目标。如果它尝试连接到服务器，但连接失败，那么它可以尝试连接到下一个负载最少的服务器。
Scope is a parameter used to control and manage access by clients to servers in a network. It is the same as the Service Location Protocol scope defined in RFC 2165 [1]. The control scope provides is necessary for two reasons:
作用域是一个参数，用于控制和管理客户端对网络中服务器的访问。它与RFC 2165[1]中定义的服务位置协议范围相同。控制范围规定的必要性有两个原因：
As your network, the number of clients, and the number of servers grow, it becomes necessary to partition access to those servers by the growing number of clients in order to reduce overall traffic on the network. It allows administrators to organize users and servers into administrative groups.
随着网络、客户端数量和服务器数量的增长，有必要根据不断增长的客户端数量对这些服务器的访问进行分区，以减少网络上的总体流量。它允许管理员将用户和服务器组织到管理组中。
The meaning of the values of scope is defined by the administrator of the network. These values can represent any entity. Commonly, they fall along either departmental, geographical, or organizational lines.
范围值的含义由网络管理员定义。这些值可以表示任何实体。通常，它们属于部门、地域或组织范围。
Each TN3270E server can be assigned to a single scope or multiple scopes. TN3270E clients using these servers can be configured for a single specific scope. If TN3270E clients are not configured with a scope they MUST use the scope "default".
每个TN3270E服务器可以分配给单个作用域或多个作用域。可以为单个特定范围配置使用这些服务器的TN3270E客户端。如果TN3270E客户端未配置作用域，则它们必须使用“默认”作用域。
SLP Service Agents and Directory Agents (DA) need to reside in the network that support the TN3270E server with configured scopes.
SLP服务代理和目录代理（DA）需要驻留在支持配置了作用域的TN3270E服务器的网络中。
Attribute information for Service Types pertaining to a specific scope can be obtained from Directory Agents (DA). The DA will not return a result unless the requested scope matches.
可以从目录代理（DA）获取与特定范围相关的服务类型的属性信息。除非请求的作用域匹配，否则DA不会返回结果。
For more information on SLP scope refer to Service Location Protocol [1].
有关SLP作用域的更多信息，请参阅服务位置协议[1]。
The DA Discovery time-out value, is used to control how long the SLP API must wait to discover Directory Agents (DAs) in the network. The discovery request is a multicast, and the amount of time required to gather all DA responses might vary depending on many factors. If there are no DAs in the network, this time-out value can be set to
DA发现超时值用于控制SLP API必须等待多长时间才能在网络中发现目录代理（DAs）。发现请求是一个多播，收集所有DA响应所需的时间可能因许多因素而异。如果网络中没有DAs，则可以将此超时值设置为
zero to indicate that no DA discovery is to be done. The time-out is expressed in milliseconds. Time-out intervals and default values should be handled as described in RFC 2165 [1].
零表示不进行DA发现。超时以毫秒表示。超时间隔和默认值应按照RFC 2165[1]中所述进行处理。
The SA Multicast time-out value, is used to control how long the SLP API must wait to discover services, attributes, or service types in a network without at least one DA that supports the scope of the request. In this situation, these requests are multicast and the User Agent waits the time-out value to gather the multiple responses that are returned. The time-out is expressed in milliseconds. Time-out intervals and default values should be handled as described in RFC 2165 [1].
SA多播超时值用于控制SLP API必须等待多长时间才能在没有至少一个支持请求范围的DA的网络中发现服务、属性或服务类型。在这种情况下，这些请求是多播的，用户代理等待超时值以收集返回的多个响应。超时以毫秒表示。超时间隔和默认值应按照RFC 2165[1]中所述进行处理。
A TN3270E client that implements TN3270E SLP session balancing does not need to configure an IP Host Address or TCP Port for the TN3270E server it desires to connect to. Instead, the IP Host Address and TCP Port of the least loaded TN3270E server is discovered by using the SLP session balancing described in this document.
实现TN3270E SLP会话平衡的TN3270E客户端不需要为其希望连接的TN3270E服务器配置IP主机地址或TCP端口。相反，负载最少的TN3270E服务器的IP主机地址和TCP端口是通过使用本文档中描述的SLP会话平衡来查找的。
The discovery of the least loaded TN3270E server is done entirely outside of and before the TN3270E telnet negotiation. Once the IP Host address and TCP Port of the least loaded TN3270E server is discovered, the TN3270E client can then start normal TN3270E telnet negotiation.
负载最少的TN3270E服务器的发现完全在TN3270E telnet协商之外和之前完成。一旦发现负载最少的TN3270E服务器的IP主机地址和TCP端口，TN3270E客户端就可以开始正常的TN3270E telnet协商。
The TN3270E client MUST allow for configuration of the following parameters. These SLP specific configuration items are covered by configuration parameters in the SLP API [5].
TN3270E客户端必须允许配置以下参数。SLP API[5]中的配置参数涵盖了这些特定于SLP的配置项。
Enable SLP Session Balancing
启用SLP会话平衡
This configuration parameter indicates whether or not SLP session balancing is enabled. If it is enabled the following three configuration parameters MUST also be configurable. If this parameter is disabled, SLP session balancing is not supported and normal TN3270E telnet negotiation is performed.
此配置参数指示是否启用SLP会话平衡。如果启用，则还必须配置以下三个配置参数。如果禁用此参数，则不支持SLP会话平衡，并执行正常的TN3270E telnet协商。
Scope Name The scope name is a text string that specifies a group of TN3270E servers. The scope name can be used to identify groups of TN3270E servers in a departmental or geographic setting. For
范围名称范围名称是一个文本字符串，用于指定一组TN3270E服务器。作用域名称可用于标识部门或地理环境中的TN3270E服务器组。对于
example, if the scope name is Building-D, then the SLP session balancing would search all TN3270E servers in the Building-D scope to find the least loaded TN3270E server.
例如，如果作用域名称为Building-D，则SLP会话平衡将搜索Building-D作用域中的所有TN3270E服务器，以查找负载最少的TN3270E服务器。
If the scope name is blank, then the scope name is not used. This is referred to as unscoped. It should be noted as in section 4.1 above that any reference to unscoped services applies to Service Location Protocol version 1 only [1]. Service Location Protocol version 2 doesn't allow unscoped services but does allow the use of default scope [4]. In this case all TN3270E servers, with or without scope names, can be used to satisfy the request for least loaded TN3270E servers. In order to cut down on network overhead, it is recommended that either all servers be scoped or no servers be scoped. Refer back to section 4.1 for more discussion of scope.
如果作用域名称为空，则不使用作用域名称。这被称为无范围。应注意的是，如上文第4.1节所述，对非范围服务的任何提及仅适用于服务位置协议第1版[1]。服务位置协议版本2不允许非作用域服务，但允许使用默认作用域[4]。在这种情况下，所有TN3270E服务器（有或没有作用域名称）都可以用来满足负载最少的TN3270E服务器的请求。为了减少网络开销，建议对所有服务器进行范围限定，或者不对任何服务器进行范围限定。有关范围的更多讨论，请参阅第4.1节。
DA Discovery Time Out Value
DA发现超时值
This value is specified in milliseconds and is fully described in section 4.2 of this document.
该值以毫秒为单位指定，并在本文件第4.2节中详细说明。
SA Multicast Time Out Value
SA多播超时值
This value is specified in milliseconds and is fully described in section 4.3 of this document.
该值以毫秒为单位指定，并在本文件第4.3节中详细说明。
A TN3270E client that implements SLP session balancing uses API calls to obtain the list of TN3270E servers supporting SLP session balancing.
实现SLP会话平衡的TN3270E客户端使用API调用获取支持SLP会话平衡的TN3270E服务器列表。
The following Service Location Version 2 API [5] calls, could be used with TN3270E SLP session balancing:
以下服务位置版本2 API[5]调用可用于TN3270E SLP会话平衡：
SLPOpen - returns an SLPHandle handle to be used
SLPOpen-返回要使用的SLPHandle句柄
SLPFindSrvs - issues the query for services
SLPFindSrvs-发出服务查询
SLPFindAttrs - returns service attributes matching the attribute ids for the indicated service URL or service type.
SLPFindAttrs-返回与指定服务URL或服务类型的属性ID匹配的服务属性。
SLPClose - frees all resources associated with the handle.
SLPClose-释放与句柄关联的所有资源。
The TN3270E client must first open a handle with the SLP User Agent. For Service Location Protocol version 2, SLPOpen API call [5] The SA multicast time out and DA discovery time out values would be passed as parameters to the SLPOpen API call.
TN3270E客户端必须首先打开SLP用户代理的句柄。对于服务位置协议版本2，SLPOpen API调用[5]SA多播超时和DA发现超时值将作为参数传递给SLPOpen API调用。
The TN3270E client then queries for the list of TN3270E servers supporting SLP. This is done by using the Service Request API call.
然后，TN3270E客户端查询支持SLP的TN3270E服务器列表。这是通过使用服务请求API调用完成的。
The request string contains information that determines which type of TN3270E servers that this client desires to connect to. The request string can contain the scope name, pool name, session type and 3270 screen size.
请求字符串包含确定此客户端希望连接到哪种类型的TN3270E服务器的信息。请求字符串可以包含作用域名称、池名称、会话类型和3270屏幕大小。
The SLPv1 query string has the following format:
SLPv1查询字符串的格式如下：
TN3270/<scope name>/LUPOOL/ == <pool name><TAB><device type>
TN3270/<scope name>/LUPOOL/ == <pool name><TAB><device type>
The <scope name> is the name of the scope that is configured for the TN3270E client. If the scope is blank or null (unscoped request), then the scope is not inserted into the request string.
<scope name>是为TN3270E客户端配置的作用域的名称。如果作用域为空或null（非作用域请求），则不会将作用域插入请求字符串中。
The <pool name> is a 1 to 8 character upper case string that indicates the name of the pool to which the TN3270E client desires to connect. For SLP session balancing, the same pool name must be configured on different TN3270E servers.
<pool name>是一个1到8个字符的大写字符串，表示TN3270E客户端希望连接到的池的名称。对于SLP会话平衡，必须在不同的TN3270E服务器上配置相同的池名称。
The <TAB> is the '/t' tab character which is hexadecimal 0x09. the <TAB> is a literal and is used as a separator.
<TAB>是“/t”制表符，它是十六进制0x09。<TAB>是一个文本，用作分隔符。
The <device type> can be any of the following:
<device type>可以是以下任意一种：
3270DSC for TN3270E device type IBM-3287-1 3270002 for TN3270E device types IBM-3278-2 and IBM-3278-2-E 3270003 for TN3270E device types IBM-3278-3 and IBM-3278-3-E 3270004 for TN3270E device types IBM-3278-4 and IBM-3278-4-E 3270005 for TN3270E device types IBM-3278-5 and IBM-3278-5-E * for TN3270E device type IBM-DYNAMIC
3270DSC适用于TN3270E设备类型IBM-3287-1 3270002适用于TN3270E设备类型IBM-3278-2和IBM-3278-2-E 3270003适用于TN3270E设备类型IBM-3278-3和IBM-3278-3-E 3270004适用于TN3270E设备类型IBM-3278-4和IBM-3278-4-E 3270005适用于TN3270E设备类型IBM-3278-5和IBM-3278-5-E*适用于TN3270E设备类型IBM-DYNAMIC
Example:
例子：
For a TN3270E client searching for TN3270E servers in the ENGINEERING scope for a model 2 screen size and LUPOOL name pool2, the following request SLPv1 string would be constructed:
对于在2型屏幕大小和LUPOOL name pool2的工程范围内搜索TN3270E服务器的TN3270E客户端，将构造以下请求SLPv1字符串：
"TN3270/ENGINEERING/LUPOOL/ == POOL2<TAB>3270002"
"TN3270/ENGINEERING/LUPOOL/ == POOL2<TAB>3270002"
Note: The " characters before and after the string are not part of the request string.
注意：字符串前后的“字符”不是请求字符串的一部分。
For SLPv2 the scope and service type are no longer part of the query string. These are now separate fields in the message. The service type name is required to have the "service:" prepended. The service type field would look like "service:TN3270", and the scope field would be a comma separated list of scopes. A scope name is always required in SLPv2, if no other name is known, the scope name "DEFAULT" is used. The example below uses the same parameters as used in above section 5.3.2.
对于SLPv2，范围和服务类型不再是查询字符串的一部分。这些现在是消息中的独立字段。服务类型名称必须有“服务：”前缀。服务类型字段看起来像“service:TN3270”，范围字段是以逗号分隔的范围列表。SLPv2中始终需要范围名称，如果不知道其他名称，则使用范围名称“DEFAULT”。下面的示例使用了与上述第5.3.2节相同的参数。
Example: Service Type: service:TN3270 Scope string: ENGINEERING The query string would have the following format:
示例：服务类型：服务：TN3270范围字符串：工程查询字符串的格式如下：
(LUPOOL=<POOL2> <32700002>)
(LUPOOL=<POOL2> <32700002>)
In SLPv2 queries, all whitespace is compressed to a single space character during matching, so the identity of the separator character does not matter. The tab character could be added for readability, but it will not affect the outcome of the query.
在SLPv2查询中，所有空格在匹配期间压缩为单个空格字符，因此分隔符的标识无关紧要。可以添加制表符以提高可读性，但它不会影响查询结果。
An attribute request for "service:tn3270e" specifying the attribute LOAD can be made and you will get back all the available loads. Say these are 35,88,78. You can then issue a service request for all tn3270E servers with "LOAD<40" for instance. Even if the load changes between the time you get the attribute reply and when you issue the request, you will still get the best the network has to offer.
可以为“service:tn3270e”发出属性请求，指定属性加载，您将获得所有可用加载。假设这些是35,88,78。然后，您可以为所有tn3270E服务器发出一个服务请求，例如“负载<40”。即使负载在您获得属性回复和发出请求之间发生变化，您仍将获得网络提供的最佳性能。
The TN3270E client then uses the TN3270E server's IP Host address to start normal Telnet TN3270E negotiation.
然后，TN3270E客户端使用TN3270E服务器的IP主机地址启动正常的Telnet TN3270E协商。
The TN3270E client SHOULD display the IP hostname and TCP Port that is being used for the TN3270E connection. This gives the user knowledge of which TN3270E server the session is connected to. For example, the IP host address could be displayed in the window system status bar.
TN3270E客户端应显示用于TN3270E连接的IP主机名和TCP端口。这让用户知道会话连接到哪个TN3270E服务器。例如，IP主机地址可以显示在窗口系统状态栏中。
The TN3270E client SHOULD display the resource name that is returned by the TN3270E server after connection and TN3270E negotiation is completed. This gives the user knowledge of which LU resource name in the LUPOOL the session is connected to. For example, the resource name could be displayed in the Windows status bar, or even in the 3270 OIA line.
在连接和TN3270E协商完成后，TN3270E客户端应显示TN3270E服务器返回的资源名称。这让用户知道会话连接到的LU池中的哪个LU资源名称。例如，资源名称可以显示在Windows状态栏中，甚至可以显示在3270 OIA行中。
In the event that after the TN3270E client has determined the least loaded server and the connection to that server fails for some reason, the connection should be closed and an attempt made to connect to other TN3270E servers in the list of least loaded servers.
如果在TN3270E客户端确定负载最少的服务器后，与该服务器的连接因某种原因失败，则应关闭连接，并尝试连接到负载最少的服务器列表中的其他TN3270E服务器。
For example, a TN3270E server may reject a connection to a specific pool if the pool is full, or if the device type does not match what is available in the pool. If this occurs, then an attempt to other least loaded TN3270E servers SHOULD be performed.
例如，如果池已满，或者设备类型与池中可用的设备类型不匹配，TN3270E服务器可能会拒绝与特定池的连接。如果发生这种情况，则应尝试访问其他负载最少的TN3270E服务器。
This sample trace flow is provided for informational purposes only.
此示例跟踪流仅供参考。
SLP API: Service Request: TN3270//LUPOOL == POOL2 3270002/
SLP API: Service Request: TN3270//LUPOOL == POOL2 3270002/
SLP API: Service Reply: service:tn3270://206.109.45.139:23
SLP API: Service Reply: service:tn3270://206.109.45.139:23
SLP API: Service Reply: service:tn3270://206.109.45.140:23
SLP API: Service Reply: service:tn3270://206.109.45.140:23
Connecting to 206.109.45.139:23...
连接到206.109.45.139:23。。。
TerminalType=NVT
终端类型=NVT
Connection established
建立连接
Recv <- DO TN3270E
Recv<-DO TN3270E
Send -> WILL TN3270E
发送->将使用TN3270E
TerminalType=TN3270E
终端类型=TN3270E
Recv <- SEND DEVICE_TYPE
Recv<-发送设备类型
Send -> DEVICE_TYPE REQUEST IBM-3278-2-E CONNECT POOL2
发送->设备类型请求IBM-3278-2-E连接池2
Recv <- DEVICE_TYPE IS IBM-3278-2-E CONNECT TN8003
Recv<-设备类型为IBM-3278-2-E CONNECT TN8003
Send -> FUNCTIONS REQUEST BIND_IMAGE SYSREQ
发送->函数请求绑定\图像系统请求
Recv <- FUNCTIONS IS BIND_IMAGE SYSREQ
Recv<-函数为BIND_IMAGE SYSREQ
The Service Location Protocol uses the "service:" URL scheme name to define URLs called "service: URLs". These schemes provide a way for clients to obtain configuration information that is needed to establish a 3270 session through the TN3270E server. The Service Location Protocol provides for service: URLs to be registered and discovered.
服务位置协议使用“服务：”URL方案名称来定义称为“服务：URL”的URL。这些方案为客户端提供了通过TN3270E服务器建立3270会话所需的配置信息。服务位置协议提供要注册和发现的服务：URL。
Service Registration These service registrations contain a service: URL, and possible attributes associated with that service. The service registration information are shown below for the server.
服务注册这些服务注册包含一个Service:URL以及与该服务相关联的可能属性。服务器的服务注册信息如下所示。
Service Templates Service templates are documents defining in a formal way the attributes associated with that service that a client may want to use. For more information on service templates please refer to, Service Templates and service: Schemes. [2]. The server service template and TN3270 service templates are shown below.
服务模板服务模板是以正式方式定义客户机可能希望使用的与该服务相关联的属性的文档。有关服务模板的更多信息，请参阅，服务模板和服务：方案。[2]. 服务器服务模板和TN3270服务模板如下所示。
The 'service:tn3270:' template defined below conforms to the grammar described in "Service Templates and service: Schemes". Please refer to [2] for detailed explanation of the syntax.
下面定义的“service:tn3270:”模板符合“service Templates and service:Schemes”中描述的语法。有关语法的详细解释，请参阅[2]。
Name of submitters: Jim Naugle <jnaugle@us.ibm.com> Gregg Ledford <gledford@zephyrcorp.com> K. Kasthurirangan <kasthuri@us.ibm.com> Language of service template: en Security Considerations: Service Location Protocol can help clients discover security services supported by the TN3270E server. If security services are important or required, using SLP authentication, and protected scopes in Service Location Protocol version 1 is recommended [1]. Well known ciphersuite names are used in the template [3].
提交人姓名：Jim Naugle<jnaugle@us.ibm.com>格雷格·莱德福德<gledford@zephyrcorp.com>K.卡斯图里兰甘<kasthuri@us.ibm.com>服务语言模板：en安全注意事项：服务位置协议可以帮助客户端发现TN3270E服务器支持的安全服务。如果安全服务很重要或需要，建议在服务位置协议版本1中使用SLP身份验证和受保护的作用域[1]。模板[3]中使用了众所周知的密码套件名称。
Template text:
----------------------template begins here -------------------------
Template text:
----------------------template begins here -------------------------
template-type=tn3270e
模板类型=tn3270e
template-version=1.0
模板版本=1.0
template-description= The tn3270 service provides 3270 gateway access to an SNA network via the TN3270 protocol. The attributes reflect the types of 3270 devices, LU Pools, and load information available on the server.
template description=tn3270服务通过tn3270协议提供对SNA网络的3270网关访问。这些属性反映服务器上可用的3270设备、LU池和负载信息的类型。
template-url-syntax=
# service:tn3270://<hostname>:<port>
# <hostname>
# <port>
template-url-syntax=
# service:tn3270://<hostname>:<port>
# <hostname>
# <port>
load=integer # This is the load balancing quantity to use in determining the # least loaded TN3270E server to attach to for the service. The #range of valid values is an integral 0 to 100 with 0 indicating the #lowest possible load and 100 the highest
load=integer#这是用于确定要连接到服务的#负载最少的TN3270E服务器的负载平衡量。有效值的#范围为0到100的整数，其中0表示#可能的最低负载，100表示最高负载
LUPool=string X M L
# This attribute takes on one or more values as defined below.
# The <TAB> char. 0x09 is literal and will be used as a separator.
#
#
# <pool name> = <name> / <name> "<TAB>" <dev type>
# <name> = 1*ALPHANUM
# "3270DSC"
#
#
#
#
# Identifies the LU pool names of LU pools available for use on this
# service with the associated device types supported in each pool.
# Each value is a record where the first token is the pool name of
# the pool and the second token is a device type supported in that
# pool. A pool name without a device type indicates that LUs of
# unknown type are included in the pool. Records associated with a
# given pool name are repeated for each supported device type. A
# given pool is included in a registration request if any PU profile
# that contributes at least one LU to the pool is active on the
# server. The range of valid dev_types are:
#
# dev_type Meaning
#
LUPool=string X M L
# This attribute takes on one or more values as defined below.
# The <TAB> char. 0x09 is literal and will be used as a separator.
#
#
# <pool name> = <name> / <name> "<TAB>" <dev type>
# <name> = 1*ALPHANUM
# "3270DSC"
#
#
#
#
# Identifies the LU pool names of LU pools available for use on this
# service with the associated device types supported in each pool.
# Each value is a record where the first token is the pool name of
# the pool and the second token is a device type supported in that
# pool. A pool name without a device type indicates that LUs of
# unknown type are included in the pool. Records associated with a
# given pool name are repeated for each supported device type. A
# given pool is included in a registration request if any PU profile
# that contributes at least one LU to the pool is active on the
# server. The range of valid dev_types are:
#
# dev_type Meaning
#
# 3270002 Lu Type 2 Model 2 # # 3270003 Lu Type 2 Model 3 # # 3270004 Lu Type 2 Model 4 # # 3270005 Lu Type 2 Model 5 # # 3270DSC Printer LU #
#3270002 Lu类型2型号2##3270003 Lu类型2型号3##3270004 Lu类型2型号4##3270005 Lu类型2型号5##3270DSC打印机Lu#
BIND=keyword # The server supports the SNA bind image TN3270E function.
BIND=keyword#服务器支持SNA绑定映像TN3270E功能。
DATA=keyword # The non-SNA 3270 data stream is supported by server.
DATA=keyword#服务器支持非SNA 3270数据流。
RESPONSES=keyword # The server supports SNA response mode.
RESPONSES=keyword#服务器支持SNA响应模式。
SCS=keyword # The server supports SNA 3270 SCS data stream.
SCS=关键字#服务器支持SNA 3270 SCS数据流。
SYSREQ=keyword # The SYSREQ keyboard key is supported on server.
SYSREQ=关键字#服务器上支持SYSREQ键盘键。
RFC1576=keyword # RFC1576 options supported.
RFC1576=支持关键字#RFC1576选项。
RFC1646=keyword # RFC1646 options supported.
RFC1646=支持关键字#RFC1646选项。
RFC2355=keyword # RFC2355 options supported.
RFC2355=关键字#支持RFC2355选项。
security=string M # This is the security technique supported on the server. # The defined values are: NONE SSLV3
security=string M#这是服务器上支持的安全技术定义的值为：无SSLV3
Ciphersuites=string M # Cipher specifications supported by this server. # Additional values will be defined in future templates. NULL_NULL, NULL_MD5, NULL_SHA, RC4_MD5_EXPORT,
CipherSuite=字符串M#此服务器支持的密码规范。#其他值将在以后的模板中定义。空\u空，空\u MD5，空\u SHA，RC4\u MD5\u导出，
RC4_MD5_US, RC4_SHA_US, RC2_MD5_EXPORT, DES_SHA_EXPORT, TRIPLE_DES_SHA_US
RC4_MD5_US、RC4_SHA_US、RC2_MD5_EXPORT、DES_SHA_EXPORT、TRIPLE_DES SHA_US
platform=string X # This is the network operating system platform underlying the # advertising service. The defined values are: # # IW Server uses IntranetWare or NetWare operating system # # NT Server uses the Microsoft NT operating system # # OS2 Server uses the OS2 operating system # # AIX Server uses the AIX operating system # IW,NT,OS2,AIX
platform=string X#这是作为#广告服务基础的网络操作系统平台。定义的值是：##IW服务器使用内部网或NetWare操作系统##NT服务器使用Microsoft NT操作系统##OS2服务器使用OS2操作系统##AIX服务器使用AIX操作系统#IW、NT、OS2、AIX
protocol=string X
# This is the protocol(s) supported by the server providing this
# service. The defined values are:
#
# IP Server supports client connections over IP (TCP/IP or
# UDP/IP)
#
# IPX Server supports client connections over IPX (SPX/IPX)
#
IP,IPX
protocol=string X
# This is the protocol(s) supported by the server providing this
# service. The defined values are:
#
# IP Server supports client connections over IP (TCP/IP or
# UDP/IP)
#
# IPX Server supports client connections over IPX (SPX/IPX)
#
IP,IPX
server name=string # This is the name of the server that was configured during # installation.
server name=string#这是在#安装期间配置的服务器的名称。
release=string X # This is the version and release level of the server advertising # services. Its format is vv.rr.mm where "vv" is the major version # number, "rr" is the minor version number, and "mm" is the # modification level. All numbers are padded on the left with zeroes # to two characters. # Example: version 3, release 0, mod level 0 is "03.00.00"
release=string X#这是服务器广告服务的版本和发布级别。其格式为vv.rr.mm，其中“vv”为主要版本号，“rr”为次要版本号，“mm”为修改级别。所有数字的左边都用0填充，最多两个字符示例：版本3，版本0，修改级别0为“03.00.00”
------------------template ends here -------------------------------
------------------template ends here -------------------------------
The 'service:commserver:' template defined below conforms to the grammar described in "Service Templates and service: Schemes". Please refer to [2] for detailed explanation of the syntax.
下面定义的“service:commserver:”模板符合“service Templates and service:Schemes”中描述的语法。有关语法的详细解释，请参阅[2]。
Name of submitters: Jim Naugle <jnaugle@us.ibm.com> Gregg Ledford <gledford@zephyrcorp.com> K. Kasthurirangan <kasthuri@us.ibm.com> Language of service template: en Security Considerations: Service Location Protocol can help clients discover security services supported by the TN3270E server. If security services are important or required, using SLP authentication, and protected scopes [1] is recommended.
提交人姓名：Jim Naugle<jnaugle@us.ibm.com>格雷格·莱德福德<gledford@zephyrcorp.com>K.卡斯图里兰甘<kasthuri@us.ibm.com>服务语言模板：en安全注意事项：服务位置协议可以帮助客户端发现TN3270E服务器支持的安全服务。如果安全服务很重要或需要，建议使用SLP身份验证和受保护的作用域[1]。
Template text:
模板文本：
-------------------template begins below this line------------------
-------------------template begins below this line------------------
template-type=commserver
模板类型=commserver
template-version=1.0
模板版本=1.0
template-description= The server service type is registered whenever the communications software is loaded on the server. It describes generic attributes of the server. These attributes are also repeated on the other service types provided.
template description=每当在服务器上加载通信软件时，都会注册服务器服务类型。它描述了服务器的一般属性。这些属性也在提供的其他服务类型上重复。
template-url-syntax=
# service:commserver://<hostname>:<port>
# <hostname>
# <port>
template-url-syntax=
# service:commserver://<hostname>:<port>
# <hostname>
# <port>
platform=string X # This is the network operating system platform underlying the # advertising service. The defined values are: # # IW Server uses Novell IntranetWare or NetWare operating # system # NT Server uses the Microsoft NT operating system # # OS2 Server uses the OS2 operating system # # AIX Server uses the AIX operating system # IW,NT,OS2,AIX
platform=string X#这是作为#广告服务基础的网络操作系统平台。定义的值是：#IW服务器使用Novell IntranetWare或NetWare操作系统#NT服务器使用Microsoft NT操作系统##OS2服务器使用OS2操作系统#AIX服务器使用AIX操作系统#IW、NT、OS2、AIX
protocol=string X
# This is the protocol(s) supported by the server providing this
# service. The defined values are:
#
# IP Server supports client connections over IP (TCP/IP or
# UDP/IP)
#
# IPX Server supports client connections over IPX (SPX/IPX)
#
IP,IPX
protocol=string X
# This is the protocol(s) supported by the server providing this
# service. The defined values are:
#
# IP Server supports client connections over IP (TCP/IP or
# UDP/IP)
#
# IPX Server supports client connections over IPX (SPX/IPX)
#
IP,IPX
server name=string # This is the name of the server that was configured during # installation.
server name=string#这是在#安装期间配置的服务器的名称。
release=string X # This is the version and release level of the commserver # advertising services. Its format is vv.rr.mm where "vv" is the # major version number, "rr" is the minor version number, and "mm" # is the modification level. All numbers are padded on the left with # zeroes to two characters. # # Example: version 3, release 0, mod level 0 is "03.00.00"
release=string X#这是commserver广告服务的版本和发布级别。其格式为vv.rr.mm，其中“vv”为主要版本号，“rr”为次要版本号，“mm”为修改级别。所有数字的左边都用#0填充为两个字符。#示例：版本3，版本0，修改级别0为“03.00.00”
---------------------template ends above this line---------------------
---------------------template ends above this line---------------------
Jim Naugle <jnaugle@us.ibm.com>
Kasthuri Kasthurirangan <kasthuri@us.ibm.com>
Gregg Ledford <gledford@zephyrcorp.com>
Jim Naugle <jnaugle@us.ibm.com>
Kasthuri Kasthurirangan <kasthuri@us.ibm.com>
Gregg Ledford <gledford@zephyrcorp.com>
Service type templates provide information that is used to interpret information obtained by the Service Location Protocol. If these templates are modified or if false templates are distributed, services may not correctly register themselves, or clients might not be able to interpret service information.
服务类型模板提供用于解释服务位置协议获得的信息的信息。如果修改了这些模板或分发了错误的模板，则服务可能无法正确注册自身，或者客户端可能无法解释服务信息。
The service: URLs themselves specify the service access point and protocol for a particular service type. These service: URLs could be distributed and indicate the location of a service other than that normally wanted to used. SLP [1] provides an authentication mechanism that allows service: URLs of registered services to be signed and for the signatures to be verified by clients.
服务：URL本身为特定服务类型指定服务访问点和协议。这些服务：URL可以是分布式的，并指示服务的位置，而不是通常想要使用的位置。SLP[1]提供了一种身份验证机制，允许对服务：注册服务的URL进行签名，并允许客户端验证签名。
Service Location Protocol can help clients discover security services supported by the TN3270E server. If security services are important or required, using SLP authentication, and protected scopes [1] is recommended.
服务位置协议可以帮助客户端发现TN3270E服务器支持的安全服务。如果安全服务很重要或需要，建议使用SLP身份验证和受保护的作用域[1]。
URL: service:tn3270://<addr-spec>:<port-number> Attributes:
URL:service:tn3270://<addr spec>：<port number>属性：
[(SCOPE=<string>),]
[(SCOPE=<string>),]
(RELEASE=03.00.00),
（发布时间=03.00.00），
(PLATFORM=IW),
（平台=IW），
(PROTOCOL=IP),
（协议=IP），
(SERVERNAME=<string>),
（服务器名=<string>），
(LOAD=<integer 0 to 100>),
（加载=<整数0到100>），
[(LUPOOL=pool-name0/tANY,
[（LUPOOL=pool-name0/tANY，
pool-name1/tdevice_type1,
池名1/t设备类型1，
pool-name2/tdevice-type2, ...
池名称2/t设备类型2。。。
pool-namen/tdevice-typen)]
池名称n/t设备类型n）]
BIND,
绑定
DATA,
数据
RESPONSES,
响应，
SCS,
公务员事务局局长，
SYSREQ,
SYSREQ，
(SECURITY=NONE),
（安全=无），
RFC1576,
RFC1576，
RFC1646,
RFC1646，
RFC2355
RFC2355
URL:service:commserver://<addr-spec>:<port-number>
URL:service:commserver://<addr-spec>:<port-number>
Attributes: [(SCOPE=<string>),]
Attributes: [(SCOPE=<string>),]
(RELEASE=03.00.00),
（发布时间=03.00.00），
(PLATFORM=IW),
（平台=IW），
(PROTOCOL=IP),
（协议=IP），
(SERVERNAME=<string>)
(SERVERNAME=<string>)
[1] Veizades, J., Guttman, E., Perkins, C., and S. Kaplan, "Service Location Protocol", RFC 2165, July 1997.
[1] Veizades，J.，Guttman，E.，Perkins，C.，和S.Kaplan，“服务位置协议”，RFC 21651997年7月。
[2] Guttman, E., Perkins, C. and J. Kempf, "Service Templates and service: Schemes", RFC 2609, June 1999.
[2] Guttman，E.，Perkins，C.和J.Kempf，“服务模板和服务：方案”，RFC 26091999年6月。
[3] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC 2246, January 1999.
[3] Dierks，T.和C.Allen，“TLS协议1.0版”，RFC 2246，1999年1月。
[4] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service Location Protocol Version 2", RFC 2608, June 1999.
[4] Guttman，E.，Perkins，C.，Veizades，J.和M.Day，“服务位置协议版本2”，RFC 26081999年6月。
[5] Kempf, J. and E. Guttman, "An API for Service Location", RFC 2614, June 1999.
[5] Kempf，J.和E.Guttman，“服务位置的API”，RFC 26141999年6月。
[6] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[6] Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
Jim Naugle IBM P.O. Box 12195 Research Triangle Park, N.C. 27709-2195 USA
Jim Naugle IBM美国北卡罗来纳州三角研究公园12195号邮政信箱，邮编27709-2195
Phone: (919) 254-8789 EMail: jnaugle@us.ibm.com
电话：（919）254-8789电子邮件：jnaugle@us.ibm.com
Kasthuri Kasthurirangan IBM P.O. Box 12195 Research Triangle Park, N.C. 27709-2195 USA
美国北卡罗来纳州三角研究公园12195号邮政信箱，邮编27709-2195
Phone: (919) 254-5721 EMail: kasthuri@us.ibm.com
电话：（919）254-5721电子邮件：kasthuri@us.ibm.com
Gregg Ledford Zephyr Development Corporation 8 Greenway Plaza Suite 1400 Houston, Texas 77046 USA
美国德克萨斯州休斯顿格林威广场8号1400室格雷格·莱德福德西风开发公司，邮编：77046
Phone: (713) 623-0089 EMail: gledford@zephyrcorp.com
电话：（713）623-0089电子邮件：gledford@zephyrcorp.com
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编辑功能的资金目前由互联网协会提供。