Dan Wing (dwing@cisco.com)
Mon, 27 Aug 2001 17:23:44 -0700
Jason,
We're powerless to unsubscribe you. None
of us are in charge of these mailing lists.
In looking at the list of recipients, I am
guessing you are subscribed to one or more
of the following mailing lists:
vpim@lists.neystadt.org
ietf-fax@imc.org
receipt@cs.utk.edu
To unsubscribe, try sending a message to:
vpn-request@lists.neystadt.org
ietf-fax-request@imc.org
receipt-request@cs.utk.edu
with the word "unsubscribe" in the body of
your message. If that doesn't do it, please
send me email directly (do not do a reply-all)
and I'll attempt to help you unsubscribe.
-d
> -----Original Message-----
> From: Jason McCurry [mailto:jasonm@speakeasy.org]
> Sent: Monday, August 27, 2001 5:16 PM
> To: Dan Wing; Vaudreuil, Greg M (Greg); receipt@cs.utk.edu
> Cc: vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> I'm not sure what you guys are talking about, or even how I got onto this
> list? Can whoever is in charge of this make sure jasonm@speakeasy.org is
> removed from whatever list is making me get these?
>
> Thanks,
>
> Jason McCurry
>
>
> -----Original Message-----
> From: Dan Wing [mailto:dwing@cisco.com]
> Sent: Monday, August 27, 2001 3:20 PM
> To: Vaudreuil, Greg M (Greg); receipt@cs.utk.edu
> Cc: vpim@lists.neystadt.org; ietf-fax@imc.org
> Subject: RE: I-D ACTION:draft-vaudreuil-mdnbis-00.txt
>
>
> Greg,
>
> Thanks for forwarding this.
>
> > The following ID announcement is for a revision to the MDN specification
> in
> > preparation for Draft Standard. Please note: Many seemingly
> unimplemented
> > dispositions and all disposition modifiers have been removed.
>
> The ABNF in section 3.2.6 seems to still list the disposition modifiers.
>
> > If someone
> > can name TWO interoperable implementations of any of the deleted
> > dispositions or disposition modifiers, I will be happy to add them
> > back into the document.
> >
> > 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.
> >
> > This document also adds an additional section for gateway advice. The
> > previous document was silent about what to do when gatewaying a MDN
> request
> > into a foreign network. Given that most email networks do not have a
> > separate disposition-notification-to: recipient, that was a bit of an
> > oversight.
>
> Section 8.3 has a sentence which begins:
>
> In other most email systems,
>
> which should be corrected.
>
> > Please review and send comments. It is my hope that we can quickly
> advance
> > this to Draft Standard.
>
> Section 3.2.2 and the 'Status of this memo' section both seem to be missing
> some runoff commands to format the text correctly.
>
> -d
>
>
>
This archive was generated by hypermail 2.0b3 on Tue Aug 28 2001 - 03:24:31 IDT