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

[Martin Hoffmann <[e-mail]>]

Tim Bruijnzeels wrote:
> On 17 Dec 2018, at 17:14, Job Snijders <[e-mail]> wrote:
> > 
> > Section 2.1 "ASCII" should probably be UTF-8, this is 2018 and we
> > are the IETF  
> 
> So, the machines will most likely ignore this anyway. I guess that
> UTF-8 should be okay, provided we restrict the allowed line breaks to
> <CRLF> or <LF> for these lines as well. So maybe rephrase:
> 
> Current:
> 
>    1.  an optional comment section consisting of one or more lines
>        starting with the '#' character, containing human readable
>        informational ASCII text, followed by an empty line using a
>        "<CRLF>" or "<LF>" line break only.
> 
> New:
> 
>    1.  an optional comment section consisting of one or more lines
>        starting with the '#' character, containing human readable
>        informational UTF-8 text, and ending with a "<CRLF>" or 
>        "<LF>" line break. Followed by an empty line using a
>        "<CRLF>" or "<LF>" line break only.

I don’t quite see why the empty line after the comment is necessary at
all. Since all the comment lines start with a hash, the end of the
comment section can be identified by the first line not starting with a
hash.

Kind regards,
Martin