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

Russ Housley <housley@vigilsec.com> Thu, 09 July 2020 20:05 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 5A39D3A059F for <sidrops@ietfa.amsl.com>; Thu, 9 Jul 2020 13:05:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 10PVO_K_6RIa for <sidrops@ietfa.amsl.com>; Thu, 9 Jul 2020 13:05:50 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8C5F3A00D4 for <sidrops@ietf.org>; Thu, 9 Jul 2020 13:05:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 51178300B7C for <sidrops@ietf.org>; Thu, 9 Jul 2020 15:59:31 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GsFYPtGcixl5 for <sidrops@ietf.org>; Thu, 9 Jul 2020 15:59:26 -0400 (EDT)
Received: from a860b60074bd.fios-router.home (pool-72-66-113-56.washdc.fios.verizon.net [72.66.113.56]) by mail.smeinc.net (Postfix) with ESMTPSA id 37EA23005C6; Thu, 9 Jul 2020 15:59:26 -0400 (EDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.14\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
Date: Thu, 09 Jul 2020 15:59:27 -0400
Cc: SIDR Operations WG <sidrops@ietf.org>, SIDROps Chairs <sidrops-chairs@ietf.org>, sidrops-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D6C23623-70E5-4C25-B3D2-8CB271964B8F@vigilsec.com>
References: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>
X-Mailer: Apple Mail (2.3445.104.14)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/UcM8cH49g3qcelSA1HGy627thm8>
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: Thu, 09 Jul 2020 20:05:53 -0000

I support adoption.  This captures things that were discussed at the recent virtual interims.

Russ


> On Jul 9, 2020, at 2:32 PM, 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