[ippm] Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-20: (with DISCUSS and COMMENT)

Gorry Fairhurst via Datatracker <noreply@ietf.org> Sat, 14 June 2025 13:39 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: ippm@ietf.org
Delivered-To: ippm@mail2.ietf.org
Received: from [10.244.8.178] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id CFE8634F07B3; Sat, 14 Jun 2025 06:39:03 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gorry Fairhurst via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.41.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174990834371.300.3017693070913631655@dt-datatracker-75bbdb9cc5-qvb4t>
Date: Sat, 14 Jun 2025 06:39:03 -0700
Message-ID-Hash: 63S7UYLMH5SJZ5WORQ5LROOQGBF4CK5F
X-Message-ID-Hash: 63S7UYLMH5SJZ5WORQ5LROOQGBF4CK5F
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ippm.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-ippm-capacity-protocol@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [ippm] Gorry Fairhurst's Discuss on draft-ietf-ippm-capacity-protocol-20: (with DISCUSS and COMMENT)
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/qL1-2Y9JcYFFXlKLU9xZHSRg7wE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Owner: <mailto:ippm-owner@ietf.org>
List-Post: <mailto:ippm@ietf.org>
List-Subscribe: <mailto:ippm-join@ietf.org>
List-Unsubscribe: <mailto:ippm-leave@ietf.org>

Gorry Fairhurst has entered the following ballot position for
draft-ietf-ippm-capacity-protocol-20: 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-ippm-capacity-protocol/



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

Thank you for this I-D that defines a method for measuring Network Capacity
metrics. The measurement flows generate Internet packet flows that are
rate-controlled. The primary concerns are about the use of Datagrams
(addressing and packet size), the security model, and the congestion control
functions. This is therefore a significant piece of transport work and there is
a much longer than a normal DISCUSS. I hope to update my ballot once
resolutions have been agreed.

DISCUSS Topics from the TSV-ART review.

The I-D needs to therefore consider implications around security. Thanks to the
TSVART team for their review. In the security design, I saw many changes and
thank the editors et al for these updates in the present revision. Thanks.

This review also noted the way that datagram size was handled - and I note that
this is an important part of any service over UDP. In my review, I found the
guidance in the following section is inadequate :
   /A simplified approach is to choose the
   default datagram size small enough to prevent fragmentation.  MTU
   size detection prior to a test is out of scope of this document.  A
   method for a path MTU size discovery, as for example proposed by
   [RFC8899], is left for future design and implementation./

- RFC8899 could indeed be applicable, but the requires support is not defined
in this specification, so this is more than a future implementation issue. This
will actually require changes to the protocol, especially if a method is to be
interoperable.

DISCUSS Topics 1. Normative Dependencies

I would like to discuss the normative dependence on two external references for
key components of the design.

There are two Normative References to external documents:

   [TR-471]   Morton, A,, Editor., "Broadband Forum TR-471: IP Layer
              Capacity Metrics and Measurement, Issue 4", September
              2024, <https://www.broadband-forum.org/technical/download/
              TR-471.pdf>.

   [Y.1540]   ITU-T, "Internet protocol data communication service - IP
              packet transfer and availability performance parameters",
              ITU-T Recommendation Y.1540, December 2019,
              <https://www.itu.int/rec/T-REC-Y.1540-201912-I/en>.

DISCUSS 1.1 What is the process by which these have been revised by the IETF?

- I have a concern about the external definitions for terms, metrics and
algorithms used in this I-D.

- I note that describes itself as a technical report, that has been approved by
members of the Forum and that this Technical Report is subject to change. The
Broadband Forum has submitted a number of revisions of the report TR-471 in
recent years. I would like to discuss whether the normative reference is to a
particular version? If not what is expected if this standard evolves, how will
this evolution be managed?

TR-471 seems to provide relevant, although I have yet to review that in detail
and there is useful information to the use of the method being specified.

DISCUSS 1.2 TR-471 is used to normatively define a set of parameters - this
makes the current I-D normatively dependent on changes to another spec. Has the
working group fully considered the implications of changes to these
specifications, rather than normatively defining the operation to be identical
to the current specification of this external reference?

Examples include:

useOwDelVar

ignoreOooDup: Boolean, see ReordDupIgnoreEnable in Table 3 of  [TR-471].

subIntPeriod: Test Sub-interval period in [ms], see dt (TestSubInterval) in
Table 1 of [TR-471], default 1000 ms. Why is this a suitable interval?

lowThresh, upperThresh: are defined in Table 3 of [TR-471].

testIntTime: see TestInterval, Table 3 of [TR-471].

dscpEcn: specified by [TR-471] (see also my discuss topic 8).

