Dynamic Hostname Exchange Mechanism for IS-IS
draft-ietf-isis-rfc2763bis-00

[Ballot discuss]
The document should say what a router should do if it receives a
(name, systemID) mapping for a name or systemID it already has a
(different) mapping for. Documenting what existing
implementations do would be sufficient.

The security considerations text should say where the existing
security considerations are discussed (e.g. in rfc3567bis).

There's also one new security consideration; here's my proposal for
text (rough sketch only; suggestions for better text are welcome if
the WG doesn't like this one):

"Since the name-to-systemID mapping relies on information provided by
the routers themselves, a misconfigured or compromised router can
inject false mapping information. Thus, this information needs to be
treated with suspicion when e.g. doing diagnostics about a suspected
security incident."

[Ballot discuss]
This document needs to describe its relationship to IDN (RFC 3490).  This
should be simple to fix.  I suggest one or two sentences similar to:

The VALUE field is encoded in 7-bit ASCII.  If a user-interface for
configuring or displaying this field permits Unicode characters, that
user-interface is responsible for applying the ToASCII and/or ToUnicode
algorithm as described in RFC 3490 to achieve the correct format for
transmission or display.

[Ballot discuss]
INTRODUCTION, paragraph 12:
>    The intention of this document is to provide an update to [RFC 2763].

  DISCUSS: I believe this obsoletes RFC2763 (instead of updating it).
  This also needs to be added to the first-page header.

IANA Last Call comments:

Upon approval of this document, the IANA will make the following
changes in the "IS-IS TLV Codepoints per [RFC3563]" registry at
http://www.iana.org/assignments/isis-tlv-codepoints
sub-registry "TLV Codepoints Registry"

OLD:

Name        Value IIH LSP SNP Status/Reference
------------ ----- --- --- --- ----------------
Dynamic Name 137  n  y  n  [RFC2763]


NEW:

Name        Value IIH LSP SNP Status/Reference
------------ ----- --- --- --- ----------------
Dynamic Name 137  n  y    n  [RFC2763][RFC-isis-rfc2763bis-00]


We understand the above to be the only IANA Action for this
document.