[Sidrops] I-D Action: draft-ietf-sidrops-roa-considerations-02.txt

internet-drafts@ietf.org Fri, 29 April 2022 07:39 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 7341DC159483; Fri, 29 Apr 2022 00:39:28 -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: 8.1.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: sidrops@ietf.org
Message-ID: <165121796844.7454.9216190561668830223@ietfa.amsl.com>
Date: Fri, 29 Apr 2022 00:39:28 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/Z05KG6rA3qbfK3YJMMcztqSF1jQ>
Subject: [Sidrops] I-D Action: draft-ietf-sidrops-roa-considerations-02.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.34
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: Fri, 29 Apr 2022 07:39:28 -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           : Avoidance for ROA Containing Multiple IP Prefixes
        Authors         : Zhiwei Yan
                          Randy Bush
                          Guanggang Geng
                          Jiankang Yao
	Filename        : draft-ietf-sidrops-roa-considerations-02.txt
	Pages           : 7
	Date            : 2022-04-29

Abstract:
   In RPKI, the address space holder needs to issue an ROA object when
   authorizing one or more ASes to originate routes to IP prefix(es).
   During ROA issurance process, the address space holder may need to
   specify an origin AS for a list of IP prefixes.  Additionally, the
   address space holder is free to choose to put multiple prefixes into
   a single ROA or issue separate ROAs for each prefix according to the
   current specification.  This memo analyzes some operational problems
   which may arise from ROAs containing multiple IP prefixes and
   recommends avoiding placing multiple IP prefixes in one ROA.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-roa-considerations/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-roa-considerations-02

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-roa-considerations-02


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts