idnits 2.17.1 draft-ietf-fax-tiff-regbis-05.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 3302 5 Title: Tag Image File Format (TIFF) - image/tiff MIME 6 Sub-type Registration 7 Author(s): G. Parsons, J. Rafferty 8 Status: Standards Track 9 Date: September 2002 10 Mailbox: gparsons@nortelnetworks.com, jraff@brooktrout.com 11 Pages: 8 12 Characters: 15183 13 Obsoletes: 2302 15 I-D Tag: draft-ietf-fax-tiff-regbis-05.txt 17 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3302.txt 19 This document describes the registration of the MIME sub-type 20 image/tiff. This document refines an earlier sub-type registration in 21 RFC 1528. 23 This document obsoletes RFC 2302. 25 This document is a product of the Internet Fax Working Group of the 26 IETF. 28 This is now a Proposed Standard Protocol. 30 This document specifies an Internet standards track protocol for 31 the Internet community, and requests discussion and suggestions 32 for improvements. Please refer to the current edition of the 33 "Internet Official Protocol Standards" (STD 1) for the 34 standardization state and status of this protocol. Distribution 35 of this memo is unlimited. 37 This announcement is sent to the IETF list and the RFC-DIST list. 38 Requests to be added to or deleted from the IETF distribution list 39 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 40 added to or deleted from the RFC-DIST distribution list should 41 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 43 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 44 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 45 help: ways_to_get_rfcs. For example: 47 To: rfc-info@RFC-EDITOR.ORG 48 Subject: getting rfcs 50 help: ways_to_get_rfcs 52 Requests for special distribution should be addressed to either the 53 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 54 specifically noted otherwise on the RFC itself, all RFCs are for 55 unlimited distribution.echo 56 Submissions for Requests for Comments should be sent to 57 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 58 Authors, for further information.