Network Working Group M. Davison
Request for Comments: 2603 Cisco Systems
Category: Standards Track June 1999
Network Working Group M. Davison
Request for Comments: 2603 Cisco Systems
Category: Standards Track June 1999
ILMI-Based Server Discovery for NHRP
基于ILMI的NHRP服务器发现
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 (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
Abstract
摘要
This memo defines how ILMI-based Server Discovery, which provides a method for ATM-attached hosts and routers to dynamically determine the ATM addresses of servers, shall be used to locate NHRP servers.
本备忘录定义了如何使用基于ILMI的服务器发现来定位NHRP服务器，该发现为ATM连接的主机和路由器提供了一种动态确定服务器ATM地址的方法。
Presently, configuring a host or router to use NHRP [1] is cumbersome and error-prone since it requires at least one ATM address to be statically configured on each host or router in the network. Further, it is impossible to implement a diskless host to use NHRP since local configuration is required. ILMI-based Server Discovery, hereafter referred to as "server discovery," provides a solution to these problems.
目前，将主机或路由器配置为使用NHRP[1]非常麻烦且容易出错，因为它要求在网络中的每个主机或路由器上至少静态配置一个ATM地址。此外，由于需要本地配置，因此不可能实现使用NHRP的无盘主机。基于ILMI的服务器发现（以下简称“服务器发现”）为这些问题提供了解决方案。
A brief overview of the Integrated Local Management Interface (ILMI) and the Service Registry MIB, as defined by the ATM Forum, are provided in this memo. The reader should consult [2] for a complete description of ILMI and this MIB, but the information contained here is sufficient for an understanding of its use to support NHRP server discovery.
本备忘录简要概述了ATM论坛定义的集成本地管理接口（ILMI）和服务注册MIB。读者应参考[2]了解ILMI和该MIB的完整描述，但此处包含的信息足以理解其用于支持NHRP服务器发现的用途。
The Integrated Local Management Interface (ILMI) [2] provides a mechanism for ATM-attached devices, such as hosts, routers, and ATM switches, to transfer management information. It is based on the Simple Network Management Protocol (SNMP), Version 1, and supports
集成本地管理接口（ILMI）[2]为ATM连接的设备（如主机、路由器和ATM交换机）提供了传输管理信息的机制。它基于简单网络管理协议（SNMP）版本1，并支持
get, get-next, set and trap operations.
获取、获取下一步、设置和陷阱操作。
The ILMI specification designates the switch side of the ATM link as the 'network side' and the host/router side of the ATM link as the ' user side.' The Service Registry MIB, which is outlined in Section 3, is implmented on the network side and is queried from the user side.
ILMI规范将ATM链路的交换机端指定为“网络端”，将ATM链路的主机/路由器端指定为“用户端”。第3节中概述的服务注册MIB在网络端实现，并从用户端查询。
Server discovery utilizes the Service Registry MIB defined by the ATM Forum in ILMI Specification Version 4.0 [2]. To support the existing framework for IP over ATM, ATM switches must support the Service Registry MIB.
服务器发现利用由ATM论坛在ILMI规范版本4.0[2]中定义的服务注册表MIB。为了支持现有的IP over ATM框架，ATM交换机必须支持服务注册MIB。
A row in the service registry table [2] is defined as:
服务注册表表[2]中的一行定义为：
AtmfSrvcRegEntry ::= SEQUENCE {
atmfSrvcRegPort INTEGER,
atmfSrvcRegServiceID OBJECT IDENTIFIER,
atmfSrvcRegATMAddress AtmAddress,
atmfSrvcRegAddressIndex INTEGER,
atmfSrvcRegParm1 OCTET STRING
}
AtmfSrvcRegEntry ::= SEQUENCE {
atmfSrvcRegPort INTEGER,
atmfSrvcRegServiceID OBJECT IDENTIFIER,
atmfSrvcRegATMAddress AtmAddress,
atmfSrvcRegAddressIndex INTEGER,
atmfSrvcRegParm1 OCTET STRING
}
The definition of each field in this structure is:
此结构中每个字段的定义如下：
atmfSrvcRegPort - The ATM port number for which this entry contains management information. The value of zero may be used to indicate the ATM interface over which a management request was received.
atmfSrvcRegPort—此条目包含其管理信息的ATM端口号。零值可用于指示接收到管理请求的ATM接口。
atmfSrvcRegServiceID - This is the service identifier that uniquely identifies the type of service at the address provided in the table. (See Section 3.2 for NHRP OID.)
atmfSrvcRegServiceID—这是唯一标识表中提供地址处服务类型的服务标识符。（NHRP OID见第3.2节。）
atmfSrvcRegATMAddress - This is the full address of the service. The ATM client will use this address to establish a connection with the service.
ATMFSRVCregatAddress-这是服务的完整地址。ATM客户端将使用此地址与服务建立连接。
atmfSrvcRegAddressIndex - An arbitrary integer to differentiate multiple rows containing different ATM addresses for the same service on the same port.
ATMFSRVCREGADDRESINDEX-一个任意整数，用于区分同一端口上同一服务包含不同ATM地址的多行。
atmfSrvcRegParm1 - An octet string whose size and meaning is determined by the value of atmfSrvcRegServiceID.
atmfSrvcRegParm1-一个八位字节字符串，其大小和含义由atmfSrvcRegServiceID的值决定。
The service registry table is indexed by atmfSrvcRegPort, atmfSrvcRegServiceID and atmfSrvcRegAddressIndex.
服务注册表表由atmfSrvcRegPort、atmfSrvcRegServiceID和ATMFSRVCREGADDRESINDEX编制索引。
A generic parameter string is defined in the service registry table, thus allowing protocol-specific parameters to be specified. To be consistent with [1], the parameter string for NHRP shall be:
通用参数字符串在服务注册表表中定义，因此允许指定协议特定的参数。为与[1]一致，NHRP的参数字符串应为：
ar$pro.type 16 bits Protocol type ar$pro.snap 40 bits Optional extension to protocol type ar$plen 8 bits Length of protocol address ar$addr plen octets Network address ar$mask plen octets Network mask
ar$pro.type 16位协议类型ar$pro.snap 40位协议类型的可选扩展ar$plen 8位协议地址长度ar$addr plen八位字节网络地址ar$mask plen八位字节网络掩码
Where
哪里
ar$pro.type - See [1]. (IPv4 is 0x0800, IPv6 is 0x86DD)
ar$pro.type-请参见[1]。（IPv4为0x0800，IPv6为0x86DD）
ar$pro.snap - See [1]. (IPv4 and IPv6 are 0)
ar$pro.snap-请参见[1]。（IPv4和IPv6为0）
ar$plen - Length of the protocol address. (IPv4 is 4, IPv6 is 16)
ar$plen—协议地址的长度。（IPv4为4，IPv6为16）
ar$addr - Network address represented in network byte order
ar$addr—以网络字节顺序表示的网络地址
ar$mask - Network mask represented in network byte order
ar$mask—以网络字节顺序表示的网络掩码
This OID, assigned in the ATM Forum Service Registry MIB, names ATMARP within the context of server discovery.
这个OID在ATM论坛服务注册表MIB中分配，在服务器发现上下文中命名为ATMARP。
atmfSrvcRegNHRP OBJECT IDENTIFIER ::= { 1.3.6.1.4.1.353.1.5.5 }
atmfSrvcRegNHRP OBJECT IDENTIFIER ::= { 1.3.6.1.4.1.353.1.5.5 }
It does not name any managed objects, rather is used to locate appropriate rows in the service registery table.
它不命名任何托管对象，而是用于在服务注册表表中定位适当的行。
An Next Hop Client NHC) will access the service registry table via
ILMI using the SNMP GetNext operator to "sweep" (SNMP parlance for a
linear search) beginning with {Port = 0, ServiceID = <see Section
3.2>, Index = 0} while holding the port number and the serviceID
constant. (Port number 0 is used within ILMI to indicate "this
port.")
An Next Hop Client NHC) will access the service registry table via
ILMI using the SNMP GetNext operator to "sweep" (SNMP parlance for a
linear search) beginning with {Port = 0, ServiceID = <see Section
3.2>, Index = 0} while holding the port number and the serviceID
constant. (Port number 0 is used within ILMI to indicate "this
port.")
An NHC with no local configuration, such as a diskless workstation,
无本地配置的NHC，如无盘工作站，
must use the row with the lowest index value if multiple Next Hop Server (NHS), possibly for multiple networks, are listed.
如果列出了多个下一跳服务器（NHS）（可能用于多个网络），则必须使用索引值最低的行。
NHC that have local IP configuration must use a row that has the appropriate IP address. For example, consider the case where an IP router has 3 logical interfaces defined on a single physical interface with IP addresses 1.0.0.1/8, 128.10.0.1/16 and 171.69.150.226/24. The router will sweep the service registry table looking for rows that have atmfSrvcRegParm1 values as shown below:
具有本地IP配置的NHC必须使用具有适当IP地址的行。例如，考虑IP路由器具有在IP地址1.0.0.1/8、1287.0.1/16和171.69150.226/24的单个物理接口上定义的3个逻辑接口的情况。路由器将扫描服务注册表表，查找具有ATMFSRVCREGREPARM1值的行，如下所示：
Net number/mask atmfSrvcRegParm1
---------------- --------------------------------------------------
1.0.0.0/8 08 00 00 00 00 00 00 04 01 00 00 00 ff 00 00 00
128.10.0.0/16 08 00 00 00 00 00 00 04 80 0a 00 00 ff ff 00 00
171.69.150.0/24 08 00 00 00 00 00 00 04 ab 45 96 00 ff ff ff 00
Net number/mask atmfSrvcRegParm1
---------------- --------------------------------------------------
1.0.0.0/8 08 00 00 00 00 00 00 04 01 00 00 00 ff 00 00 00
128.10.0.0/16 08 00 00 00 00 00 00 04 80 0a 00 00 ff ff 00 00
171.69.150.0/24 08 00 00 00 00 00 00 04 ab 45 96 00 ff ff ff 00
When the correct atmfSrvcRegParm1 values are located, the router may then establish an SVC to the selected NHS and perform the appropriate protocol operations.
当找到正确的atmfSrvcRegParm1值时，路由器可随后建立到所选NHS的SVC并执行适当的协议操作。
Redundant NHS are supported with multiple rows in the service registry table. This list of NHS is ordered with the primary NHS having the lowest index value. The NHC must attempt to utilize the primary NHS before utilizing a secondary NHS. Administrators must ensure that the listed NHS are synchronized.
服务注册表表中的多行支持冗余NHS。此NHS列表按索引值最低的主要NHS排序。NHC必须在使用二级NHS之前尝试使用初级NHS。管理员必须确保列出的NHS是同步的。
A Next Hop Server (NHS) shall be locally configured. The NHS may retrieve the NHRP service registry data to validate the results. If an incorrect row is retrieved the error may be flagged in a locally significant way.
应在本地配置下一跳服务器（NHS）。NHS可检索NHRP服务注册数据以验证结果。如果检索到不正确的行，则可能会以局部有效的方式标记错误。
An augmented version PNNI ("PNNI Augmented Routing," or PAR) [3] has been developed by the ATM Forum. PAR can distribute data such as NHS addresses. Further, the ATM Forum is developing a proxy mechanism for PAR (Proxy PAR) that would allow a UNI-attached host or router to access PAR data without a full PAR implementation.
ATM论坛开发了一个增强版PNNI（“PNNI增强路由”，或PAR）[3]。PAR可以分发诸如NHS地址的数据。此外，ATM论坛正在开发一种用于PAR（代理PAR）的代理机制，该机制允许UNI附加主机或路由器在没有完全PAR实现的情况下访问PAR数据。
These mechanisms offer a promising way to manage the service registry tables maintained on each switch in an ATM network, yet would not require changes to the mechanism defined in this memo. Hosts and routers can continue to utilize ILMI-based or Proxy PAR-based server discovery and network administrators could manage the service registry data with local configuration or via PAR and Proxy PAR.
这些机制为管理ATM网络中每个交换机上维护的服务注册表表提供了一种很有希望的方法，但不需要更改本备忘录中定义的机制。主机和路由器可以继续使用基于ILMI或基于代理的PAR的服务器发现，并且网络管理员可以通过本地配置或通过PAR和代理PAR来管理服务注册表数据。
The server discovery mechanism is built on the ILMI managment framework and the security embodied in that framework. Access, to user- or network-side information is controlled by MIB design rather than protocol security mechanisms.
服务器发现机制构建在ILMI管理框架和该框架中体现的安全性之上。对用户或网络端信息的访问由MIB设计控制，而不是由协议安全机制控制。
The service registery MIB, the table containing information for server discovery, is defined in [2] with read-only access. This means that any user-side device may query the service registry, but may not modify the service registry via ILMI. Instead, the sevice registry table must be modified via local configuration on the ATM switch.
服务注册表MIB（包含服务器发现信息的表）在[2]中定义为只读访问。这意味着任何用户端设备都可以查询服务注册表，但不能通过ILMI修改服务注册表。相反，必须通过ATM交换机上的本地配置修改服务注册表表。
References
工具书类
[1] Luciani, J., et al., "NBMA Next Hop Resolution Protocol", RFC 2332, April 1998.
[1] Luciani，J.等人，“NBMA下一跳解决方案”，RFC 2332，1998年4月。
[2] ATM Forum, "Integrated Local Management Interface (ILMI) Specification Version 4.0," af-ilmi-0065.000, September 1996.
[2] ATM论坛，“集成本地管理接口（ILMI）规范版本4.0”，af-ILMI-0065.000，1996年9月。
[3] ATM Forum, "PNNI Augmented Routing (PAR) Version 1.0," af-ra-0104, January 1999.
[3] ATM论坛，“PNNI增强路由（PAR）1.0版”，af-ra-0104，1999年1月。
Author's Address
作者地址
Mike Davison Cisco Systems 170 West Tasman Drive San Jose, California 95134
迈克·戴维森思科系统有限公司加利福尼亚州圣何塞西塔斯曼大道170号，邮编95134
Phone: (408) 526-4000 EMail: mike.davison@cisco.com
电话：（408）526-4000电子邮件：迈克。davison@cisco.com
Full Copyright Statement
完整版权声明
Copyright (C) The Internet Society (1999). All Rights Reserved.
版权所有（C）互联网协会（1999年）。版权所有。
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编辑功能的资金目前由互联网协会提供。