---
DISCUSS Topics 2. This I-D defines a protocol layered on top of UDP. Therefore,
what level of IETF review has been performed to evaluate the way the flow rate
controlled? The I-D is subject to the BCP that defines UDP Usage [RFC8085] that
sets out expectations for when the protocol is used in the Internet. It is
defined for performance testing, and as such it is possible generate
considerable Internet load.

DISCUSS 2.1 RFC 2914 defines the need for congestion control. Section 3.1.1,
3.1.2 and 3.1.5 of RFC 8085 provides the current BCP guidance on Congestion
Control. RFC9743 (BCP 133) provides guidance on how to specify new congestion
control methods. RFC 8084 provides an alternative, to define an envelope that
controls the overall envelope of a connection. I think these RFCs apply to this
I-D. - Was there any review by ICCRG or CCWG, or analysis of the impact from a
congestion control perspective?

DISCUSS 2.2 At the end of Section 4.2:
To ensure readers are clear about the importance, I'd strongly recommend to add
a note stating that the described method is necessary also to avoid potentially
inducing congestion after there is a overload/loss on the control path.

DISCUSS 2.3 In section 7.1: If I understand the sending rate decrease based on
feedback intervals - which seems like it is heading in the correct direction. I
do not see how these intervals are adjusted to the path RTT, could they be?

DISCUSS 2.4 In section 5.1. on the responsiveness (what CC experts often call
aggressive behaviour) of a flow: I note that the LOAD CONTROL as define uses a
statically configured watchdog interval -  which I think allows a flow to
contribute excess congestions for 3 seconds after this is detected, longer if
small levels of loss/congestion is not considered a trigger. For an arbitrary
path RTT this could be a large number of RTTs (e.g. 300 for a 10mS path). -
There are specific recommendations on the use of UDP that describe this case:
RFC 8085.

---
DISCUSS Topics 3: How do we know the suitability of the specified rate
adaptation mechanisms?

DISCUSS 3.1 In section 7.1 there is a description of another alternative
congestion control method. Algorithm (B, see [Y.1540]) is a CC algorithm
defined outside the IETF, please explain how this has been shown to be safe for
use as a CC in the Internet?

DISCUSS 3.2 In section 7.1: The present I-D says:
   /Algorithm B also has two modes for increasing/decreasing the sending
   rate:/

If I understand the sending rate decrease based on feedback intervals - which
seems like it is heading in the correct direction. I did not see how these
intervals adjust to the path RTT. I would like to discuss how they adapt or why
they do not?

DISCUSS 3.3 There seems little discussion of the risk to the network and other
flows when performing a fixed-rate test, or whether this is applicable usage
across an Internet path. The present I-D says:
   /The reasons to conduct a fixed-rate test include
   stable measurement at the maximum determined by the load rate
   adjustment algorithm, or the desire to test at a known subscribed
   rate without searching./

Also:
   /The client MAY communicate the desired fixed rate in its test
   activation request./

I see that the test also maintains rttMinimum and rttVarSample, so this could
be used to develop an Internet circuit breaker as described in RFC 8085, but I
would be keen to understand what sets the acceptable envelop for use across the
Internet.

DISCUSS 3.4 In section 7.2, Status PDU: Please explain (and specify in the
text) what happens in the case of the first para of section 7.2 when there is
severe congestion on the return path - I assume this could result in
significant loss, and no Status PDU is sent?

   The watchdog timer at the Load PDU sender SHALL be reset each time a
   Status PDU is received.  See non-graceful test stop in Section 8 for
   handling the watchdog timeout expiration at each endpoint.

DISCUSS 3.5 In section 7.2, Status PDU. The present I-D says:
/ The watchdog timer at the Load PDU sender SHALL be reset each time a
   Status PDU is received.  See non-graceful test stop in Section 8 for
   handling the watchdog timeout expiration at each endpoint./
- Please explain (and specify in the text) why is it safe to reset the timer
even if the Status PDU does not indicate correct reception?

---
DISCUSS Topics 4. Concurrent flows.

4.1 In section 9.0:
   /It is obviously counterproductive to run more than one independent
   and concurrent test/
- Is there a congestion control or DoS issue here, I think so, can we discuss
why the I-D says this is allowed without a mechanism to defend against this?

---
DISCUSS Topics 5. Definition of an IANA Registry for alternative rate control
algorithms.

The present I-D says: "Test Activation PDU Rate Adjustment Algo.  Registry"
Why should the IETF publish a registry for this protocol with a private space
and no overarching congestion control framework?

In 11.2.8, the present I-D says:

   Value   Description             Reference
   (Numeric)
   ===================================================
    A(n/a)  Not used                <this RFC>

    B(0)    Rate algorithm Type B   <this RFC>

    C(1)    Rate algorithm Type C   <this RFC>

   Table 16: Initial Test Activation PDU Rate Adjustment Algo. values

