Re: Status of and comments on the draft-ietf-fax-tiff-fx-11.txt document

Ned,

Thanks for your advice.

As a co-chair, I have a comment for RFC 3302.

> whole moving to draft situation a bit tricky. My proposed plan is to simply ask
> for RFC 3302 to move to draft as-is based on the current TIFF interop report.
> (Note that RFC 3302 was approved as proposed rather than as a BCP so this is a
> necessary step.) However, RFC 3250 cannot advance as-is since it contains a
> normative reference to RFC 2301. I therefore suggest creating a new
> Internet-Draft containing the text of RFC 2301 with the only change being to
> refer to draft-ietf-fax-tiff-fx-11.txt rather than to RFC 2301. The
> [TIFF-FX-REG] reference then needs to change to refer to this new draft.

Attached were the request for IESG considerdation
for image/tiff MIME sub-type registration from our WG (2nd one).

We requestd it as BCP. I am a little surprised that
RFC 3302 was approved as Proposed Standard.
Unfortunately, nobody found it even within 48 hours check
from RFC-Editor.

Anyway, my questions are,
why is the status to changed to proposed from BCP?
and
is your intension that RFC 3302 should move to Draft Standard
and BCP is not appropriate status?

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