FW: [AVT] RFC 4040 on RTP Payload Format for a 64 kbit/s TransparentCall

[simao.campos at ITU.INT]

Dear experts,

FYI.

Best regards,
Simao

-----Original Message-----
From: avt-bounces at ietf.org [mailto:avt-bounces at ietf.org] On Behalf Of
rfc-editor at rfc-editor.org
Sent: 21 April 2005 01:05
To: ietf-announce at ietf.org
Cc: avt at ietf.org; rfc-editor at rfc-editor.org
Subject: [AVT] RFC 4040 on RTP Payload Format for a 64 kbit/s
TransparentCall


--NextPart


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


        RFC 4040

        Title:      RTP Payload Format for a 64 kbit/s
                    Transparent Call
        Author(s):  R. Kreuter
        Status:     Standards Track
        Date:       April 2005
        Mailbox:    ruediger.kreuter at siemens.com
        Pages:      8
        Characters: 15363
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-avt-rtp-clearmode-05.txt

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


This document describes how to carry 64 kbit/s channel data
transparently in RTP packets, using a pseudo-codec called "Clearmode".
It also serves as registration for a related MIME type called
"audio/clearmode".

"Clearmode" is a basic feature of VoIP Media Gateways.

This document is a product of the Audio/Video Transport Working Group of
the IETF.

This is now a Proposed Standard Protocol.

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

..

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

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type:  Message/External-body;
        access-type="mail-server";
        server="RFC-INFO at RFC-EDITOR.ORG"

Content-Type: text/plain
Content-ID: <050420160230.RFC at RFC-EDITOR.ORG>

RETRIEVE: rfc
DOC-ID: rfc4040

--OtherAccess
Content-Type:   Message/External-body;
        name="rfc4040.txt";
        site="ftp.isi.edu";
        access-type="anon-ftp";
        directory="in-notes"

Content-Type: text/plain
Content-ID: <050420160230.RFC at RFC-EDITOR.ORG>

--OtherAccess--
--NextPart--

_______________________________________________
Audio/Video Transport Working Group
avt at ietf.org
https://www1.ietf.org/mailman/listinfo/avt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 3554 bytes
Desc: not available
URL: <https://lists.packetizer.com/pipermail/sg16-avd/attachments/20050422/add9933c/attachment-0003.bin>