Re: [Sidrops] RPKI Signed Checklists - draft-spaghetti-sidrops-rpki-rsc-01

Job Snijders <job@fastly.com> Fri, 05 February 2021 22:07 UTC

Return-Path: <job@fastly.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 C94C63A0C56 for <sidrops@ietfa.amsl.com>; Fri, 5 Feb 2021 14:07:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 54HqcPR6l-6f for <sidrops@ietfa.amsl.com>; Fri, 5 Feb 2021 14:07:08 -0800 (PST)
Received: from mail-wr1-x434.google.com (mail-wr1-x434.google.com [IPv6:2a00:1450:4864:20::434]) (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 378D13A0C55 for <sidrops@ietf.org>; Fri, 5 Feb 2021 14:07:07 -0800 (PST)
Received: by mail-wr1-x434.google.com with SMTP id b3so9346195wrj.5 for <sidrops@ietf.org>; Fri, 05 Feb 2021 14:07:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=3r/7usR5btsXin54tFrzHLXFUstXdtqvrUaZifh8voc=; b=gZgQgMz7H1u3gn/fxJIvfry20TKshp4EVVrC4Oi1UdZN9KVTyCyR7CODXj3FoZX12u lLP0rhGgelt1uFYOfz2Dpe/a8I6ST5mSQ+X3FLximC4IDQWQIBiffh2Jt0NExt3Qkb2z Amt9shW9UcffnmGMuyXHFC643kUCMaT+vYn5w=
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:references :mime-version:content-disposition:in-reply-to; bh=3r/7usR5btsXin54tFrzHLXFUstXdtqvrUaZifh8voc=; b=ExDLGDKiHvn4Bd5ajFg4U3M80s4tGNvJ7XiJGZECRw3AamzAMpyYTNF6thggSPBhDU YmUtW2/Ym/fC3bHW9vQOVI5pRpCMgbILsjT7B0qS3DFktcn1SXIKP+8WHvtwllUM53iv 6KzODlPZU1pUMeLBMRoXyHC7f4UOq77DUUCXNmF3b/CqrMadrZyg33xj1haDoV1U+aXZ JpQ2C+Xcx9Ga649IobQL2Zdrult1KP/fAt2SZIsYbzD5kCKCeKAeQSPAZYj0O3vdVhdg AV1CMTzB0VwOruDHfeK0S227o87XD8ouGPZLLMyvcKozEmWUfFdJtDOMjxfk9gIMgYVh REIQ==
X-Gm-Message-State: AOAM530+CWn+xNcutiewIRN/r6I6/sD2i/h2So4SXKEsCQC6FyYj+9U4 lOXgUSfbmuONpyHfKty+LKgS7XVrZyfHqamzpgjIQemkK2rHpBiseDnn+YC5m2/3Ixe0hGs8s6w icwbcpVPEvlOTBqVQG6A1IlGwDSCEvmUKL2ojvGiff1CWzLa+Dnz9RTE=
X-Google-Smtp-Source: ABdhPJzmko3r0KqV1baq0uKcg9D7uk30wYCnP53iwXhTE7yNbkzQqrucO6J5CRn2GuNJr3pQPPnmWg==
X-Received: by 2002:a5d:6191:: with SMTP id j17mr7114060wru.281.1612562825016; Fri, 05 Feb 2021 14:07:05 -0800 (PST)
Received: from snel (mieli.sobornost.net. [45.138.228.4]) by smtp.gmail.com with ESMTPSA id b4sm13056692wrn.12.2021.02.05.14.07.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 05 Feb 2021 14:07:03 -0800 (PST)
Date: Fri, 5 Feb 2021 23:07:01 +0100
From: Job Snijders <job@fastly.com>
To: sidrops@ietf.org
Message-ID: <YB3BhRECFDAGnxts@snel>
References: <YBwv0jryMQ9KL9OO@snel>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="McZkFGNLFxCT+zU9"
Content-Disposition: inline
In-Reply-To: <YBwv0jryMQ9KL9OO@snel>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/u84Y70tVM8YqiAFKZch_f5jzBUI>
Subject: Re: [Sidrops] RPKI Signed Checklists - draft-spaghetti-sidrops-rpki-rsc-01
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: Fri, 05 Feb 2021 22:07:10 -0000

Dear working group,

I.... hopefully managed to generate the world's first RPKI Signed
Checklist! It is possible this RSC was generated incorrectly, I don't
have a proper validator yet. Generating this RSC .sig involved an ASN.1
to C to XML to DER conversion process, the Lament Configuration, and vi.

Attached to this email are 3 files:

    432K Feb  5 21:31 b42_ipv6_loa.png             \_ arbitrary files
    212B Feb  5 21:31 b42_service_definition.json  /
    1.6K Feb  5 21:31 checklist.sig                <!-- the RSC!

The 'b42_ipv6_loa.png' and 'b42_service_definition.json' files are part
of an imaginary private business to business process in which I try to
prove to a service provider I'm authorized to use 2001:67c:208c::/48.

The 'b42_service_definition.json' could be part of a challenge/response
process initiated by the ISP. The RPKI can now be used to sign arbitrary
files, even hand-written BYOIP Letters Of Authority (LOAs) like the .png :-)

The content-type OID in 'checklist.sig' is '1.3.6.1.4.1.41948.49'. This
OID is a placeholder from the PEN realm, for testing until an assignment
in the relevant SMI registry has been created. Make sure to keep this
OID on a feature branch or hidden behind a compile time option! The
on-the-wire format can still change in future versions of the draft!

The EE certificate in 'checklist.sig' should be validatable via SKI
2C:CA:BC:2A:5D:CB:91:61:AA:B6:27:1A:68:B9:7A:20:01:92:B0:9E (a copy can
be found here: http://console.rpki-client.org/rpki.ripe.net/repository/DEFAULT/LMq8Kl3LkWGqticaaLl6IAGSsJ4.cer.html)
towards the RIPE NCC Trust Anchor.

The 'checklist.sig' eContent is also available in XML format here:
https://github.com/job/draft-rpki-checklists/blob/main/example/b42.xml

The ASN.1 module is here https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-rsc-01

I hope this helps interested parties to implement signers or validators.

Kind regards,

Job