VPIM BOF

1
http//www.ema.org/vpim
Mailing list vpim_at_lists.neystadt.org To
subscribe send a message to majordomo_at_
lists.neystadt.org with 'subscribe VPIM' as
the body
2
Agenda

• 1300 - Welcome Agenda Bashing
• 1305 - Charter Chair discussion (15 min)
• 1320 - VPIM v2 (20 min)
• draft-ema-vpim-vpimv2r2-02.txt - Glenn Parsons
• 1340 - VPIM Directory (15 min)
• draft-ema-vpimdir-schema-01.txt - Anne Brown
• draft-brown-e164-01.txt

3
Agenda (contd)

• 1355 - VPIM Desktop (60 min)
• Goals - Laile Di Silvestro
• draft-ema-vpimv3-goals-00.txt
• Core - Stuart McCrae
• draft-ema-vpim-voicemsg-00.txt
• Primary Content - Glenn Parsons
• Partial Non-Delivery - Eric Burger
• Associated
• draft-ema-vpim-wav-00.txt
• draft-ema-vpim-msgsm-00.txt
• draft-ema-vpim-address-00.txt
• draft-ema-vpim-imap-01.txt
• 1455 - Wrap up Next Meeting (5 min)
• 1500 - Close

4
WG Status

• Proposed Charter
• Approved by mailing list and approved by IESG
• WG Chair
• ADs recommend having a non-partisan chair
• WG Approval
• Awaiting resolution of chair

5
VPIM v2 Status

• Approved by IETF as a Proposed Standard in
  September 1998
• Next steps
• Document interoperability
• Inter vendor testing
• Fix specification
• Clarify ambiguities in VPIM v2
• Reissue
• Propose progression to Draft Standard

6
VPIM v2 Progression to Draft

• Requirements
• 6 months since publication
• multiple (at least 2) interworking
  implementations
• specification clarified as required
• all features implemented
• all normative references must be Draft Standard
• To do
• determine status of references
• review revised clarification proposal
• report on implementations

7
VPIM v2 References

• Standard - SMTP, MAIL, DNS, ...
• Draft Standard - Pipelining, MIME, ...
• Proposed Standard
• Content duration, multipart/voice-message,
  audio/32kadpcm
• image/tiff
• vCard, text/directory
• DSN, MDN, Enhanced Status Codes
• Experimental - Binary
• Informational - TIFF-F
• ITU-T Standard - E.164, G.726

8
VPIM v2 Clarifications

• Clarified prose using send and receive rules
  aligned Appendix A
• Notable changes since 01
• vCard reverted to attached
• Sensitivity MUST prohibit from forwarding
• MAY discard fax to deliver voice
• Some Issues
• Distribution List Addressing
• MUST vs SHOULD delete all addresses if some are
  unknown
• Positional Recommendation
• Multipart/voice-message SHOULD be first in
  multipart/mixed
• VM Client - Server
• Clarifications for Notifications
• Define use of ESMTP ORCPT

9
VPIM v2 Interoperability Website

• Driving requirement
• Customer confidence that VPIM products are
  conformant and actually do interoperate
• Process onus on vendor
• No test labs, no policing, no sticker -- casual
  interop testing
• Declaration of Compatibility
• List all features implemented
• Declaration of Interoperability
• Results of inter-vendor testing
• EMA is Registrar and repository of Declarations

http//www.ema.org/vpim/conformance/conformance.ht
ml
10
VPIM Directory Schema

• ltdraft-ema-vpimdir-schema-01.txtgt
• Anne Brown
• One use of a directory service is the retrieval
  of information, such as email address and spoken
  name, to support voice messaging. This document
  defines the directory schema required for an
  X.500/LDAP-based directory service for use by
  applications supporting Voice Profile for
  Internet Mail VPIM2. The directory service is
  intended to assist the exchange of voice messages
  between voice messaging systems.

11
VPIM Directory

• ltdraft-brown-e164-01.txtgt
• Anne Brown
• This paper addresses global access to address
  information and additional subscriber and
  equipment information, given a telephone number
  as input. VPIM is one of the driving
  applications.

12
VPIM Desktop

• Does not obsolete VPIM v2
• Voice messaging email
• One codec
• Backwards compatibility with VPIM v2 is optional
• New features for all email
• Primary content indication
• Partial NDN

13
VPIM Desktop Goals

• ltdraft-ema-vpimv3-goals-00.txtgt
• Laile Di Silvestro
• This document describes the goals of the Voice
  Profile for Internet Messaging (VPIM), Version 3
  and establishes a baseline of desired
  functionality against which proposed MIME
  profiles for Internet voice messaging can be
  judged.

This draft has not been updated to reflect the
revised goals...
14
VPIM v3 Goals Summary

• Interoperability
• Desktop clients
• Voice messaging systems
• Unified messaging systems
• Traditional email servers
• Conformance to existing standards
• DRUMS (RFC822 et al)
• VPIM v2
• Backward compatibility
• v3 is a superset of v2
• Robustness
• messages survive through gateways to AMIS-A, etc.

15
VPIM v3 Desktop Goals

• Desktop friendly
• Multiple codecs (but keep mandatory to a minimum)
• available codec on desktops available source
  code
• no IPR
• minimal encoding/decoding complexity
• VoIP friendly
• WAV wrapper
• Streaming
• Handling Rules
• Text handling by VM systems
• voice is primary content
• discarding other contents for delivery
• Voice handling by non-audio clients

16
VPIM v3 Specification

• ltdraft-ema-vpimv3-00.txtgt
• Greg Vaudreuil Glenn Parsons
• This document describes a new version of the VPIM
  specification for the interchange of voice
  messages between a voice messaging system as
  defined in VPIM and a unified messaging system.
  In this sense, a unified messaging system is
  capable of sending and receiving each of several
  different message types.

