On Mon, Oct 04, 2021 at 11:48:12PM +0330, Ehsan Ghazizadeh wrote:
> Its an old doc worth reading.
You are offering the working group information from 2009. The same year
"Call of Duty: Modern Warfare 2" was released.
Since then, a number of IETF-consensus documents have been published.
For example the BGPsec specification itself. Here is a timeline:
Feb 2014, RFC 7132 - Threat Model for BGP Path Security
Aug 2014, RFC 7353 - Security Requirements for BGP Path Validation
Sep 2017, RFC 8205 - BGPsec Protocol Specification
Sep 2017, RFC 8206 - BGPsec Considerations for Autonomous System (AS)
Migration
Sep 2017, RFC 8207 - BGPsec Operational Considerations
Sep 2017, RFC 8208 - BGPsec Algorithms, Key Formats, and Signature Formats
Sep 2017, RFC 8209 - A Profile for BGPsec Router Certificates, Certificate
Revocation Lists, and Certification Requests
Apr 2018, RFC 8374 - BGPsec Design Choices and Summary of Supporting
Discussions
Jun 2019, RFC 8608 - BGPsec Algorithms, Key Formats, and Signature Formats
Aug 2019, RFC 8634 - BGPsec Router Certificate Rollover
Aug 2019, RFC 8635 - Router Keying for BGPsec
If at this point there still are undocumented gotcha's, they aren't
gonna be found in a vacuum. Lowering barriers (by for example making it
easier to manage BGPsec in the RPKI dashboard) will increase the number
of people able to take a look at BGPsec, and subsequently improve the
technology.
Kind regards,
Job
