Last Call Review of draft-ietf-sfc-hierarchical-08
review-ietf-sfc-hierarchical-08-secdir-lc-turner-2018-05-29-00
| Request | Review of | draft-ietf-sfc-hierarchical |
|---|---|---|
| Requested rev. | no specific revision (document currently at 11) | |
| Type | Last Call Review | |
| Team | Security Area Directorate (secdir) | |
| Deadline | 2018-05-21 | |
| Requested | 2018-05-07 | |
| Draft last updated | 2018-05-29 | |
| Completed reviews |
Rtgdir Last Call review of -08 by Ines Robles
(diff)
Genart Last Call review of -08 by Vijay Gurbani (diff) Secdir Last Call review of -08 by Sean Turner (diff) |
|
| Assignment | Reviewer | Sean Turner |
| State | Completed | |
| Review | review-ietf-sfc-hierarchical-08-secdir-lc-turner-2018-05-29 | |
| Reviewed rev. | 08 (document currently at 11) | |
| Review result | Ready | |
| Review completed: | 2018-05-29 |
Review
review-ietf-sfc-hierarchical-08-secdir-lc-turner-2018-05-29
Hi! I’m no expert on SFC so I spent some time reviewing RFC7665 and Simon Josefsson’s secdir review [0] as well as RFC 8300 and 8393. It looks like all the things I was going to pick on are addressed by the references. I’ll let somebody else on the IESG debate whether Figure 4 is trying to be a little different than the rest of this architectural document by specify some protocols bits; informational still? [0] https://datatracker.ietf.org/doc/review-ietf-sfc-architecture-08-secdir-lc-josefsson-2015-05-28/