draft-ietf-isis-dyname-00.txt   draft-ietf-isis-dyname-01.txt 
Internet Engineering Task Force Naiming Shen Internet Engineering Task Force Naiming Shen
INTERNET-DRAFT Cisco Systems INTERNET-DRAFT Cisco Systems
draft-ietf-isis-dyname-00.txt Henk Smit draft-ietf-isis-dyname-01.txt Henk Smit
Cisco Systems Expiration Date: March 2000 Cisco Systems
January 1999 September 1999
Dynamic Hostname Exchange Mechanism Dynamic Hostname Exchange Mechanism
for IS-IS for IS-IS
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet-Draft and is in full conformance with
documents of the Internet Engineering Task Force (IETF), its Areas, all provisions of Section 10 of RFC2026 except that the right to
and its Working Groups. Note that other groups may also distribute produce derivative works is not granted.
working documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six Internet-Drafts are working documents of the Internet Engineering
months. Internet Drafts may be updated, replaced, or obsoleted by Task Force (IETF), its areas, and its working groups. Note that
other documents at any time. It is not appropriate to use Internet other groups may also distribute working documents as
Drafts as reference material or to cite them other than as a Internet-Drafts.
``working draft'' or ``work in progress``.
To view the entire list of current Internet-Drafts, please check Internet-Drafts are draft documents valid for a maximum of six months
the "1id-abstracts.txt" listing contained in the Internet-Drafts and may be updated, replaced, or obsoleted by other documents at any
Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net time. It is inappropriate to use Internet- Drafts as reference
(Northern Europe), ftp.nic.it (Southern Europe), munnari.oz.au material or to cite them other than as "work in progress."
(Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu
(US West Coast). The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Abstract Abstract
Currently there does not exist a simple and dynamic mechanism for Currently there does not exist a simple and dynamic mechanism for
routers running IS-IS to learn about symbolic hostnames. This routers running IS-IS to learn about symbolic hostnames. This
document defines a new TLV which allows the IS-IS routers to flood 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. their name to system ID mapping information across the IS-IS network.
1. Introduction 1. Introduction
skipping to change at page 3, line 22 skipping to change at page 3, line 22
The Dynamic hostname TLV is optional. This TLV may be present in any 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 fragment of a non-pseudo node LSP. The value field identifies the
symbolic name of the router originating the LSP. This symbolic name 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 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 string operators want to use for the router. The use of FQDN or a
subset of it is strongly recommended. It is one byte per character, subset of it is strongly recommended. It is one byte per character,
7-bit ASCII. The string is not null-terminated. The 7-bit ASCII. The string is not null-terminated. The
systemID of this router can be derived from the LSP identifier. systemID of this router can be derived from the LSP identifier.
If this TLV is present in a pseudo node LSP, then it should not be
interpreted as the DNS hostname of the router.
4. Implementation 4. Implementation
The Dynamic Hostname TLV is optional. When originating an LSP, a 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 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 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 TLV, or to install the symbolic name and systemID in its hostname
mapping table. mapping table.
This protocol extension has been implemented by Cisco Systems. 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.
5. Security Considerations 5. Security Considerations
Security issues are not discussed in this document. 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].
6. Acknowledgments 6. Acknowledgments
[TBD] The authors would like to thank Enke Chen and Yakov Rekhter for
their comments on this work.
7. Author's Address: 7. References
[1] ISO, "Intermediate system to Intermediate system routeing
information exchange protocol for use in conjunction with the
Protocol for providing the Connectionless-mode Network Service
(ISO 8473)," ISO/IEC 10589:1992.
[2] draft-ietf-isis-hmac-00.txt, "IS-IS HMAC-MD5 Authentication",
T. Li, work in progress.
8. Author's Address:
Naiming Shen Naiming Shen
Cisco Systems, Inc. Cisco Systems, Inc.
170 Tasman Drive 170 Tasman Drive
San Jose, CA, 95134 San Jose, CA, 95134
Email: naiming@cisco.com Email: naiming@cisco.com
Henk Smit Henk Smit
Cisco Systems, Inc. Cisco Systems, Inc.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/