FAX WG status

Hiroshi Tamura <[email protected]>
Newsgroups gmane.ietf.fax
Message-ID <[email protected]>
Folks,

We have a few remaing things to do. I comment them below,
according to the order of the SLC minutes.
I was not at the SLC meeting. So, if there are mistakes
or something, please let us know.
Also, any comments are appreciated.

1 Service (draft-ietf-fax-service-v2-05.txt)

We already have done for WG Last Call and IESG request.
There are few differences from the previous version.
Not technical, just trivial things.
No action is necessary. Only reference issue.

2 Content Negotiation (draft-ietf-fax-content-negotiation-05.txt)

The IETF last call finished. It is in RFC-editors' queue.
No action is necessary.

3 Timely Delivery (draft-ietf-fax-timely-delivery-05.txt)

The WG last call finished.
Claudio or I will request IETF last call to the IESG.

4 Fax Gateway (draft-ietf-fax-gateway-protocol-06.txt)
              (draft-ietf-fax-gateway-options-04.txt)

The WG last call finished. Last year I requested IETF last call.
It is in Ned's queue. After his review, we may do action.

5 FFPIM (draft-ietf-fax-ffpim-01.txt)

After Dave submits the new version, we can do WG last call.
The content has no problems, I think. We wait fot it.

6 ESMTP-CONNEG (draft-ietf-fax-esmtp-conneg-01.txt)

There was modification from the previous version. But, according to -01,
there seems to be no problems. If you agree to it, we can do WG last call.
Claudio or I will do it soon. 

7 Terminal mode issue (draft-maeda-faxwg-terminal-mode-goals-01.txt)
                      (draft-maeda-faxwg-terminal-mode-protocol-01.txt)
                      (draft-maeda-faxwg-fax-processing-status-01.txt)

We agree to the dropping from our milestone. This is the final notice.
If anything, please say it. Unless there are lots of support,
we should drop them.

8 TIFF-FX extension (draft-ietf-fax-tiff-fx-extension-1-01.txt)
                    (darft-mcintyre-feature-schema-extension1-00.txt)

Until the TIFF-FX itself is solved, there is no action.

9 Addressing issue (draft-allocchio-gstn-01.txt)

Claudio will submit the new version. We wait for it.

10 ITU-T

In the next month, the meeting is held. I will prepare the letter,
according to the result of SLC meeting.

11 TIFF-FX (draft-ietf-fax-tiff-fx-11.txt)

The difference is the description about the use of two content-types:
image/tiff and image/tiff-fx. There are no problems.
We should do WG Last Call as recycle ***Proposed Standard*** at first,
according to the result of the SLC meeting.

Claudio and Lloyd, Am I right?

12 TIFF registration (draft-ietf-fax-tiff-regbis-04.txt)

It is corrected for Magic Number issue. We can do WG last call as BCP.
Claudio or I will do it soon. 

13 TIFF-FX registration (draft-ietf-fax-tiff-fx-reg-01.txt)

It seems that there are no problems. We can do WG last call as BCP.
Claudio or I will do it soon. 
Also, the interoperability test will be necessary for Draft Standard.

14 Impl. Guide (draft-ietf-fax-implementers-guide.08.txt)

The content-type issue is reflected in it. The IETF Last Call is finished.
But, there is only one reference issue on draft-ietf-fax-tiff-fx-reg-01.txt.
So, I think the two I-D should be published at the same time,,,.
Is it true?

.........

BTW, Minneapolis meeting is coming. I think it is better
to have our meeting for the status confirmation,
although there are few things to discuss.

Claudio, what do you think about it?

I have been very busy these days. Please do not expect my early response.

Regards,
--
Hiroshi Tamura, Ricoh Company, LTD.
E-mail: [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.