Internet-Drafts@ietf.org Thu, 10 February 2000 12:00 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19089; Thu, 10 Feb 2000 07:00:36 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id GAA08410 for ietf-123-outbound.10@ietf.org; Thu, 10 Feb 2000 06:55:01 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id GAA08287 for <all-ietf@loki.ietf.org>; Thu, 10 Feb 2000 06:45:03 -0500 (EST)
Received: from oass09.cstelecom.cie-signaux.fr (mailhub.cie-signaux.fr [194.2.40.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18753 for <all-ietf@loki.ietf.org>; Thu, 10 Feb 2000 06:45:01 -0500 (EST)
Received: from hermes2.fty.cstelecom.com (hermes2.cstelecom.cie-signaux.fr [172.17.68.52]) by oass09.cstelecom.cie-signaux.fr with ESMTP id MAA27059 for <all-ietf@loki.ietf.org>; Thu, 10 Feb 2000 12:39:26 +0100 (MET)
From: Internet-Drafts@ietf.org
Received: from gl17.fty.cstelecom.com ([172.17.68.34]) by hermes2.fty.cstelecom.com (Netscape Messaging Server 3.62) with ESMTP id 410; Thu, 10 Feb 2000 12:43:53 +0100
Received: from cc25.fty (cc25 [172.17.68.42]) by gl17.fty.cstelecom.com (8.8.8+Sun/jtpda-5.3) with SMTP id MAA17228 ; Thu, 10 Feb 2000 12:40:07 +0100 (MET)
Received: by cc25.fty (SMI-8.6/SMI-SVR4) id MAA23462; Thu, 10 Feb 2000 12:40:07 +0100
Date: Thu, 10 Feb 2000 12:40:07 +0100
Message-Id: <200002101140.MAA23462@cc25.fty>
Apparently-To: 06:31:01@ietf.org
Apparently-To: 08@ietf.org
Apparently-To: Date:@ietf.org
Apparently-To: rem-conf@es.net
Apparently-To: 200002081131.GAA13434@ietf.org
Apparently-To: 06:31:02@ietf.org
Apparently-To: all-ietf@loki.ietf.org
Apparently-To: -0500@ietf.org
Apparently-To: 06:45:01@ietf.org
Apparently-To: 2000@ietf.org
Apparently-To: Feb@ietf.org
Apparently-To: 8@ietf.org
Apparently-To: Tue@ietf.org
Apparently-To: ietf-123-outbound.02@ietf.org;
Apparently-To: for@ietf.org
Apparently-To: a.burgain@CSTELECOM.COM
Apparently-To: ;;;;;;@ietf.org;;;;;;;;;;
Apparently-To: IETF-Announce:@ietf.org
--NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : RTP Payload for Text Conversation Author(s) : G. Hellstrom Filename : draft-ietf-avt-rtp-text-04.txt Pages : 9 Date : 07-Feb-00 This memo describes how to carry text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140 [1]. Text conversation is used alone or in connection to other conversational facilities such as video and voice, to form multimedia conversation services. This RTP payload description contains an optional possibility to include redundant text from already transmitted packets in order to reduce the risk of text loss caused by packet loss. The redundancy coding follows RFC 2198. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-text-04.txt Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-avt-rtp-text-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-avt-rtp-text-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <20000207125401.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-avt-rtp-text-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-avt-rtp-text-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20000207125401.I-D@ietf.org> --OtherAccess-- --NextPart--