Network Working Group D. Peterson
Request for Comments: 3822 Computer Network Technology (CNT)
Category: Standards Track July 2004
Network Working Group D. Peterson
Request for Comments: 3822 Computer Network Technology (CNT)
Category: Standards Track July 2004
Finding Fibre Channel over TCP/IP (FCIP) Entities Using Service Location Protocol version 2 (SLPv2)
使用服务位置协议版本2（SLPv2）查找TCP/IP上的光纤通道（FCIP）实体
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 (2004).
版权所有（C）互联网协会（2004年）。
Abstract
摘要
This document defines the use of Service Location Protocol version 2 (SLPv2) by Fibre Channel over TCP/IP (FCIP) Entities.
本文档定义了TCP/IP光纤通道（FCIP）实体对服务位置协议版本2（SLPv2）的使用。
This document describes the use of the Service Location Protocol version 2 in performing dynamic discovery of participating Fibre Channel over TCP/IP (FCIP) Entities. Implementation guidelines, service type templates, and security considerations are specified.
本文档介绍了服务位置协议版本2在执行TCP/IP光纤通道（FCIP）参与实体的动态发现时的使用。指定了实现准则、服务类型模板和安全注意事项。
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 [RFC2119].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“应”、“不应”、“建议”、“可”和“可选”应按照[RFC2119]中所述进行解释。
Here are some definitions that may aid readers that are unfamiliar with either SLP or FCIP. Some of these definitions have been reproduced from [RFC2608] and [RFC3105].
以下是一些可能有助于不熟悉SLP或FCIP的读者的定义。其中一些定义已从[RFC2608]和[RFC3105]中复制。
User Agent (UA) A process working on the client's behalf to establish contact with some service. The UA retrieves service information from the Service Agents or Directory Agents.
用户代理（UA）代表客户与某些服务建立联系的过程。UA从服务代理或目录代理检索服务信息。
Service Agent (SA) A process working on behalf of one or more services to advertise the services and their capabilities.
服务代理（SA）代表一个或多个服务宣传服务及其功能的过程。
Directory Agent (DA) A process which collects service advertisements. There can only be one DA present per given host.
目录代理（DA）收集服务广告的进程。每个给定主机只能有一个DA。
Scope A named 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、属性和生存期（指示广告有效的时间），提供特定服务的服务访问信息和功能描述。
FCIP Entity The principle FCIP interface point to the IP network.
FCIP实体FCIP接口主要指向IP网络。
FCIP Entity Name The world wide name of the switch if the FCIP Entity resides in a switch or the world wide node name of the associated Nx_Port.
FCIP实体名称如果FCIP实体位于交换机中，则该交换机的全球通用名称或关联Nx_端口的全球通用节点名称。
FCIP Discovery Domain The FCIP Discovery Domain specifies which FCIP Entities are allowed to discover each other within the bounds of the scope.
FCIP发现域FCIP发现域指定允许哪些FCIP实体在范围内相互发现。
At least two FCIP Entities must be involved in the entity discovery process. The end result is that an FCIP Entity will discover one or more peer FCIP Entities.
实体发现过程中必须至少涉及两个FCIP实体。最终结果是FCIP实体将发现一个或多个对等FCIP实体。
Figure 1 shows the relationship between FCIP Entities and their associated SLPv2 agents.
图1显示了FCIP实体与其关联的SLPv2代理之间的关系。
+--------------------------------------+
| FCIP Entity |
+----------------------------------+ |
| FCIP Control and Services Module | |
+----------------+ | |
| SA | UA | | |
+----------------+-----------------+ |
| TCP/UDP/IP | |
+----------------+-----------------+ |
| Interface | |
| 192.0.2.10 | |
+----------------+-----------------+---|
|
+------------+ |
| SLPv2 DA |----+ IP Network
+------------+ |
|
+----------------+-----------------+---|
| Interface | |
| 192.0.2.20 | |
+----------------+-----------------+ |
| TCP/UDP/IP | |
+----------------+-----------------+ |
| SA | UA | | |
+----------------+ | |
| FCIP Control and Services Module | |
+--------------------------------- + |
| FCIP Entity |
+--------------------------------------+
+--------------------------------------+
| FCIP Entity |
+----------------------------------+ |
| FCIP Control and Services Module | |
+----------------+ | |
| SA | UA | | |
+----------------+-----------------+ |
| TCP/UDP/IP | |
+----------------+-----------------+ |
| Interface | |
| 192.0.2.10 | |
+----------------+-----------------+---|
|
+------------+ |
| SLPv2 DA |----+ IP Network
+------------+ |
|
+----------------+-----------------+---|
| Interface | |
| 192.0.2.20 | |
+----------------+-----------------+ |
| TCP/UDP/IP | |
+----------------+-----------------+ |
| SA | UA | | |
+----------------+ | |
| FCIP Control and Services Module | |
+--------------------------------- + |
| FCIP Entity |
+--------------------------------------+
Figure 1: FCIP Entity and SLPv2 Agent Relationship.
图1:FCIP实体和SLPv2代理关系。
As indicated in Figure 1, each FCIP Entity contains an FCIP Control and Services Module that interfaces to an SLPv2 SA and UA.
如图1所示，每个FCIP实体包含一个与SLPv2 SA和UA接口的FCIP控制和服务模块。
The SA constructs a service advertisement of the type "service:fcip:entity" for each of the service URLs it wishes to register. The service advertisement contains a lifetime, along with other attributes defined in the service template.
SA为其希望注册的每个服务URL构造类型为“service:fcip:entity”的服务公告。服务公告包含生存期以及服务模板中定义的其他属性。
The remainder of the discovery process is identical to that used by any client/server pair implementing SLPv2:
发现过程的其余部分与实现SLPv2的任何客户机/服务器对使用的过程相同：
1. If an SLPv2 DA is found [RFC2608], the SA contacts the DA and registers the service advertisement. Whether or not one or more SLPv2 DAs are discovered, the SA maintains the service advertisement itself and answers multicast UA queries directly.
1. 如果找到SLPv2 DA[RFC2608]，SA将联系DA并注册服务公告。无论是否发现一个或多个SLPv2 DAs，SA都会维护服务广告本身并直接回答多播UA查询。
2. When the FCIP Entity requires contact information for a peer FCIP Entity, the UA either contacts the DA using unicast or the SA using multicast using an SLPv2 service request. The UA service request includes a query, based on the attributes, to indicate the characteristics of the peer FCIP Entities it requires.
2. 当FCIP实体需要对等FCIP实体的联系信息时，UA使用单播联系DA，或使用SLPv2服务请求使用多播联系SA。UA服务请求包括基于属性的查询，以指示其所需对等FCIP实体的特征。
3. Once the UA has the IP address and port number of a peer FCIP Entity, it may begin the normal connection procedure, as described in [RFC3821], to a peer FCIP Entity.
3. 一旦UA拥有对等FCIP实体的IP地址和端口号，它可以开始到对等FCIP实体的正常连接过程，如[RFC3821]中所述。
The use of a DA is RECOMMENDED for SLPv2 operations in an FCIP environment.
建议将DA用于FCIP环境中的SLPv2操作。
The concept of a discovery domain provides further granularity of control of allowed discovery between FCIP Entities within a specific SLPv2 scope.
发现域的概念为特定SLPv2范围内FCIP实体之间允许的发现提供了进一步的粒度控制。
Figure 2 shows an example relationship between FCIP Entities and their associated discovery domains within a specified SLPv2 scope.
图2显示了指定SLPv2范围内FCIP实体及其关联发现域之间的关系示例。
=================fcip=======================================
= =
= *************************purple*********************** =
= * * =
= * #####orange###################### * =
= * # ------------ //////blue//////+/////////////// * =
= * # | FCIP | / # / * =
= * # | Entity A | / # / * =
= * # ------------ / # ------------ / * =
= * # / # | FCIP | / * =
= * # / # | Entity C | / * =
= * # / ------------ # ------------ / * =
= * # / | FCIP | # / * =
= * # / | Entity B | # / * =
= * # / ------------ # / * =
= * ################+################ / * =
= * //////////////////////////////// * =
= * * =
= ****************************************************** =
= =
============================================================
=================fcip=======================================
= =
= *************************purple*********************** =
= * * =
= * #####orange###################### * =
= * # ------------ //////blue//////+/////////////// * =
= * # | FCIP | / # / * =
= * # | Entity A | / # / * =
= * # ------------ / # ------------ / * =
= * # / # | FCIP | / * =
= * # / # | Entity C | / * =
= * # / ------------ # ------------ / * =
= * # / | FCIP | # / * =
= * # / | Entity B | # / * =
= * # / ------------ # / * =
= * ################+################ / * =
= * //////////////////////////////// * =
= * * =
= ****************************************************** =
= =
============================================================
Figure 2: FCIP Entity and Discovery Domain Example.
图2:FCIP实体和发现域示例。
Within the specified scope "fcip", the administrator has defined a discovery domain "purple", allowing FCIP Entities A, B, and C to discover each other. This discovery domain is illustrated using the "*" character.
在指定的范围“fcip”内，管理员定义了一个发现域“紫色”，允许fcip实体a、B和C相互发现。此发现域使用“*”字符进行说明。
Within the specified scope "fcip", the administrator has defined a discovery domain "orange", allowing FCIP Entity A to discover FCIP Entity B, but not FCIP Entity C. This discovery domain is illustrated using the "#" character.
在指定的范围“fcip”内，管理员定义了一个发现域“橙色”，允许fcip实体a发现fcip实体B，但不允许fcip实体C。此发现域使用“#”字符进行说明。
Within the specified scope "fcip", the administrator has defined a discovery domain "blue", allowing FCIP Entity C to discover FCIP Entity B, but not FCIP Entity A. This discovery domain is illustrated using the "/" character.
在指定的范围“fcip”内，管理员定义了一个发现域“蓝色”，允许fcip实体C发现fcip实体B，但不允许fcip实体a。此发现域使用“/”字符进行说明。
For the example relationship shown in Figure 2, the value of the fcip-discovery-domain attribute for each FCIP Entity is as follows:
对于图2所示的示例关系，每个fcip实体的fcip发现域属性的值如下所示：
FCIP Entity A = orange,purple
FCIP实体A=橙色、紫色
FCIP Entity B = orange,blue,purple
FCIP实体B=橙色、蓝色、紫色
FCIP Entity C = blue,purple
FCIP实体C=蓝色、紫色
Two templates are provided: an FCIP Entity template, and an abstract template to provide a means of adding other FCIP related templates in the future.
提供了两个模板：FCIP实体模板和抽象模板，以提供将来添加其他FCIP相关模板的方法。
This template defines the abstract service "service:fcip". It is used as a top-level service to encapsulate all other FCIP related services.
此模板定义抽象服务“service:fcip”。它用作顶级服务来封装所有其他FCIP相关服务。
Name of submitter: David Peterson Language of service template: en Security Considerations: see section 6.
提交人姓名：David Peterson服务语言模板：en安全注意事项：见第6节。
Template Text:
-------------------------template begins here-----------------------
template-type=fcip
Template Text:
-------------------------template begins here-----------------------
template-type=fcip
template-version=0.1
模板版本=0.1
template-description= This is an abstract service type. The purpose of the fcip service
template description=这是一种抽象服务类型。fcip服务的目的
type is to encompass all of the services used to support the FCIP protocol.
类型包括用于支持FCIP协议的所有服务。
template-url-syntax =
模板url语法=
url-path= ; Depends on the concrete service type.
url路径=；取决于具体的服务类型。
--------------------------template ends here------------------------
--------------------------template ends here------------------------
This template defines the service "service:fcip:entity". A device containing FCIP Entities that wishes to have them discovered via SLPv2 would register each of them with each of their addresses, as this service type.
此模板定义服务“service:fcip:entity”。包含希望通过SLPv2发现的FCIP实体的设备将使用每个地址将每个实体注册为此服务类型。
FCIP Entities wishing to discover other FCIP Entities in this manner will generally use one of the following example query strings:
希望以这种方式发现其他FCIP实体的FCIP实体通常会使用以下示例查询字符串之一：
1. Find a specific FCIP Entity, given its FCIP Entity Name:
1. 查找特定FCIP实体，给定其FCIP实体名称：
Service: service:fcip:entity
Scope: fcip-entity-scope-list
Query: (fcip-entity-name=\ff\10\00\00\60\69\20\34\0C)
Service: service:fcip:entity
Scope: fcip-entity-scope-list
Query: (fcip-entity-name=\ff\10\00\00\60\69\20\34\0C)
2. Find all of the FCIP Entities within a specified FCIP Discovery Domain:
2. 查找指定FCIP发现域中的所有FCIP实体：
Service: service:fcip:entity
Scope: fcip-entity-scope-list
Query: (fcip-discovery-domain=fcip-discovery-domain-name)
Service: service:fcip:entity
Scope: fcip-entity-scope-list
Query: (fcip-discovery-domain=fcip-discovery-domain-name)
3. In addition, a management application may wish to discover all FCIP Entities:
3. 此外，管理应用程序可能希望发现所有FCIP实体：
Service: service:fcip:entity
Scope: management-service-scope-list
Query: none
Service: service:fcip:entity
Scope: management-service-scope-list
Query: none
Name of submitter: David Peterson Language of service template: en Security Considerations: see section 6.
提交人姓名：David Peterson服务语言模板：en安全注意事项：见第6节。
Template Text:
-------------------------template begins here-----------------------
template-type=fcip:entity
Template Text:
-------------------------template begins here-----------------------
template-type=fcip:entity
template-version=0.1
模板版本=0.1
template-description= This is a concrete service type. The fcip:entity service type is used to register individual FCIP Entity addresses to be discovered by others. UAs will generally search for these by including one of the following: - the FCIP Entity Name for which an address is needed - the FCIP Discovery Domain Name for which addresses are requested - the service URL
template description=这是一种具体的服务类型。fcip:entity服务类型用于注册由其他人发现的单个fcip实体地址。UAs通常会通过以下方式之一进行搜索：-需要地址的FCIP实体名称-请求地址的FCIP发现域名-服务URL
template-url-syntax =
url-path = hostport
hostport = host [ ":" port ]
host = hostname / hostnumber
hostname = *( domainlabel "." ) toplabel
alphanum = ALPHA / DIGIT
domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum
toplabel = ALPHA / ALPHA * [ alphanum / "-" ] alphanum
hostnumber = ipv4-number
ipv4-number = 1*3DIGIT 3("." 1*3DIGIT)
port = 1*DIGIT
template-url-syntax =
url-path = hostport
hostport = host [ ":" port ]
host = hostname / hostnumber
hostname = *( domainlabel "." ) toplabel
alphanum = ALPHA / DIGIT
domainlabel = alphanum / alphanum * [alphanum / "-"] alphanum
toplabel = ALPHA / ALPHA * [ alphanum / "-" ] alphanum
hostnumber = ipv4-number
ipv4-number = 1*3DIGIT 3("." 1*3DIGIT)
port = 1*DIGIT
;
; A DNS host name should be used along with the well-known
; IANA FCIP port number for operation with NAT/NAPT devices.
;
; Examples:
; service:fcip:entity://host.example.com
; service:fcip:entity://192.0.2.0:4000
;
;
; A DNS host name should be used along with the well-known
; IANA FCIP port number for operation with NAT/NAPT devices.
;
; Examples:
; service:fcip:entity://host.example.com
; service:fcip:entity://192.0.2.0:4000
;
fcip-entity-name = opaque L # If the FCIP Entity is a VE_Port/B_Access implementation [FC-BB-2] # residing in a switch, the fcip-entity-name is the Fibre Channel # Switch Name [FC-SW-3]. Otherwise, the fcip-entity-name is the # Fibre Channel Node Name [FC-FS] of the port (e.g., an Nx_Port) # associated with the FCIP Entity. # An entity representing multiple endpoints must register each of # the endpoints using SLPv2.
fcip实体名称=不透明L#如果fcip实体是驻留在交换机中的VE_端口/B_访问实现[FC-BB-2]#，则fcip实体名称为光纤通道#交换机名称[FC-SW-3]。否则，fcip实体名称是与fcip实体关联的端口（例如Nx#U端口）的#光纤通道节点名称[FC-FS]。#表示多个端点的实体必须使用SLPv2注册每个端点。
transports = string M L tcp # This is a list of transport protocols that the registered entity # supports. FCIP is currently supported over TCP only. tcp
transports=string M L tcp#这是注册实体支持的传输协议列表。目前仅通过TCP支持FCIP。tcp
mgmt-entity = string M O L
# The URL's of the management interface(s) are appropriate for SNMP,
# web-based, or telnet management of the FCIP Entity.
# Examples:
# http://fcipentity.example.com:1080/
# telnet://fcipentity.example.com
mgmt-entity = string M O L
# The URL's of the management interface(s) are appropriate for SNMP,
# web-based, or telnet management of the FCIP Entity.
# Examples:
# http://fcipentity.example.com:1080/
# telnet://fcipentity.example.com
fcip-discovery-domain = string M L fcip # The fcip-discovery-domain string contains the name(s) of the FCIP # discovery domain(s) to which this FCIP Entity belongs.
fcip发现域=字符串M L fcip#fcip发现域字符串包含此fcip实体所属的fcip#发现域的名称。
--------------------------template ends here------------------------
--------------------------template ends here------------------------
The SLPv2 security model as specified in [RFC2608] does not provide confidentiality, but does provide an authentication mechanism for UAs to assure that service advertisements only come from trusted SAs with the exception that it does not provide a mechanism for authenticating "zero-result responses". See [RFC3723] for a discussion of the SLPv2 [RFC2608] security model.
[RFC2608]中规定的SLPv2安全模型不提供机密性，但为UAs提供了身份验证机制，以确保服务广告仅来自受信任的SA，但不提供验证“零结果响应”的机制。有关SLPv2[RFC2608]安全模型的讨论，请参见[RFC3723]。
Once an FCIP Entity is discovered, authentication and authorization are handled by the FCIP protocol. It is the responsibility of the providers of these services to ensure that an inappropriately advertised or discovered service does not compromise their security.
一旦发现FCIP实体，身份验证和授权将由FCIP协议处理。这些服务的提供商有责任确保不适当的广告或发现服务不会损害其安全性。
When no security is used for SLPv2, there is a risk of distribution of false discovery information. The primary countermeasure for this risk is authentication. When this risk is a significant concern, IPsec SAs SHOULD be used for FCIP traffic subject to this risk to ensure that FCIP traffic only flows between endpoints that have participated in IKE authentication. For example, if an attacker distributes discovery information falsely claiming that it is an FCIP endpoint, it will lack the secret information necessary to successfully complete IKE authentication, and hence will be prevented from falsely sending or receiving FCIP traffic.
当SLPv2没有使用安全性时，存在分发错误发现信息的风险。针对这种风险的主要对策是身份验证。当此风险是一个重大问题时，应将IPsec SAs用于存在此风险的FCIP流量，以确保FCIP流量仅在参与IKE身份验证的端点之间流动。例如，如果攻击者错误地分发发现信息，声称它是FCIP端点，那么它将缺少成功完成IKE身份验证所需的机密信息，因此将防止错误地发送或接收FCIP流量。
There remains a risk of a denial of service attack based on repeated use of false discovery information that will cause the initiation of IKE negotiation. The countermeasures for this are administrative configuration of each FCIP Entity to limit the peers that it is willing to communicate with (i.e., by IP address range and/or DNS domain), and maintenance of a negative authentication cache to avoid repeatedly contacting an FCIP Entity that fails to authenticate. These three measures (i.e., IP address range limits, DNS domain limits, negative authentication cache) MUST be implemented.
仍然存在基于重复使用虚假发现信息的拒绝服务攻击的风险，这将导致发起IKE协商。对此的对策是对每个FCIP实体进行管理配置，以限制其愿意与之通信的对等方（即，通过IP地址范围和/或DNS域），并维护负面身份验证缓存，以避免重复接触无法进行身份验证的FCIP实体。必须实施这三项措施（即IP地址范围限制、DNS域限制、负面身份验证缓存）。
Security for SLPv2 in an IP storage environment is specified in [RFC3723]. IPsec is mandatory-to-implement for IPS clients and servers. Thus, all IP storage clients, including those invoking SLP, can be assumed to support IPsec. SLP servers, however, cannot be assumed to implement IPsec, since there is no such requirement in standard SLP. In particular, SLP Directory Agents (DA) may be running on machines other than those running the IPS protocols.
[RFC3723]中规定了IP存储环境中SLPv2的安全性。IPsec是IPS客户端和服务器必须实现的。因此，可以假定所有IP存储客户端（包括调用SLP的客户端）都支持IPsec。然而，不能假设SLP服务器实现IPsec，因为标准SLP中没有这样的要求。特别是，SLP目录代理（DA）可能在运行IPS协议的机器以外的机器上运行。
IPsec SHOULD be implemented for SLPv2 as specified in [RFC3723]; this includes ESP with a non-null transform to provide both authentication and confidentiality.
应按照[RFC3723]中的规定为SLPv2实施IPsec；这包括带有非空转换的ESP，以提供身份验证和机密性。
Because the IP storage services have their own authentication capabilities when located, SLPv2 authentication is OPTIONAL to implement and use (as discussed in more detail in [RFC3723]).
由于IP存储服务在定位时具有自己的身份验证功能，因此SLPv2身份验证是可选的（如[RFC3723]中更详细的讨论）。
This document describes two SLP Templates in Section 5. They should be registered in the IANA "SVRLOC Templates" registry. This process is described in the IANA Considerations section of [RFC2609].
本文档在第5节中介绍了两个SLP模板。它们应在IANA“SVRLOC模板”注册表中注册。[RFC2609]的IANA注意事项部分描述了该过程。
SLP allows internationalized strings to be registered and retrieved. Attributes in the template that are not marked with an 'L' (literal) will be registered in a localized manner. An "en" (English) localization MUST be registered, and others MAY be registered.
SLP允许注册和检索国际化字符串。模板中未标记为“L”（文字）的属性将以本地化方式注册。必须注册“en”（英语）本地化，其他本地化也可以注册。
This document describes how SLPv2 can be used by FCIP Entities to find other FCIP Entities. Service type templates for FCIP Entities are presented.
本文档描述了FCIP实体如何使用SLPv2查找其他FCIP实体。提供了FCIP实体的服务类型模板。
This document was produced by the FCIP discovery team, including Todd Sperry (Adaptec), Larry Lamars (SanValley), Robert Snively (Brocade), Ravi Natarajan (Lightsand), Anil Rijhsinghani (McData), and Venkat Rangan (Rhapsody Networks). Thanks also to Mark Bakke (Cisco) for initial help and consultation, and David Black, Erik Guttman, and James Kempf for assistance during expert review.
本文件由FCIP发现团队制作，包括Todd Sperry（Adaptec）、Larry Lamars（SanValley）、Robert Snifly（Brocade）、Ravi Natarajan（Lightsand）、Anil Rijhsinghani（McData）和Venkat Rangan（Rhapsody Networks）。还要感谢Mark Bakke（思科）提供的初步帮助和咨询，以及David Black、Erik Guttman和James Kempf在专家评审期间提供的帮助。
[RFC2608] Guttman, E., Perkins, C., Veizades, J. and M. Day, "Service Location Protocol, Version 2", RFC 2608, June 1999.
[RFC2608]Guttman，E.，Perkins，C.，Veizades，J.和M.Day，“服务位置协议，版本2”，RFC 26081999年6月。
[RFC2609] Guttman, E., Perkins, C. and J. Kempf, "Service Templates and Service: Schemes", RFC 2609, June 1999.
[RFC2609]Guttman，E.，Perkins，C.和J.Kempf，“服务模板和服务：方案”，RFC 26091999年6月。
[RFC2119] Bradner, S., "Key Words for Use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2119]Bradner，S.，“RFC中用于表示需求水平的关键词”，BCP 14，RFC 2119，1997年3月。
[RFC3821] Rajagopal, M., Bhagwat, R. and R. Weber, "Fibre Channel Over TCP/IP (FCIP)", RFC 3821, July 2004.
[RFC3821]Rajagopal，M.，Bhagwat，R.和R.Weber，“TCP/IP上的光纤通道（FCIP）”，RFC 38212004年7月。
[FC-SW-3] Fibre Channel Switch Fabric - 3, ANSI INCITS 384-2004.
[FC-SW-3]光纤通道交换机结构-3，ANSI INCITS 384-2004。
[FC-BB-2] Fibre Channel Backbone - 2, ANSI INCITS 372-2003.
[FC-BB-2]光纤通道主干-2，ANSI INCITS 372-2003。
[FC-FS] Fibre Channel Framing and Signaling, T11 Project 1331-D, Rev 1.90, April 9, 2003.
[FC-FS]光纤通道成帧和信令，T11项目1331-D，版本1.902003年4月9日。
[RFC3723] Aboba, B., Tseng, J., Walker, J., Rangan, V. and F. Travostino, "Securing Block Storage Protocols over IP", RFC 3723, April 2004.
[RFC3723]Aboba，B.，Tseng，J.，Walker，J.，Rangan，V.和F.Travostino，“通过IP保护块存储协议”，RFC 37232004年4月。
[RFC3105] Kempf, J. and G. Montenegro, "Finding an RSIP Server with SLP", RFC 3105, October 2001.
[RFC3105]Kempf，J.和G.黑山，“使用SLP查找RSIP服务器”，RFC 3105，2001年10月。
David Peterson Computer Network Technology (CNT) 6000 Nathan Lane North Minneapolis, MN 55442
David Peterson计算机网络技术公司（CNT）明尼苏达州明尼阿波利斯市北内森巷6000号，邮编55442
Phone: 763-268-6139 EMail: dap@cnt.com
电话：763-268-6139电子邮件：dap@cnt.com
Copyright (C) The Internet Society (2004). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights.
版权所有（C）互联网协会（2004年）。本文件受BCP 78中包含的权利、许可和限制的约束，除其中规定外，作者保留其所有权利。
This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM 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.
本文件及其包含的信息是按“原样”提供的，贡献者、他/她所代表或赞助的组织（如有）、互联网协会和互联网工程任务组不承担任何明示或暗示的担保，包括但不限于任何保证，即使用本文中的信息不会侵犯任何权利，或对适销性或特定用途适用性的任何默示保证。
Intellectual Property
知识产权
The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79.
IETF对可能声称与本文件所述技术的实施或使用有关的任何知识产权或其他权利的有效性或范围，或此类权利下的任何许可可能或可能不可用的程度，不采取任何立场；它也不表示它已作出任何独立努力来确定任何此类权利。有关RFC文件中权利的程序信息，请参见BCP 78和BCP 79。
Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr.
向IETF秘书处披露的知识产权副本和任何许可证保证，或本规范实施者或用户试图获得使用此类专有权利的一般许可证或许可的结果，可从IETF在线知识产权存储库获取，网址为http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org.
IETF邀请任何相关方提请其注意任何版权、专利或专利申请，或其他可能涵盖实施本标准所需技术的专有权利。请将信息发送至IETF的IETF-ipr@ietf.org.
Acknowledgement
确认
Funding for the RFC Editor function is currently provided by the Internet Society.
RFC编辑功能的资金目前由互联网协会提供。