datatracker.ietf.org
Sign in
Version 5.6.4.p1, 2014-10-20
Report a bug

Router Keying for BGPsec
draft-ietf-sidr-rtr-keying-07

Document type: Active Internet-Draft (sidr WG)
Document stream: IETF
Last updated: 2014-05-23
Intended RFC status: Unknown
Other versions: plain text, pdf, html

IETF State: WG Document
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

SIDR Working Group                                             S. Turner
Internet-Draft                                                IECA, Inc.
Intended status: BCP                                            K. Patel
Expires: November 24, 2014                                 Cisco Systems
                                                                 R. Bush
                                         Internet Initiative Japan, Inc.
                                                            May 23, 2014

                        Router Keying for BGPsec
                     draft-ietf-sidr-rtr-keying-07

Abstract

   BGPsec-speaking routers are provisioned with private keys to sign BGP
   messages; the corresponding public keys are published in the global
   RPKI (Resource Public Key Infrastructure) thereby enabling
   verification of BGPsec messages.  This document describes two ways of
   provisioning the public-private key-pairs: router-driven and
   operator-driven.

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 http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on August 27, 2013.

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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
 

Turner, et al.         Expires November 24, 2014                [Page 1]
Internet-Draft          Router Keying for BGPsec            May 23, 2014

   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.

1.  Introduction

   BGPsec-speaking routers are provisioned with private keys, which
   allow them to digitally sign BGP messages.  To verify the signature,
   the public key, in the form of a certificate [I-D.ietf-sidr-bgpsec-
   pki-profiles], is published in the RPKI (Resource Public Key
   Infrastructure).  This document describes two methods for
   provisioning the necessary public-private key-pairs: router-driven
   and operator-driven.

   The difference between the two methods is where the keys are
   generated: on the router in the router-driven method and elsewhere in
   the operator-driven method.  Routers are expected to support either
   one, the other, or both methods to work in various deployment
   environments.  Some routers may not allow the private key to be off-
   loaded while other routers may.  Off-loading of private keys would
   support swapping of routing engines which could then have the same
   private key installed in the soon-to-be online engine that had
   previously been installed in the soon-to-be removed card.

   The remainder of this document describes how operators can use the
   two methods to provision new and existing routers.

   Note: [I-D.ietf-sidr-bgpsec-pki-profiles] specifies the format for
   the PKCS #10 request and [I-D.ietf-sidr-bgpsec-algs] specifies the
   algorithms used to generate the signature.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" are to
   be interpreted as described in RFC 2119 [RFC2119] only when they
   appear in all upper case.  They may also appear in lower or mixed
   case as English words, without normative meaning.

   Readers are assumed to be familiar with the BGPsec protocol [I-
   D.ietf-sidr-bgpsec-overview][I-D.ietf-sidr-bgpsec-protocol] and the
   RPKI [RFC6480] as well as the BGPsec-specific PKI (Public Key
   Infrastructure) specifications [I-D.ietf-sidr-bgpsec-pki-profiles][I-
   D.ietf-sidr-bgpsec-algs].

3.  Provisioning a New Router

 

Turner, et al.         Expires November 24, 2014                [Page 2]

[include full document text]