BGPSEC Protocol Specification
draft-ietf-sidr-bgpsec-protocol-02

The information below is for an old version of the document
Document Type Active Internet-Draft (sidr WG)
Last updated 2012-03-12
Replaces draft-lepinski-bgpsec-protocol
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                   M. Lepinski, Ed.
Internet-Draft                                                       BBN
Intended status: Standards Track                          March 12, 2012
Expires: September 13, 2012

                     BGPSEC Protocol Specification
                   draft-ietf-sidr-bgpsec-protocol-02

Abstract

   This document describes BGPSEC, an extension to the Border Gateway
   Protocol (BGP) that provides security for the AS-PATH attribute in
   BGP update messages.  BGPSEC is implemented via a new optional non-
   transitive BGP path attribute that carries a digital signature
   produced by each autonomous system on the AS-PATH.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in RFC 2119 [4].

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 September 13, 2012.

Copyright Notice

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

Lepinski               Expires September 13, 2012               [Page 1]
Internet-Draft               BGPSEC Protocol                  March 2012

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  BGPSEC Negotiation . . . . . . . . . . . . . . . . . . . . . .  3
   3.  The BGPSEC_Path_Signatures Attribute . . . . . . . . . . . . .  6
   4.  Generating a BGPSEC Update . . . . . . . . . . . . . . . . . .  9
     4.1.  Originating a New BGPSEC Update  . . . . . . . . . . . . . 10
     4.2.  Propagating a Route Advertisement  . . . . . . . . . . . . 13
   5.  Processing a Received BGPSEC Update  . . . . . . . . . . . . . 16
     5.1.  Validation Algorithm . . . . . . . . . . . . . . . . . . . 17
   6.  Algorithms and Extensibility . . . . . . . . . . . . . . . . . 20
     6.1.  Algorithm Suite Considerations . . . . . . . . . . . . . . 21
     6.2.  Extensibility Considerations . . . . . . . . . . . . . . . 21
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 22
   8.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 25
     8.1.  Authors  . . . . . . . . . . . . . . . . . . . . . . . . . 25
     8.2.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . 26
   9.  Normative References . . . . . . . . . . . . . . . . . . . . . 26
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 27

Lepinski               Expires September 13, 2012               [Page 2]
Internet-Draft               BGPSEC Protocol                  March 2012

1.  Introduction

   This document describes BGPSEC, a mechanism for providing path
   security for Border Gateway Protocol (BGP) [1] route advertisements.
   That is, a BGP speaker who receives a valid BGPSEC update has
   cryptographic assurance that the advertised route has the following
   two properties:

   1.  The route was originated by an AS that has been explicitly
       authorized by the holder of the IP address prefix to originate
       route advertisements for that prefix.

   2.  Every AS listed in the AS_Path attribute of the update explicitly
       authorized the advertisement of the route to the subsequent AS in
       the AS_Path.

   This document specifies a new optional (non-transitive) BGP path
   attribute, BGPSEC_Path_Signatures.  It also describes how a BGPSEC-
   compliant BGP speaker (referred to hereafter as a BGPSEC speaker) can
   generate, propagate, and validate BGP update messages containing this
   attribute to obtain the above assurances.

   BGPSEC relies on the Resource Public Key Infrastructure (RPKI)
   certificates that attest to the allocation of AS number and IP
Show full document text