Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal

Dear all,

I reviewed the document (and previously suggested the addition of the
'#' comment). I'd like to see this document published as IETF RFC.

Some small nitpicks:

Section 1.1 terminology should also point to 8174

Section 2.1 "ASCII" should probably be UTF-8, this is 2018 and we are the IETF

Section 4: "Therefore, the Relying Party MUST continue to retrieve the
data in case of errors." I am not sure software "MUST" continue when
errors are found - maybe those errors should just be fixed. Generally
I'm not a fan of being too forgiving, I'd reconsider the RFC 2119/8174
terminology here, or leave the sentence out.

Kind regards,

Job

On Mon, Dec 17, 2018 at 5:03 PM Tim Bruijnzeels <tim@nlnetlabs.nl> wrote:
>
> I don’t remember seeing any comments on this one. What’s the next step?
>
> Tim
>
> > On 5 Nov 2018, at 03:55, Christopher Morrow <christopher.morrow@gmail.com> wrote:
> >
> > Howdy WG Folks,
> >
> > Please read/review the document: draft-ietf-sidrops-https-tal
> >
> > The abstract:
> >   "This document defines a Trust Anchor Locator (TAL) for the Resource
> >    Public Key Infrastructure (RPKI).  This document obsoletes RFC 7730
> >    by adding support for HTTPS URIs in a TAL."
> >
> > explains the gist, and the document is a short 10 page read/review... Let's have a read/comment and push to get this moved into the IESG process before xmas 2018!
> >
> > -chris
> > co-chair-sidrops
> > _______________________________________________
> > Sidrops mailing list
> > Sidrops@ietf.org
> > https://www.ietf.org/mailman/listinfo/sidrops
>
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal - ENDS Nov 26 2018 (11/26/2018)