RFC 5022, "Media Server Control Markup Language (MSCML) and Protocol", September 2007Source of RFC: INDEPENDENT
Errata ID: 1250
Publication Format(s) : TEXT
Reported By: Alfred Hoenes
Date Reported: 2008-01-04
Rejected by: Nevil Brownlee
Date Rejected: 2011-03-28
Section 8, p.49-50 says:
MIME Type or: MIME type (multiple instances each)
It should say:
Media Type or: media type
The RFC should apply IETF standard terminology.
In this case, it is clear that the RFC does *not* apply to the
context of email, and hence "MIME" should be avoided even more!
Please use the terminology established in RFC 2045 ff. !
Furthermore, Table 3 on page 50 contains a couple of questionable
audio/x-alaw-basic is a private media type;
audio/ms-gsm looks like an IETF tree media subtype,
but it has not been registered with the IANA;
audio/x-wav is also a private media type; I guess it should
better be audio/vnd.wave (RFC 2361)
-- although the IANA apparently has lost
records of this media type registration.
Authors comment: In four years of deployment, no one has run into a real problem in the real world. This is not a standards track RFC.