Skip to main content

A Profile for BGPSEC Router Certificates, Certificate Revocation Lists, and Certification Requests
draft-turner-sidr-bgpsec-pki-profiles-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Mark Reynolds , Sean Turner
Last updated 2012-03-08 (Latest revision 2011-08-02)
Replaced by draft-ietf-sidr-bgpsec-pki-profiles
RFC stream (None)
Intended RFC status (None)
Formats
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-sidr-bgpsec-pki-profiles
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

This document defines a standard profile for X.509 certificates for the purposes of supporting validation of Autonomous System (AS) paths in the Border Gateway Protocol (BGP), as part of an extension to that protocol known as BGPSEC. BGP is a critical component for the proper operation of the Internet as a whole. The BGPSEC protocol is under development as a component to address the requirement to provide security for the BGP protocol. The goal of BGPSEC is to design a protocol for full AS path validation based on the use of strong cryptographic primitives. The end-entity (EE) certificates specified by this profile are issued under Resource Public Key Infrastructure (RPKI) Certification Authority (CA) certificates, containing the AS number extension, to routers within the Autonomous System (AS). The certificate asserts that the router(s) holding the private key are authorized to send out secure route advertisements on behalf of the specified AS. This document also profiles the Certificate Revocation List (CRL), profiles the format of certification requests, and specifies Relying Party certificate path validation procedures. The document extends the RPKI; therefore, this documents updates the RPKI Resource Certificates Profile (draft-ietf-sidr-res-cert-profile).

Authors

Mark Reynolds
Sean Turner

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)