Re: [Sidrops] [WG ADOPTION]: draft-ymbk-sidrops-6486bis - ENDS: 07/23/2020 (July 23)

Tim Bruijnzeels <tim@nlnetlabs.nl> Fri, 10 July 2020 07:11 UTC

Return-Path: <tim@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 4B0713A0E00; Fri, 10 Jul 2020 00:11:35 -0700 (PDT)
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=nlnetlabs.nl
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 d-B92C_iYsnV; Fri, 10 Jul 2020 00:11:34 -0700 (PDT)
Received: from dicht.nlnetlabs.nl (dicht.nlnetlabs.nl [185.49.140.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB6D13A0DFF; Fri, 10 Jul 2020 00:11:33 -0700 (PDT)
Received: from [IPv6:2001:981:4b52:1:89e0:9c91:eb0d:e348] (unknown [IPv6:2001:981:4b52:1:89e0:9c91:eb0d:e348]) by dicht.nlnetlabs.nl (Postfix) with ESMTPSA id 7AFB81FA99; Fri, 10 Jul 2020 09:11:29 +0200 (CEST)
Authentication-Results: dicht.nlnetlabs.nl; dmarc=fail (p=none dis=none) header.from=nlnetlabs.nl
Authentication-Results: dicht.nlnetlabs.nl; spf=fail smtp.mailfrom=tim@nlnetlabs.nl
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nlnetlabs.nl; s=default; t=1594365089; bh=MMYrG3bs487jhhcb7hSZI/3KsK9EF4u12Rpm5vKF5EY=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=bFjBmmnGLISVaALxRiVNyq/o+RyP3U6uKw4ktJub25BxiR+uBCCZeZ2GhZGdMGSVh lUoJlKh4DM7jO3oYiaIh5393FBPEAMIi5WLj0djQAX7RYbc05ed0Vudl0tp9tGR5is svecaIgmD6951CQQhXABV2rNGZJ6ye92nZxj8inw=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Tim Bruijnzeels <tim@nlnetlabs.nl>
In-Reply-To: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
Date: Fri, 10 Jul 2020 09:11:28 +0200
Cc: SIDR Operations WG <sidrops@ietf.org>, SIDROps Chairs <sidrops-chairs@ietf.org>, sidrops-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <2DE961B9-C1DC-4A1C-81B9-8C15928800C3@nlnetlabs.nl>
References: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/K1uxTVh25NInrxZQlcFtL1ZhJhw>
Subject: Re: [Sidrops] [WG ADOPTION]: draft-ymbk-sidrops-6486bis - ENDS: 07/23/2020 (July 23)
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, 10 Jul 2020 07:11:35 -0000

I support adoption!

> On 9 Jul 2020, at 20:32, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> 
> Howdy WG Folks!
> The authors of the 6486-bis document:
>  draft-ymbk-sidrops-6486bis
> 
> would appreciate you all spending a few minutes to read/review and
> comment about adoptability in the working group. The abstract of same:
> 
>  "This document defines a "manifest" for use in the Resource Public Key
>   Infrastructure (RPKI).  A manifest is a signed object (file) that
>   contains a listing of all the signed objects (files) in the
>   repository publication point (directory) associated with an authority
>   responsible for publishing in the repository.  For each certificate,
>   Certificate Revocation List (CRL), or other type of signed objects
>   issued by the authority that are published at this repository
>   publication point, the manifest contains both the name of the file
>   containing the object and a hash of the file content.  Manifests are
>   intended to enable a relying party (RP) to detect certain forms of
>   attacks against a repository.  Specifically, if an RP checks a
>   manifest's contents against the signed objects retrieved from a
>   repository publication point, then the RP can detect "stale" (valid)
>   data and deletion of signed objects."
> 
> Thanks for your consideration, reading and commentary!
> -chris
> co-chair persona
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops