Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-rsc-07.txt

Russ Housley <housley@vigilsec.com> Thu, 19 May 2022 18:38 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 B83B5C20D6AB for <sidrops@ietfa.amsl.com>; Thu, 19 May 2022 11:38:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 oW1Ztt6zOLtX for <sidrops@ietfa.amsl.com>; Thu, 19 May 2022 11:38:16 -0700 (PDT)
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 895B3C20D6A7 for <sidrops@ietf.org>; Thu, 19 May 2022 11:38:16 -0700 (PDT)
Received: from mail3.g24.pair.com (localhost [127.0.0.1]) by mail3.g24.pair.com (Postfix) with ESMTP id 6F59F182CC7; Thu, 19 May 2022 14:38:15 -0400 (EDT)
Received: from [10.0.1.2] (pfs.iad.rg.net [198.180.150.6]) (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 5887518277D; Thu, 19 May 2022 14:38:15 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <3BDB58DF-0431-4676-9606-611C129A4B0B@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_55C929A2-9D87-44CD-A2EB-5D5AC01F0AAB"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\))
Date: Thu, 19 May 2022 14:38:15 -0400
In-Reply-To: <DB9P190MB10839201BF38E8D1BCD485BBC0D09@DB9P190MB1083.EURP190.PROD.OUTLOOK.COM>
Cc: Job Snijders <job=40fastly.com@dmarc.ietf.org>, "sidrops@ietf.org" <sidrops@ietf.org>
To: Ben Maddison <benm@workonline.africa>
References: <165298105049.28270.14685971986743868185@ietfa.amsl.com> <YoZ/bsYUeHpCW3Mc@snel> <D55CE24C-36E2-4976-84BB-BDB19E0E2CC2@vigilsec.com> <DB9P190MB10839201BF38E8D1BCD485BBC0D09@DB9P190MB1083.EURP190.PROD.OUTLOOK.COM>
X-Mailer: Apple Mail (2.3445.104.21)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/HB45jXw0lL5V0TkJsXsn2Hr7srk>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-rsc-07.txt
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.34
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: Thu, 19 May 2022 18:38:18 -0000

Ben:

Sorry that I was not clear.  Since the goal is to align with RFC 3779, we should use the same definition as was used there, which is OCTET STRING (SIZE (2..3)).

Russ

> On May 19, 2022, at 1:46 PM, Ben Maddison <benm@workonline.africa> wrote:
> 
> Hi Russ,
> 
> SAFI is meaningless in this context, and we decided to enforce its omission in the ASN.1, since we were constraining the 3779 types anyway.
> 
> The point of the revision as a whole is to incorporate the constraints we want into the asn1 module whilst still producing DER that is decodable by 3779 implementations.
> 
> Cheers,
> 
> Ben
> From: Sidrops <sidrops-bounces@ietf.org> on behalf of Russ Housley <housley@vigilsec.com>
> Sent: Thursday, May 19, 2022 7:40:03 PM
> To: Job Snijders <job=40fastly.com@dmarc.ietf.org>
> Cc: sidrops@ietf.org <sidrops@ietf.org>
> Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-rpki-rsc-07.txt
>  
> Job:
> 
> I understand that inheritance is purposfully being removed.  No concerns there.
> 
> However, RFC 779 says:
> 
>    IPAddressFamily     ::= SEQUENCE {    -- AFI & optional SAFI --
>       addressFamily        OCTET STRING (SIZE (2..3)),
>       ipAddressChoice      IPAddressChoice }
> 
> Why is the addressFamily in this document limited to two octets?
> 
> Russ
> 
> 
> > On May 19, 2022, at 1:33 PM, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote:
> > 
> > Dear all,
> > 
> > Based on feedback from RPKI Cache Validator implementers the wire format
> > was adjusted Surely For Last Time! [tm] :-)
> > 
> > The new RSC ASN.1 module permits the use of existing RFC 3779
> > encoders/decoders, with two major constraints: inheritance is not
> > permitted, and RDI is not a thing. This update enables implementers to
> > use commonly deployed high-level API functions, or generate code from
> > the ASN.1 module which will impose the desired constraints.
> > 
> > @ Chairs - I think the ball now is back in your court? :-)
> > 
> > Kind regards,
> > 
> > Job
> > 
> > On Thu, May 19, 2022 at 10:24:10AM -0700, internet-drafts@ietf.org wrote:
> >> 
> >> 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           : A profile for Resource Public Key Infrastructure (RPKI) Signed Checklists (RSC)
> >>        Authors         : Job Snijders
> >>                          Tom Harrison
> >>                          Ben Maddison
> >>       Filename        : draft-ietf-sidrops-rpki-rsc-07.txt
> >>       Pages           : 16
> >>       Date            : 2022-05-19
> >> 
> >> Abstract:
> >>   This document defines a Cryptographic Message Syntax (CMS) profile
> >>   for a general purpose listing of checksums (a 'checklist'), for use
> >>   with the Resource Public Key Infrastructure (RPKI).  The objective is
> >>   to allow an attestation, in the form of a listing of one or more
> >>   checksums of arbitrary digital objects (files), to be signed "with
> >>   resources", and for validation to provide a means to confirm a
> >>   specific Internet Resource Holder produced the Signed Checklist.  The
> >>   profile is intended to provide for the signing of an arbitrary
> >>   checksum listing with a specific set of Internet Number Resources.
> >> 
> >> 
> >> 
> >> The IETF datatracker status page for this draft is:
> >> https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-rsc/ <https://datatracker.ietf.org/doc/draft-ietf-sidrops-rpki-rsc/>
> >> 
> >> There is also an HTML version available at:
> >> https://www.ietf.org/archive/id/draft-ietf-sidrops-rpki-rsc-07.html <https://www.ietf.org/archive/id/draft-ietf-sidrops-rpki-rsc-07.html>
> >> 
> >> A diff from the previous version is available at:
> >> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-rpki-rsc-07 <https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-rpki-rsc-07>
> >> 
> >> 
> >> Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts
> >> 
> >> 
> >> _______________________________________________
> >> Sidrops mailing list
> >> Sidrops@ietf.org
> >> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>
> > 
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>