[manet] Re: Roman Danyliw's Discuss on draft-ietf-manet-dl ep-traffic-classification-13: (with DISCUSS and COMMENT)

Don Fedyk <[email protected]>
Newsgroups gmane.ietf.manet
Message-ID <PH7PR14MB53680B78C570EC28C99E8C4EBBD92@PH7PR14MB5368.namprd14.prod.outlook.com>
Hi Roman

Thanks for your review and comments.  We have updated the draft Based on all input.   I think I have addressed your points.
https://www.ietf.org/archive/id/draft-ietf-manet-dlep-traffic-classification-14.txt
Please check the current IANA request. I cleaned up the text. We are asking for a range that is Specification Required not expert review.

Thanks
Don

________________________________
From: Roman Danyliw via Datatracker <[email protected]>
Sent: Monday, February 3, 2025 4:42 PM
To: The IESG <[email protected]>
Cc: [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>; [email protected] <[email protected]>
Subject: Roman Danyliw's Discuss on draft-ietf-manet-dlep-traffic-classification-13: (with DISCUSS and COMMENT)

Roman Danyliw has entered the following ballot position for
draft-ietf-manet-dlep-traffic-classification-13: 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/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-manet-dlep-traffic-classification/



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

** Section 5.2 defines a registry which includes code points with an allocation
policy of Specification Required.  Implicit in policy is the review of a
designated expert (DE).  However, this document does not provide guidance to
the DE on what to approve.  See Sections 4.5 and 4.6 of RFC8126.


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

** Section 2.  Editorial.
   The Traffic Classification Data Item represents a list of flows that
   may be used at the same time for traffic sent from a router to a
   modem.

"Used at the same time" to do what?

** Section 2.1
  When an extension requires use of this
   Data Item the Traffic Classification Data Item SHOULD be included by
   a modem in any Session Initialization Response Message

-- Are “Data Item” and “Traffic Classification Data Item” the same data item?

-- What is the alternative to using his Data Item in a Session Initialization
Response Message?

** Section 5.2.  Should the new registry defined in this section have an
additional column which is a reference to a document which provides further
details?

_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.