[OPSAWG]Re: Fw: New Version Notification for draft-song-op sawg-ipfix-ecn-00.txt

Greg Mirsky <[email protected]> Sat, 10 Jan 2026 13:59:56 -0800
Newsgroups gmane.ietf.opsawg,gmane.ietf.tsvwg,gmane.ietf.mpls
Message-ID <CA+RyBmWrneCE99Ju_g_4w+Ajfb=RM1iBJQP6595Z35=0ESFQXg@mail.gmail.com>
--===============2808008424199414060==
Content-Type: multipart/alternative; boundary="000000000000d9a18306480fc396"

--000000000000d9a18306480fc396
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Xueyan,
thank you for sharing the updated draft. A relatively new draft
draft-halmir-mpls-ecn
<https://datatracker.ietf.org/doc/draft-halmir-mpls-ecn/> on supporting ECN
in the MPLS using MNA might be of interest to you and others involved in
the matter. And I have a question. As I understand the ECN, it is a host
that is expected to act on the information collected in the ECN field along
the path of a packet. If that is correct, who's the intended target of the
IPFIX notification about the ECN? Is the intention to act on ECN
information obtained on a segment, e.g., a tunnel, rather than based on the
e2e ECN information? I read Section 5, but was left with these questions.

Regards,
Greg

On Fri, Jan 9, 2026 at 1:53=E2=80=AFAM <[email protected]> wrote:

> Hello OPSAWG and TSVWG,
>
>
> We submited a new draft and posted it in the IETF datatracker
> <https://datatracker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/>
> https://datatracker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/
>
> The following IPFIX information elements are introduced for L4S ECN
> monitoring:
>
> - ECN field capture in protocol layer, including ECN field in IPv4/IPv6
> ECN field, MPLS EXP and tunnel ECN negotiation status
>
> - ECN codepoint statistics, including incremenatl and total count for
> non-ECT, ECT(0), ECT(1) and CE packets
>
> - L4S performance indicator, providing short-term and long-term view of
> congestion experienced by L4S traffic
>
>
> Your review, comments and questions are welcome.
>
>
> Best regards,
>
> Xueyan
>
>
> Original
> *From: *[email protected] <[email protected]>
> *To: *=E5=AE=8B=E9=9B=AA=E9=9B=8100038118;=E5=88=98=E5=B0=A700165286;
> *Date: *2025=E5=B9=B412=E6=9C=8826=E6=97=A5 16:33
> *Subject: **New Version Notification for
> draft-song-opsawg-ipfix-ecn-00.txt*
> A new version of Internet-Draft draft-song-opsawg-ipfix-ecn-00.txt has be=
en
> successfully submitted by Xueyan Song and posted to the
> IETF repository.
>
> Name:     draft-song-opsawg-ipfix-ecn
> Revision: 00
> Title:    Export of L4S ECN in IP Flow Information Export (IPFIX)
> Date:     2025-12-26
> Group:    Individual Submission
> Pages:    14
> URL:
> https://www.ietf.org/archive/id/draft-song-opsawg-ipfix-ecn-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/
> HTML:
> https://www.ietf.org/archive/id/draft-song-opsawg-ipfix-ecn-00.html
> HTMLized:
> https://datatracker.ietf.org/doc/html/draft-song-opsawg-ipfix-ecn
>
>
> Abstract:
>
>    This document defines a set of IP Flow Information Export (IPFIX)
>    Information Elements for monitoring the Low Latency, Low Loss, and
>    Scalable throughput (L4S) service.  Specially, these elements enable
>    network operators to monitor the Explicit Congestion Notification
>    (ECN) information of L4S deployment and performance of traffic.
>
>
>
> The IETF Secretariat
>
>
> _______________________________________________
> OPSAWG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
>

--000000000000d9a18306480fc396
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Xueyan,<div>thank you for sharing the updated draft. A=
=C2=A0relatively new draft=C2=A0<a href=3D"https://datatracker.ietf.org/doc=
/draft-halmir-mpls-ecn/">draft-halmir-mpls-ecn</a>=C2=A0on supporting ECN i=
n the MPLS using MNA might be of interest to you and others involved in the=
 matter. And I have a question. As I understand the ECN, it is a host that =
