Network Working Group                                           N. Shen
Request for Comments: 2763                                Siara Systems
Category: Informational                                         H. Smit
                                                          Cisco Systems
                                                          February 2000
        
Network Working Group                                           N. Shen
Request for Comments: 2763                                Siara Systems
Category: Informational                                         H. Smit
                                                          Cisco Systems
                                                          February 2000
        

Dynamic Hostname Exchange Mechanism for IS-IS

IS-IS的动态主机名交换机制

Status of this Memo

本备忘录的状况

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited.

本备忘录为互联网社区提供信息。它没有规定任何类型的互联网标准。本备忘录的分发不受限制。

Copyright Notice

版权公告

Copyright (C) The Internet Society (2000). All Rights Reserved.

版权所有(C)互联网协会(2000年)。版权所有。

Abstract

摘要

Currently, there does not exist a simple and dynamic mechanism for routers running IS-IS to learn about symbolic hostnames. This document defines a new TLV which allows the IS-IS routers to flood their name to system ID mapping information across the IS-IS network.

目前,运行IS-IS的路由器不存在一种简单的动态机制来了解符号主机名。本文档定义了一个新的TLV,该TLV允许IS-IS路由器在IS-IS网络中将其名称与系统ID映射信息一致。

1. Introduction
1. 介绍

IS-IS uses a 1-8 byte system ID (normally 6 bytes) to represent a node in the network. For management and operation reasons, network operators need to check the status of IS-IS adjacencies, entries in the routing table and the content of the IS-IS link state database. It is obvious that, when looking at diagnostics information, hexadecimal representations of systemIDs and LSP identifiers are less clear than symbolic names.

IS-IS使用1-8字节的系统ID(通常为6字节)表示网络中的节点。出于管理和操作原因,网络运营商需要检查IS-IS邻接的状态、路由表中的条目以及IS-IS链路状态数据库的内容。很明显,在查看诊断信息时,SystemID和LSP标识符的十六进制表示形式不如符号名清晰。

One way to overcome this problem is to define a name-to-systemID mapping on a router. This mapping can be used bidirectionally. E.g., to find symbolic names for systemIDs, and to find systemIDs for symbolic names. One way to build this table of mappings is by static definitions. Among network administrators who use IS-IS as their IGP it is current practice to define such static mappings.

克服此问题的一种方法是在路由器上定义名称到systemID的映射。此映射可以双向使用。例如,查找SystemID的符号名称,以及查找符号名称的SystemID。构建此映射表的一种方法是通过静态定义。在使用IS-IS作为IGP的网络管理员中,目前的做法是定义此类静态映射。

Thus every router has to maintain a table with mappings between router names and systemIDs. These tables need to contain all names and systemIDs of all routers in the network.

因此,每个路由器都必须维护一个表,其中包含路由器名称和系统ID之间的映射。这些表需要包含网络中所有路由器的所有名称和系统ID。

There are several ways one could build such a table. One is via static configurations. Another scheme that could be implemented is via DNS lookups. In this document we propose a third solution. We hope the proposed solution is easier and more manageable than static mapping or DNS schemes.

有几种方法可以建立这样一个表。一种是通过静态配置。另一个可以实现的方案是通过DNS查找。在本文件中,我们提出了第三种解决方案。我们希望提出的解决方案比静态映射或DNS方案更容易管理。

2. Possible solutions
2. 可能的解决方案

The obvious drawback of static configuration of mappings is the issue of scalability and maintainability. The network operators have to maintain the name tables. They have to maintain an entry in the table for every router in the network. They have to maintain this table on each router in the network. The effort to create and maintain these static tables grows with the total number of routers on the network. Changing the name or systemID of one router, or adding one new router introduced will affect the configurations of all the other routers on the network. This will make it very likely that those static tables are outdated.

映射的静态配置的明显缺点是可伸缩性和可维护性问题。网络运营商必须维护名称表。他们必须在表中为网络中的每个路由器维护一个条目。他们必须在网络中的每个路由器上维护此表。创建和维护这些静态表的工作量随着网络上路由器的总数的增加而增加。更改一个路由器的名称或systemID,或添加一个新引入的路由器将影响网络上所有其他路由器的配置。这将使这些静态表很可能已经过时。

Having one table that can be updated in a centralized place would be helpful. One could imagine using the DNS system for this. A drawback is that during the time of network problems, the response time of DNS services might not be satisfactory or the DNS services might not even be available. Another possible drawback might be the added complexity of DNS. Also, some DNS implementations might not support A and PTR records for CLNS NSAPs.

有一个可以在集中的地方更新的表会很有帮助。可以想象使用DNS系统来实现这一点。缺点是,在网络出现问题期间,DNS服务的响应时间可能不令人满意,或者DNS服务甚至可能不可用。另一个可能的缺点可能是DNS的复杂性增加。此外,某些DNS实现可能不支持CLNS NSAP的A和PTR记录。

