Greg (gregv@lucent.com)
Tue, 28 Aug 2001 09:03:19 -0600
Are there any implementations of the error, warning, or failure fields? I
have not personally seen any or heard of any. Unless someone can identify
two or more implementations of these fields, I will delete them.
These fields are distinct from the disposition modifiers discussed in the
attached message.
Note also that the intent of these fields is to provide additional textual
description of the MDN exception case. It seems this purpose can be met by
supplying X- extension fields or text in the first part of the
multipart/report structure.
Greg V.
-----Original Message-----
From: Tony Hansen [mailto:tony@att.com]
Sent: Monday, August 27, 2001 9:24 PM
To: McIntyre, Lloyd
Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
Subject: Re: [VPIM] RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
Absolutely. If there ARE two (or more) implementations of anything we
removed, we'll put them back in to the updated MDN document.
So, just let us know of the implementations.
Tony Hansen
tony@att.com
"McIntyre, Lloyd" wrote:
>
> My understanding is that the "dispatched" feature may be retained if
> information can be provided to verify that there are interoperable
> implementations.
> Tamura-san is it possible to have two or more manufacturers document
> interoperability of sending and receiving MDN with the dispatched feature?
>
> Lloyd
>
> > -----Original Message-----
> > From: Dan Wing [mailto:dwing@cisco.com]
> > Sent: Monday, August 27, 2001 4:22 PM
> > To: Hiroshi Tamura; gregv@lucent.com
> > Cc: receipt@cs.utk.edu; vpim@lists.neystadt.org; ietf-fax@imc.org
> > Subject: RE: FW: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
> >
> >
> >
> > > > Note that the requirements for draft standard are explicit that
> > > all features
> > > > and options need to have at least two, interoperable
> > implementations. If
> > > > they are still useful, the unimplemented dispositions
> > deleted from this
> > > > document may be standardized at a later date as an MDN extension.
> > >
> > > I do not read all, but I say,
> > >
> > > Some Ifax devices already use:
> > > "dispatched" or "processed" without modifiers
> > > when succesfully decoding the received TIFF-FX file
> > > "processed/error" in the case of the failure.
> >
> > Those devices will remain compliant with the Proposed
> > Standard RFC2298,
> > but won't be compliant with the Draft Standard that Greg is authoring.
> >
> >
> > As soon as Greg's document becomes an RFC, I'll ask our development
> > group here in Cisco to bring our implementation in line with his
> > new Draft Standard.
> >
> > -d
> >
> ----------------------------------------------------------
> This message was sent to you, since you are subscribed to
> > vpim@lists.neystadt.org. You can manage your subscription at
> http://www.neystadt.org/cgi-bin/majordomo
----------------------------------------------------------
This message was sent to you, since you are subscribed to
vpim@lists.neystadt.org. You can manage your subscription at
http://www.neystadt.org/cgi-bin/majordomo
This archive was generated by hypermail 2.0b3 on Tue Aug 28 2001 - 18:03:38 IDT