Last Call Review of draft-ietf-spring-segment-routing-msdc-08
review-ietf-spring-segment-routing-msdc-08-opsdir-lc-tsou-2018-01-18-00
Request | Review of | draft-ietf-spring-segment-routing-msdc |
---|---|---|
Requested revision | No specific revision (document currently at 11) | |
Type | IETF Last Call Review | |
Team | Ops Directorate (opsdir) | |
Deadline | 2017-12-14 | |
Requested | 2017-11-30 | |
Authors | Clarence Filsfils , Stefano Previdi , Gaurav Dawra , Ebben Aries , Petr Lapukhov | |
I-D last updated | 2019-12-06 (Latest revision 2018-11-29) | |
Completed reviews |
Rtgdir IETF Last Call review of -03
by Susan Hares
(diff)
Opsdir IETF Last Call review of -08 by Tina Tsou (Ting ZOU) (diff) Secdir IETF Last Call review of -06 by Takeshi Takahashi (diff) Tsvart Telechat review of -08 by Martin Stiemerling (diff) |
|
Assignment | Reviewer | Tina Tsou (Ting ZOU) |
State | Completed | |
Request | IETF Last Call review on draft-ietf-spring-segment-routing-msdc by Ops Directorate Assigned | |
Reviewed revision | 08 (document currently at 11) | |
Result | Ready | |
Completed | 2018-01-18 |
review-ietf-spring-segment-routing-msdc-08-opsdir-lc-tsou-2018-01-18-00
Dear all, Reviewer: Carlos Martinez Review Result: Ready 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. I found this document well written to be READY for publication as an informational document. Some nits: 4.2 eBGP Labeled Unicast (RFC8277) Each node peers with its neighbors via a eBGP session should be Each node peers with its neighbors via an eBGP session 7. Addressing the open problems the same could be re-used in context of other domains as well A period is missing in the end. Are the centralized controller and centralized agent the same components? Even though the design in this document is specified for same domain, it would be useful to develop an approach for inter-domain without leaking intra-domain topology and policy. Have this feature been included or being aligned with carrier grade FIB in FD.io VPP https://wiki.fd.io/view/VPP ? -- Thank you, Tina