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

internet-drafts@ietf.org Mon, 02 November 2020 15:59 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 5219E3A1184; Mon, 2 Nov 2020 07:59:27 -0800 (PST)
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: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sidrops@ietf.org
Message-ID: <160433276728.27937.10370357022765531639@ietfa.amsl.com>
Date: Mon, 02 Nov 2020 07:59:27 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/prY3YjP3k_427Kls9lOOSHfuvGU>
Subject: [Sidrops] I-D Action: draft-ietf-sidrops-rpkimaxlen-05.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: Mon, 02 Nov 2020 15:59:35 -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-05.txt
	Pages           : 12
	Date            : 2020-11-02

   This document recommends ways to reduce forged-origin hijack attack
   surface by prudently limiting the set of IP prefixes that are
   included in a Route Origin Authorization (ROA).  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 the use of Distributed Denial of Service (DDoS)
   mitigation services.  Considerations related to ROAs and origin
   validation in the context 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: