[Detnet] Roman Danyliw's No Objection on draft-ietf-detnet-oam-framework-10: (with COMMENT)

[Roman Danyliw via Datatracker <[e-mail]>]

Roman Danyliw has entered the following ballot position for
draft-ietf-detnet-oam-framework-10: 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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


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



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

** Section 2.
   Many legacy OAM tools can be used in DetNet networks, but they are
   not able to cover all the aspects of deterministic networking.

What is a legacy tool?

** Section 2.

   For example, appropriate placing of MEPs along the path of a DetNet
   flow is not always a trivial task and may require proper design,
   together with the design of the service component of a given DetNet
   flow.

Agreed.  However, it seems me to that there is a missing sentence explicitly
linking OAM to placing these MEPs.

** Section 8.  This section seems to be missing mentioned that OAM mechanism
could be tampered with depending on their construction and that some OAM tools
are dual-use potentially enabling reconnaissance by an attacker.  These and
other topics are covered in the Security Considerations of RFC7276.

** Section 9.  The GENART reviewer (Mallory Knodel) also notes that OAM
mechanism can be used as the further basis of reconnaissance by fingerprinting
their features.