DISCUSS 5.1: What is Value A in Table 16 (PDU Rate Adjustment)?

DISCUSS 5.2 : There is no specification in this I-D for these algorithms.

And related, please explain the testing for use of this algorithm:
   /An OPTIONAL load rate adjustment algorithm (designated C) has been
   defined in [TR-471].  Algorithm C operation and modes are similar to
   B, but C uses multiplicative increases in the fast mode to reach the
   Gigabit range quickly and adds the possibility to re-try the fast
   mode during a test (which improves the measurement accuracy in
   dynamic or error-prone access, such as radio access)./

DISCUSS 5.3 RFC 9473 has provided guidance on the IETF process if this is being
considered for use on Internet paths. Why is the IETF standardising use of a
rate adjustment algorithm defined elsewhere, without bounding its over-arching
congestion control properties? Please explain how these methods were evaluated,
and by whom. How in the future will this be tested for congestion control and
how this will be maintained.

DISCUSS 5.4  What is the scope of use for a rate adjustment algorithm defined
as experimental. RFC 9473 provided guidance on this topic. Why is this not
scoped only for use in limited domains?

---
DISCUSS Topics 6. How are the congestion control methods evaluated and
specified?

DISCUSS 6.1 Please see this text:
 /On the other hand, the test configuration MAY use a fixed sending
   rate requested by the client, using the field srIndexConf./
- A fixed rate test brings additional concerns, and I didn't find this
analysis. Is there a need to scope this as a non-default mode? Should it be
restricted to certain domains.

DISCUSS 6.2 Please add a note to the reaction to lack of feedback in Section
4.2: I agree that "the test session will prematurely terminate (no further load
traffic SHALL be transmitted)"

- To be clear about the importance, I'd recommend to add a note saying this is
necessary also to avoid potentially inducing congestion after there is a
overload/loss on the control path.

---
DISCUSS Topic 7: UDP Checksum Usage

- I have concerns around the definition of method that uses an optional
checksum. Section 3.4 of RFC 8085 provides the IETF current BCP on this topic
for both IPv4 and IPv6.

DISCUSS 7.1 In Section 4.5 on Optional Checksum.
- Why does this does not be enable the UDP checksum for IPv4, this would align
with RFC8085.

DISCUSS 7.2 IPv6 requires a UDP checksum except for very specific usage, this
does not appear to be one of those cases (tell me if I am wrong), and so can
this require an IPv6 checksum?

---
DISCUSS Topic 8: ECN:

I can't understand if this I-D is intended to refer to ECN or not, but it does
mention the ECN code point in a variable definition. RFC 3819 specifies the
requirements for new transport methods to utilise an ECT() code point (see also
3.1.7 of RFC 8085). The transfer as defined does not support ECN, i.e. it does
not change its rate in response to ECN marks. TR471 is silent about the use of
ECN.

8.1  I think that this violates the conditions under which ECT() can be sent
and I assert that it needs to explain that the ECN field is always set to zero
(not-ECT) with this version of the specification.

---
DISCUSS Topic 9: Use of Addresses:
Specification (or non-specification) of support for Multicast, Broadcast and
Anycast addresses.

9.1 I think this looks like it has no multicast considerations and hence it
ought to be scoped to only unicast and not broadcast or multicast addresses. 
Could this be specified for unicast address only ?

9.2 Could this method be used with an Anycast address?

---
DISCUSS Topic 10: Some parameters appear underspecified in this I-D, please
check. e.g.:

seqErrLoss/seqErrOoo/seqErrDup

===


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

I have a number of non-blocking comments that I expect could be addressed in
the next revision of this I-D:

In section 3:
Typos:/resepcitvely/respectively/
/the bottleneck is congested,/if the bottleneck is congested,/
In section 4.2:
- Is /Once the modes requiring or optionally adding
   authentication or encryption are implemented and configured locally,
   the unauthenticated mode must be disabled./ - Could this be a MUST?
In section 5,1: /A IANA is/IANA is/
In section 5.2.2: I expect the following text helps, but does this ensure or
assist in the firewall traversal? /To ensure that a server's local firewall
will successfully allow
   packets received for the new ephemeral port, the server SHALL
   immediately send a Null Request with the corresponding values
   including the source and destination IP addresses and port numbers./
In 6.1,  /continuosly/continuously/
In 6.2, Server Processes Test Activation Request and Generates Response:

In this I-D, the following keyword use seems odd to me and could be improved:
 /   After the server receives the Test Activation Request on the new
     connection, it MUST choose to accept, ignore or modify any of the
     test parameters. /
- is this an exclusive list of things that is required or a list of all that
are required? I do wonder if this is simply a list of what the protocol does
next?

In section 12: /comprehensability/comprehensibility/
Also in section 12: /sheperded/shepherded/