RFC Errata

Errata Search

Source of RFC  
Summary Table Full Records

RFC 3887, "Message Tracking Query Protocol", September 2004

Note: This RFC has been updated by RFC 8553, RFC 8996

Source of RFC: msgtrk (app)
See Also: RFC 3887 w/ inline errata

Errata ID: 3721
Status: Verified
Type: Technical
Publication Format(s) : TEXT

Reported By: Ned Freed
Date Reported: 2013-09-10
Verifier Name: Barry Leiba
Date Verified: 2013-09-11

Section 4.1 says:

S: Content-Type: multipart/related; boundary=%%%%; type=tracking-status

It should say:

S: Content-Type: multipart/related; boundary=%%%%;
S:  type="message/tracking-status"


According to RFC 2387 section 3.1, the value of the type parameter for
multipart/related is supposed to be the "MIME media type of the 'root' body
part." Additionaly, section 3 of RFC 3886 specifically states that the value is
supposed to be "message/tracking-status". But all seven examples in section 4.1
show just the subtype as the parameter value.

*** This errata report applies to all of the examples in Section 4.1 ***

Report New Errata

Advanced Search