Re: Delivery Notifications in SMTP

Steve Kille <S.Kille@isode.com> Mon, 04 October 1993 16:40 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01774; 4 Oct 93 12:40 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01770; 4 Oct 93 12:40 EDT
Received: from mhs-relay.cs.wisc.edu by CNRI.Reston.VA.US id aa21893; 4 Oct 93 12:40 EDT
Received: from cs.wisc.edu by mhs-relay.cs.wisc.edu with SMTP (PP) id <19245-0@mhs-relay.cs.wisc.edu>; Mon, 4 Oct 1993 11:06:03 +0000
Received: from haig.cs.ucl.ac.uk by cs.wisc.edu; Mon, 4 Oct 93 11:05:53 -0500
Received: from glengoyne.isode.com by haig.cs.ucl.ac.uk with Internet SMTP id <g.04280-0@haig.cs.ucl.ac.uk>; Mon, 4 Oct 1993 17:05:35 +0100
To: "Erik Huizer (SURFnet BV)" <Erik.Huizer@surfnet.nl>
Cc: ietf-osi-x400ops@cs.wisc.edu, David Crocker <dcrocker@mordor.stanford.edu>, John C Klensin <KLENSIN@infoods.mit.edu>
Subject: Re: Delivery Notifications in SMTP
Phone: +44-81-332-9091
In-Reply-To: Your message of Wed, 29 Sep 1993 12:42:01 +0100. <9309291142.AA01844@survival.surfnet.nl>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 04 Oct 1993 17:05:22 +0100
Message-Id: <17539.749750722@glengoyne.isode.com>
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Steve Kille <S.Kille@isode.com>

Erik,

From a user perspective, I sympathise with what you are trying to do
here.  However,  I am not convinced that it is right.

The DR mapping in 1327 has two objectives to achieve.  

1) Present the user information to the end RFC 822 user.

2) Ensure that key diagnostic information is not lost.   Throwing away
information in the mapping is very very bad news.   Some fields are
often so much cruft, but sometimes the information is key to
disgnosing a problem.

987 got this badly wrong, a we found out when we started to deploy
it.  1148 chooses a copromise.  There is a user-oriented description
of the problem at the front, followed by a fully mapped and parseable
representation of the DR.  I had hoped that 822 UAs in the mixed
environment would be adapted to strip out the machine oriented format
(it is triv to do this, and will be even easier in the next update
which will use MIME to separate the bits), so that the user would only
see the user-oreinted bit, but the machine oriented bit would be preserved.


I think that unless the new 822 format is designed with gatewaying in
mind, it is unlikely that an upgraded 1327 would be able to use it
effectively.



RNs (IPNs) seem to be a non-issue in 822.   This is primarily because
you can't request them.  I believe that there are some environments
where they will be very valuable.   Lets not prejudge them from an
environment which cannot properly support them.



Steve