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

Di Ma <madi@rpstir.net> Fri, 10 July 2020 06:35 UTC

Return-Path: <madi@rpstir.net>
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 C46323A0DC6; Thu, 9 Jul 2020 23:35:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 lrBQn7KgXklM; Thu, 9 Jul 2020 23:35:27 -0700 (PDT)
Received: from out20-63.mail.aliyun.com (out20-63.mail.aliyun.com [115.124.20.63]) (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 D81DF3A0C66; Thu, 9 Jul 2020 23:35:22 -0700 (PDT)
X-Alimail-AntiSpam: AC=CONTINUE; BC=0.1970709|-1; CH=green; DM=|CONTINUE|false|; DS=CONTINUE|ham_system_inform|0.178795-0.0195301-0.801675; FP=0|0|0|0|0|-1|-1|-1; HT=e02c03293; MF=madi@rpstir.net; NM=1; PH=DS; RN=4; RT=4; SR=0; TI=SMTPD_---.I.STS2s_1594362914;
Received: from 192.168.218.230(mailfrom:madi@rpstir.net fp:SMTPD_---.I.STS2s_1594362914) by smtp.aliyun-inc.com(10.147.42.197); Fri, 10 Jul 2020 14:35:15 +0800
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Di Ma <madi@rpstir.net>
In-Reply-To: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
Date: Fri, 10 Jul 2020 14:35:13 +0800
Cc: SIDR Operations WG <sidrops@ietf.org>, sidrops-ads@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <E62EE6B4-E051-499B-A8B1-EF93E2A63076@rpstir.net>
References: <CAL9jLaY4E4FAaWL1fAVV6VLCLA+_x-f72aLb2nyeiSfu-01eSw@mail.gmail.com>
To: Christopher Morrow <christopher.morrow@gmail.com>, SIDROps Chairs <sidrops-chairs@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/5Ckd_W3TEVhqXGWeRwMXlVMuG2E>
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 06:35:30 -0000

I am in support of adoption of this document as WG item.

And I will take part in discussions on it as I update RPSITR 2 the RP software to reflect new requirements on MFT.

Di

> 2020年7月10日 02:32,Christopher Morrow <christopher.morrow@gmail.com> 写道:
> 
> 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