Thanks Gyan
On Sun, Jul 3, 2022 at 4:44 PM Brian E Carpenter < brian.e.carpen...@gmail.com> wrote: > Gyan, > > https://mailarchive.ietf.org/arch/msg/int-area/gNA1peWM46q1upmSybUkcd9MUtY > > There was also this report sometime last year (look for slide 8): > > https://netdevconf.info/0x15/session.html?BIG-TCP > > Regards > Brian Carpenter > > On 04-Jul-22 00:42, Gyan Mishra wrote: > > > > Thanks Brian for 6MAN clarification on RFC 2365 that it has been > implemented for very specialized environments. > > > > I agree it does no harm to anyone who doesn’t use it. > > > > What is the application where it was implemented if you have a link > would be greatly appreciated. > > > > Thanks > > > > Gyan > > > > On Sun, Jul 3, 2022 at 1:08 AM Brian E Carpenter < > brian.e.carpen...@gmail.com <mailto:brian.e.carpen...@gmail.com>> wrote: > > > > Hi Gyan, > > > > On 03-Jul-22 16:25, Gyan Mishra wrote: > > ... > > > So bottom line is RFC 2675 would never come to fruition and > should really be deprecated or made obsolete. > > > > Why? Firstly, it has come to fruition, as an earlier message in this > thread said. Secondly, it was intentionally designed for very special > environments with unusual hardware, rather than for any commodity > environment. Thirdly, it does no harm whatever to anyone that doesn't use > it, so there is no reason whatever to deprecate it. > > > > > I believe this was discussed on 6MAN. > > > > I believe the conclusion was to leave it as is. > > > > Brian > > > > -- > > > > <http://www.verizon.com/> > > > > *Gyan Mishra* > > > > /Network Solutions A//rchitect / > > > > /Email gyan.s.mis...@verizon.com <mailto:gyan.s.mis...@verizon.com>// > > / > > > > /M 301 502-1347 > > > > / > > > > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *Email gyan.s.mis...@verizon.com <gyan.s.mis...@verizon.com>* *M 301 502-1347*
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
