[mpls] Barry Leiba's No Objection on draft-ietf-mpls-sfl-framework-10: (with COMMENT)

[Barry Leiba via Datatracker <[e-mail]>]

Barry Leiba has entered the following ballot position for
draft-ietf-mpls-sfl-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/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-mpls-sfl-framework/



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

Thanks for a clear, well-written document that was an easy read.  Just a few
nits here:

— Section 3 —

   would introduce network wide forwarding state.

“network-wide” needs a hyphen

   Note that to achieve the goals set out above SFLs need to be
   allocated from the platform label table.

A comma after “above” will help readability here (avoiding a reading of “above
SFLs”).

— Section 4.1 —
The title says “applications label” and the first paragraph says “application
label”.  It seems that this should be consistent.

   function present runs over the "normal" stack, and SFL enabled flows

“SFL-enabled” needs a hyphen (also in Section 4.2).

— Section 4.1.1 —

   However it is recognised that, if
   there is an applications need, the SFL MAY be to some other value.

I think “MAY be set to some other value” (add “set”) reads better.

— Section 4.2 —

   If the LSP label is present, it processed exactly as it would
   normally processed and then it is popped.

Missing words: “it is processsed” and “normally be processed”.

   This reveals the SFL which
   in the case of [RFC6374] measurements is simply counted and then

Punctuation: “SFL, which, in the case of [RFC6374] measurements, is”

   system described in this document the behaviour of two approaches are
   indistinguishable and thus either may be implemented.

Missing word: “of the two approaches”.
And “behaviours”, needs to be plural.

— Section 4.3 —

   application is large, and consequently the increase in the number of
   allocated labels needed to support the SFL actions consequently
   becomes too large to be viable.

You have “consequently” twice, and should remove one of them.

— Section 5 —

   The introduction to an SFL to an existing flow may cause that flow to

Make it, “The introduction of an SFL to an existing flow”.

   This in turn may invalidate the certain uses

Remove “the”.

— Section 6 —

   This privacy threat may
   be mitigated by encrypting the control protocol packets, regularly
   changing the synonymous labels and by concurrently using a number of
   such labels.

The second item isn’t parallel to the other two.  Either make it “by regularly”
(to make the second item match the third) or remove “by” before “concurrently”
(to make the third match the second).

Also, is “and” right?  Would you do all three of these together?  Or should it
be “or”?  I’m not sure, but I wanted to check.