Last Call Review of draft-ietf-bess-mvpn-expl-track-09
review-ietf-bess-mvpn-expl-track-09-rtgdir-lc-pignataro-2018-09-12-00
| Request | Review of | draft-ietf-bess-mvpn-expl-track |
|---|---|---|
| Requested revision | No specific revision (document currently at 13) | |
| Type | Last Call Review | |
| Team | Routing Area Directorate (rtgdir) | |
| Deadline | 2018-09-24 | |
| Requested | 2018-05-07 | |
| Requested by | Martin Vigoureux | |
| Authors | Andrew Dolganow , Jayant Kotalwar , Eric C. Rosen , Zhaohui (Jeffrey) Zhang | |
| I-D last updated | 2018-09-12 | |
| Completed reviews |
Rtgdir Last Call review of -09
by Carlos Pignataro
(diff)
Secdir Last Call review of -11 by Christian Huitema (diff) Genart Last Call review of -10 by Brian E. Carpenter (diff) Genart Telechat review of -12 by Brian E. Carpenter (diff) |
|
| Assignment | Reviewer | Carlos Pignataro |
| State | Completed | |
| Request | Last Call review on draft-ietf-bess-mvpn-expl-track by Routing Area Directorate Assigned | |
| Reviewed revision | 09 (document currently at 13) | |
| Result | Has nits | |
| Completed | 2018-09-12 |
review-ietf-bess-mvpn-expl-track-09-rtgdir-lc-pignataro-2018-09-12-00
This is a very well written and detailed document. I have only one concern, which I believe should be addressed before moving this document forward: I found the rational and specific details on what this document "Updates" from three previous RFCs to be lacking, and confusing. I recommend an "Updates from RFC XYZ" section in which there is a textual explanation and ideally Old/New specifics on how this document updates previous RFCs. At least, something more inline with current thinking as per https://www.ietf.org/mail-archive/web/ietf/current/msg109106.html Thanks, Carlos Pignataro.