Skip to main content

Last Call Review of draft-ietf-mpls-deprecate-bgp-entropy-label-01
review-ietf-mpls-deprecate-bgp-entropy-label-01-genart-lc-campbell-2014-11-03-00

Request Review of draft-ietf-mpls-deprecate-bgp-entropy-label
Requested revision No specific revision (document currently at 02)
Type Last Call Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2014-11-03
Requested 2014-10-23
Authors John Scudder , Kireeti Kompella
I-D last updated 2014-11-03
Completed reviews Genart Last Call review of -01 by Ben Campbell (diff)
Secdir Last Call review of -01 by Scott G. Kelly (diff)
Assignment Reviewer Ben Campbell
State Completed
Request Last Call review on draft-ietf-mpls-deprecate-bgp-entropy-label by General Area Review Team (Gen-ART) Assigned
Reviewed revision 01 (document currently at 02)
Result Ready w/issues
Completed 2014-11-03
review-ietf-mpls-deprecate-bgp-entropy-label-01-genart-lc-campbell-2014-11-03-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-mpls-deprecate-bgp-entropy-label-01
Reviewer: Ben Campbell
Review Date: 2014-11-03
IETF LC End Date:
IESG Telechat date: (if known)

Summary: Draft is ready for publication as a proposed standard. I have a few
comments that might be worth considering if there are further updates, but
should not block publication in any way.

Major issues: None

Minor issues:

Am I correct in understanding that this draft deprecates all applicability of
RFC 6790 to BGP, but lets stand its use in all other protocol contexts? If so,
an explicit mention of that might be helpful.

Nits/editorial comments:

-- Section 2:

Is the "subsequent to the publication of this document" disclaimer really
needed? We update protocols all the time without offering date-based
grandfather clauses.

-- Section 3:

There's a comma splice at the end of the paragraph. I suggest something to the
effect of "... , _with_ reference _to_ this RFC."