Draft Letter To ITU-T meeting from IETF-FAX WG

Folks,

The draft letter is below. ITU-T SG16 meeting is held from Oct 15th.

I will input 4 documents: This letter, RFC 3250, RFC 3302 and RFC 3249.
In order to keep the same specification between RFCs and ITU-T T.37,
three RFCs should be reflected in T.37.

If there are comments, please say by Oct 7th.

Regards,
--
Hiroshi Tamura, Co-chair of IETF-FAX WG
E-mail: [email protected]

----------------------------------------------------------------------

TITLE:	Communication from IETF FAX Working Group

This letter is to notify the current status of IETF FAX Working Group,
with regard to T.37 related issue.

1 TIFF-FX
1.1 image/tiff and image/tiff-fx
In the previos letter to ITU-T, FAX WG already showed that there is
a compatibility issue with regard to the use of image/tiff MIME
content type for Profile J (JBIG), C (Color), L (JBIG color) and
M (MRC) for some TIFF readers. We, therefore, decided to use two MIME
content-types, the current image/tiff for Profile S (MH) and F (MR, MMR)
and a new image/tiff-fx content-type for other Profiles,
when transported by MIME.

Now, two RFCs has come out. One is RFC 3302 which is the document about
image/tiff MIME Sub-type Registration. The other is RFC 3250 which is
the document about image/tiff-fx MIME Sub-type Registration.

According to the RFCs, T.37 should be modified. Both RFCs are inputed
as temporary documents in this meeting.

1.2 Draft Standard process
We are still trying to do for TIFF-FX itself (RFC 2301). An additional
implementation report was requested by AD. We will submit it
within this month. After the review, it will become Draft Standard.

2 Draft Standard process for Simple Mode (RFC 2305)
IESG already approved the document as Draft Standard and it is now
on RFC-Editors' queue, i.e. wating for publication. But, there are a
reference issue. All normative references must be Draft Standard or
Standard in order that the document becomes Draft Standard.
FAX WG will let you know after it becomes Draft Standard.

3 Implementers Guide
The guide has become RFC 3249. It is informational, but there are lots of
useful information for implementation. T.37 Appendix can refer it,
as the letter from ITU-T suggested last year. The RFC is also inputed
as a temporary document in this meeting.