VPIM BOF

1
http//www.ema.org/vpim
Mailing list vpim-l_at_ema.org To subscribe
send a message to listserv_at_ema.org with
'subscribe VPIM-L' as the subject
2
Agenda

• 1930 - Welcome Agenda bashing
• 1935 - Charter Bashing
• 2000 - VPIM v2 (RFC 2421)
• requirements for progression to Draft Standard
  (5 min)
• draft-ema-vpim-vpimv2r2-00.txt (15 min)
• 2030 - VPIM v3
• Goals
• draft-ema-vpim-goals-00.txt (10 min)
• Addressing
• draft-ema-vpim-addressing-00.txt (10 min)
• Codecs
• draft-ema-vpim-msgsm-00.txt (10 min)
• draft-ema-vpim-wav-00.txt (10 min)

3
Agenda (contd)

• 2030 - VPIM v3 (contd)
• Primary content
• draft-ema-vpim-um-01.txt (10 min)
• Base Document
• draft-ema-vpim-vpimv3-01.txt (10 min)
• draft-ema-vpim-simplev3-01.txt (10 min)
• 2140 - IMAP Voice
• draft-ema-vpim-imap-01.txt (10 min)
• 2150 - Wrap up and next steps
• 2200 - Close

4
Proposed Charter
ltsee details in text documentgt
5
VPIM v2 Status

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

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 references must be Draft Standard
• To do
• review initial clarification proposal
• report on implementations
• determine status of references

7
VPIM v2 Clarifications

• Clarified prose using send and receive rules
  aligned Appendix A
• Addressing
• non-mail-user downgraded to SHOULD
• Reply-to use discouraged
• downgrade to SHOULD NOT delete Received lines
• Sensitivity
• downgraded to SHOULD prohibit from forwarding
• still MUST NDN if unsupported
• vCard
• Role dropped
• Change current attach spoken name to inline
  -- controversial
• May be used for replies
• Fax (and other) content
• downgrade to MAY discard fax to deliver to
  client
• clarify behaviour on reception of non-voice
  content

8
VPIM Conformance

• Main requirement
• Customer confidence that VPIM products are
  conformant and actually do interoperate
• End systems should be content and transport
  conformant
• Intermediate mail gateways should be transport
  conformant
• Process
• Registration by vendor
• Declaration of Compatibility Interoperability
• No test labs, no policing, no sticker -- casual
  interop testing
• EMA is Registrar

http//www.ema.org/vpimdir/conformance/conformance
.html
9
VPIM v3 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.

10
VPIM v3 Goals

• The primary goal for this version is to support
  interoperability with desktop clients. Other
  goals include expanded interoperability with
  unified messaging systems, backward
  compatibility, and conformance to Internet
  standards. This is in addition to the goals that
  were met fully by VPIM version 2.

11
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.

12
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

13
VPIM Unified Messaging MIME Sub-type Registration

• ltdraft-ema-vpim-um-01.txtgt
• Greg Vaudreuil, Glenn Parsons, Marty Cohen
• This document describes the registration of the
  MIME sub-types multipart/voice-message and
  multipart/fax-message for use with the Voice
  Profile for Internet Mail (VPIM) and other
  Internet Mail profiles for Unified Messaging

14
Primary Content Types

• The primary content type identifies the essence
  of a multipart message
• Supporting clients can treat different content
  type differently, for example
• Content type specific display icon
• Appropriate viewer/player launched and/or preview
  presented
• Meaningful discard rules
• Non-supporting clients will treat messages as
  multipart/mixed
• Resolves some outstanding ambiguities with MDNs,
  and read status. Only the primary message
  content is considered when
• An MDN is returned after the message is
  displayed or otherwise processed.
• The client typically changes the status of a
  message from unseen to seen when the message
  has been viewed.

15
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 has been formally
  associated with this type. However, many clients
  treat it as though Primary content type is TEXT

16
Driving 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

17
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.

18
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

19
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)

20
audio/msgsm Specification

• ltdraft-ema-vpim-msgsm-00.txtgt
• 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.

21
audio/wav Specification

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

22
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.

23
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.

24
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

25
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

26
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.

27
Proposed VPIM IMAP Extensions

• Binary Attachment Transfer
• 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

28
Focus?

• VPIM v2 progression to Draft Standard
• revision of document
• documentation of interoperability
• VPIM v3 Unified Messaging
• Goals -- IMAP Extensions
• Primary Content Types ? -- Directory Profile
• Partial MDN MDN ? -- Content Negotiation
• Addressing
• MS GSM WAV
• Core Spec (detailed or simple)

29
Whats Next?

• Discussion on the Mailing List
• VMAE meeting - October in Montreux
• EMA VPIM meeting - October in Washington
• IETF VPIM WG - November in Washington
• Work on specifications
• VPIM v3 Interop Testing starting Fall 1999