RPKI Autonomous Systems Cones: A Profile To Define Sets of Autonomous Systems Numbers To Facilitate BGP Filtering
draft-ss-grow-rpki-as-cones-00

Document Type Active Internet-Draft (individual)
Last updated 2018-05-01
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Global Routing Operations                                    J. Snijders
Internet-Draft                                                       NTT
Intended status: Informational                                M. Stucchi
Expires: November 2, 2018                                       RIPE NCC
                                                             May 1, 2018

 RPKI Autonomous Systems Cones: A Profile To Define Sets of Autonomous
              Systems Numbers To Facilitate BGP Filtering
                     draft-ss-grow-rpki-as-cones-00

Abstract

   This document describes a way to define groups of Autonomous System
   numbers in RPKI [RFC6480].  We call them AS-Cones.  AS-Cones provide
   a mechanism to be used by operators for filtering BGP-4 [RFC4271]
   announcements.

Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

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 https://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 November 2, 2018.

Copyright Notice

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

Snijders & Stucchi      Expires November 2, 2018                [Page 1]
Internet-Draft                RPKI AS Cones                     May 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://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.  Format of AS-Cone objects . . . . . . . . . . . . . . . . . .   3
     2.1.  Policy definition object  . . . . . . . . . . . . . . . .   3
       2.1.1.  Naming convention for Policy definition objects . . .   3
       2.1.2.  ASN.1 format of a Policy Definition object  . . . . .   3
       2.1.3.  Naming convention for neighbour relationships . . . .   4
     2.2.  AS-Cone definition object . . . . . . . . . . . . . . . .   4
       2.2.1.  Naming convention for AS-Cone objects . . . . . . . .   4
       2.2.2.  ASN.1 format of an AS-Cone  . . . . . . . . . . . . .   5
   3.  Validating an AS-Cone . . . . . . . . . . . . . . . . . . . .   5
   4.  Recommendations for use of AS-Cones at Internet Exchange
       points  . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Publication of AS-Cones as IRR objects  . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   7
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   8.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   7
     10.2.  Informative References . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   8

1.  Introduction

   The main goal of the Resource Public Key Infrastructure (RPKI) system
   [RFC6480] is to support improved security for the global routing
   system.  This is achieved through the use of information stored in a
   distributed repository system comprised of signed objects.  A
   commonly used object type is the Route Object Authorisation (ROAs),
   which describe the prefixes originated by ASNs.

   There is however no way for an operator to assert the routes for its
   customer networks, making it difficult to use the information carried
   by RPKI to create meaningful BGP-4 filters without relying on RPSL
   [RFC2622] as-sets.

Snijders & Stucchi      Expires November 2, 2018                [Page 2]
Internet-Draft                RPKI AS Cones                     May 2018
Show full document text