Then how would you propose to distinguish this from SMTP DSN/MDN receipt
..which we know is a problem in many cases?
> >Proposed solutions:
> >
> >Proposed solutions should not impose undue burdens on implementers in order
> >that the protocol should be available on a wide variety of devices and
>systems.
> >
> >The group will take note of other areas within the IETF that may have
> >direct bearing on reliable document delivery.
> >
> >Relevant areas include:
> >
> >- Security, Authentication and Encryption (TLS, etc)
> >- Sender Identification (vCard)
> >- RFC 2301 File Formats
> >- Digital Signatures and Certificates
>
>Also?
>
>- RESCAP
>- IMPP
>- ENUM
Yes of course.....
> >Goals and Milestones:
> >
> >Feb 2000 : Submit Internet Draft of Goals and Objectives for Quality
> >Document Distribution or submit addendum to RFC 2542 (Goals and Terminology
> >for Internet Fax)
>
>Haven't we already done this? Do you mean "Submit ... for publication as
>informational RFC?
Yes Publication....
Will be corrected ASAP.
> >June 2000 : Submit Internet Draft for Quality Document Distribution Gateway
> >Services (Based on Selected Protocols)
>
>How long is a piece of string? Gateway to *what*?
:-) Gateway to other Messaging Services??? or drop entirely as "out of
scope".. just make sure the QUALDOCS "protocol'" can carry sufficient data
for gateway functions ???
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey
Shockey Consulting LLC
8045 Big Bend Blvd. Suite 110
St. Louis, MO 63119
Voice 314.918.9020
eFAX Fax to EMail 815.333.1237 (Preferred for Fax)
INTERNET Mail & IFAX : rshockey@ix.netcom.com
GSTN Fax 314.918.9015
MediaGate iPost VoiceMail and Fax 800.260.4464
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<