Moin, > Apologies, I’ve not been tracking, but I’m confused. > > How is this "document replaces RFC7454 / BCP194?” > > One of the biggest risk on the Internet today is operator’s > ignoring RFC7454 / BCP194. > > https://dashboard.shadowserver.org/statistics/combined/tree/?day=2023 > -06- > 28&source=population&source=population6&tag=bgp&geo=all&data_set=coun > t&scale=log >
RFC7454 / BCP194 is heavily outdated and contains some nuggets that are plain dangerous. The problem we are facing is that explicit technical guidance does not age well. We hence decided to move for a document that is very high level, using two referenced adopted I-D's as the repository for concrete implementation details. The document containing the wealth of operational guidance that, before, was in 7454 is this one: https://datatracker.ietf.org/doc/draft-ietf-grow-routing-ops-sec-inform/ With best regards, Tobias -- Dr.-Ing. Tobias Fiebig T +31 616 80 98 99 M [email protected] Pronouns: he/him/his _______________________________________________ GROW mailing list -- [email protected] To unsubscribe send an email to [email protected]
