RFC 3362 on MIME Sub-type image/t38
rfc-editor@rfc-editor.org Wed, 04 September 2002 00:26 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18210; Tue, 3 Sep 2002 20:26:10 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA06048 for ietf-123-outbound.10@ietf.org; Tue, 3 Sep 2002 20:25:01 -0400 (EDT)
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 UAA05873 for <all-ietf@loki.ietf.org>; Tue, 3 Sep 2002 20:00:24 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA17639 for <all-ietf@ietf.org>; Tue, 3 Sep 2002 19:58:48 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g8400MD04602; Tue, 3 Sep 2002 17:00:22 -0700 (PDT)
Message-Id: <200209040000.g8400MD04602@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3362 on MIME Sub-type image/t38
Cc: rfc-editor@rfc-editor.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 03 Sep 2002 17:00:22 -0700
Sender: rfc-ed@ISI.EDU
A new Request for Comments is now available in online RFC libraries. RFC 3362 Title: Real-time Facsimile (T.38) - image/t38 MIME Sub-type Registration Author(s): G. Parsons Status: Standards Track Date: August 2002 Mailbox: gparsons@nortelnetworks.com Pages: 5 Characters: 8301 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-parsons-itu-t38-reg-00.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3362.txt This document describes the registration of the MIME sub-type image/t38. The encoding is defined by ITU Recommendation T.38 and is intended for use as an Session Description Protocol (SDP) media descriptor. This is now a Proposed 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@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@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@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@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.
- RFC 3362 on MIME Sub-type image/t38 rfc-editor