is expected to act on the information collected in the ECN field along the =
path of a packet. If that is correct, who&#39;s the intended target of the =
IPFIX notification about the ECN? Is the intention to act on ECN informatio=
n obtained on a segment, e.g., a tunnel, rather than based on the e2e ECN i=
nformation? I read Section 5, but was left with these questions.</div><div>=
<br></div><div>Regards,</div><div>Greg</div></div><br><div class=3D"gmail_q=
uote gmail_quote_container"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, J=
an 9, 2026 at 1:53=E2=80=AFAM &lt;<a href=3D"mailto:[email protected]=
">[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex"><div><p style=3D"font-size:14px;font-family:=E5=BE=
=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&quot;">Hello OPSAWG an=
d TSVWG,</p><p style=3D"font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=
=85=E9=BB=91,&quot;Microsoft YaHei&quot;"><br></p><p style=3D"font-size:14p=
x;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&qu=
ot;">We submited a new draft and posted it in the IETF datatracker=C2=A0<a =
href=3D"https://datatracker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/" targ=
et=3D"_blank"></a><a href=3D"https://datatracker.ietf.org/doc/draft-song-op=
sawg-ipfix-ecn/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-s=
ong-opsawg-ipfix-ecn/</a></p><p style=3D"font-size:14px;font-family:=E5=BE=
=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&quot;">The following I=
PFIX information elements are introduced for L4S ECN monitoring:</p><p styl=
e=3D"font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;=
Microsoft YaHei&quot;">- ECN field capture in protocol layer, including ECN=
 field in IPv4/IPv6 ECN field, MPLS EXP and tunnel ECN negotiation status</=
p><p style=3D"font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=
=91,&quot;Microsoft YaHei&quot;">- ECN codepoint statistics, including incr=
emenatl and total count for non-ECT, ECT(0), ECT(1) and CE packets</p><p st=
yle=3D"font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quo=
t;Microsoft YaHei&quot;">- L4S performance indicator, providing short-term =
and long-term view of congestion experienced by L4S traffic</p><p style=3D"=
font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Micro=
soft YaHei&quot;"><br></p><p style=3D"font-size:14px;font-family:=E5=BE=AE=
=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&quot;">Your review, comme=
nts and questions are welcome.</p><p style=3D"font-size:14px;font-family:=
=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&quot;"><br></p><=
p style=3D"font-size:14px;font-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,=
&quot;Microsoft YaHei&quot;">Best regards,</p><p style=3D"font-size:14px;fo=
nt-family:=E5=BE=AE=E8=BD=AF=E9=9B=85=E9=BB=91,&quot;Microsoft YaHei&quot;"=
>Xueyan</p><p style=3D"display:none"><label></label><span></span></p><p sty=
le=3D"margin:0px;line-height:20px"><br></p><div style=3D"display:block"><di=
v style=3D"width:100%;height:28px;line-height:28px;background-color:rgb(224=
,229,233);color:rgb(19,136,255);text-align:center">Original</div><div id=3D=
"m_-3763961488533818572zwriteHistoryContainer"><div><div style=3D"padding:8=
px;background-color:rgb(245,246,248)"><div><strong>From:=C2=A0</strong><spa=
n><a href=3D"mailto:[email protected]" target=3D"_blank">internet-dr=
[email protected]</a> &lt;<a href=3D"mailto:[email protected]" target=3D=
"_blank">[email protected]</a>&gt;</span></div><div><strong>To:=C2=
=A0</strong><span style=3D"display:inline">=E5=AE=8B=E9=9B=AA=E9=9B=8100038=
118;</span><span style=3D"display:inline">=E5=88=98=E5=B0=A700165286;</span=
></div><div><strong>Date:=C2=A0</strong><span>2025=E5=B9=B412=E6=9C=8826=E6=
=97=A5 16:33</span></div><div><strong>Subject:=C2=A0</strong><span><strong>=
New Version Notification for draft-song-opsawg-ipfix-ecn-00.txt</strong></s=
pan></div></div><div>A=C2=A0new=C2=A0version=C2=A0of=C2=A0Internet-Draft=C2=
=A0draft-song-opsawg-ipfix-ecn-00.txt=C2=A0has=C2=A0been<br>successfully=C2=
=A0submitted=C2=A0by=C2=A0Xueyan=C2=A0Song=C2=A0and=C2=A0posted=C2=A0to=C2=
=A0the<br>IETF=C2=A0repository.<br> <br>Name:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
draft-song-opsawg-ipfix-ecn<br>Revision:=C2=A000<br>Title:=C2=A0=C2=A0=C2=
=A0=C2=A0Export=C2=A0of=C2=A0L4S=C2=A0ECN=C2=A0in=C2=A0IP=C2=A0Flow=C2=A0In=
formation=C2=A0Export=C2=A0(IPFIX)<br>Date:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A020=
25-12-26<br>Group:=C2=A0=C2=A0=C2=A0=C2=A0Individual=C2=A0Submission<br>Pag=
es:=C2=A0=C2=A0=C2=A0=C2=A014<br>URL:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0<a=
 href=3D"https://www.ietf.org/archive/id/draft-song-opsawg-ipfix-ecn-00.txt=
