Milt Roselinsky (Milt@Software.com)
Wed, 18 Aug 1999 13:42:24 -0700
There's an additional topic I'd like to see added to the charter.
This is translating a destination phone number to the VPIM
address where messages can be delivered. In other words,
how do you find the mailhost that will receive VPIM messages
for a particular phone number?
There may be work in TBGP that could be leveraged for this, but
that might not be the best approach.
I don't know if anyone has already tackled this, if not, can it be
added to the charter?
Thanks,
Milt
At 02:34 PM 8/19/99 -0400, Glenn Parsons wrote:
>Folks,
>
>This is what I propose as the final charter that we present to our ADs
>for consideration as a working group. I believe I have covered all the
>comments. As I mentioned last week, I would like to close on this by
>Friday the 20th.
>
>Cheers,
>Glenn.
>
>--------
>
>
>Voice Profile for Internet Mail (VPIM)
>======================================
>
> Chair(s):
>
> Glenn Parsons <gparsons@nortelnetworks.com>
>
> Applications Area Director(s):
> Keith Moore <moore+iesg@cs.utk.edu>
> Patrik Fältström <paf@swip.net>
>
> Area Advisor
> Keith Moore <moore+iesg@cs.utk.edu>
>
> Mailing list:
> General Discussion: vpim@lists.neystadt.org
> To Subscribe: send a message to
> majordomo@lists.neystadt.org with
> 'subscribe vpim' as the message body
> Archive: http://www.ema.org/vpimdir/minutes.html
>
>Description of Working Group:
>
>The Voice Profile for Internet Mail (VPIM) Version 2 is
>currently a Proposed Standard (RFC 2421) Applicability
>Statement. It is an application of Internet Mail originally
>intended for sending voice messages between voice messaging
>systems. As such, VPIM imposes several restrictions on the
>message and transport to support the characteristics of
>voice messaging. Many voice mail vendors have implemented
>systems according to RFC 2421 and are in the process of
>deploying these systems around the world. Most vendors have
>completed (or are currently involved in) interoperability
>testing of VPIM products and have posted their results on
>the VPIM website. This working group will promote the
>advancement of VPIM v2 on the standards track.
>
>Several minor problems with VPIM v2 have been identified
>during the development and testing of products. These
>problems can easily be fixed with minor clarifications to
>the protocol. A revised VPIM v2 (and related protocols as
>necessary) will be produced to reflect these clarifications.
>No protocol changes will be introduced in this update.
>
>Though VPIM uses Internet Mail, its restrictions can be
>inconvenient when sending and receiving messages from
>traditional desktop email clients. As a result, there is
>interest in loosening the restrictions of VPIM in a new
>version and make it the voice component of a unified
>messaging protocol suite. This would make it easier for
>desktop clients to send, receive, and forward voice messages
>while maintaining support for the characteristics of a voice
>message.
>
>The primary goal of Version 3 is to support interoperability
>with deployed desktop email clients. A secondary goal is to
>specify interoperability with Version 2. The result is that
>the semantics of a voice or fax message within an email
>message can be interpreted at as many clients as possible.
>
>An initial proposal for VPIM v3 is currently documented in
>several Internet Drafts (see draft-ema-vpimv3-*): VPIM v3
>Goals, VPIM v3 Unified Messaging (Primary Content), VPIM
>Addressing and VPIM v3 Specification. As well, several
>supporting protocol extensions may need to be worked in this
>group or in collaboration with other groups. These are:
>IMAP voice extensions, voice directory profiles, content
>negotiation details for voice and partial non-delivery
>notifications.
>
>The working group will initially focus on agreement of the
>goals and then define a set of protocol documents to address
>the media, addressing, and handling semantics. Finally, VPIM
>v2 - v3 Interworking will be documented separately if
>needed.
>
>Collaboration
>
>The voice mail vendors and several email vendors have been
>meeting in the VPIM work group at the Electronic Messaging
>Association (EMA) for several years. This team produced VPIM
>v1 (RFC 1911) and VPIM v2 (RFC 2421). This group meets
>three times a year in between IETF meetings and is regularly
>attended by core VPIM proponents. As a result, there is
>benefit to using this venue as an interim meeting.
>
>In addition, the work of this group is related to similar
>work by the Internet Fax WG. It is intended that Version 3
>will use at least the Simple Mode of Internet Fax.
>
>As well, other IETF WGs may be interested in proposed voice
>extensions to protocols. There may be value in
>collaborating on some work items.
>
>Goals and Milestones:
>
>VPIM v2
>
>Jul 1999 Issue revised VPIM v2 Internet Draft with minor
> clarifications
>Aug 1999 Document interworking VPIM v2 implementations
>Sep 1999 Issue updated VPIM v2 Internet Draft
>Oct 1999 WG last call on revised VPIM v2 for Draft Standard
>Nov 1999 Submit VPIM v2 to IESG for consideration as a
> Draft Standard RFC
>
>VPIM v3
>
>Mar 1999 Issue initial VPIM v3 Internet Drafts
>Jun 1999 Issue updated drafts of VPIM v3 Goals, VPIM v3
> Specification and related protocol documents as
> Internet Drafts
>Sep 1999 Issue updated Internet Drafts of VPIM addressing
>Sep 1999 Issue updated Internet Drafts of VPIM directory
>Oct 1999 WG last call on VPIM v3 Goals as Informational RFC
>Oct 1999 Issue updated Internet Drafts of VPIM IMAP extensions
>Oct 1999 Issue revised VPIM v3 Specification and relate
> protocol documents as Internet Drafts
>Oct 1999 Issue initial Internet Drafts of VPIM v3 content
> negotiation
>Nov 1999 Submit VPIM v3 Goals to IESG for consideration as
> Informational RFC
>Nov 1999 WG last call on VPIM v3 Specification and related
> protocol documents as Proposed Standards RFCs
>Dec 1999 Submit VPIM v3 et al to IESG for consideration as
> a Proposed Standard
>Dec 1999 WG last call on VPIM IMAP extensions as Standards
> Track RFC
>Jan 2000 Submit VPIM IMAP extensions to IESG for
> consideration as Standards Track RFC
>Jan 2000 WG last call on VPIM addressing as Standards Track RFC
>Jan 2000 WG last call on VPIM directory profile as
> Standards Track RFC
>Feb 2000 Submit VPIM addressing to IESG for consideration as
> Standards Track RFC
>Feb 2000 Submit VPIM directory to IESG for consideration as
> Standards Track RFC
>Feb 2000 WG last call on VPIM v3 content negotiation as
> Proposed Standard RFC
>Mar 2000 Submit VPIM content negotiation to IESG for
> consideration as Proposed Standard RFC
>Mar 2000 Review final work items and close
>
>
>
>
>
This archive was generated by hypermail 2.0b3 on Tue Mar 19 2002 - 01:04:45 IDT