Re: [OPSAWG] Benjamin Kaduk's Discuss on draft-ietf-opsawg-finding-geofeeds-12: (with DISCUSS and COMMENT)

[Russ Housley <[e-mail]>]

Ben:

>>>> 
>>>>  text.  Trailing space characters MUST NOT appear on a line of text.
>>>>  That is, the space or tab characters must not be followed by the
>>>>  <CRLF> sequence.  [...]
>>>> 
>>>> Is the restriction on Unicode characters of category "space separator"
>>>> ("space characters") or the two listed characters?  (Why just those two,
>>>> and not form feed as well?)
>>> 
>>> Looking at the ABNF in RFC 8805, It does not look like there should be
>>> any trailing whitespace, this was more for consistency with RFC 5485.
>> 
>> perhaps a clearer phrasing would be
>> 
>>    Trailing space characters MUST NOT appear on a line of text.  That
>>    is, space or tab characters must not immediately preceed a <CRLF>
>>    sequence.
> 
> Hmm, so I'm supposed to read "space characters" and think "a sequence of
> one or more 0x20 bytes"?  I guess I can maybe see that, but do kind of want
> an answer on whether we care about other unicode codepoints that are
> "whitespace" appearing immediately prior to <CRLF>.  For better or for
> worse, things get complicated and messy once we go past 7-bit ASCII.

RFC 8805 says that each feed entry is a text line of the form:

   ip_prefix,alpha2code,region,city,postal_code

The first three fields are ASCII.  The city can be UTF-8, except comma.  The postal_code is optional and deprecated, but it can be can be UTF-9, except comma.

By that description, trailing whitespace is allowed, but not helpful.

I guess we can drop that sentence.

Russ