Re: [OPSAWG] AD review of draft-ietf-opsawg-finding-geofeeds-04

[Russ Housley <[e-mail]>]

> On Apr 12, 2021, at 7:33 PM, Randy Bush <[e-mail]> wrote:
> 
>>>> 3. The definition of canonicalization refers to section 2.2 of RFC
>>>> 5485 (which talks about ASCII) vs RFC8805 which talks about UTF-8.  Is
>>>> this disparity an issue?
>>> 
>>> russ, how do you want to handle?
>> 
>> This is really about line endings, but it would probably be best to
>> assign a content type for UTF8 Test with CRLF.
> 
> yuchh.  send text, if you would please.

Actually, I went back to the I-D, and I withdraw my suggestions.

This I-D already defines a new content type: id-ct-geofeedCSVwithCRLF.

This new content type already handles the situation as I was thinking.  It could be more clear, and I suggest:

OLD:

   Borrowing detached signatures from [RFC5485], after text file
   canonicalization (Sec 2.2), the Cryptographic Message Syntax (CMS)
   [RFC5652] would be used to create a detached DER encoded signature
   which is then BASE64 encoded and line wrapped to 72 or fewer
   characters.

NEW:

   The canonicalization procedure converts the data from its internal
   character representation to the UTF-8 [RFC3629] character encoding,
   and the <CRLF> sequence MUST be used to denote the end of a
   line of 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.  Thus, a blank line is represented solely by
   the <CRLF> sequence.  Other nonprintable characters, such as
   backspace, are not expected.  For robustness, any nonprintable
   characters MUST NOT be changed by canonicalization.  Trailing
   blank lines MUST NOT appear at the end of the file.  That is, the
   file must not end with multiple consecutive <CRLF> sequences.
   Any end-of-file marker used by an operating system is not considered
   to be part of the file content.  When present, such end-of-file
   markers MUST NOT be processed by the digital signature algorithm.

   Borrowing detached signatures from [RFC5485], after file
   canonicalization, the Cryptographic Message Syntax (CMS)
   [RFC5652] would be used to create a detached DER encoded signature
   which is then BASE64 encoded and line wrapped to 72 or fewer
   characters.

END

Russ