EMA Voice Messaging Committee Meeting

1
EMA Voice Messaging Committee Meeting

• October 18th, 1999
• Fairfax, VA

2
Voice Messaging Committee8am - 10am

• 1. Introductions 10 min
• 2. Review of goals 20 min
• 3. EMA Support 20 min
• (mailing lists, web page, etc.)
• 4. Update on VPIM deployment 60 min
• - EMA/TMIA ICMA
• - VMA GVMS Telecom 99
• 5. Other business 10 min

3
VMC Goals

• Industry promotion, marketing education
• Voice Messaging
• Computer Telephony Integration
• Wireless Messaging
• Support of interoperability standards development
• Support of interoperability trials

4
EMA Support

• EMA Goals - The Electronic Business Forum
• Promotion of E-business
• Premier Forum
• EMA Support to VMC
• Meeting facilities
• Mailing list and web page
• Budget maintenance

5
Update on Activities

• VMA
• Global Voice Mail Service
• Telecom 99
• Inter Company Messaging Agreements
• Joint with TMIA
• Wireless Messaging Group
• Others?

6
EMA VPIM Work Group Meeting

• October 18th, 1999
• Fairfax, VA

7
VPIM work group10am - 12pm

• 1. Introductions 10 min
• 2. Review of goals 20 min
• IETF vs EMA Role
• 3. Directory for VPIM 90 min
• - Review proposals
• - original VPIM directory proposal
• - ICMA proposal
• - VMA proposal
• - Plan to go forward

8
VPIM work group1pm - 6pm

• 4. Interoperability Testing 30 min
• 5. IETF VPIM BOF 30 min
• 6. VPIM v2 60 min
• - clarifications
• - progression (to IETF Draft Standard) roadblocks
• 7. VPIM v3 90 min
• - Goals
• - Specification (Codec, partial NDN, primary
  content)
• 8. VPIM Addenda 60 min
• - Content Negotiation
• - Security (integrity, authentication, etc.)
• - IMAP Voice - Addressing

9
EMA VPIM WG Goals

• VPIM Testing
• testing coordination
• declaration of compatibility and
  interoperability
• Inter-company Messaging Agreements
• Deployment issues
• Marketing and education efforts
• under VM Committee
• Technical advice on specifications

10
IETF VPIM WG Goals

• Technical details
• VPIM v2 progression to Draft Standard
• Revision of spec
• Driving progression of supporting standards
• VPIM v3 development
• Creation of main specification
• VPIM Addenda standardization
• IMAP voice
• Directory

11
Directory for VPIM

• Requirements
• Return email address for mailbox/telephone number
• Return of spoken name
• Optional return of additional capabilities
  information
• Options
• Original VPIM Directory proposal
• ICMA directory proposal
• VMA GVMS directory
• Others?
• Plan to go forward?

12
VPIM work group1pm - 6pm

• 4. Interoperability Testing 30 min
• 5. IETF VPIM BOF 30 min
• 6. VPIM v2 60 min
• - clarifications
• - progression (to IETF Draft Standard) roadblocks
• 7. VPIM v3 90 min
• - Goals
• - Specification (Codec, partial NDN, primary
  content)
• 8. VPIM Addenda 60 min
• - Content Negotiation
• - Security (integrity, authentication, etc.)
• - IMAP Voice - Addressing

13
IETF VPIM BOF

• Charter Approved by meeting
• v2 - v3 Compatible where possible
• Pending IESG approval -- Chair issue
• VPIM v2 - review of clarified draft
• Leave Forward Sensitive as MUST NOT
• vCard cannot be changed to progress
• May discard fax to deliver voice (with NDN)
• VPIM v3 Goals
• Support interoperability with desktops
• WAV/GSM mandatory, G.726 optional

14
IETF VPIM BOF -- continued

• VPIM v3 Specifications
• Base specification
• Simple preferred
• UM specification
• Premise accepted, proposal rejected
• Use multipart/related with parameters
• MS-GSM WAV
• Apparent agreement, but confusion
• VPIM Addenda
• IMAP Voice
• Voice specific except for binary
• Addressing
• Directory

15
VPIM v2

• Status
• Approved by IETF as a Proposed Standard in
  September 1998
• Goal
• Elevate to IETF Draft Standard
• VPIM v2 revised ltdraft-ema-vpim-vpimv2r2-00.txtgt
• Clarifications
• Dependent References (see table)
• Interoperability Report
• Required to show all features implemented
• Roadblocks?

16
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

17
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

18
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
19
VPIM v2 Interoperability Report

• IETF Format
• Based on Declarations
• Additional info from Demonstrations
• Volunteers?

20
VPIM v2 Dependent References

• See Table for details
• Key references
• vCard et al -- is there any other interest in
  elevating this
• MDN DSN -- in Oslo some said that this could
  elevate if pushed the time was right
• binary -- again in Oslo some said that the time
  was right to make this standards track

21
VPIM v3

• It is just email - full desktop interoperability
• Primary VPIM v3 Documents
• Goals
• Core Specification (simple)
• MS GSM WAV
• Partial MDN DSN
• Primary content type

22
VPIM v3 Goals

• ltdraft-ema-vpimv3-goals-00.txtgt
• Laile Di Silvestro
• 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.

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

24
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

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

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

27
VPIM v3 Differences

• Codec G.726 and ...
• MS-GSM G.711- mu law
• Note this will be changed based on IETF meeting
  results
• May use capabilities negotiation
• Primary Content types
• This will be using parameters
• Partial non-delivery notifications
• Body part discard rules
• vCard inline attached

28
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

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

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

31
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

Rejected Proposal
32
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.

33
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

34
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
  (DSN) or displayed (MDN)
• Send partial NDN when content dropped for
  delivery
• Indication that the voice or fax is primary
  content
• Message is read only when voice or fax is played

35
Partial Notifications

• No documents yet - volunteers?
• Based on Requirements
• Anticipated Documents
• MDN extension
• DSN extension
• Primary body part(s) parameter

36
VPIM Unified Messaging

• Additional Documents
• IMAP Voice extensions
• Addressing
• Directory Profile
• Content Negotiation
• Related Work
• Fax
• DRUMS
• Instant Messaging?

37
VPIM IMAP Extensions

• ltdraft-ema-vpim-imap-01.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.

38
Proposed VPIM IMAP Extensions

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

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

40
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

41
VPIM v3 Addresses

• Any valid email address
• 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)

42
Additional Documents

• No documents yet -- volunteers?
• Content Negotiation
• Determine alternative codec support, etc.
• Based on CONNEG work and parallel to Fax
• Initial proposal by Glenn Graham
• Directory
• Based on outcome of directory discussions
• Likely document as IETF BCP
• Security
• Use S/MIME, Ipsec, SSL, ?
• Add section to VPIM v3 or separate document
• Others?

43
Related Groups

• Internet Fax
• Collaborate on partial NDN primary content
• DRUMS
• Assorted Internet Mail extensions
• Instant Messaging Presence
• Others?

44
Whats Next?

• IETF VPIM Meeting
• Nov 8-12 in Washington
• Attendance is encouraged
• Internet Drafts
• Updates and new documents encouraged before
  deadline of October 20th
• Mailing List
• Please participate
• Next EMA Meeting
• January 2000