17
VPIM v3 Simple Specification

• ltdraft-ema-vpim-simplev3-00.txtgt
• Glenn Parsons
• This document describes a simpler new version of
  the VPIM specification for the interchange of
  voice messages. It leverages the concepts
  defined in VPIM but allows media of any type
  and only profiles Internet Mail features that are
  tightened.

18
VPIM v3 Differences

• Codec G.726 and ...
• MS-GSM
• G.711- mu law
• May use capabilities negotiation
• Primary Content types
• Partial non-delivery notifications
• Body part discard rules
• vCard inline attached

19
VPIM v3 Simple vs Detailed

• Minimal profiling of Internet Mail features
• Defines fewer mandatory codecs
• Mandatory MDN DSN
• Directory support for addressing
• Current trial TBD as BCP
• Use of VPIMv2 multipart/voice-message
• No UM (primary content) version
• Requires partial MDN NDNs

20
Internet Voice Messaging

• ltdraft-ema-vpim-voicemsg-00.txtgt
• Stuart McRae
• This document provides for the carriage of
  voicemail messages over the Internet. The
  concept described in this document was originally
  called VPIM v3. This term has been dropped to
  reflect the fact that it is not a successor
  format to VPIM v2, but rather an alternative
  specification for a different application.

21
Primary Content Requirements
Identify content as a voice or fax message

• Launch a helper application with the voice or fax
  message content
• main audio, spoken name, etc.
• Deliver only voice content if recipient is legacy
  voice mail
• Deliver only fax content if recipient is legacy
  fax machine
• Send NDN if voice or fax cannot be delivered
• Send partial NDN when content dropped for
  delivery
• Message is read only when voice or fax is played

22
Primary Content Types

• Multipart/voice-message
• Primary content type is VOICE
• Multipart/fax-message
• Primary content type is FAX
• Multipart/mixed
• No primary content type . However, many clients
  treat it as though Primary content type is TEXT
• Multipart/related
• Indicate primary content with new parameter

23
Partial Non-Delivery

• Sent when a (primary) content could not be
• Delivered (DSN)
• Rendered (MDN)
• Unified Message Store
• MDN from thin client
• Voice Mail via gateway
• DSN from gateway

24
VPIM Addressing

• ltdraft-ema-vpim-address-00.txtgt
• Glenn Parsons
• This document lists the various VPIM email
  addresses that are currently in common use and
  defines several new address formats for special
  case usage.

25
VPIM v2 Addresses

• Mailbox
• for use as a private numbering plan (any number
  of digits)
• e.g. 5552722_at_lucent.com, 6137637582_at_nortelnetwo
  rks.com
• Mailbox Numberextension
• for use as a private numbering plan with
  extensions any number of digits, use of as
  separator
• e.g. 5552722111_at_lucent.com
• international number
• for international telephone numbers conforming to
  E.164 - maximum of 15 digits
• e.g. 16137637582_at_nortelnetworks.com
• international numberextension
• for international telephone numbers conforming to
  E.164 - maximum of 15 digits, with an extension
  (e.g. behind a PBX) that has a maximum of 15
  digits.
• - e.g. 17035245550230_at_ema.org

26
VPIMv3 Addresses

• Onramp/Offramp - RFC2303 based
• VPIM
• Onramp submission to a VPIM gateway
• E.g., vpim6137637582_at_gateway.net
• VOICE
• Offramp to voice delivery via out call
• E.g., voice2125551234_at_bellatlantic.net
• AMIS
• Gateway address to AMIS systems
• E.g., amis4013278144/sysnum4013279542_at_company.co
  m
• FAX
• Offramp to fax terminal (per Fax WG)

27
audio/msgsm Specification

• ltdraft-ema-vpim-msgsm-00.txtgt
• Greg Baribault, Erik Hedberg Laile Di Silvestro
• This document describes a new audio content type
  for Microsoft GSM -- a common desktop codec --
  for use with VPIM v3. The differences from ETSI
  GSM 6.10 are also described.

28
audio/wav Specification

• ltdraft-ema-vpim-wav-00.txtgt
• Greg Baribault Laile Di Silvestro
• This document describes the audio content type
  for carrying Microsoft WAV audio files. This
  formalizes a long used defacto content type.

29
VPIM IMAP Extensions

• ltdraft-ema-vpim-imap-00.txtgt
• Glenn Parsons
• This document describes several proposals for
  various extensions to IMAP to meet requirements
  of voice mail systems. It is anticipated that
  the final versions of agreed extensions will be
  progressed in separate documents.

30
Proposed VPIM IMAP Extensions

• Binary Attachment Transfer - IMAPext
• new BINARY part specifier for FETCH
• External Reference
• optional keyword TO in DATA
• Alternate Codec request
• new DECODE command
• Streaming Audio Attachments
• new STREAM part specifier for FETCH
• Message length indication
• parameter of existing header
• Body part read indication
• /SEEN per body part

31
BOF/WG Focus

• VPIM v2 progression to Draft Standard
• revision of documents
• documentation of interoperability
• VPIM Desktop - Internet Voice Messaging
• Goals -- Core Specification
• Primary Content Indication -- Content Negotiation
  
• Partial MDN DSN -- MS GSM WAV
• VPIM Addenda
• Addressing -- IMAP Extensions
• Directory Profile

32
Whats Next?

• Work on specifications
• Discussion on the Mailing List
• Next Meetings
• EMA VPIM meeting - Jan/Feb in California
• IETF VPIM WG - March in Adelaide
• IETF VPIM interim meeting?
• VPIM v2 Interop Testing ongoing