Early Review of draft-ietf-idr-bgp-gr-notification-03

Request Review of draft-ietf-idr-bgp-gr-notification
Requested rev. no specific revision (document currently at 16)
Type Early Review
Team Routing Area Directorate (rtgdir)
Deadline 2014-09-28
Requested 2014-08-29
Authors Keyur Patel, Rex Fernando, John Scudder, Jeffrey Haas
Draft last updated 2014-09-28
Completed reviews Rtgdir Early review of -03 by Mach Chen (diff)
Rtgdir Early review of -05 by Mach Chen (diff)
Rtgdir Early review of -07 by Emmanuel Baccelli (diff)
Rtgdir Telechat review of -15 by Bruno Decraene (diff)
Opsdir Last Call review of -15 by Qin Wu (diff)
Secdir Last Call review of -15 by Yoav Nir (diff)
Assignment Reviewer Mach Chen
State Completed
Review review-ietf-idr-bgp-gr-notification-03-rtgdir-early-chen-2014-09-28
Reviewed rev. 03 (document currently at 16)
Review result Has Nits
Review completed: 2014-09-28


Hi Authors,

I was assigned to do a QA review on draft-ietf-idr-bgp-gr-notification-03. For more detail what's is RtgDir QA review, please refer to 



Overall, the document is well-written and clear, after review, I have the following comments. 

1.  Abstract

2.  Section 2:
    Flags for Address Family:

            This field contains bit flags relating to routes that were
            advertised with the given AFI and SAFI.

                0 1 2 3 4 5 6 7
               |F|N| Reserved  |

   The usage of second most significant bit "N" is deprecated.  This bit
   MUST be advertised as 0 and MUST be ignored upon receipt.
The "N" bit was firstly introduced in a previous version of this document, but deprecated in later version. I don't understand why a document need deprecate a functionality introduced by itself, why not just remove it?

In addition, since there is no changes to the AF related flags, the last sentence of the first paragraph of section 2 should be changed as bellow:

"the Restart flags field and the Flags field for Address Family are augmented as follows:"

"the Restart flags field are augmented as follows:"

3.  Section 3.1

"Subcode is a BGP Error Subcode (as documented in the IANA BGP Error
   Subcodes registry) as appropriate for the ErrCode.  Similarly, Data
   is as appropriate for the ErrCode and Subcode."
This is just an introduction to the Subcode itself, it's better to explicitly state that the subcode should be set to the Hard Reset (9).

4.  Section 4
"Once the session is re-established, both BGP speakers SHOULD set
   their "Forwarding State" bit to 1."

Here it implies that the speakers are required to set the "Forwarding State" no matter what the speakers have the ability to preserve the forwarding state. Is it the intention?  

I guess it's not, if so, some text may needed to clarify this.

5. I run idnits tool and found the following nits:

== Unused Reference: 'RFC3392' is defined on line 269, but no explicit reference was found in the text.

Best regards,