[tsvwg] Re: draft-song-opsawg-ipfix-ecn update

[[e-mail]]

Hi Djamel,

The current draft focuses on packet-level counters, because one main L4S use case is congestion signal analysis, which is packet-level. But agree with you, in some cases, such as per-codepoint bandwidth utilization analysis, byte-level counters would be useful. 
We can add byte level counters in the next version, thank you for your suggestion.


Best regards,
Xueyan









Original


From: DjamelSadok <[e-mail]>
To: Koen De Schepper (Nokia) <koen.de_schepper=[e-mail]>;
Cc: 宋雪雁00038118;[e-mail] <[e-mail]>;
Date: 2026年07月30日 23:51
Subject: Re: [tsvwg] Re: draft-song-opsawg-ipfix-ecn update




Hi Song, thank you for the draft,

Is there a reason for not including byte level monitoring in addition to packet numbers? 

Djamel




--------------------------------------------------------------------------------

From: "Koen De Schepper (Nokia)" <koen.de_schepper=[e-mail]>
To: "song xueyan2" <[e-mail]>, [e-mail]
Sent: Tuesday, July 28, 2026 1:17:19 PM
Subject: [tsvwg] Re: draft-song-opsawg-ipfix-ecn update



Hi Xueyan,
 
Thanks for bringing this draft for the important topic of ECN monitoring (especially for L4S) to the IETF.
 
I’m not so familiar with IPFIX, so some questions from the viewpoint of a potential user:

Are these IEs related to the ECN field that is observed from passing traffic at the observation point?

Or is it related to what the network node is applying/changing in the ECN field(s) (only related to nodes that are changing ECN for setting CE, I hope)

How can I detect the level of CE “setting” on a link in a NW node?

Can I derive the rate per flow that this node is limiting to? (if you know the node’s per link mark “setting” rate, you can calculate the estimated maximum rate per flow on that link by r = 1/p – 1 in Mbps)

Do you plan to provide extra counters that are related to “the setting” of ECN codepoints or do you foresee a mechanism to derive it in some way?

Can these ECN changes also be done per original codepoint. This would be useful to know if ECT0 is transitioned into CE or ECT1 to CE. But not all (if any) HW might be capable of directly providing this info?


 
Maybe a section with some suggestions on how to use these information elements for L4S might be useful (which can answer the above questions)?
 
Regards,
Koen.
 
 

From: [e-mail] <[e-mail]> 
 Sent: Friday, July 24, 2026 7:15 AM
 To: [e-mail]
 Subject: [tsvwg] draft-song-opsawg-ipfix-ecn update


 


 


CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information.

 
Hi TSVWG,
 
Due to time constraints, we unfortunately did not have the chance to present and discuss the change of draft-song-opsawg-ipfix-ecn during the session.
To move the draft forward, I would like to share the link of presentation slides and latest v-03 for your review.
Presentation slides: https://datatracker.ietf.org/doc/slides-126-tsvwg-export-of-ecn-information-in-ipfix/ 
Latest drfat version: https://datatracker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/ 
 
We would appreciate your review and feedback, and continued discussion on the list.
 
Best regards,
Xueyan (on behalf-of co-authors)