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

Document Type Active Internet-Draft (sidr WG)
Last updated 2015-11-01
Replaces draft-ymbk-bgpsec-rtr-rekeying
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                            R. Bush
Internet-Draft                             IIJ Lab / Dragon Research Lab
Intended status: Standards Track                               S. Turner
Expires: May 5, 2016                                          IECA, Inc.
                                                                K. Patel
                                                           Cisco Systems
                                                        November 2, 2015

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

Abstract

   BGPsec-speaking routers are provisioned with private keys in order to
   sign BGPsec announcements.  The corresponding public keys are
   published in the global Resource Public Key Infrastructure, enabling
   verification of BGPsec messages.  This document describes two methods
   of generating the public-private key-pairs: router-driven and
   operator-driven.

Requirements Language

   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.

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 May 5, 2016.

Bush, et al.               Expires May 5, 2016                  [Page 1]
Internet-Draft          Router Keying for BGPsec           November 2015

Copyright Notice

   Copyright (c) 2015 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
   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Management / Router Communication . . . . . . . . . . . . . .   3
   3.  Exchanging Certificates . . . . . . . . . . . . . . . . . . .   4
   4.  Set-Up  . . . . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  PKCS#10 Generation  . . . . . . . . . . . . . . . . . . . . .   4
     5.1.  Router-Generated Keys . . . . . . . . . . . . . . . . . .   4
     5.2.  Operator-Generated Keys . . . . . . . . . . . . . . . . .   5
   6.  Installing Signed Keys  . . . . . . . . . . . . . . . . . . .   5
   7.  Key Management  . . . . . . . . . . . . . . . . . . . . . . .   6
     7.1.  Key Validity  . . . . . . . . . . . . . . . . . . . . . .   7
     7.2.  Key Roll-Over . . . . . . . . . . . . . . . . . . . . . .   7
     7.3.  Key Revocation  . . . . . . . . . . . . . . . . . . . . .   8
     7.4.  Router Replacement  . . . . . . . . . . . . . . . . . . .   8
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     10.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Appendix A.  Management/Router Channel Security . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   BGPsec-speaking routers are provisioned with private keys, which
   allow them to digitally sign BGPsec announcements.  To verify the
   signature, the public key, in the form of a certificate
   [I-D.ietf-sidr-bgpsec-pki-profiles], is published in the Resource
   Public Key Infrastructure (RPKI).  This document describes
Show full document text