Last Call Review of draft-ietf-bess-mvpn-bidir-ingress-replication-02
review-ietf-bess-mvpn-bidir-ingress-replication-02-opsdir-lc-kumari-2015-10-19-00

Be ye not afraid.

I have reviewed this document as part of the Operational directorate's
ongoing effort to review all IETF documents being processed by the IESG.  These
comments were written with the intent of improving the operational
aspects of the IETF drafts. Comments that are not addressed in last call may be
included in AD reviews during the IESG review.  Document editors and
WG chairs should treat these comments just like any other last call
comments.

Document reviewed:  draft-ietf-bess-mvpn-bidir-ingress-replication-03

Summary: Ready, typo / grammar nits.

General:
I found this document to be very dense. At some point my brain started
dribbling out my ears and I largely gave up on trying to understand
the mechanism. This seems to be very much a niche application, and my
IP multicast and deep MPLS knowledge isn't up to the level of finding
issues with the logic.

Nits:

Abstract:
This document specifiess how
[O] specifiess
[P] specifies
[R] spelling

1: Introduction:
   With these two methods, all PEs of a particular VPN are separated
[O] all PEs
[P] all PEs (Provider Edge router)
[R] first use of acronym. The document does say it assumed familiarity
with terminology from [RFC5015], [RFC6513], [RFC6514], and [RFC7582],
but this is before that, and also expanding PE here will help people
understand if they want to continue reading...

W





-- 
I don't think the execution is relevant when it was obviously a bad
idea in the first place.
This is like putting rabid weasels in your pants, and later expressing
regret at having chosen those particular rabid weasels and that pair
of pants.
   ---maf