Last Call Review of draft-ietf-l3vpn-acceptown-community-08
review-ietf-l3vpn-acceptown-community-08-opsdir-lc-bonica-2014-12-15-00
| Request | Review of | draft-ietf-l3vpn-acceptown-community |
|---|---|---|
| Requested revision | No specific revision (document currently at 10) | |
| Type | Last Call Review | |
| Team | Ops Directorate (opsdir) | |
| Deadline | 2014-12-08 | |
| Requested | 2014-11-28 | |
| Authors | Jim Uttaro , Prodosh Mohapatra , David Smith , Robert Raszuk , John Scudder | |
| Draft last updated | 2014-12-15 | |
| Completed reviews |
Genart Telechat review of -09
by
Francis Dupont
(diff)
Opsdir Last Call review of -08 by Ron Bonica (diff) |
|
| Assignment | Reviewer | Ron Bonica |
| State | Completed | |
| Review |
review-ietf-l3vpn-acceptown-community-08-opsdir-lc-bonica-2014-12-15
|
|
| Reviewed revision | 08 (document currently at 10) | |
| Result | Has Issues | |
| Completed | 2014-12-15 |
review-ietf-l3vpn-acceptown-community-08-opsdir-lc-bonica-2014-12-15-00
Folks, 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 primarily for the benefit of the operational area directors. Document editors and WG chairs should treat these comments just like any other last call comments. This document is well written and well thought out. It is almost ready for publication with one small issue. In Section 2.3, the authors say, " ACCEPT_OWN handling SHOULD be controlled by configuration, and SHOULD default to being disabled. IMO, they should say, "ACCEPT_OWN handling MUST be controlled by configuration, and MUST default to being disabled." AFAIKS, you would never want to build a router where ACCEPT_OWN behavior is always on and cannot be disabled by configuration. Likewise, you would never want to build a router where ACCEPT_OWN behavior is the default. Ron Bonica