IETF Logo Mail Archive

Re: [Sidrops] I-D Action: draft-ietf-sidrops-aspa-profile-15.txt

Martin Hoffmann <martin@nlnetlabs.nl> Tue, 13 June 2023 07:44 UTC

Return-Path: <martin@nlnetlabs.nl>
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 A9E4DC14CE4C for <sidrops@ietfa.amsl.com>; Tue, 13 Jun 2023 00:44:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=nlnetlabs.nl
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 elV52b4Hnh3d for <sidrops@ietfa.amsl.com>; Tue, 13 Jun 2023 00:44:17 -0700 (PDT)
Received: from outbound.soverin.net (outbound.soverin.net [185.233.34.146]) (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 580F7C14F749 for <sidrops@ietf.org>; Tue, 13 Jun 2023 00:44:16 -0700 (PDT)
Received: from smtp.soverin.net (c04smtp-lb01.int.sover.in [10.10.4.74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by outbound.soverin.net (Postfix) with ESMTPS id 4QgLCy3LD9z6w; Tue, 13 Jun 2023 07:44:14 +0000 (UTC)
Received: from smtp.soverin.net (smtp.soverin.net [10.10.4.99]) by soverin.net (Postfix) with ESMTPSA id 4QgLCx4rlFzL1; Tue, 13 Jun 2023 07:44:13 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nlnetlabs.nl; s=soverin; t=1686642254; bh=gtFI8d1l13qF66+kEYrkF4wq0tcPe9J7oMYRicNlUTM=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=yetOsY/64n/hP4OR5ZfctPXEKRCHR7AwOpTWfBQvj0DKBpyRm8V9NSYpIcIM/1A1d cJG8EgLQtTIDNAakZnplEQu+0BLAtI68NZd+tqiGBzFejks47f7jjr/7xxh3f5zaRw 33woxDtl6rFSOv9b+qyLtDbmvK1LuikiJZoUO2TRkm0v0c9gHNiogfyfNEym3MWYLC PHU+7iTkGb4BIUfLIqlQjkVlzlcpx1YHFuz7I0lEXnVlFCVoeM8DecDw92oVrJStnP cL+gl1P4I+rUMY6CkXYKfi4J/ic2Zkh6z+ohws5bPCKtkvWa7Mi30RUNxmuaJ7Y+FK 6R6kZiEUO0VdA==
Date: Tue, 13 Jun 2023 09:44:13 +0200
X-Soverin-Authenticated: true
From: Martin Hoffmann <martin@nlnetlabs.nl>
To: Russ Housley <housley@vigilsec.com>
Cc: Ties de Kock <tdekock@ripe.net>, Job Snijders <job=40fastly.com@dmarc.ietf.org>, sidrops@ietf.org
Message-ID: <20230613094413.364aaa8c@smaug.local.partim.org>
In-Reply-To: <96D52BC8-C3BA-43C8-90E1-DD2621C2292F@vigilsec.com>
References: <168621843689.33017.6897451444105786551@ietfa.amsl.com> <ZIGogKIH4Srb8Nxt@snel> <20230608181440.33d6926f@glaurung.nlnetlabs.nl> <0C543A94-F70E-4A40-8350-C98FAAB5A9B5@vigilsec.com> <D100381E-6498-4EAD-B056-18F89836C097@ripe.net> <96D52BC8-C3BA-43C8-90E1-DD2621C2292F@vigilsec.com>
Organization: NLnet Labs
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/mclKu731BK-LFGe6gnHEeiiB1_I>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-aspa-profile-15.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: Tue, 13 Jun 2023 07:44:21 -0000

Russ Housley wrote:
> > On Jun 9, 2023, at 9:28 AM, Ties de Kock <tdekock@ripe.net> wrote:
> > 
> > We have  
> >> The elements of providers MUST be ordered in ascending numerical
> >> order.  
> > 
> > In the text. My understanding of how a DER encoded SET is that this
> > would imply this order. Is this correct?  
> 
> Not really.  The sort includes the tag, the length, and the value, so
> it depends of the SET definition whether you will get ascending order.

But for a SET OF INTEGER (0..4294967295) this should actually be
correct? The tag will be the same, shorter length sorts first, and
equal length values sort with the smaller value first.

If that is correct, then we are using a SEQUENCE because it is easier
and then require away what makes it easier.


  --  Martin

v2.23.0 | Report a Bug | By Email