Documents: draft-ietf-avt-text-red-05.txt
Reviewer: Elwyn Davies
AD: Alison Mankin
Trigger: IETF tele-chat, 17 March 2005
Review Date: 13 March 2005
Intended status: Proposed Standard

Summary: A trivial MIME type registration request.  I am not qualified to check 
out all the parameter mappings but it seems ready to go, except for a couple of 
nits (although one absolutely needs resolution) and some formatting glitches.

Review:
This should be ready to go except as follows:

Section 3:
3.   IANA Considerations

    One new MIME sub-type is to be registered, as described below:

       MIME media type name: text

       MIME subtype name: RED

-	Is the subtype name (RED) intended to be uppercase?  Every other mime 
(sub)type I know uses lowercase and the document refers to text/red at 
various points in the description.  I have been unable to determine whether 
case is significant in subtype names from a brief reading of the MIME RFCs.


Section 4:
    -  The pt parameter is mapped to an a=3Dfmtp attribute by eliminating
       the parameter name (pt) and changing the commas to slashes.  For
       example, 'pt=3D"101,102"' maps to 'a=3Dfmtp:99 101/102', where =
'99' is
       the payload type of the redundancy frames.  Note that the single
       quote marks (') used in this example is not present in the
       actual message encoding, but is present here only for readability.
       The level of redundancy is shown by the number of elements in the
       payload type list.

-	I think this paragraph has got mangled by the text processing tools used (the 
= may be spurious)... there are a couple of other places where lines have 
overrun and an '=' appears at the end of the previous line.  Run idnits on 
the text to be sure!  Maybe using 99 next to 101/102 doesn't make it terribly 
clear that 99 is a placeholder.

References:
Maybe this document should reference RFC2048 (MIME registrations) as well as 
2045.