[OPSAWG] Zaheduzzaman Sarker's Discuss on draft-ietf-opsawg-l3sm-l3nm-11: (with DISCUSS and COMMENT)

[Zaheduzzaman Sarker via Datatracker <[e-mail]>]

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-opsawg-l3sm-l3nm-11: Discuss

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/blog/handling-iesg-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-opsawg-l3sm-l3nm/



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

This specification refers to ietf-opsawg-vpn-common for qos related matching,
hence I am raising similar discussion as I had for ietf-opsawg-vpn-common (see
here https://datatracker.ietf.org/doc/draft-ietf-opsawg-vpn-common/).

This specification specifies qos classification based on L4 criteria and
describes the procedure for TCP and UDP. It is possible that new L4 protocols
(for example QUIC) use UDP as substrate hence can create ambiguity based of the
procedure described in the specification.

This specification should consider such potential substrate usage of L4
protocols (specially UDP) and hint on the potential augmentations (there might
be several ways to do that) or scope it down to not support such cases.


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

Thanks to the authors for their efforts in the specification.

Additional comment(s)-

* I think if would be good if this specification also discusses the implication
of wrong classification (e.g. for qos) based on the model specified here (no
particular suggestion from me where but may be in security considerations).