Why does anyone even use an Auto responder in 2025? On Mon, Nov 10, 2025, 9:06 AM Samaneh Tajalizadehkhoob via NANOG < [email protected]> wrote:
> I am not checking my emails until Nov 14th, 2025. Thanks, Samaneh > > On Nov 7, 2025, at 7:37 AM, Vasilenko Eduard via NANOG < > [email protected]> wrote: > > I suppose that the number of people who understand it well enough is below > 2k worldwide. IPv6 1st hop is very complex. > Ed/ > -----Original Message----- > From: Nick Hilliard via NANOG <[email protected]> > Sent: Thursday, November 6, 2025 17:58 > To: North American Network Operators Group <[email protected]> > Cc: Nick Hilliard <[email protected]> > Subject: Re: Artificial Juniper SRX limitations preventing IPv6 deployment > (and sales) > > Vasilenko Eduard via NANOG wrote on 06/11/2025 12:13: > Nope. It is an extremally complex bunch of protocols on the1st hope > (between the computer and the router). > > it's pretty simple really. Neighbor discovery is defined in RFC4861. > > There's also formal updates in RFCs 8319, 8425, 9131, 5942, 6980, 7048, > 7527, 7559, 8028, 9685, and 9762. Various other notes areincluded in 7217, > 8978, 8981, and 4941. > > After that rfc8415 defines DHCPv6, with extensions and various updates in > 8156, 8168, 8639, 8948, 8987, 9527, 9663, 9686 and 9818. > > Obviously everyone needs yang so dhcpv6/yang is in 9243. > > Then there's secure neighbour discovery. And ND proxy and LPWAN. Lots of > RFCs there. 4943, 5269, 5909, 6273, 6494, 6495, 6496, 6583, 6775, 6980, > 7219, 7342, 8161, 8302, 8425, 8505, 8928, and 9131 for starters. > > And plenty of other references inside other RFCs. > > Oh yeah, and 15 errata for rfc4861 (there was another one confirmed > earlier today and placed in HDU status): > > > https://urldefense.com/v3/__https://www.rfc-editor.org/errata_search.php?rfc=4861__;!!PtGJab4!5bms0W562aKe7iiJJgStzP7pAb16LDBfq9yXvAQXIHMY1oMthRRzsNO2GpKkFUtx9RYWC0BOvq5J91_RQvpvG5ctWfc$ > [rfc-editor[.]org] > > Hopefully this clearly shows to the OP that IPv6 neighbor discovery isn't > remotely complicated. > > Nick > _______________________________________________ > NANOG mailing list > > https://urldefense.com/v3/__https://lists.nanog.org/archives/list/[email protected]/message/NEEBC5FV3GQ2KAUMRWE4KVSVSOGEA6KP/__;!!PtGJab4!5bms0W562aKe7iiJJgStzP7pAb16LDBfq9yXvAQXIHMY1oMthRRzsNO2GpKkFUtx9RYWC0BOvq5J91_RQvpvC2E818U$ > [lists[.]nanog[.]org] > _______________________________________________ > NANOG mailing list > > https://urldefense.com/v3/__https://lists.nanog.org/archives/list/[email protected]/message/L2AJT7HN7BJX5W2FKWGODVTEH7DHR2LQ/__;!!PtGJab4!5bms0W562aKe7iiJJgStzP7pAb16LDBfq9yXvAQXIHMY1oMthRRzsNO2GpKkFUtx9RYWC0BOvq5J91_RQvpvbJdMNwA$ > [lists[.]nanog[.]org] > _______________________________________________ > NANOG mailing list > > https://lists.nanog.org/archives/list/[email protected]/message/3SEY6ZZLYGADFVTSY5LTXNIVYJQG7KZK/ _______________________________________________ NANOG mailing list https://lists.nanog.org/archives/list/[email protected]/message/GBQLKBVRKT2FRJSPFB5CS64VOFXKAPLF/
