I'm also not aware of any IPR. mike
On Tue, Jan 27, 2026 at 11:13 PM [email protected] < [email protected]> wrote: > Sorry for missing the IPR call... > > No, I'm not aware of any IPR that applies to this draft. Thanks. > B.R. > Yongqing Zhu > ------------------------------ > [email protected] > > > *From:* [email protected] > *Date:* 2026-01-23 19:06 > *To:* Yingzhen Qu <[email protected]>; [email protected]; > [email protected]; [email protected]; > [email protected] > *Subject:* [fantel] Re: Call for adoption: > draft-dong-fantel-problem-statement-03 (Ends 2026-01-30) > Hi, > I support the WG adoption of this draft as a co-author. > China Telecom has massively provided AI-related services, such as > coordinated training, AI infrastructure leasing, and P/D splitting > inference, on the IP backbone networks and MANs (Metropolitan Area > Network), all of which require stringent SLAs (e.g., ultra-low latency and > packet loss). We have deployed some existing technologies, including BFD, > In-situ OAM, SRv6 Policy, and FRR, to try to fulfill these requirements, > but didn't work well. Per our research, the lack of lightweight and > real-time notification mechanisms to the target recipients (e.g., source > node, upstream nodes) is the major cause of this. > After many rounds of online and offline discussions, I think this draft > has clearly clarified the problem space of "fast notification" and is ready > for adoption. > B.R. > Yongqing Zhu > ------------------------------ > [email protected] > > > *From:* Yingzhen Qu via Datatracker <[email protected]> > *Date:* 2026-01-16 03:12 > *To:* [email protected]; [email protected]; > [email protected]; [email protected] > *Subject:* [fantel] Call for adoption: > draft-dong-fantel-problem-statement-03 (Ends 2026-01-30) > This message starts a rtgwg WG Call for Adoption of: > draft-dong-fantel-problem-statement-03 > > This Working Group Call for Adoption ends on 2026-01-30 > > Abstract: > Modern networks require adaptive traffic manipulation including > Traffic Engineering (TE), load balancing, flow control, and > protection, to support high-throughput, low-latency, and lossless > applications such as Artificial Intelligence (AI) /Machine Learning > (ML) training and real-time services. A good and timely > understanding of network operational status, such as congestion and > failures, can help to improve network utilization, enable the > selection of paths with reduced latency, and enable faster response > to critical events. This document describes the existing problems > and why a new set of fast network notification solutions are needed. > > Please reply to this message and indicate whether or not you support > adoption > of this Internet-Draft by the rtgwg WG. Comments to explain your preference > are greatly appreciated. Please reply to all recipients of this message and > 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 be > 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-fantel-problem-statement/ > > There is also an HTMLized version available at: > > https://datatracker.ietf.org/doc/html/draft-dong-fantel-problem-statement-03 > > A diff from the previous version is available at: > > https://author-tools.ietf.org/iddiff?url2=draft-dong-fantel-problem-statement-03 > > _______________________________________________ > fantel 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]
