Re: [Sidrops] Interim Meeting Follow-up Mail

In one place "PR" should be "RP"

Russ

> On Oct 28, 2020, at 12:02 PM, Stephen Kent <stkent=40verizon.net@dmarc.ietf.org> wrote:
> 
> Tim,
> 
> I looked at the revised bullet points we agreed upon and crafted a new Section 6.4 to reflect the last point. (The first three were already covered in this or other sub-sections of Section 6.) The proposed, revised text is below. If you concur, I'll ask that 6486-bis be revised accordingly.
> 
> 
> 
> 
> 6.4.  Acquiring Files Referenced by a Manifest
> 
>    The RP MUST acquire all of the files enumerated in the manifest
>    (fileList) from the publication point. If there are files listed in the
>    manifest that cannot be retrieved from the publication point, or if
>    they fail the validity tests specified in [RFC6488], the fetch has
>    failed and the RP MUST proceed to Section 6.7; otherwise, proceed to
>    Section 6.5. Note that the set of retrieved objects may include types that
>    the PR is not prepared to process, e.g., objects other than CRLs, certificates, 
>    and Ghostbuster records (all of which MUST be processed by an RP, if present). 
>    When such objects are encountered by an RP, the RP MUST NOT attempt to validate 
>    the eContent (as described in Section 2.1.3.2 above) of such objects; 
>    encountering such objects does not, per se, result in a failed fetch.
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org <mailto:Sidrops@ietf.org>
> https://www.ietf.org/mailman/listinfo/sidrops <https://www.ietf.org/mailman/listinfo/sidrops>