Telechat Review of draft-ietf-bess-mvpn-bidir-ingress-replication-03
review-ietf-bess-mvpn-bidir-ingress-replication-03-genart-telechat-carpenter-2015-10-09-00

Request Review of draft-ietf-bess-mvpn-bidir-ingress-replication
Requested rev. no specific revision (document currently at 04)
Type Telechat Review
Team General Area Review Team (Gen-ART) (genart)
Deadline 2015-10-13
Requested 2015-10-08
Authors Zhaohui Zhang, Yakov Rekhter, Andrew Dolganow
Draft last updated 2015-10-09
Completed reviews Genart Last Call review of -02 by Brian Carpenter (diff)
Genart Telechat review of -03 by Brian Carpenter (diff)
Opsdir Last Call review of -02 by Warren Kumari (diff)
Assignment Reviewer Brian Carpenter
State Completed
Review review-ietf-bess-mvpn-bidir-ingress-replication-03-genart-telechat-carpenter-2015-10-09
Reviewed rev. 03 (document currently at 04)
Review result Ready
Review completed: 2015-10-09

Review
review-ietf-bess-mvpn-bidir-ingress-replication-03-genart-telechat-carpenter-2015-10-09

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please wait for direction from your
document shepherd or AD before posting a new version of the draft.

For more information, please see the FAQ at
<

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

Document: draft-ietf-bess-mvpn-bidir-ingress-replication-03.txt
Reviewer: Brian Carpenter
Review Date: 2015-10-09
IETF LC End Date: 2015-10-08
IESG Telechat date: 2015-10-15

Summary: Ready
--------

Comments:
---------

Thanks for responding to my Last Call comments.

Minor Issues:
-------------

> These specifications update RFC 6514.

Is that actually true? Or is it just an *extension* of RFC 6514, which
doesn't merit a formal "Updates: 6514"? [In other words, will anything bad
happen if an implementation of RFC 6514 doesn't add this?]