Subject: Re: [pkix] [Editorial Errata Reported] RFC7030 (5779)

From: Benjamin Kaduk <[email-masked]>
Date: Wed, 17 Jul 2019 19:03:02 -0500

On Fri, Jul 12, 2019 at 06:26:09PM -0700, RFC Errata System wrote:
> The following errata report has been submitted for RFC7030,
> "Enrollment over Secure Transport".
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid5779
> 
> --------------------------------------
> Type: Editorial
> Reported by: Simon Edänge <[email-masked]>
> 
> Section: A.4
> 
> Original Text
> -------------
>  Because the DecryptKeyIdentifier attribute is not included in this
>    request, the response does not include additional encryption beyond
>    the TLS session.  The EST server response is:
> 
>    HTTP/1.1 200 OK
>    Status: 200 OK
>    Content-Type: multipart/mixed ; boundary=estServerExampleBoundary
>    Content-Length: 3219
> 
>    This is the preamble.  It is to be ignored, though it
>    is a handy place for estServer to include an explanatory note,
>    including contact or support information.
>    --estServerExampleBoundary
>    Content-Type: application/pkcs8
>    Content-Transfer-Encoding: base64
> 
> Corrected Text
> --------------
>  Because the DecryptKeyIdentifier attribute is not included in this
>    request, the response does not include additional encryption beyond
>    the TLS session.  The EST server response is:
> 
>    HTTP/1.1 200 OK
>    Status: 200 OK
>    Content-Type: multipart/mixed; boundary=estServerExampleBoundary
>    Content-Length: 3219
> 
>    This is the preamble.  It is to be ignored, though it
>    is a handy place for estServer to include an explanatory note,
>    including contact or support information.
>    --estServerExampleBoundary
>    Content-Type: application/pkcs8
>    Content-Transfer-Encoding: base64
> 
> Notes
> -----
> Content-Type: multipart/mixed ; boundary=estServerExampleBoundary
> 
> The ; has a space, believe it or not, we implemented it that way.

https://tools.ietf.org/html/rfc7231#section-3.1.1.1 says

     media-type = type "/" subtype *( OWS ";" OWS parameter )

which would seem to allow for whitespace before the semicolon.
So  I think this should be rejected.

-Ben