[Sidrops] RPKI Signed Checklists - draft-spaghetti-sidrops-rpki-rsc-00

Job Snijders <job@fastly.com> Thu, 04 February 2021 17:33 UTC

Return-Path: <job@fastly.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5050C3A09BB for <sidrops@ietfa.amsl.com>; Thu, 4 Feb 2021 09:33:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fastly.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id 3FXfvPsCsHvL for <sidrops@ietfa.amsl.com>; Thu, 4 Feb 2021 09:33:11 -0800 (PST)
Received: from mail-wr1-x42d.google.com (mail-wr1-x42d.google.com [IPv6:2a00:1450:4864:20::42d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B26233A1626 for <sidrops@ietf.org>; Thu, 4 Feb 2021 09:33:11 -0800 (PST)
Received: by mail-wr1-x42d.google.com with SMTP id u14so4523577wri.3 for <sidrops@ietf.org>; Thu, 04 Feb 2021 09:33:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:subject:message-id:mime-version:content-disposition; bh=Xq47yl74RWt8T+xijl5VIOxRGLf+6quMxJKNhBDg6QI=; b=D7+FowI83STth6KeYNgL4Xnz4ejM+fVnKeA1CYZCKfk1eOQbKsOdRjjaBO/Ps2uc5t Upxk+IE2VoSv0yeIOWV/A1DJSfWScQfoQDEEIsDeQf+Ki/m8VF8/50Hx/93d3f2lf5Bx P1eNA8hHkU+2g+j+c6vSzKPBIOcKWFOHVffcA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mime-version :content-disposition; bh=Xq47yl74RWt8T+xijl5VIOxRGLf+6quMxJKNhBDg6QI=; b=lTflQ9Gqjz49TyadtYyYNNrtGdDKNZ0g9kAj1D2wOtKpmMyj97WYJQg3DxgJr8K0/p qt+DvqtZrw3lNvxstG081/js3GJSBSk1nAnp908udDuBGP3KFuOgHiKQ9U9vKM4smBwE mYoFRc+9f9qm4muj+CvUKhcI6ebcLy1kGSf1raFxwr6MFV8BtPHTOgzFRvqJ6dWN60ZE ylJG6o8ji13ckd/YXr7DjzjSQ1rbIen1tcGZNFVLzjuqacSo1nwGh3aNWkAeJUApM/EV BVC7doEQ4uN/jie4aPP/nzcDRqSZRoaYhMMHtNJJ8CR4R1ESQxlpMKEWEcsqwAs3n80m Eo4g==
X-Gm-Message-State: AOAM531Luv2QQYFtT7nP89CPnbjs5ZMMm5/2DSLDb4YqWWpD88cdmCvO /YCumCXLMBDlTo8B24VNgsVfHU2u+T9Ew5OY59NWhI9dWMtaljwGkmA/FLTB2DVF7b20ARMqF2y mKGvxmA12NSvdnP4p6y3fQzBiFh980BH/xTiQNgfIL3xuByfA/UGLcAg=
X-Google-Smtp-Source: ABdhPJwFM+e5vNJBzDvWS+n532WF4CcGSDigoWumABW4htgJXyLF5bN1l3V8+ud4e+rDqwWy0FELaQ==
X-Received: by 2002:adf:e68e:: with SMTP id r14mr507742wrm.242.1612459989575; Thu, 04 Feb 2021 09:33:09 -0800 (PST)
Received: from snel (mieli.sobornost.net. []) by smtp.gmail.com with ESMTPSA id w2sm7269654wmg.27.2021. (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 04 Feb 2021 09:33:09 -0800 (PST)
Date: Thu, 4 Feb 2021 18:33:06 +0100
From: Job Snijders <job@fastly.com>
To: sidrops@ietf.org
Message-ID: <YBwv0jryMQ9KL9OO@snel>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/XgkW5Mm-mKDl3K7at4YiP7dBdmc>
Subject: [Sidrops] RPKI Signed Checklists - draft-spaghetti-sidrops-rpki-rsc-00
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Feb 2021 17:33:13 -0000

Dear Working Group,

I've produced a specification which at a high level might appear similar
to RTA, but has fundamentally different semantics.

RTA enables multiple signers to attest exactly one hash for an unnamed
digital object, but RSC on the other hand enables a single signer to
attest one or more named digital objects.

I believe the ability to pass filenames around will greatly improve
operations for administrators.

Another advantage of RSC should be that in closely following the RFC
6488 template the burden of implementation is significantly reduced.

I would appreciate the working group taking a look and considering
adoption. After adoption the IANA early allocation procedure can be used
to obtain OIDs, after which running code can demonstrated, and then
perhaps onwards to deployment.

Kind regards,


----- Forwarded message from internet-drafts@ietf.org -----

Date: Thu, 04 Feb 2021 09:20:26 -0800
From: internet-drafts@ietf.org
To: Job Snijders <job@fastly.com>
Subject: New Version Notification for draft-spaghetti-sidrops-rpki-rsc-00.txt

A new version of I-D, draft-spaghetti-sidrops-rpki-rsc-00.txt
has been successfully submitted by Job Snijders and posted to the
IETF repository.

Name:		draft-spaghetti-sidrops-rpki-rsc
Revision:	00
Title:		RPKI Signed Checklists
Document date:	2021-02-04
Group:		Individual Submission
Pages:		8
URL:            https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-rsc-00.txt
Status:         https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-rsc/
Htmlized:       https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-rsc
Htmlized:       https://tools.ietf.org/html/draft-spaghetti-sidrops-rpki-rsc-00

   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 a checksum listing
   with an arbitrary set of Internet Number Resources.


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

----- End forwarded message -----