RFC 7132 on Threat Model for BGP Path Security

rfc-editor@rfc-editor.org Sat, 22 February 2014 00:33 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 5083B1A02FC; Fri, 21 Feb 2014 16:33:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.45
X-Spam-Status: No, score=-2.45 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.548, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Gh6rjG3Ukx42; Fri, 21 Feb 2014 16:33:09 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id B2DA51A02B5; Fri, 21 Feb 2014 16:32:59 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id BAF017FC3B5; Fri, 21 Feb 2014 16:32:55 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7132 on Threat Model for BGP Path Security
From: rfc-editor@rfc-editor.org
Message-Id: <20140222003255.BAF017FC3B5@rfc-editor.org>
Date: Fri, 21 Feb 2014 16:32:55 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/uP3mbY0FpoIDcRI-EaAYU4Jkm4k
Cc: drafts-update-ref@iana.org, sidr@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Feb 2014 00:33:15 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 7132

        Title:      Threat Model for BGP Path 
        Author:     S. Kent, A. Chi
        Status:     Informational
        Stream:     IETF
        Date:       February 2014
        Mailbox:    kent@bbn.com, 
        Pages:      20
        Characters: 52539
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-sidr-bgpsec-threats-09.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7132.txt

This document describes a threat model for the context in which
External Border Gateway Protocol (EBGP) path security mechanisms will
be developed.  The threat model includes an analysis of the Resource
Public Key Infrastructure (RPKI) and focuses on the ability of an
Autonomous System (AS) to verify the authenticity of the AS path info
received in a BGP update.  We use the term "PATHSEC" to refer to any
BGP path security technology that makes use of the RPKI.  PATHSEC
will secure BGP, consistent with the inter-AS security focus of the

The document characterizes classes of potential adversaries that are
considered to be threats and examines classes of attacks that might
be launched against PATHSEC.  It does not revisit attacks against
unprotected BGP, as that topic has already been addressed in the
BGP-4 standard.  It concludes with a brief discussion of residual

This document is a product of the Secure Inter-Domain Routing Working Group of the IETF.

INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC