FW: RFC 3802 on Toll Quality Voice - 32 kbit/s Adaptive Different

[simao.campos at ITU.INT]

Dear colleagues,

For your information. (A reminder that the packetization that the
I.362-compliant packetization has not yet been progressed...)

Best regards,
Simao Campos

-----Original Message-----
From: rfc-editor at rfc-editor.org [mailto:rfc-editor at rfc-editor.org] 
Sent: Thursday, June 24, 2004 23:24
Cc: vpim at lists.neystadt.org; rfc-editor at rfc-editor.org
Subject: RFC 3802 on Toll Quality Voice - 32 kbit/s Adaptive Differential
Pulse Code Modulation (ADPCM) MIME Sub-type Registration



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


        RFC 3802

        Title:      Toll Quality Voice - 32 kbit/s Adaptive
                    Differential Pulse Code Modulation (ADPCM) MIME
                    Sub-type Registration
        Author(s):  G. Vaudreuil, G. Parsons
        Status:     Standards Track
        Date:       June 2004
        Mailbox:    gregv at ieee.org, gparsons at nortelnetworks.com
        Pages:      7
        Characters: 11686
        Obsoletes:  2422

        I-D Tag:    draft-ietf-vpim-vpimv2r2-32k-03.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3802.txt


This document describes the registration of the MIME sub-type audio/32KADPCM
Adaptive Differential Pulse Code Modulation for toll quality audio.  This
audio encoding is defined by the ITU-T in Recommendation G.726.

This document is a product of the Voice Profile for Internet Mail Working
Group of the IETF.

This is now a Draft Standard Protocol.

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.echo 
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

...

Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.