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

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

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

IETF State: WG Document
Waiting for Referenced Document, Revised I-D Needed - Issue raised by WGLC, Other - see Comment Log
Document shepherd: No shepherd assigned

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

Network Working Group                                   M. Lepinski, Ed.
Internet-Draft                                                       BBN
Intended status: Standards Track                            July 4, 2014
Expires: January 5, 2015                                                

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

Abstract

   This document describes BGPSEC, an extension to the Border Gateway
   Protocol (BGP) that provides security for the path of autonomous
   systems through which a BGP update message passes.  BGPSEC is
   implemented via a new optional non-transitive BGP path attribute that
   carries a digital signature produced by each autonomous system that
   propagates the update message.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" are to be interpreted as described in RFC 2119 [1] 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 January 5, 2015.

Copyright Notice

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

 

Lepinski                 Expires January, 2015                  [Page 1]
Internet-Draft              BGPSEC Protocol                    July 2014

   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.  BGPSEC Negotiation . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  The BGPSEC Capability  . . . . . . . . . . . . . . . . . .  3
     2.2.  Negotiating BGPSEC Support . . . . . . . . . . . . . . . .  4
   3.  The BGPSEC_Path Attribute  . . . . . . . . . . . . . . . . . .  5
     3.1.  Secure_Path  . . . . . . . . . . . . . . . . . . . . . . .  7
     3.2.  Signature_Block  . . . . . . . . . . . . . . . . . . . . .  8
   4.  Generating a BGPSEC Update . . . . . . . . . . . . . . . . . . 10
     4.1.  Originating a New BGPSEC Update  . . . . . . . . . . . . . 11
     4.2.  Propagating a Route Advertisement  . . . . . . . . . . . . 13
     4.3.  Processing Instructions for Confederation Members  . . . . 17
     4.4.  Reconstructing the AS_PATH Attribute . . . . . . . . . . . 19
   5.  Processing a Received BGPSEC Update  . . . . . . . . . . . . . 20
     5.1.  Overview of BGPSEC Validation  . . . . . . . . . . . . . . 22
     5.2.  Validation Algorithm . . . . . . . . . . . . . . . . . . . 23
   6.  Algorithms and Extensibility . . . . . . . . . . . . . . . . . 27
     6.1.  Algorithm Suite Considerations . . . . . . . . . . . . . . 27
     6.2.  Extensibility Considerations . . . . . . . . . . . . . . . 27
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 28
     7.1 Security Guarantees  . . . . . . . . . . . . . . . . . . . . 28
     7.2 On the Removal of BGPSEC Signatures  . . . . . . . . . . . . 29
     7.3 Mitigation of Denial of Service Attacks  . . . . . . . . . . 30
     7.4 Additional Security Considerations . . . . . . . . . . . . . 31
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 31
   9.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 32
     9.1.  Authors  . . . . . . . . . . . . . . . . . . . . . . . . . 32
     9.2.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . 32
   10.  Normative References  . . . . . . . . . . . . . . . . . . . . 33

[include full document text]