Skip to main content

Last Call Review of draft-ietf-teas-actn-framework-13
review-ietf-teas-actn-framework-13-opsdir-lc-bradner-2018-04-29-00

Request Review of draft-ietf-teas-actn-framework
Requested revision No specific revision (document currently at 15)
Type Last Call Review
Team Ops Directorate (opsdir)
Deadline 2018-04-30
Requested 2018-04-16
Authors Daniele Ceccarelli , Young Lee
I-D last updated 2018-04-29
Completed reviews Rtgdir Last Call review of -11 by Bruno Decraene (diff)
Genart Last Call review of -13 by Peter E. Yee (diff)
Secdir Last Call review of -13 by Catherine Meadows (diff)
Opsdir Last Call review of -13 by Scott O. Bradner (diff)
Genart Telechat review of -14 by Peter E. Yee (diff)
Assignment Reviewer Scott O. Bradner
State Completed
Request Last Call review on draft-ietf-teas-actn-framework by Ops Directorate Assigned
Reviewed revision 13 (document currently at 15)
Result Has nits
Completed 2018-04-29
review-ietf-teas-actn-framework-13-opsdir-lc-bradner-2018-04-29-00
I did an OPS-DIR review of Framework for Abstraction and Control of Traffic
Engineered Networks (draft-ietf-teas-actn-framework-13). As a framework
document rather than a technical specification this document does not have any
direct operational issues though the framework is for a technology that is "all
operations." With that in mind I did not see any particular operational worry
other than the overall complexity of the solution.

I will defer to Bruno Decranene's review for his detailed listing of nits.

My only real comment is a meta one - I generally question the likelihood of
widespread use of a system of this level of multi-player complexity in
environments where it is reasonably easy to throw bandwidth at this class of
problem.

That said, I see no reason to not publish this as an Informational RFC just in
case the thought that went into this could be useful to others or, maybe, if
the use of the technology itself proves to be more cost effective than adding
bandwidth.