[rfc-dist] RFC 4393 on MIME Type Registrations for 3GPP2 Multimedia Files

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Mar 17 15:27:56 PST 2006


A new Request for Comments is now available in online RFC libraries.

        
        RFC 4393

        Title:      MIME Type Registrations for 3GPP2 
                    Multimedia Files 
        Author:     H. Garudadri
        Status:     Standards Track
        Date:       March 2006
        Mailbox:    hgarudadri at qualcomm.com
        Pages:      7
        Characters: 14369
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-garudadri-avt-3gpp2-mime-02.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4393.txt

This document serves to register and document the standard MIME
types associated with the 3GPP2 multimedia file format, which is
part of the family based on the ISO Media File Format.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 
unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list