errata logo graphic

Found 4 records.

Status: Verified (3)

RFC5337, "Internationalized Delivery Status and Disposition Notifications", September 2008

Note: This RFC has been obsoleted by RFC6533

Source of RFC: eai (app)

Errata ID: 1512

Status: Verified
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Verifier Name: Lisa Dusseault
Date Verified: 2008-09-16

Section Heading says:

Updates: 3461, 3464, 3798

It should say:

Updates: 3461, 3462, 3464, 3798

Notes:

Within Section 4, the text in the RFC on page 8 clearly updates the
definition of the multipart/report media type defined in RFC 3642.
This should be made visible in the front matter and the metadata
of the RFC.


Errata ID: 1513

Status: Verified
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 4, pg.7 says:

|  text-fixed = %d1-9 /      ; Any Unicode character except for NUL,
|              %d11 /       ; CR and LF, encoded in UTF-8
               %d12 /
               %d14-127
     ; Same as <text> from [RFC2822], but without <obs-text>.
     ; If/when RFC 2822 is updated to disallow <obs-text>,
     ; this should become just <text>
     ; Also, if/when RFC 2822 is updated to disallow control characters
     ; this should become a reference to RFC 2822upd instead.

   utf8-text = text-fixed / UTF8-non-ascii

It should say:

|  text-fixed = %d1-9 /     ; Any US-ASCII character except for NUL,
|               %d11 /      ; CR and LF
                %d12 /
                %d14-127
     ; Same as <text> from [RFC2822], but without <obs-text>.
     ; If/when RFC 2822 is updated to disallow <obs-text>,
     ; this should become just <text>
     ; Also, if/when RFC 2822 is updated to disallow control characters
     ; this should become a reference to RFC 2822upd instead.

   utf8-text = text-fixed / UTF8-non-ascii

Notes:

The long comment as well as the subsequent definition of
<utf8-text> shows that the inline comment in the first two
lines must be in error.
The replacement inline comment is the translation of the
ABNF (assumed to be correct) to english text.


Errata ID: 1515

Status: Verified
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Verifier Name: Alexey Melnikov
Date Verified: 2009-07-06

Section 5, 3rd para says:

   The MDN specification also defines the Disposition-Notification-To
|  header, which is an address header and thus follows the same 8-bit
|  rules as other address headers such as "From" and "To" when used in a
   UTF-8 header message.

It should say:

   The MDN specification also defines the Disposition-Notification-To
|  header field, which is an address header field and thus follows the
|  same 8-bit rules as other address header fields such as "From" and
   "To" when used in a UTF-8 header message.

Notes:

Long-standing terminology established in the IEFT should be applied
in this paragraph as well, making the precise distinction between a
"header" and the "header fields" it it comprised of (other parts of
the document already do it the right way).


Status: Held for Document Update (1)

RFC5337, "Internationalized Delivery Status and Disposition Notifications", September 2008

Note: This RFC has been obsoleted by RFC6533

Source of RFC: eai (app)

Errata ID: 1514

Status: Held for Document Update
Type: Technical

Reported By: Alfred Hoenes
Date Reported: 2008-09-15
Held for Document Update by: Alexey Melnikov

Section 4, pg. 8 says:

a)
    MIME type                 [[one instance]], and

b)
    MIME types                [[two instances]]

It should say:

a)
    media type  

b)
    media types   

Notes:

Correct usage of established IETF terminology;
see RFC 4288 (et al.) for rationale.


Report New Errata