ITU "full mode" goals and schedule

[Graham Klyne <GK@xxxxxxxxxxxxxx>]

I'm cross-posting this because of the reference to "capabilities" in fax.

Specifically, should we be aiming to defining a MIME type to carry
capability information?

#g


>Date: Wed, 17 Jun 1998 14:35:37 +0200
>To: ietf-fax@xxxxxxx
>From: Dave Crocker <dcrocker@xxxxxxxxxxxxxxx>
>Subject: ITU "full mode" goals and schedule
>Cc: Keith Moore <moore@xxxxxxxxxx>, Patrik Fältström <paf@xxxxxxxxxxx>,
>        jrafferty@xxxxxxxxxxxxxxxx
>Sender: owner-ietf-fax@xxxxxxx
>
>Greetings from truly beautiful Geneva,
>
>This is an entirely unofficial -- that is, entirely personal -- note.  An
>"official" communique' is going through the approval cycle.  James Rafferty
>is also sending his own unofficial note, so we will benefit from
>verification/correction of my own comments.
>
>ITU SG8/Q.4 T.37 enhancement efforts, to consider embellishing the simple
>mode produced by the IETF, so as to bring the level of service essentially
>up to full equivalence of telephone-based G3 fax, reviewed the work being
>done by the IETF.  
>
>I believe there are 3 important details to come out of the discussions:
>
>1.  Full mode (probably best referred to as the EIFax, from IETF
>perspective) must support an appropriate confirmation mechanism and an
>ability for senders to obtain information about the capabilities of
receivers.
>
>2.  It appears reasonable and appropriate to use DSN for the confirmation
>mechanism, but with a specific enhancement
>
>3.  The formal ITU schedule makes it extremely important to try to complete
>the IETF work (through the IESG) no later than the end of January, 1999.
>
>
>Capabilities
>------------
>
>There wasn't any detailed discussion on this, due to time constraints.
>Still, the requirement for capabilities was (pardon the pun) confirmed.  My
>own belief is that the IETF working group should define a MIME type for the
>data, or specify a profile for an existing MIME type, perhaps such as
>vcard.  My guess is that we do not need to specify the means of conveying
>that data, since MIME data can be transported in many ways, and it is the
>transport mechanism which seems to be getting the most debate.
>
>

[Rest of message chopped:  see ietf-fax list for full message]


------------
Graham Klyne