Re: [art] [Technical Errata Reported] RFC7578 (5616)

[[e-mail] (Dale R. Worley)]

RFC Errata System <[e-mail]> writes:
> [RFC7578] Section: 4.5
>
> Original Text
> -------------
> For example, a form with a text field in
> which a user typed "Joe owes <eu>100", where <eu> is the Euro symbol,
> might have form data returned as:
>     --AaB03x
>     content-disposition: form-data; name="field1"
>     content-type: text/plain;charset=UTF-8
>     content-transfer-encoding: quoted-printable
>
>     Joe owes =E2=82=AC100.
>     --AaB03x
>
> Corrected Text
> --------------
> For example, a form with a text field in
> which a user typed "Joe owes <eu>100", where <eu> is the Euro symbol,
> might have form data returned as:
>     --AaB03x
>     content-disposition: form-data; name="field1"
>     content-type: text/plain;charset=UTF-8
>     content-transfer-encoding: quoted-printable
>
>     Joe owes <eu>100.
>     --AaB03x
>
> Notes
> -----
> Section 4.7 says that "Senders SHOULD NOT generate any parts with a Content-Transfer-Encoding header field."

The "Original Text" gives an example, which seems to me to be correct.
However, as the erratum notes, the example violates the SHOULD NOT in
section 4.7.  And as section 4.7 notes, "Currently, no deployed
implementations that send such bodies have been discovered.", suggesting
that the example is not representative of current practice.

But the proposed "Corrected Text" is itself incorrect, in that the
Content-Transfer-Encoding header is still present -- the given body
isn't valid for quoted-printable.

Dale