MIME-Version: 1.0
References: 
 <178524015053.1230393.14124574133204422376@dt-datatracker-d4d6ff9d9-fsx7d>
In-Reply-To: 
 <178524015053.1230393.14124574133204422376@dt-datatracker-d4d6ff9d9-fsx7d>
From: CARLOS JESUS BERNARDOS CANO <cjbc@it.uc3m.es>
Date: Thu, 27 Aug 2026 09:57:41 +0200
Message-ID: 
 <CALypLp_BJvojUrZ9p6y8s2E2TjPCJCKUHE3ix2awpsD-OdoQnQ@mail.gmail.com>
To: =?UTF-8?Q?Carlos_Jes=C3=BAs_Bernardos?= <cjbc@it.uc3m.es>
Content-Type: multipart/alternative; boundary="000000000000c2158e065a02b11c"
Message-ID-Hash: MM4PVZVD5LK2SCSXE3B7EK7HQIS7XLIM
CC: fann@ietf.org, fann-chairs@ietf.org,
 draft-dong-fann-problem-statement@ietf.org
Precedence: list
Subject: =?utf-8?q?=5BFann=5D_Re=3A_Call_for_adoption=3A_draft-dong-fann-problem-stat?=
	=?utf-8?q?ement-00_=28Ends_2026-08-18=29?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/fann/TwmYBLGs9c6Ufrltt1kRK6l8NDo>

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

Hi all,

This concludes the call for adoption of:

  draft-dong-fann-problem-statement-00
  Fast Network Notifications Problem Statement

The document is adopted as a FANN WG document.

Authors, please submit the same version as
draft-ietf-fann-problem-statement-00.

The feedback received from the WG during the adoption call should be
addressed in subsequent iterations of the document (-01 onwards).

Thanks,

Carlos and Eddie
FANN WG Co-chairs

On Tue, Jul 28, 2026 at 2:02=E2=80=AFPM Carlos Jes=C3=BAs Bernardos via Dat=
atracker <
noreply@ietf.org> wrote:

> This message starts a fann WG Call for Adoption of:
> draft-dong-fann-problem-statement-00
>
> This Working Group Call for Adoption ends on 2026-08-18
>
> Abstract:
>    Many network applications, ranging from Artificial Intelligence (AI)
>    /Machine Learning (ML) training/inference to cloud services, require
>    networks with various combination of high bandwidth, low delay and
>    low jitter and minimal packet loss in data transfer.  This requires
>    that the networks must rapidly adapt to the presence of faults,
>    degradation and congestion.  However, existing routing and traffic
>    management mechanisms often face limitations in responsiveness,
>    coverage, and operational complexity, particularly in large-scale and
>    high-bandwidth network environments (e.g. data center (DC) and data
>    center interconnect (DCI)).  A good and timely understanding of
>    network conditions can help to enable faster response to critical
>    events, so as to enable the selection of paths with reduced latency
>    and improve network utilization.  This document describes the gap
>    analysis and the need for fast network notification, and identifies
>    the set of problems which a fast network notification solution needs
>    to address.
>
> Please reply to this message and indicate whether or not you support
> adoption
> of this Internet-Draft by the fann WG. Comments to explain your preferenc=
e
> are greatly appreciated. Please reply to all recipients of this message a=
nd
> include this message in your response.
>
> Authors, and WG participants in general, are reminded of the Intellectual
> Property Rights (IPR) disclosure obligations described in BCP 79 [2].
> Appropriate IPR disclosures required for full conformance with the
> provisions
> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
> Sanctions available for application to violators of IETF IPR Policy can b=
e
> found at [3].
>
> Thank you.
> [1] https://datatracker.ietf.org/doc/bcp78/
> [2] https://datatracker.ietf.org/doc/bcp79/
> [3] https://datatracker.ietf.org/doc/rfc6701/
>
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-dong-fann-problem-statement/
>
> There is also an HTMLized version available at:
> https://datatracker.ietf.org/doc/html/draft-dong-fann-problem-statement-0=
0
>

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

