We use RFC3971 IPv6 ND message options in our implementation of the AERO/OMNI services. The implementation is not ready for public release yet, but trending in that direction. I would not like to see the RFCs in question designated as historic.
Thank you - Fred > -----Original Message----- > From: Job Snijders <[email protected]> > Sent: Thursday, November 13, 2025 11:41 AM > To: [email protected] > Subject: [EXTERNAL] [Int-area] Designate some RPKI/SEND-related RFCs as > "Historic"? > > EXT email: be mindful of links/attachments. > > > > Dear all, > > Is anyone aware of functional & actively supported implementations of > the following specifications? > > * SEcure Neighbor Discovery (SEND) > https://www.rfc-editor.org/rfc/rfc3971 > > * Certificate Profile and Certificate Management for SEND > https://datatracker.ietf.org/doc/html/rfc6494 > > * Subject Key Identifier (SKI) SEND Name Type Fields > https://datatracker.ietf.org/doc/html/rfc6495 > > I found some references to implementation work of RFC 3971 (for example > Cisco IOS 12, Junos 9, and DoCoMo's SEND Project) - but those nowadays > seem discontinued? > > Context: I'm wondering whether the above listed RFCs should be > designated as "Historic". > > Kind regards, > > Job > > _______________________________________________ > Int-area mailing list -- [email protected] > To unsubscribe send an email to [email protected] _______________________________________________ Int-area mailing list -- [email protected] To unsubscribe send an email to [email protected]
