RE: [VPIM] Re: draft-ema-vpim-simpleV3-01.txt


Eric.Burger@centigram.com
Thu, 23 Mar 2000 18:13:41 -0800


I agree that a separate document for how IVM touches the Internet
infrastructure is overkill. However, overspecifying is overkill, as well.

The description of the suggested end-to-end scenario belongs in a Best
Practices document, or at least as a Note in this document. My rationale is
that the format for IVM is independent of transport. This issue is larger
than saying we should include WebDAV, too. If we include WebDAV, is there
any reason not to include POP3? I can think of lots of reasons not to
publish POP3 for retrieval. However, IVM will still work as advertised
even if you (have the time and) download your mailbox using POP3.

How about we say something like "IVM messages use the Internet mail
infrastructure for delivery to the far-end system." Today, that probably
means ESMTP and IMAP4. Who knows (or cares) what it will be in the future,
so long as the future system meets the IVM profile requirements?

I'm not proposing that we publish an IVM XYZZY profile. Let's take the
case of an IVM MDN/DSN profile. We don't need one. However, if MDN
doesn't meet IVM's needs, we will extend it (PNDN). This does make sense
as (1) PNDN has use beyond IVM and (2) if I'm a MHS developer, and I want
to make sure my UA conforms to IETF standards, it's easier to look for
delivery notification RFC's than it is to go through every flavor of VPIM,
IVM, ietf-fax, etc RFC's.

This is the same argument for streaming IMAP: it's not part of IVM IMAP.
However, IVM IMAP can drive it.

From: "Glenn Parsons" <gparsons@nortelnetworks.com> on 03/23/2000 01:00 PM
      GMT
[snip]
My intent was to cover an end-to-end scenario in the profile. To me IMAP
was the obvious choice, but I presume we could include something like
Webdav
as well.

Eric's point is should we include the client server part. I would suggest
yes, unless this becomes so big that we have to split it up. So, I don't
think it is necessary to have a separate document for:
* IVM MIME profile
* IVM ESMTP profile
* IVM MDN/DSN profile
* IVM IMAP profile
* IVM LDAP/DNS profile
* etc.
[snip]



This archive was generated by hypermail 2.0b3 on Fri Mar 24 2000 - 05:10:25 IDT