<div dir=3D"ltr">Hi all,<br><br>This concludes the call for adoption of:<br=
><br>=C2=A0 draft-dong-fann-problem-statement-00<br>=C2=A0 Fast Network Not=
ifications Problem Statement<br><br>The document is adopted as a FANN WG do=
cument.<br><br>Authors, please submit the same version as draft-ietf-fann-p=
roblem-statement-00.<br><br>The feedback received from the WG during the ad=
option call should be<br>addressed in subsequent iterations of the document=
 (-01 onwards).<br><br>Thanks,<br><br><div>Carlos and Eddie<br>FANN WG Co-c=
hairs<br></div></div><br><div class=3D"gmail_quote gmail_quote_container"><=
div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 28, 2026 at 2:02=E2=80=AFP=
M Carlos Jes=C3=BAs Bernardos via Datatracker &lt;<a href=3D"mailto:noreply=
@ietf.org">noreply@ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">This message starts a fann WG Call for Adoption =
of:<br>
draft-dong-fann-problem-statement-00<br>
<br>
This Working Group Call for Adoption ends on 2026-08-18<br>
<br>
Abstract:<br>
=C2=A0 =C2=A0Many network applications, ranging from Artificial Intelligenc=
e (AI)<br>
=C2=A0 =C2=A0/Machine Learning (ML) training/inference to cloud services, r=
equire<br>
=C2=A0 =C2=A0networks with various combination of high bandwidth, low delay=
 and<br>
=C2=A0 =C2=A0low jitter and minimal packet loss in data transfer.=C2=A0 Thi=
s requires<br>
=C2=A0 =C2=A0that the networks must rapidly adapt to the presence of faults=
,<br>
=C2=A0 =C2=A0degradation and congestion.=C2=A0 However, existing routing an=
d traffic<br>
=C2=A0 =C2=A0management mechanisms often face limitations in responsiveness=
,<br>
=C2=A0 =C2=A0coverage, and operational complexity, particularly in large-sc=
ale and<br>
=C2=A0 =C2=A0high-bandwidth network environments (e.g. data center (DC) and=
 data<br>
=C2=A0 =C2=A0center interconnect (DCI)).=C2=A0 A good and timely understand=
ing of<br>
=C2=A0 =C2=A0network conditions can help to enable faster response to criti=
cal<br>
=C2=A0 =C2=A0events, so as to enable the selection of paths with reduced la=
tency<br>
=C2=A0 =C2=A0and improve network utilization.=C2=A0 This document describes=
 the gap<br>
=C2=A0 =C2=A0analysis and the need for fast network notification, and ident=
ifies<br>
=C2=A0 =C2=A0the set of problems which a fast network notification solution=
 needs<br>
=C2=A0 =C2=A0to address.<br>
<br>
Please reply to this message and indicate whether or not you support adopti=
on<br>
of this Internet-Draft by the fann WG. Comments to explain your preference<=
br>
are greatly appreciated. Please reply to all recipients of this message and=
<br>
include this message in your response.<br>
<br>
Authors, and WG participants in general, are reminded of the Intellectual<b=
r>
Property Rights (IPR) disclosure obligations described in BCP 79 [2].<br>
Appropriate IPR disclosures required for full conformance with the provisio=
ns<br>
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.<br>
Sanctions available for application to violators of IETF IPR Policy can be<=
br>
found at [3].<br>
<br>
Thank you.<br>
[1] <a href=3D"https://datatracker.ietf.org/doc/bcp78/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp78/</a><br>
[2] <a href=3D"https://datatracker.ietf.org/doc/bcp79/" rel=3D"noreferrer" =
target=3D"_blank">https://datatracker.ietf.org/doc/bcp79/</a><br>
[3] <a href=3D"https://datatracker.ietf.org/doc/rfc6701/" rel=3D"noreferrer=
" target=3D"_blank">https://datatracker.ietf.org/doc/rfc6701/</a><br>
<br>
The IETF datatracker status page for this Internet-Draft is:<br>
<a href=3D"https://datatracker.ietf.org/doc/draft-dong-fann-problem-stateme=
nt/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.org/doc/=
draft-dong-fann-problem-statement/</a><br>
<br>
There is also an HTMLized version available at:<br>
<a href=3D"https://datatracker.ietf.org/doc/html/draft-dong-fann-problem-st=
atement-00" rel=3D"noreferrer" target=3D"_blank">https://datatracker.ietf.o=
rg/doc/html/draft-dong-fann-problem-statement-00</a><br>
</blockquote></div>

--000000000000c2158e065a02b11c--