" target=3D"_blank">https://www.ietf.org/archive/id/draft-song-opsawg-ipfix=
-ecn-00.txt</a><br>Status:=C2=A0=C2=A0=C2=A0<a href=3D"https://datatracker.=
ietf.org/doc/draft-song-opsawg-ipfix-ecn/" target=3D"_blank">https://datatr=
acker.ietf.org/doc/draft-song-opsawg-ipfix-ecn/</a><br>HTML:=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0<a href=3D"https://www.ietf.org/archive/id/draft-song-opsawg=
-ipfix-ecn-00.html" target=3D"_blank">https://www.ietf.org/archive/id/draft=
-song-opsawg-ipfix-ecn-00.html</a><br>HTMLized:=C2=A0<a href=3D"https://dat=
atracker.ietf.org/doc/html/draft-song-opsawg-ipfix-ecn" target=3D"_blank">h=
ttps://datatracker.ietf.org/doc/html/draft-song-opsawg-ipfix-ecn</a><br> <b=
r> <br>Abstract:<br> <br>=C2=A0=C2=A0=C2=A0This=C2=A0document=C2=A0defines=
=C2=A0a=C2=A0set=C2=A0of=C2=A0IP=C2=A0Flow=C2=A0Information=C2=A0Export=C2=
=A0(IPFIX)<br>=C2=A0=C2=A0=C2=A0Information=C2=A0Elements=C2=A0for=C2=A0mon=
itoring=C2=A0the=C2=A0Low=C2=A0Latency,=C2=A0Low=C2=A0Loss,=C2=A0and<br>=C2=
=A0=C2=A0=C2=A0Scalable=C2=A0throughput=C2=A0(L4S)=C2=A0service.=C2=A0=C2=
=A0Specially,=C2=A0these=C2=A0elements=C2=A0enable<br>=C2=A0=C2=A0=C2=A0net=
work=C2=A0operators=C2=A0to=C2=A0monitor=C2=A0the=C2=A0Explicit=C2=A0Conges=
tion=C2=A0Notification<br>=C2=A0=C2=A0=C2=A0(ECN)=C2=A0information=C2=A0of=
=C2=A0L4S=C2=A0deployment=C2=A0and=C2=A0performance=C2=A0of=C2=A0traffic.<b=
r> <br> <br> <br>The=C2=A0IETF=C2=A0Secretariat<br> <br></div></div></div><=
/div><p><br></p></div>_______________________________________________<br>
OPSAWG mailing list -- <a href=3D"mailto:[email protected]" target=3D"_blank"=
>[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]" ta=
rget=3D"_blank">[email protected]</a><br>
</blockquote></div>

--000000000000d9a18306480fc396--


--===============2808008424199414060==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KT1BTQVdHIG1h
aWxpbmcgbGlzdCAtLSBvcHNhd2dAaWV0Zi5vcmcKVG8gdW5zdWJzY3JpYmUgc2VuZCBhbiBlbWFp
bCB0byBvcHNhd2ctbGVhdmVAaWV0Zi5vcmcK

--===============2808008424199414060==--