BGP Algorithms, Key Formats, & Signature Formats

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2014-03-27
Replaces draft-turner-sidr-bgpsec-algs
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream WG state WG Document
Waiting for Referencing Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Secure Inter-Domain Routing Working Group                      S. Turner
Internet-Draft                                                      IECA
Updates: 6485 (if approved)                               March 27, 2014
Intended Status: Standards Track
Expires: September 28, 2014

            BGP Algorithms, Key Formats, & Signature Formats

   This document specifies the algorithms, algorithms' parameters,
   asymmetric key formats, asymmetric key size and signature format used
   in BGPSEC (Border Gateway Protocol Security).  This document updates
   the Profile for Algorithms and Key Sizes for use in the Resource
   Public Key Infrastructure (RFC 6485).

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   ( in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.


Turner                 Expires September 28, 2014               [Page 1]
Internet-Draft    BGPSEC Algs, Key & Signature Formats    March 27, 2014

1.  Introduction

   This document specifies:
      o the digital signature algorithm and parameters;
      o the hash algorithm and parameters;
      o the public and private key formats; and,
      o the signature format
   used by Resource Public Key Infrastructure (RPKI) Certification
   Authorities (CA), and BGPSEC (Border Gateway Protocol Security)
   speakers (i.e., routers).  CAs use these algorithms when issuing
   BGPSEC Router Certificates [ID.sidr-bgpsec-pki-profiles] and CRLs
   [RFC6487].  BGPSEC routers use these when requesting BGPSEC
   certificates [ID.sidr-bgpsec-pki-profiles], generating BGPSEC Update
   messages [ID.sidr-bgpsec-protocol], and verifying BGPSEC Update
   messages [ID.sidr-bgpsec-protocol].

   This document is referenced by the BGPSEC specification [ID.sidr-
   bgpsec-protocol] and the profile for BGPSEC Router Certificates and
   Certification Requests [ID.sidr-bgpsec-pki-profiles].  Familiarity
   with these documents is assumed.  Implementers are reminded, however,
   that, as noted in Section 2 of [ID.sidr-bgpsec-pki-profiles], the
   algorithms used to sign CA Certificates, BGPSEC Router Certificates,
   and CRLs are found in [RFC6485].

   This document updates [RFC6485] to add support for a) a different
   algorithm for BGPSEC certificate requests, which are only issued by
   BGPSEC speakers; b) a different Subject Public Key Info format for
   BGPSEC certificates, which is needed for the specified BGPSEC
   signature algorithm; and, c) a different signature format for BGPSEC
   signatures, which is needed for the specified BGPSEC signature
   algorithm.  The BGPSEC certificate are differentiated from other RPKI
   certificates by the use of the BGPSEC Extended Key Usage defined in

1.1.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "OPTIONAL" in this document are to be interpreted as described in

2.  Algorithms

   Four cryptographic algorithms are used to support BGPSEC:

     o The signature algorithm used when issuing BGPSEC certificates and
       CRLs, which would revoke BGPSEC certificates, MUST be as
       specified in [RFC6485]. 

Turner                 Expires September 28, 2014               [Page 2]
Internet-Draft    BGPSEC Algs, Key & Signature Formats    March 27, 2014

     o The signature algorithm used in certification requests and BGPSEC
       Update messages MUST be Elliptic Curve Digital Signature
       Algorithm (ECDSA) [RFC6090].
Show full document text