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

[[e-mail]]

Hi Greg,

draft says
3.1.  Non-Queue-Building Behavior
https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-nqb-14#section-3.1
   Other types of QB flows include those that frequently send
   at a high burst rate (e.g., several consecutive packets sent well in
   excess of 1 Mbps) even if the long-term average data rate is much
   lower.

[RG] I assume the server to be NQB compliant, if it sends several consecutive packets not in excess of 1 Mbps. Correct?

If yes, please clarify what's meant by the statement:
- the server isn't allowed to send packets with a spacing corresponding to 1 Mbit/s
- the server isn't allowed to send more than <1 Mbps * 1 sec> [bit] per second
- other (please be precise)

Regards,

Ruediger



-----Ursprüngliche Nachricht-----
Von: tsvwg <[e-mail]> Im Auftrag von Greg White
Gesendet: Montag, 24. Oktober 2022 21:22
An: [e-mail]
Betreff: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-nqb-14.txt

TSVWG participants,

I've uploaded two revisions of the NQB draft recently:  draft-13 on Friday, and draft-14 today.  Draft-14 was the result of a top-to-bottom editorial review by my co-author, which uncovered some inconsistent punctuation, and a number of other typographical changes (thanks Thomas!).

Here is a summary of the changes.

Draft-13 (relative to Draft-12): diff here: https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-nqb-13
- Add a clarification in the Security Guidelines section
- Expand "UEs" to "User Equipment"
- Insert a comma in 8.3.1

Draft-14 (relative to Draft-13): diff here: https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-nqb-14
- More consistent usage of commas
- More consistent usage of hyphens
- More consistent capitalization of terms
- Simplifying the wording in several cases (e.g., "The vast majority of packets" became "Most packets")
- Other similarly minor editorial changes

While draft-14 contains quite a lot of individual edits, in all, the only changes in these two revisions that border on being of substance are:

The deletion of the word "fairly" in this recommendation sentence in the 4th paragraph of Section 4.1:
If the application's traffic exceeds more than a few packets per RTT or exceeds a fairly small fraction of the expected path capacity on an instantaneous (e.g., inter-packet, or a suitably short time interval) basis, the application SHOULD NOT mark its traffic with the NQB DSCP.
See: https://www.ietf.org/rfcdiff?url1=draft-ietf-tsvwg-nqb-13&url2=draft-ietf-tsvwg-nqb-14&difftype=--html#part-6

The additional text in Section 11. Security Guidelines explaining on-path attacks.
See: https://www.ietf.org/rfcdiff?url1=draft-ietf-tsvwg-nqb-12&url2=draft-ietf-tsvwg-nqb-13&difftype=--html#part-5


At this point, the authors believe that the NQB draft as contained in draft-ietf-tsvwg-nqb-14 is ready to begin WGLC.


Best Regards,
Greg








On 10/24/22, 12:39 PM, "tsvwg on behalf of [e-mail]" <[e-mail] on behalf of [e-mail]> wrote:


    A New Internet-Draft is available from the on-line Internet-Drafts directories.
    This draft is a work item of the Transport Area Working Group WG of the IETF.

            Title           : A Non-Queue-Building Per-Hop Behavior (NQB PHB) for Differentiated Services
            Authors         : Greg White
                              Thomas Fossati
      Filename        : draft-ietf-tsvwg-nqb-14.txt
      Pages           : 22
      Date            : 2022-10-24

    Abstract:
       This document specifies properties and characteristics of a Non-
       Queue-Building Per-Hop Behavior (NQB PHB).  The purpose of this NQB
       PHB is to provide a separate queue that enables smooth, low-data-
       rate, application-limited traffic flows, 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 without rate policing,
       making it suitable for environments where the use of these features
       may be 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 flows.


    The IETF datatracker status page for this draft is:
    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-14.html

    A diff from the previous version is available at:
    https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-nqb-14


    Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts