[Sidrops] I-D Action: draft-ietf-sidrops-rpkimaxlen-03.txt

internet-drafts@ietf.org Thu, 24 October 2019 16:29 UTC

Return-Path: <internet-drafts@ietf.org>
X-Original-To: sidrops@ietf.org
Delivered-To: sidrops@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F2B4120013; Thu, 24 Oct 2019 09:29:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: sidrops@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sidrops@ietf.org
Message-ID: <157193457128.11345.8163888964309891372@ietfa.amsl.com>
Date: Thu, 24 Oct 2019 09:29:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/K7pCuZs25qshjkNfDms3p6PzYPg>
Subject: [Sidrops] I-D Action: draft-ietf-sidrops-rpkimaxlen-03.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Oct 2019 16:29:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the SIDR Operations WG of the IETF.

        Title           : The Use of Maxlength in the RPKI
        Authors         : Yossi Gilad
                          Sharon Goldberg
                          Kotikalapudi Sriram
                          Job Snijders
                          Ben Maddison
	Filename        : draft-ietf-sidrops-rpkimaxlen-03.txt
	Pages           : 12
	Date            : 2019-10-24

   This document recommends ways to reduce forged-origin attack surface
   by prudently limiting the address space that is included in Route
   Origin Authorizations (ROAs).  One recommendation is to avoid using
   the maxLength attribute in ROAs except in some specific cases.  The
   recommendations complement and extend those in RFC 7115.  The
   document also discusses creation of ROAs for facilitating Distributed
   Denial of Service (DDoS) mitigation services.  Considerations related
   to ROAs and origin validation for the case of destination-based
   Remote Triggered Black Hole (RTBH) filtering are also highlighted.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at: