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

I support the publication of this document.

Yet the key words section of this document is supposed to use the following the description:

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   “OPTIONAL” in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

Besides, I suggest changing

‘an rsync URI [RFC5781], or an HTTPS URI [RFC7230]'

into 

‘either an rsync URI [RFC5781], or an HTTPS URI [RFC7230]'

in Section 2.1 Trust Anchor Locator Format.

The single OR could lead to a different comprehending logically.

Di  Ma
RPSTIR
https://bgpsecurity.net

> 在 2018年6月8日，21:45，Chris Morrow <morrowc@ops-netman.net> 写道：
> 
> 
> Howdy Gentle Folks,
> 
> The authors of: draft-ietf-sidrops-https-tal-03 would like the WG to
> consider a WGLC of their document, 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."
> 
> Please have a read through the document and send along
> comments/questions/additions/subtractions so the authors can amend if
> required with the intent to move this document along the proper path
> in short order.
> 
> thanks!
> -chris
> co-chair
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops

Re: [Sidrops] WGLC: draft-ietf-sidrops-https-tal-03 - ENDS 22 June 2018