The Use of Maxlength in the RPKI
draft-yossigi-rpkimaxlen-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
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)
Network Working Group                                           Y. Gilad
Internet-Draft                                               S. Goldberg
Intended status: Best Current Practice                 Boston University
Expires: September 14, 2017                                    K. Sriram
                                                                    NIST
                                                          March 13, 2017

                    The Use of Maxlength in the RPKI
                      draft-yossigi-rpkimaxlen-00

Abstract

   This document recommends that operators avoid using the maxLength
   attribute when issuing Route Origin Authorizations (ROAs) in the
   Resource Public Key Infrastructure (RPKI).  These recommendations
   complement those in [RFC7115].

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 14, 2017.

Copyright Notice

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

Gilad, et al.          Expires September 14, 2017               [Page 1]
Internet-Draft               RPKI maxLength                   March 2017

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements  . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Suggested Reading . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Forged Origin Subprefix Hijack  . . . . . . . . . . . . . . .   3
   4.  Measurements of Today's RPKI  . . . . . . . . . . . . . . . .   5
   5.  Use Minimal ROAs without Maxlength  . . . . . . . . . . . . .   6
     5.1.  When a Minimal ROA Cannot Be Used?  . . . . . . . . . . .   6
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .   7
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The RPKI [RFC6480] uses Route Origin Authorizations (ROAs) to create
   a trusted mapping from an IP prefix to a set of autonomous systems
   (ASes) that are authorized to originate this prefix.  Each ROA
   contains a set of IP prefixes, and an AS number of an AS authorized
   originate all the IP prefixes in the set [RFC6482].  Each ROA is
   cryptographically signed by the party that is authorized to allocate
   the set of IP prefixes.

   The RPKI also supports a maxLength attribute.  According to
   [RFC6482], "When present, the maxLength specifies the maximum length
   of the IP address prefix that the AS is authorized to advertise."
   Thus, rather than requiring the ROA to explictly list each prefix the
   AS is authorized to originate, the maxLength attribute provides a
   shorthand that authorizes an AS to announce a set of IP prefixes.

   However, measurements of current RPKI deployments have found that use
   of the maxLength in ROAs tends to lead to security problems.
   Specifically, as of September 2016, 89% of the prefixes specified in
   ROAs that use the maxLength attribute, are vulnerable to a forged-
   origin subprefix hijack.  The forged-origin subprefix hijack affects
   any IP prefix that is authorized in ROA but is not announced in BGP.
   The impact of such an attack is the same as standard subprefix hijack
   on an IP prefix that is unprotected by a ROA in the RPKI.

   For this reason, this document recommends that operators avoid using
   the maxLength attribute in their ROAs as a best current practice.
Show full document text