Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-prefixlist-01.txt

Russ Housley <housley@vigilsec.com> Wed, 24 January 2024 21:07 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3CC0C14F68F for <sidrops@ietfa.amsl.com>; Wed, 24 Jan 2024 13:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Vxx8Ybey4dTc for <sidrops@ietfa.amsl.com>; Wed, 24 Jan 2024 13:07:18 -0800 (PST)
Received: from mail3.g24.pair.com (mail3.g24.pair.com [66.39.134.11]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 45CB4C14F68B for <sidrops@ietf.org>; Wed, 24 Jan 2024 13:07:18 -0800 (PST)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 446DC1535FB for <sidrops@ietf.org>; Wed, 24 Jan 2024 16:07:17 -0500 (EST)
Received: from smtpclient.apple (unknown [96.241.2.243]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail3.g24.pair.com (Postfix) with ESMTPSA id 38EE115362E for <sidrops@ietf.org>; Wed, 24 Jan 2024 16:07:17 -0500 (EST)
From: Russ Housley <housley@vigilsec.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
Date: Wed, 24 Jan 2024 16:07:06 -0500
References: <170612503890.46313.7195737912432658695@ietfa.amsl.com>
To: sidrops <sidrops@ietf.org>
In-Reply-To: <170612503890.46313.7195737912432658695@ietfa.amsl.com>
Message-Id: <2360628E-B1CF-47B0-B5D9-AC81954F147F@vigilsec.com>
X-Mailer: Apple Mail (2.3731.700.6)
X-Scanned-By: mailmunge 3.11 on 66.39.134.11
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/dbp9JZo8xyOWRwR4era4H5TNb3E>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-prefixlist-01.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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: Wed, 24 Jan 2024 21:07:22 -0000

I am confused by this change in the syntax:

   IPv4Prefixes ::= SEQUENCE (SIZE(1..MAX)) OF AddressPrefix{32}
   IPv6Prefixes ::= SEQUENCE (SIZE(1..MAX)) OF AddressPrefix{128}

   AddressPrefix {INTEGER: len} ::= BIT STRING (SIZE(0..len))

What does it mean when the prefix is a zero length BIT STRING?

Nit: you might want to change le to maxlen to make it clear that it is a bound, not the actual length of the prefix.

Russ


> On Jan 24, 2024, at 2:37 PM, internet-drafts@ietf.org wrote:
> 
> Internet-Draft draft-ietf-sidrops-rpki-prefixlist-01.txt is now available. It
> is a work item of the SIDR Operations (SIDROPS) WG of the IETF.
> 
>   Title:   A profile for Signed Prefix Lists for Use in the Resource Public Key Infrastructure (RPKI)
>   Authors: Job Snijders
>            Geoff Huston
>   Name:    draft-ietf-sidrops-rpki-prefixlist-01.txt
>   Pages:   13
>   Dates:   2024-01-24
> 
> Abstract:
> 
>   This document defines a "Signed Prefix List", a Cryptographic Message
>   Syntax (CMS) protected content type for use with the Resource Public
>   Key Infrastructure (RPKI) to carry the complete list of prefixes
>   which an Autonomous System (AS) may originate to all or any of its
>   routing peers.  The validation of a Signed Prefix List confirms that
>   the holder of the listed ASN produced the object, and that this list
>   is a current, accurate and complete description of address prefixes
>   that may be announced into the routing system originated by this AS.
> 
> The IETF datatracker status page for this Internet-Draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-prefixlist/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-sidrops-rpki-prefixlist-01.html
> 
> A diff from the previous version is available at:
> https://author-tools.ietf.org/iddiff?url2=draft-ietf-sidrops-rpki-prefixlist-01
> 
> Internet-Drafts are also available by rsync at:
> rsync.ietf.org::internet-drafts
>