[Sidrops] Robert Wilton's No Objection on draft-ietf-sidrops-rpkimaxlen-15: (with COMMENT)

Robert Wilton via Datatracker <noreply@ietf.org> Mon, 15 August 2022 14:49 UTC

Return-Path: <noreply@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 571ACC1524B5; Mon, 15 Aug 2022 07:49:58 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Robert Wilton via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-sidrops-rpkimaxlen@ietf.org, sidrops-chairs@ietf.org, sidrops@ietf.org, morrowc@ops-netman.net, morrowc@ops-netman.net
X-Test-IDTracker: no
X-IETF-IDTracker: 8.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Robert Wilton <rwilton@cisco.com>
Message-ID: <166057499835.4940.16221131130819181598@ietfa.amsl.com>
Date: Mon, 15 Aug 2022 07:49:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/D2gpPnz6j6JRu8hufl2qqAL_niU>
Subject: [Sidrops] Robert Wilton's No Objection on draft-ietf-sidrops-rpkimaxlen-15: (with COMMENT)
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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, 15 Aug 2022 14:49:58 -0000

Robert Wilton has entered the following ballot position for
draft-ietf-sidrops-rpkimaxlen-15: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpkimaxlen/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Hi,

I considered balloting this as a discuss (for a discussion), but this is
outside my area of knowledge expertise.

Although the document indicates that the number of published ROAs should remain
the same, since each ROA can list multiple prefixes, was any consideration to
the potential increase in VRPs (if that is the right term) that this change
will cause and whether this may negatively affect routers that are consuming
the ROAs/VRPs?

Am I right in assuming that the number of valid ROAs that can be announced
should effectively be bound by the number of BGP prefixes advertised for an AS
and hence this shouldn't be a problem?

But other that the question above, I found this document to be very easy and
pleasant to read.

Regards,
Rob