[Teas] Opsdir last call review of draft-ietf-teas-actn-framework-13

Scott Bradner <sob@sobco.com> Sun, 29 April 2018 19:34 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Scott Bradner <sob@sobco.com>
To: ops-dir@ietf.org
Cc: draft-ietf-teas-actn-framework.all@ietf.org, ietf@ietf.org, teas@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152503048609.328.6923654156090705843@ietfa.amsl.com>
Date: Sun, 29 Apr 2018 12:34:46 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/vz7b6HYgmJzg5AO9jIoMqI3Fows>
Subject: [Teas] Opsdir last call review of draft-ietf-teas-actn-framework-13

Reviewer: Scott Bradner
Review result: Has Nits

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.

[Teas] Opsdir last call review of draft-ietf-teas… Scott Bradner
Re: [Teas] Opsdir last call review of draft-ietf-… Leeyoung