BGP Prefix Origin Validation
draft-ietf-sidr-pfx-validate-05

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10

Network Working Group                                       P. Mohapatra
Internet-Draft                                             Cisco Systems
Intended status: Standards Track                              J. Scudder
Expires: October 19, 2012                               Juniper Networks
                                                                 D. Ward
                                                           Cisco Systems
                                                                 R. Bush
                                         Internet Initiative Japan, Inc.
                                                              R. Austein
                                                    Dragon Research Labs
                                                          April 17, 2012

                      BGP Prefix Origin Validation
                    draft-ietf-sidr-pfx-validate-05

Abstract

   To help reduce well-known threats against BGP including prefix mis-
   announcing and monkey-in-the-middle attacks, one of the security
   requirements is the ability to validate the origination AS of BGP
   routes.  More specifically, one needs to validate that the AS number
   claiming to originate an address prefix (as derived from the AS_PATH
   attribute of the BGP route) is in fact authorized by the prefix
   holder to do so.  This document describes a simple validation
   mechanism to partially satisfy this requirement.

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 October 19, 2012.

Copyright Notice

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

Mohapatra, et al.       Expires October 19, 2012                [Page 1]
Internet-Draft        BGP Prefix Origin Validation            April 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Mohapatra, et al.       Expires October 19, 2012                [Page 2]
Internet-Draft        BGP Prefix Origin Validation            April 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  4
     1.1.  Requirements Language  . . . . . . . . . . . . . . . . . .  5
   2.  Prefix-to-AS Mapping Database  . . . . . . . . . . . . . . . .  5
     2.1.  Pseudo-Code  . . . . . . . . . . . . . . . . . . . . . . .  7
   3.  Policy Control . . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Interaction with Local Cache . . . . . . . . . . . . . . . . .  8
   5.  Deployment Considerations  . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  8
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  9
   8.  Security Considerations  . . . . . . . . . . . . . . . . . . .  9
   9.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     9.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     9.2.  Informational References . . . . . . . . . . . . . . . . . 10
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10

Mohapatra, et al.       Expires October 19, 2012                [Page 3]