--- 1/draft-ietf-idr-ls-distribution-08.txt	2015-01-21 01:14:59.813551383 -0800
+++ 2/draft-ietf-idr-ls-distribution-09.txt	2015-01-21 01:14:59.913553809 -0800
@@ -1,24 +1,24 @@
 
 Inter-Domain Routing                                          H. Gredler
 Internet-Draft                                    Juniper Networks, Inc.
 Intended status: Standards Track                               J. Medved
-Expires: July 24, 2015                                        S. Previdi
+Expires: July 25, 2015                                        S. Previdi
                                                      Cisco Systems, Inc.
                                                                A. Farrel
                                                   Juniper Networks, Inc.
                                                                   S. Ray
                                                      Cisco Systems, Inc.
-                                                        January 20, 2015
+                                                        January 21, 2015
 
   North-Bound Distribution of Link-State and TE Information using BGP
-                   draft-ietf-idr-ls-distribution-08
+                   draft-ietf-idr-ls-distribution-09
 
 Abstract
 
    In a number of environments, a component external to a network is
    called upon to perform computations based on the network topology and
    current state of the connections within the network, including
    traffic engineering information.  This is information typically
    distributed by IGP routing protocols within the network.
 
    This document describes a mechanism by which links state and traffic
@@ -46,21 +46,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at http://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on July 24, 2015.
+   This Internet-Draft will expire on July 25, 2015.
 
 Copyright Notice
 
    Copyright (c) 2015 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (http://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -920,21 +920,22 @@
 
                 Figure 16: IS-IS Area Identifier TLV Format
 
 3.3.1.3.  Node Name TLV
 
    The Node Name TLV is optional.  Its structure and encoding has been
    borrowed from [RFC5301].  The value field identifies the symbolic
    name of the router node.  This symbolic name can be the FQDN for the
    router, it can be a subset of the FQDN, or it can be any string
    operators want to use for the router.  The use of FQDN or a subset of
-   it is strongly RECOMMENDED.
+   it is strongly RECOMMENDED.  The maximum length of the 'Node Name
+   TLV' is 255 octets.
 
    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 [RFC5890] to achieve the correct
    format for transmission or display.
 
    Although [RFC5301] is an IS-IS specific extension, usage of the Node
    Name TLV is possible for all protocols.  How a router derives and
    injects node names for e.g.  OSPF nodes, is outside of the scope of
@@ -1166,21 +1167,22 @@
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 
                   Figure 23: Opaque link attribute format
 
 3.3.2.7.  Link Name TLV
 
    The Link Name TLV is optional.  The value field identifies the
    symbolic name of the router link.  This symbolic name can be the FQDN
    for the link, it can be a subset of the FQDN, or it can be any string
    operators want to use for the link.  The use of FQDN or a subset of
-   it is strongly RECOMMENDED.
+   it is strongly RECOMMENDED.  The maximum length of the 'Link Name
+   TLV' is 255 octets.
 
    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 [RFC5890] to achieve the correct
    format for transmission or display.
 
    How a router derives and injects link names is outside of the scope
    of this document.