Skip to main content

Last Call Review of draft-ietf-grow-irr-routing-policy-considerations-05
review-ietf-grow-irr-routing-policy-considerations-05-genart-lc-melnikov-2015-01-08-00

Request Review of draft-ietf-grow-irr-routing-policy-considerations
Requested revision No specific revision (document currently at 06)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-12-01
Requested 2014-11-17
Authors Danny R. McPherson , Shane Amante , Eric Osterweil , Larry Blunk , Dave Mitchell
I-D last updated 2015-01-08
Completed reviews Genart Last Call review of -05 by Alexey Melnikov (diff)
Secdir Last Call review of -05 by Takeshi Takahashi (diff)
Opsdir Last Call review of -05 by Kiran K. Chittimaneni (diff)
Rtgdir Early review of -05 by Terry Manderson (diff)
Assignment Reviewer Alexey Melnikov
State Completed
Request Last Call review on draft-ietf-grow-irr-routing-policy-considerations by General Area Review Team (Gen-ART) Assigned
Reviewed revision 05 (document currently at 06)
Result Ready w/nits
Completed 2015-01-08
review-ietf-grow-irr-routing-policy-considerations-05-genart-lc-melnikov-2015-01-08-00
I am the assigned Gen-ART reviewer for this draft. For background on

Gen-ART, please see the FAQ at

<

http://wiki.tools.ietf.org/area/gen/trac/wiki/GenArtfaq>.

Please resolve these comments along with any other Last Call comments

you may receive.

Document: draft-ietf-grow-irr-routing-policy-considerations-05

Reviewer: Alexey Melnikov

Review Date: 2015-01-08

IETF LC End Date: 2015-12-01

IESG Telechat date: 2015-01-08

Summary: Ready for publication as Proposed Standard (with nits)

Major issues: none

Minor issues: none

Nits:

In various sections: first references to:

Netconf, SSH, TLS, FTP need informative references.

In Section 6:	

   Specifically, BGP soft-reconfiguration [REF?]

This reference needs fixing

and, later,
   Route Refresh Capability for BGP-4 [RFC2918] were developed so that
   ISPs, or their customers, could induce BGP to apply a new policy
   while leaving both the existing eBGP session active as well as
   (unaffected) routes active in both the Loc-RIB and, more importantly,
   FIB of the router.