idnits 2.16.02
/tmp/draft-parsons-itu-t38-reg-00.txt:
Skipping this file; it looks like a tombstone file to me.
--------------------------------------------------------------------------------
1 A new Request for Comments is now available in online RFC libraries.
3 RFC 3362
5 Title: Real-time Facsimile (T.38) - image/t38 MIME
6 Sub-type Registration
7 Author(s): G. Parsons
8 Status: Standards Track
9 Date: August 2002
10 Mailbox: gparsons@nortelnetworks.com
11 Pages: 5
12 Characters: 8301
13 Updates/Obsoletes/SeeAlso: None
15 I-D Tag: draft-parsons-itu-t38-reg-00.txt
17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3362.txt
19 This document describes the registration of the MIME sub-type
20 image/t38. The encoding is defined by ITU Recommendation T.38 and is
21 intended for use as an Session Description Protocol (SDP) media
22 descriptor.
24 This is now a Proposed Standard Protocol.
26 This document specifies an Internet standards track protocol for
27 the Internet community, and requests discussion and suggestions
28 for improvements. Please refer to the current edition of the
29 "Internet Official Protocol Standards" (STD 1) for the
30 standardization state and status of this protocol. Distribution
31 of this memo is unlimited.
33 This announcement is sent to the IETF list and the RFC-DIST list.
34 Requests to be added to or deleted from the IETF distribution list
35 should be sent to IETF-REQUEST@IETF.ORG. Requests to be
36 added to or deleted from the RFC-DIST distribution list should
37 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
39 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
40 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
41 help: ways_to_get_rfcs. For example:
43 To: rfc-info@RFC-EDITOR.ORG
44 Subject: getting rfcs
46 help: ways_to_get_rfcs
48 Requests for special distribution should be addressed to either the
49 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless
50 specifically noted otherwise on the RFC itself, all RFCs are for
51 unlimited distribution.echo
52 Submissions for Requests for Comments should be sent to
53 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC
54 Authors, for further information.