Re: Internet FAX WG meeting summary
"Toyoda, Kiyoshi" <[email protected]>
| Newsgroups | gmane.ietf.fax |
|---|---|
| Message-ID | <[email protected]> |
>>Claudio Allocchio wrote: >> CA asked ALL the editors of current drafts to carefully check their >> documents (and the member of the WG to helpo them cross-checking, too) >> for places where image/tiff and image/tiff-fx split might be involved, >> and provide the needed corrections and updates ASAP. Again the procedures >> for the Implementers guide (i.e. the quickiest possible path) will be >> taken also for these other docments. NF confirms that the IESG will >> define the exact procedure to be folowed. > >I will check them. > draft-ietf-fax-service-v2-05: It refers RFC2301 "File Format for Internet Fax" and RFC 2302 "Tag Image File Format (TIFF)-- image/TIFF: MIME Sub-type Registration". The part which refers two RFCs is below. 2.2.3 Content The data format of the facsimile image is based on the minimum set of TIFF for Facsimile [5], also known as the S profile. Such facsimile data are included in a MIME object by use of the image/TIFF sub-type [12]. Additional rules for the use of TIFF for Facsimile, for the message-based Internet facsimile application, are defined later. I think we don't need to change description above if the two references are draft-ietf-fax-tiff-fx-11 and draft-ietf-fax-tiff-regbis-03. Of course, we should change the RFC number when draft-ietf-fax-tiff-fx-11 and draft-ietf-fax-tiff-regbis-03 become draft standard. DRAFT-IETF-FAX-ESMTP-CONNEG-01: It dose not refer either references. Regards, Kiyoshi Toyoda