A third way to build dynamic mappings would be to use the transport mechanism of the routing protocol itself to advertise symbolic names in IS-IS link-state PDU. This document defines a new TLV which allows the IS-IS routers to include the name to systemID mapping information in their LSPs. This will allow simple and reliable transport of name mapping information across the IS-IS network.

构建动态映射的第三种方法是使用路由协议本身的传输机制在IS-IS链路状态PDU中公布符号名。本文档定义了一个新的TLV,它允许IS-IS路由器在其LSP中包含名称到systemID的映射信息。这将允许通过IS-IS网络简单可靠地传输名称映射信息。

3. The Dynamic Hostname TLV
3. 动态主机名TLV

The Dynamic hostname TLV is defined here as TLV type 137.

动态主机名TLV在这里定义为TLV类型137。

LENGTH - total length of the value field.

LENGTH—值字段的总长度。

VALUE - a string of 1 to 255 bytes.

值-1到255字节的字符串。

The Dynamic hostname TLV is optional. This TLV may be present in any fragment of a non-pseudo node LSP. The value field identifies the symbolic name of the router originating the LSP. This symbolic name can be the FQDN for the router, it can be a subset of the FQDN or any string operators want to use for the router. The use of FQDN or a

动态主机名TLV是可选的。该TLV可以存在于非伪节点LSP的任何片段中。值字段标识发起LSP的路由器的符号名称。此符号名可以是路由器的FQDN,也可以是FQDN的子集或任何要用于路由器的字符串运算符。FQDN或

subset of it is strongly recommended. The content of this value is a domain name, see RFC 2181. The string is not null-terminated. The systemID of this router can be derived from the LSP identifier.

强烈建议使用它的子集。此值的内容是一个域名,请参阅RFC 2181。字符串不是以null结尾的。此路由器的systemID可以从LSP标识符派生。

If this TLV is present in a pseudo node LSP, then it should not be interpreted as the DNS hostname of the router.

如果此TLV存在于伪节点LSP中,则不应将其解释为路由器的DNS主机名。

4. Implementation
4. 实施

The Dynamic Hostname TLV is optional. When originating an LSP, a router may decide to include this TLV in its LSP. Upon receipt of an LSP with the dynamic hostname TLV, a router may decide to ignore this TLV, or to install the symbolic name and systemID in its hostname mapping table.

动态主机名TLV是可选的。当发起LSP时,路由器可决定将该TLV包括在其LSP中。在收到带有动态主机名TLV的LSP后,路由器可能会决定忽略此TLV,或者在其主机名映射表中安装符号名和systemID。

A router may also optionally insert this TLV in it's pseudo node LSP for the association of a symbolic name to a local LAN.

路由器还可以选择性地将该TLV插入其伪节点LSP中,以便将符号名称关联到本地LAN。

5. Security Considerations
5. 安全考虑

This document raises no new security issues for IS-IS. However, it is encouraged to use authentications for IS-IS routing protocol. The authentication mechanism for IS-IS protocol is specified in [1] and it is being enhanced within IETF in [2].

本文档没有为IS-IS提出新的安全问题。但是,鼓励对is-is路由协议使用身份验证。IS-IS协议的认证机制在[1]中有规定,并且在[2]中IETF中对其进行了增强。

6. Acknowledgments
6. 致谢

The authors would like to thank Enke Chen and Yakov Rekhter for their comments on this work.

作者要感谢Enke Chen和Yakov Rekhter对这项工作的评论。

7. References
7. 工具书类

[1] ISO, "Intermediate system to Intermediate system routing information exchange protocol for use in conjunction with the Protocol for providing the Connectionless-mode Network Service (ISO 8473)," ISO/IEC 10589:1992.

[1] ISO,“与提供无连接模式网络服务的协议一起使用的中间系统到中间系统路由信息交换协议(ISO 8473)”,ISO/IEC 10589:1992。

[2] Li, T., "IS-IS HMAC-MD5 Authentication", Work in Progress.

[2] Li,T.,“IS-IS HMAC-MD5认证”,正在进行中。

8. Authors' Addresses
8. 作者地址

Naiming Shen Siara Systems, Inc. 1195 Borregas Avenue Sunnyvale, CA, 94089

Naiming Shen Siara Systems,Inc.加利福尼亚州桑尼维尔Borregas大道1195号,邮编94089

   EMail: naiming@siara.com
        
   EMail: naiming@siara.com
        

Henk Smit Cisco Systems, Inc. 170 Tasman Drive San Jose, CA, 95134

亨克·斯密特思科系统公司,地址:加利福尼亚州圣何塞塔斯曼大道170号,邮编:95134

   EMail: hsmit@cisco.com
        
   EMail: hsmit@cisco.com
        
9. Full Copyright Statement
9. 完整版权声明

Copyright (C) The Internet Society (2000). All Rights Reserved.

版权所有(C)互联网协会(2000年)。版权所有。

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编辑功能的资金目前由互联网协会提供。