draft-ietf-isis-dyname-01.txt   draft-ietf-isis-dyname-02.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-01.txt Henk Smit draft-ietf-isis-dyname-02.txt Henk Smit
Expiration Date: March 2000 Cisco Systems Expiration Date: April 2000 Cisco Systems
September 1999 October 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 and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 except that the right to all provisions of Section 10 of RFC2026 except that the right to
produce derivative works is not granted. produce derivative works is not granted.
skipping to change at page 3, line 18 skipping to change at page 3, line 18
LENGTH - total length of the value field. LENGTH - total length of the value field.
VALUE - a string of 1 to 255 bytes. VALUE - a string of 1 to 255 bytes.
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. The content of this value is a
7-bit ASCII. The string is not null-terminated. The domain name, see RFC 2181. 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 If this TLV is present in a pseudo node LSP, then it should not be
interpreted as the DNS hostname of the router. 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
 End of changes. 

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