From: Dave Taht <dave.taht@gmail.com>
To: libreqos <libreqos@lists.bufferbloat.net>,
bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Fwd: [ippm] Document Action: 'Explicit Host-to-Network Flow Measurements Techniques' to Informational RFC (draft-ietf-ippm-explicit-flow-measurements-07.txt)
Date: Thu, 17 Aug 2023 07:33:20 -0700 [thread overview]
Message-ID: <CAA93jw5-a9T4BtHR7z7G9wpWV+efR9-KRtBfuc5btsLru1MPRg@mail.gmail.com> (raw)
In-Reply-To: <169222140422.60254.22895342511784569@ietfa.amsl.com>
There is some hope in measuring quic now
---------- Forwarded message ---------
From: The IESG <iesg-secretary@ietf.org>
Date: Wed, Aug 16, 2023 at 2:30 PM
Subject: [ippm] Document Action: 'Explicit Host-to-Network Flow
Measurements Techniques' to Informational RFC
(draft-ietf-ippm-explicit-flow-measurements-07.txt)
To: IETF-Announce <ietf-announce@ietf.org>
Cc: <ippm-chairs@ietf.org>, <ippm@ietf.org>,
<draft-ietf-ippm-explicit-flow-measurements@ietf.org>, The IESG
<iesg@ietf.org>, <rfc-editor@rfc-editor.org>
The IESG has approved the following document:
- 'Explicit Host-to-Network Flow Measurements Techniques'
(draft-ietf-ippm-explicit-flow-measurements-07.txt) as Informational RFC
This document is the product of the IP Performance Measurement Working Group.
The IESG contact persons are Zaheduzzaman Sarker and Martin Duke.
A URL of this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-explicit-flow-measurements/
Technical Summary
This document describes protocol independent methods called Explicit
Host-to-Network Flow Measurement Techniques that can be applicable to
transport-layer protocols between client and server. These methods
employ just a few marking bits inside the header of each packet for
performance measurements and require collaborative client and server.
Both endpoints cooperate by marking and, possibly, mirroring
information back and forward on the round-trip connection. The
techniques are especially valuable when applied to protocols that
encrypt transport headers, since they enable loss and delay
measurements by passive on-path network devices. Different
techniques are considered within this document.
Working Group Summary
Like most IPPM documents, this represents strong concurrence
from part of the WG and acquiescence from the remainder.
Document Quality
While this is not a protocol document per se, there are implementations of
the mechanisms described in the document.
Akamai and Orange have implemented setting and reading of L and Q bits for
loss measurements for QUIC traffic.
The open source tool spindump by Ericsson research contains logic for reading
bits of most proposals in this document.
Telecom Italia have implemented setting of delay, RT-loss etc in a
forked QUIC
implementation. They have also extended spindump and integrated it in
measurement tools.
Huawei have expressed interest in implementing mechanisms described in the
document.
Personnel
The Document Shepherd for this document is Marcus Ihlar. The Responsible
Area Director is Martin Duke.
IESG Note
This information draft is a merger of 6 (!) different drafts,
accounting for the over-long author list.
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm
--
Podcast: https://www.youtube.com/watch?v=bxmoBr4cBKg
Dave Täht CSO, LibreQos
parent reply other threads:[~2023-08-17 14:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <169222140422.60254.22895342511784569@ietfa.amsl.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5-a9T4BtHR7z7G9wpWV+efR9-KRtBfuc5btsLru1MPRg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=libreqos@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox