Thank you. While I still have concerns about how we will address these
problems, you have addressed my concerns and I do not object to working
group adoption.
Yours,
Joel
On 2/2/2026 11:17 AM, Dongjie (Jimmy) wrote:
Hi Joel,
Happy to do that.
Your comment about the ambiguity of "lossless" was addressed by the update of version -04, in
which "lossless” was removed and "low latency" was used instead in describing the service
requirements.
Your comment about "issues such as very-low-loss delivery should be described as
potential results, not as goals of the work" is addressed by the new text in the
second last paragraph of the introduction.
Your comment about “at the very least I would expect identification of problem
spaces with different characteristics, and possibly explicit statements that
they should be addressed with different techniques.” is addressed by the new
text in the last paragraph of the introduction.
Please let us know if they addressed your comments.
Best regards,
Jie
-----Original Message-----
From: Joel Halpern <[email protected]>
Sent: Monday, February 2, 2026 11:20 PM
To: Dongjie (Jimmy) <[email protected]>; [email protected]
Cc: [email protected]; [email protected]
Subject: Re: [rtgwg] FW: New Version Notification for
draft-dong-fantel-problem-statement-05.txt
Can you please summarize for the list the changes you made to address my
comments. I apparently missed the early proposal of resolutions.
Thank you,
Joel
On 2/2/2026 10:11 AM, Dongjie (Jimmy) wrote:
Dear WG,
Version -05 of fantel problem statement is uploaded to address the
comments received from Joel and Zafar, it also reflects the recent discussion
among the coauthors.
Thanks again for all the comments and discussion. Further review and
feedback are welcome.
Best regards,
Jie (on behalf of coauthors)
-----Original Message-----
From: [email protected] <[email protected]>
Sent: Monday, February 2, 2026 11:04 PM
To: Francois Clad (editor) <[email protected]>; Dongjie (Jimmy)
<[email protected]>; Luis M. Contreras
<[email protected]>; Mike McBride (editor)
<[email protected]>; DURMUS Mehmet
<[email protected]>;
Francois Clad <[email protected]>; Hao Lu <[email protected]>;
Jeffrey Zhang <[email protected]>; Dongjie (Jimmy)
<[email protected]>; Luis Contreras
<[email protected]>; Mehmet Durmus
<[email protected]>; Mike McBride
<[email protected]>;
Ran Pang <[email protected]>; Reshad Rahman
<[email protected]>;
Rui Zhuang <[email protected]>; Xiaohu Xu
<[email protected]>; Yadong Liu <[email protected]>;
Yongqing Zhu <[email protected]>; Zhaohui Zhang
<[email protected]>
Subject: New Version Notification for
draft-dong-fantel-problem-statement-05.txt
A new version of Internet-Draft
draft-dong-fantel-problem-statement-05.txt
has been successfully submitted by Jie Dong (editor) and posted to
the IETF repository.
Name: draft-dong-fantel-problem-statement
Revision: 05
Title: Fast Network Notifications Problem Statement
Date: 2026-02-02
Group: rtgwg
Pages: 15
URL:
https://www.ietf.org/archive/id/draft-dong-fantel-problem-statement-0
5.txt
Status:
https://datatracker.ietf.org/doc/draft-dong-fantel-problem-statement/
HTMLized:
https://datatracker.ietf.org/doc/html/draft-dong-fantel-problem-state
ment
Diff:
https://author-tools.ietf.org/iddiff?url2=draft-dong-fantel-problem-s
tatement-
05
Abstract:
Modern network applications, ranging from Artificial Intelligence
(AI) /Machine Learning (ML) training to large-scale cloud services,
require adaptive networks to ensure reliable and congestion-free data
transfer within or across multiple data centers. A good and timely
understanding of network operational status 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 existing problems and the need of fast network
notification solutions.
The IETF Secretariat
_______________________________________________
rtgwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]
_______________________________________________
rtgwg mailing list -- [email protected]
To unsubscribe send an email to [email protected]
