| 2119 | Key words for use in RFCs to Indicate Requirement LevelsS. Bradner | Best Current Practice | March 1997 |
| 4271 | A Border Gateway Protocol 4 (BGP-4)Y. Rekhter, Ed., T. Li, Ed., S. Hares, Ed. | Draft Standard | January 2006 |
| 4724 | Graceful Restart Mechanism for BGPS. Sangli, E. Chen, R. Fernando, J. Scudder, Y. Rekhter | Proposed Standard | January 2007 |
| 4760 | Multiprotocol Extensions for BGP-4T. Bates, R. Chandra, D. Katz, Y. Rekhter | Draft Standard | January 2007 |
| 5065 | Autonomous System Confederations for BGPP. Traina, D. McPherson, J. Scudder | Draft Standard | August 2007 |
| 5492 | Capabilities Advertisement with BGP-4J. Scudder, R. Chandra | Draft Standard | February 2009 |
| 6472 | Recommendation for Not Using AS_SET and AS_CONFED_SET in BGPW. Kumari, K. Sriram · obsoleted by RFC 9774 | Best Current Practice | December 2011 |
| 6480 | An Infrastructure to Support Secure Internet RoutingM. Lepinski, S. Kent | Informational | February 2012 |
| 6482 | A Profile for Route Origin Authorizations (ROAs)M. Lepinski, S. Kent, D. Kong · obsoleted by RFC 9582 | Proposed Standard | February 2012 |
| 6483 | Validation of Route Origination Using the Resource Certificate Public Key Infrastructure (PKI) and Route Origin Authorizations (ROAs)G. Huston, G. Michaelson | Informational | February 2012 |
| 6487 | A Profile for X.509 PKIX Resource CertificatesG. Huston, G. Michaelson, R. Loomans | Proposed Standard | February 2012 |
| 6793 | BGP Support for Four-Octet Autonomous System (AS) Number SpaceQ. Vohra, E. Chen | Proposed Standard | December 2012 |
| 6810 | The Resource Public Key Infrastructure (RPKI) to Router ProtocolR. Bush, R. Austein | Proposed Standard | January 2013 |
| 6811 | BGP Prefix Origin ValidationP. Mohapatra, J. Scudder, D. Ward, R. Bush, R. Austein | Proposed Standard | January 2013 |
| 7093 | Additional Methods for Generating Key Identifiers ValuesS. Turner, S. Kent, J. Manger | Informational | December 2013 |
| 7115 | Origin Validation Operation Based on the Resource Public Key Infrastructure (RPKI)R. Bush | Best Current Practice | January 2014 |
| 7132 | Threat Model for BGP Path SecurityS. Kent, A. Chi | Informational | February 2014 |
| 7606 | Revised Error Handling for BGP UPDATE MessagesE. Chen, Ed., J. Scudder, Ed., P. Mohapatra, K. Patel | Proposed Standard | August 2015 |
| 7841 | RFC Streams, Headers, and BoilerplatesJ. Halpern, Ed., L. Daigle, Ed., O. Kolkman, Ed. | Informational | May 2016 |
| 8126 | Guidelines for Writing an IANA Considerations Section in RFCsM. Cotton, B. Leiba, T. Narten | Best Current Practice | June 2017 |
| 8174 | Ambiguity of Uppercase vs Lowercase in RFC 2119 Key WordsB. Leiba | Best Current Practice | May 2017 |
| 8181 | A Publication Protocol for the Resource Public Key Infrastructure (RPKI)S. Weiler, A. Sonalker, R. Austein | Proposed Standard | July 2017 |
| 8182 | The RPKI Repository Delta Protocol (RRDP)T. Bruijnzeels, O. Muravskiy, B. Weber, R. Austein | Proposed Standard | July 2017 |
| 8206 | BGPsec Considerations for Autonomous System (AS) MigrationW. George, S. Murphy | Proposed Standard | September 2017 |
| 8207 | BGPsec Operational ConsiderationsR. Bush | Best Current Practice | September 2017 |
| 8208 | BGPsec Algorithms, Key Formats, and Signature FormatsS. Turner, O. Borchert · obsoleted by RFC 8608 | Proposed Standard | September 2017 |
| 8209 | A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification RequestsM. Reynolds, S. Turner, S. Kent | Proposed Standard | September 2017 |
| 8210 | The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1R. Bush, R. Austein | Proposed Standard | September 2017 |