[manet] Re: Murray Kucherawy's Discuss on draft-ietf-manet -dlep-traffic-classification-13: (with DISCUSS and COMMENT)

Thanks for the fast response perhaps we can resolve this.

We asked for a Traffic Classification code entry out of an existing block
This has its own registry that has two entries based on the traffic marking for QoS either Diff Serv Code Points or Ethernet DSCPs.  If any other entries desired in they future , they would have to be some identifier in a packet or a frame that could be used to indicate a separate queue/QoS treatment.   We left that for future.
We expect a new draft will have to be written that justifies the entry.

So how do we make that more clear?

Thanks
Don



________________________________
From: Murray S. Kucherawy
Sent: Wednesday, March 19, 2025 7:30 PM
To: Don Fedyk
Cc: The IESG; [email protected]; [email protected]; [email protected]; [email protected]
Subject: Re: Murray Kucherawy's Discuss on draft-ietf-manet-dlep-traffic-classification-13: (with DISCUSS and COMMENT)

On Thu, Mar 20, 2025 at 2:23 AM Don Fedyk <[email protected]<mailto:[email protected]>> wrote:
Thanks for you comments we have posted a version that tries to address all the 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.

Hi Don,

I'm looking at a diff between -13 and -14, and it doesn't look like anything changed that addresses the concern with Section 5.2.  You're still asking for a "Specification Required" chunk of the registry, but providing no advice to the designated experts for the registry regarding how they should resolve requests for that block.

Also note that my DISCUSS has no power anymore as my term has ended.  I'm happy to continue the conversation though, plus I think my replacement is likely to take ownership of it at some point soon.

-MSK

_______________________________________________
manet mailing list -- [email protected]
To unsubscribe send an email to [email protected]