> Hi, Susan, > > > On Apr 16, 2020, at 3:35 AM, Susan Hares via Datatracker > <noreply@xxxxxxxx> wrote: > > > > Reviewer: Susan Hares > > ... > > Personal plea: > > You've clear stated the BGP issue up front. > > TCP MD5 is bad (due to privacy issues) and TCP-AO > > is not deployed.. > > It is available in Cisco IOS at least. Its biggest drawback appears to be a lack of > open-source implementations. According to reference [1], Nokia SROS implements TCP-AO as well. As far as I can see, RFC 5925 and RFC 5926 are explicitly listed as supported in [1]. So, apparently two major router vendors have running code for TCP-AO. But this seems really off-topic for draft-ietf-taps-transport-security. Michael [1] Nokia SROS documentation at https://documentation.nokia.com/cgi-bin/dbaccessfilename.cgi/3HE15811AAAATQZZA01_V1_7450%20ESS%207750%20SR%207950%20XRS%20and%20VSR%20Basic%20System%20Configuration%20Guide%2020.2.R1.pdf > > Has the TAPs given any thought to > > what might be a replacement that could utilize some of the modern > > TCP. > > Given the problem with TCP-AO deployment is that there is no free > implementation and low implementation by vendors, how exactly would a new > solution with even less implemented code help? > > Joe > _______________________________________________ > Taps mailing list > Taps@xxxxxxxx > https://www.ietf.org/mailman/listinfo/taps -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
