I agree with Acee. The topic might be interesting but the Transport Area seems more appropriate for this work. Perhaps something ADs and WG Chairs can decide.
Regards, Greg On Tue, Mar 15, 2022 at 5:54 PM Acee Lindem (acee) <acee= [email protected]> wrote: > What is your point? The fact that your draft is orthogonal to a specific > transport doesn’t mean it isn’t applicable to the transport layer and its > attendant mechanisms. It obviously belongs there and not in routing. > > Thanks, > > Acee > > > > *From: *"Miao, Rui" <[email protected]> > *Reply-To: *"Miao, Rui" <[email protected]> > *Date: *Tuesday, March 15, 2022 at 8:47 PM > *To: *Acee Lindem <[email protected]>, Routing WG <[email protected]> > *Subject: *Re: New Version Notification for > draft-miao-rtgwg-hpccplus-00.txt > > > > Hi Acee, > > > > The way we pointed out that the host is able to fetch precise ``load'' > from the network via inband telemetry for congestion control can be > integrated into different transports. The independence of specific > transports stems from the fact it actually doesn't have to follow the > unnecessary DATA/ACK self-clocking, but instead can use special-generated > request-response packets. > > > > Thanks, > > Rui > > > > ------------------------------------------------------------------ > > From:Acee Lindem (acee) <[email protected]> > > Sent At:2022 Mar. 15 (Tue.) 14:47 > > To:Rui <[email protected]>; rtgwg <[email protected]> > > Subject:Re: New Version Notification for draft-miao-rtgwg-hpccplus-00.txt > > > > Hi Rui, > > > > Ok – I don’t know that the fact the telemetry which is a byproduct of the > congestion control can be used as TE path selection criteria makes this > applicable to the Routing Area. That is a real stretch…. Independent of > specific transports, congestion control is a transport problem. > > > > Thanks, > > Acee > > > > *From: *"Miao, Rui" <[email protected]> > *Reply-To: *"Miao, Rui" <[email protected]> > *Date: *Tuesday, March 15, 2022 at 5:18 PM > *To: *Acee Lindem <[email protected]>, Routing WG <[email protected]> > *Subject: *Re: New Version Notification for > draft-miao-rtgwg-hpccplus-00.txt > > > > Hi Acee, > > > > Thanks for the comment. > > > > HPCC++ proposes an approach to leverage the in-band telemetry for traffic > admission and path selection, which we think is more relevant to routing > decisions. Besides, HPCC++ is orthogonal to any transports and thus we have > several example implementations in the draft. > > > > Thanks, > > Rui > > > > ------------------------------------------------------------------ > > From:Acee Lindem (acee) <[email protected]> > > Sent At:2022 Mar. 15 (Tue.) 12:43 > > To:Rui <[email protected]>; rtgwg <[email protected]> > > Subject:Re: New Version Notification for draft-miao-rtgwg-hpccplus-00.txt > > > > Why is this draft in the Routing WG? This work is more applicable to the > Transport or Internet Area. > > > > Acee > > > > *From: *rtgwg <[email protected]> on behalf of "Miao, Rui" <miao.rui= > [email protected]> > *Reply-To: *"Miao, Rui" <[email protected]> > *Date: *Tuesday, March 15, 2022 at 2:42 PM > *To: *Routing WG <[email protected]> > *Subject: *Fw: New Version Notification for > draft-miao-rtgwg-hpccplus-00.txt > > > > Hello All, > > > > We have posted an updated version of HPCC++ at > https://datatracker.ietf.org/doc/draft-miao-rtgwg-hpccplus/ . > > > > There are two major changes since the last presentation. First, since > HPCC++ is orthogonal to different in-band telemetry formats and transport > protocols, we introduce a few reference implementations over those > protocols for people to quickly pick up. > > Second, we advocate a better routing scheme for path selection and traffic > admission, building on top of HPCC++'s precise link load information. > > > > Please provide any comments you may have on the draft or its extensions. > > > > Thanks, > > Rui > > > > > > > > > > ------------------------------------------------------------------ > > From:internet-drafts <[email protected]> > > Sent At:2022 Mar. 7 (Mon.) 14:35 > > To:Harry <[email protected]>; Barak Gafni <[email protected]>; > Changhoon Kim <[email protected]>; Jeff Tantsura < > [email protected]>; Jeongkeun Lee <[email protected]>; Rong Pan < > [email protected]>; Rui <[email protected]>; Yuval Shpigelman < > [email protected]> > > Subject:New Version Notification for draft-miao-rtgwg-hpccplus-00.txt > > > > > A new version of I-D, draft-miao-rtgwg-hpccplus-00.txt > has been successfully submitted by Rui Miao and posted to the > IETF repository. > > Name: draft-miao-rtgwg-hpccplus > Revision: 00 > Title: HPCC++: Enhanced High Precision Congestion Control > Document date: 2022-03-07 > Group: Individual Submission > Pages: 20 > URL: > https://www.ietf.org/archive/id/draft-miao-rtgwg-hpccplus-00.txt > Status: > https://datatracker.ietf.org/doc/draft-miao-rtgwg-hpccplus/ > Htmlized: > https://datatracker.ietf.org/doc/html/draft-miao-rtgwg-hpccplus > > > Abstract: > Congestion control (CC) is the key to achieving ultra-low latency, > high bandwidth and network stability in high-speed networks. > However, the existing high-speed CC schemes have inherent limitations > for reaching these goals. > > In this document, we describe HPCC++ (High Precision Congestion > Control), a new high-speed CC mechanism which achieves the three > goals simultaneously. HPCC++ leverages inband telemetry to obtain > precise link load information and controls traffic precisely. By > addressing challenges such as delayed signaling during congestion and > overreaction to the congestion signaling using inband and granular > telemetry, HPCC++ can quickly converge to utilize all the available > bandwidth while avoiding congestion, and can maintain near-zero in- > network queues for ultra-low latency. HPCC++ is also fair and easy > to deploy in hardware, implementable with commodity NICs and > switches. > > > > > > The IETF Secretariat > > > > _______________________________________________ > rtgwg mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/rtgwg >
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
