Re: [Sidrops] I-D Action: draft-ietf-sidrops-6486bis-06.txt

I confirm that I will become an editoer for this document if none of the existing authors want to do so.

Russ

> On Sep 23, 2021, at 1:38 PM, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> 
> Howdy!
> I believe this document is at the point where WGLC is the next step?
> I believe also we are adding Russ Housley as person running the show through the final boss fight with IETF@/IESG.
> I know I'd like to say: "Thanks to Stephen for his work on this, it's certainly been a journey :)"
> 
> Provided this is the state the authors agree on and they want to move to WGLC.... please verify that is the case on-list :)
> 
> 
> On Mon, Jul 26, 2021 at 9:26 AM <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the SIDR Operations WG of the IETF.
> 
>         Title           : Manifests for the Resource Public Key Infrastructure (RPKI)
>         Authors         : Rob Austein
>                           Geoff Huston
>                           Stephen Kent
>                           Matt Lepinski
>         Filename        : draft-ietf-sidrops-6486bis-06.txt
>         Pages           : 17
>         Date            : 2021-07-26
> 
> Abstract:
>    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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/ <https://datatracker.ietf.org/doc/draft-ietf-sidrops-6486bis/>
> 
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-6486bis-06 <https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-6486bis-06>
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-6486bis-06 <https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-6486bis-06>
> 
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/ <ftp://ftp.ietf.org/internet-drafts/>
> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org <mailto:Sidrops@ietf.org>
> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops