[tsvwg] Re: I-D Action: draft-ietf-tsvwg-nqb-26.txt

[Sebastian Moeller <[e-mail]>]

Hi Greg, Thomas, Ruediger,


please remove my name from the acknowledgements section. I want no connection with this ID/RFC.

Sebastian


> On 22. Oct 2024, at 05:53, Greg White <g.white=[e-mail]> wrote:
> 
> All,
> 
> This update includes edits in the Wi-Fi section that are aimed at addressing the WGLC comments raised by David Black.  This was the last remaining item that we had planned to work on as an outcome of the discussion of WGLC comments at IETF 120.  I also took this opportunity to polish a few other sentences in the draft.  At this point I believe that we have closed all open issues.
> 
> Thank you to everyone who chimed in with their support for moving to finalize the draft. I know that there are many network operators and application developers who have been waiting for the IETF process to conclude before beginning to turn on NQB support, and I hope we are now very near the time that they can begin that process.
> 
> Greg
> 
> 
> On 10/21/24, 4:40 PM, "[e-mail] <mailto:[e-mail]>" <[e-mail] <mailto:[e-mail]>> wrote:
> 
> 
> Internet-Draft draft-ietf-tsvwg-nqb-26.txt is now available. It is a work item
> of the Transport and Services Working Group (TSVWG) WG of the IETF.
> 
> 
> Title: A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services
> Authors: Greg White
> Thomas Fossati
> Rüdiger Geib
> Name: draft-ietf-tsvwg-nqb-26.txt
> Pages: 37
> Dates: 2024-10-21
> 
> 
> Abstract:
> 
> 
> This document specifies characteristics of a Non-Queue-Building Per-
> Hop Behavior (NQB PHB). The NQB PHB provides a shallow-buffered,
> best-effort service as a complement to a Default deep-buffered best-
> effort service for Internet services. The purpose of this NQB PHB is
> to provide a separate queue that enables smooth (i.e. non-bursty),
> low-data-rate, application-limited traffic microflows, which would
> ordinarily share a queue with bursty and capacity-seeking traffic, to
> avoid the latency, latency variation and loss caused by such traffic.
> This PHB is implemented without prioritization and can be implemented
> without rate policing, making it suitable for environments where the
> use of these features is restricted. The NQB PHB has been developed
> primarily for use by access network segments, where queuing delays
> and queuing loss caused by Queue-Building protocols are manifested,
> but its use is not limited to such segments. In particular,
> applications to cable broadband links, Wi-Fi links, and mobile
> network radio and core segments are discussed. This document
> recommends a specific Differentiated Services Code Point (DSCP) to
> identify Non-Queue-Building microflows, and updates the RFC8325
> guidance on mapping Diffserv to IEEE 802.11 for this codepoint.
> 
> 
> [NOTE (to be removed by RFC-Editor): This document references an ISE
> submission draft (I-D.briscoe-docsis-q-protection) that is approved
> for publication as an RFC. This draft should be held for publication
> until the queue protection RFC can be referenced.]
> 
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/ <https://datatracker.ietf.org/doc/draft-ietf-tsvwg-nqb/>
> 
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-tsvwg-nqb-26.html <https://www.ietf.org/archive/id/draft-ietf-tsvwg-nqb-26.html>
> 
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-nqb-26 <https://author-tools.ietf.org/iddiff?url2=draft-ietf-tsvwg-nqb-26>
> 
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts