[Teas] Benjamin Kaduk's No Objection on draft-ietf-teas-actn-framework-14: (with COMMENT)

[Benjamin Kaduk <[e-mail]>]

Benjamin Kaduk has entered the following ballot position for
draft-ietf-teas-actn-framework-14: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-teas-actn-framework/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for the clear and easy-to-follow document!

I do have a few minor comments, below.


Section 3

Please expand OSS and NMS on first usage.

Section 3.2

   [...] The two functions of the MDSC,
   namely, multi-domain coordination and virtualization/abstraction are
   referred to as network-related functions while the other two
   functions, namely, customer mapping/translation and virtual service
   coordination are referred to as service-related functions.

Starting out with "The two" implies that there are no others, which
is contradicted by "the other two" later.  So, I'd suggest just
starting with "Two functions of the MDSC ...".

Section 3.3

Please expand NBI (which appears to only be used once in the
document).

Section 5.3.2

It seems pretty likely that allowing repeated path computation
requests (with different parameters) would allow a malicious MDSC to
learn a fair amount of information about the topology that the PNC
is attempting to abstract away.  This is probably not a huge deal,
though.

Section 8.3

   A key objective of the MDSC is to support the customer's expression
   of the application connectivity request via its CNC as set of
   desired business needs, therefore policy will play an important
   role.

nit: "as a set of"

   Once authorized, the virtual network service will be instantiated
   via the CNC-MDSC Interface (CMI), it will reflect the customer
   application and connectivity requirements, and specific service
   transport needs.

nit: this is a comma splice; I'd change the comma before "it" to
either a semicolon or a period.  (There's a similar issue in the
following sentence, too.)

Section 9.2

Perhaps we should say something about configuring trust anchors for the PKI,
e.g., using a smaller set of trusted CAs than in the Web PKI.