home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!sdd.hp.com!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
- From: ned@sigurd.innosoft.com (Ned Freed)
- Newsgroups: vmsnet.mail.pmdf
- Subject: RE: two minor points
- Message-ID: <01GNI0QOURY6984M9M@SIGURD.INNOSOFT.COM>
- Date: 12 Aug 92 23:32:02 GMT
- Organization: The Internet
- Lines: 19
- Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
- Resent-Date: 12 Aug 1992 16:32:02 -0700 (PDT)
- Resent-From: epmdf@YMIR.CLAREMONT.EDU
- Errors-To: epmdf@YMIR.CLAREMONT.EDU
- Resent-Message-ID: <01GNI1AMGCMA94E1K3@YMIR.CLAREMONT.EDU>
- X-Vms-To: IN%"D.Nash@utexas.edu"
- X-Vms-Cc: IPMDF
- Mime-Version: 1.0
- Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
- Content-Transfer-Encoding: 7BIT
-
- One additional note on all this...
-
- The precise format of returned messages is still very much up in the air.
- Modulo MIME the format is pretty well set; it is fairly obvious what you
- need and MIME addresses it very nicely.
-
- What is still missing is the precise structure of the first part of the
- message. That is, there needs to be a standardized format for error messages
- that is both human readable (i.e. explains clearly what went wrong) as well
- as machine readable (a program can deal with these things). This format has
- not been defined yet, but there is work underway to do so.
-
- Of course the act of retrofitting this into PMDF is much less than the work
- needed to get things to be in MIME format. If all goes well the standard
- format for the error report will also make gatewaying to X.400 very
- easy, although X.400's inability to handle return-with-content in many
- places may make such conversion rather problematic.
-
- Ned
-