Re: short notes from the FAX meeting

Hallo Claudio,

Thanks for your summary.
I can use most of them as it is, for the formal report.

Comments below.

> Tamura0san reported that the following documents are already in the
> RFC editor's queue:
> 
> - draft-ietf-fax-implementers-guide-08.txt
> - draft-ietf-fax-content-negotiation-05.txt
> - draft-ietf-fax-tiff-regbis-05.txt
> - draft-ietf-fax-tiff-fx-reg-01.txt
> 
> and assured the WG that the chairs are taking action with the RFC Editor
> in order to have the RFC number assigned ASAP (i.e. prior to publication)
> to the TIFF-FX/TIFF couple of documents. It is needed for reference in
> oter documents, and by the ITU, too.

I already contacted RFC editors and IANA administrators
They are doing now.

Regarding content-negotiaion I-D, sooner or later, it will be published.

> Following, Tamura-san presented the list of documents whose IETF last call
> was completed without significative comments:
> 
> - draft-ietf-fax-gateway-protocol-08.txt
> - draft-ietf-fax-gateway-options-05.txt
> - draft-ietf-fax-service-v2-05.txt
> 
> These ones refer to DSN (RFC1894 update) and to TIFF-FX
> (draft-ietf-fax-tiff-fx-11.txt). Greg Vaudreuil reported about the status
> of DSN: after IANA questions were answered in April, and an extended
> implementation report submitted in early June, the document is
> currently on IESG table, without any apparent outstanding issue. The
> AD will check its status, too (see slides).

We confirmed, even if the targeted I-D refers other I-Ds,
it may finish IETF Last Call and move to RFC-editors' queue.
In that case, it will be published as RFC after all the reference
I-Ds become RFC. In fact, service-v2-05 I-Ds will finish IETF Last Call
sooner or later, while it refers DSN and TIFF-FX.

> On the IESG queue (Area Director review stage) we also have
> draft-ietf-fax-timely-delivery-05.txt. There were no comments and
> modification since the last meetings, thus we just wait for the AD review
> and for the reference to draft-vaudreuil-1983ext-01.txt to be solved. The
> latter status was also updated by Greg: very similar situation than DNS,
> no outstanding issues, and waiting for AD review before going to the IESG
> table.

Regarding draft-vaudreuil-1983ext-01, it expired last month.
After -02 is issued, FAX WG will do WG Last Call.

> After more that 45 minutes of debate we moved to the next topic, FFPIM.
> Dave reported the the newest version of the document contained some minor
> edits (upon suggestions from Dan Wing), and asked to those presents some
> questions:
> 
>  - Use of ESMTP options as MAY or SHOULD?
>  - FPIM conformance require RFC2305 and RFC2532 conformance?

I Already commented in another mail. Yes, requirement is our conclusion.

--
Hiroshi Tamura, co-chair of IETF-FAX WG
[email protected]