Document..........:  draft-ietf-isis-te-bis-00
Reviewer..........:  Christian Vogt
Review date.......:  2008/07/25
IESG Telechat Date:  2008/07/03


Summary:  This draft is ready for publication as a Proposed Standard RFC.


The document is clearly ready for publication.  Just two nits:

In section 3, you write:

    Further, there is no defined mechanism for extending the sub-TLV
    space for a particular neighbor.  Thus, wasting sub-TLV space is
    discouraged.

This seems to be a general issue that may be good to move to a more dominant position.  It refers to the sub-TLV concept in general, but here it is mentioned only in the specific context of the Extended IS Reachability TLV.  Consider moving this to a place that talks generally about the sub-TLV concept, e.g., to section 2.

In section 4, you write:

    This data structure can be replicated within the TLV,
    without exceeding the maximum length of the TLV.

Suggest rewording to "...as long as the maximum length of the TLV is not exceeded".