--- 1/draft-ietf-lsr-isis-rfc5306bis-00.txt	2018-12-13 18:13:13.642254299 -0800
+++ 2/draft-ietf-lsr-isis-rfc5306bis-01.txt	2018-12-13 18:13:13.694255564 -0800
@@ -1,19 +1,19 @@
 
 IS-IS for IP Internets                                       L. Ginsberg
 Internet-Draft                                                  P. Wells
 Obsoletes: 5306 (if approved)                        Cisco Systems, Inc.
-Intended status: Standards Track                        October 01, 2018
-Expires: April 4, 2019
+Intended status: Standards Track                       December 13, 2018
+Expires: June 16, 2019
 
                       Restart Signaling for IS-IS
-                   draft-ietf-lsr-isis-rfc5306bis-00
+                   draft-ietf-lsr-isis-rfc5306bis-01
 
 Abstract
 
    This document describes a mechanism for a restarting router to signal
    to its neighbors that it is restarting, allowing them to reestablish
    their adjacencies without cycling through the down state, while still
    correctly initiating database synchronization.
 
    This document additionally describes a mechansim for a router to
    signal its neighbors that it is preparing to initiate a restart while
@@ -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 https://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 April 4, 2019.
+   This Internet-Draft will expire on June 16, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -421,20 +421,23 @@
        is in the UP state and subsequently goes DOWN, the event MAY be
        ignored since it is possible this is an expected side effect of
        the restart.  Use of the Control Plane Independent state as
        signalled in BFD control packets [RFC5880] SHOULD be considered
        in the decision to ignore a BFD Session DOWN event
 
    c.  On a Point-to-Point circuit, transmission of LSPs, CSNPs, and
        PSNPs MAY be suppressed.  It is expected that the PDUs will not
        be received.
 
+   Use of the PR bit provides a means to safely support restart periods
+   which are significantly longer than standard holdtimes.
+
 2.3.  Adjacency (Re)Acquisition
 
    Adjacency (re)acquisition is the first step in (re)initialization.
    Restarting and starting routers will make use of the RR bit in the
    restart TLV, though each will use it at different stages of the
    (re)start procedure.
 
 2.3.1.  Adjacency Reacquisition during Restart
 
    The restarting router explicitly notifies its neighbor that the