< draft-ietf-vpim-vpimv2r2-04.txt   draft-ietf-vpim-vpimv2r2-05.txt >
Network Working Group Greg Vaudreuil Network Working Group Greg Vaudreuil
Internet Draft Lucent Technologies Internet Draft Lucent Technologies
Expires in six months Glenn Parsons Expires in six months Glenn Parsons
Obsoletes: RFC 2421, 2423 Nortel Networks Obsoletes: RFC 2421, 2423 Nortel Networks
October 22, 2001 February 14, 2002
Voice Profile for Internet Mail - version 2 Voice Profile for Internet Mail - version 2
<draft-ietf-vpim-vpimv2r2-04.txt> <draft-ietf-vpim-vpimv2r2-05.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are valid for a maximum of six months and may be Internet Drafts are valid for a maximum of six months and may be
updated, replaced, or obsoleted by other documents at any time. It is updated, replaced, or obsoleted by other documents at any time. It is
inappropriate to use Internet Drafts as reference material or to cite inappropriate to use Internet Drafts as reference material or to cite
them other than as a "work in progress". them other than as a "work in progress".
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
To learn the current status of any Internet-Draft, please check the To learn the current status of any Internet-Draft, please check the
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Abstract Abstract
This document specifies a restricted profile of the Internet multimedia This document specifies a restricted profile of the Internet multimedia
messaging protocols for use between voice processing server platforms. messaging protocols for use between voice processing server platforms.
skipping to change at page 2, line ? skipping to change at page 2, line ?
intended to specify the minimum common set of features to allow intended to specify the minimum common set of features to allow
interworking between conforming systems. interworking between conforming systems.
This document obsoletes RFC 2421 and describes version 2 of the profile This document obsoletes RFC 2421 and describes version 2 of the profile
with greater precision. No protocol changes were made in this revision. with greater precision. No protocol changes were made in this revision.
A list of changes from RFC 2421 are noted in Appendix F. Appendix A A list of changes from RFC 2421 are noted in Appendix F. Appendix A
summarizes the protocol profiles of this version of VPIM. summarizes the protocol profiles of this version of VPIM.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
Table of Contents Table of Contents
1. INTRODUCTION .......................................................3 1. INTRODUCTION......................................................3
1.1 Voice Messaging System Limitations ..............................4 1.1 Voice Messaging System Limitations ..............................4
1.2 Design Goals ....................................................5 1.2 Design Goals ....................................................5
2. REQUIREMENTS LANGUAGE ..............................................5 1.3 Applicability for VPIM ..........................................5
3. PROTOCOL RESTRICTIONS ..............................................6 2. REQUIREMENTS LANGUAGE.............................................6
4. VOICE MESSAGE INTERCHANGE FORMAT ...................................6 3. PROTOCOL RESTRICTIONS.............................................6
4. VOICE MESSAGE INTERCHANGE FORMAT..................................7
4.1 VPIM Message Addressing Formats .................................7 4.1 VPIM Message Addressing Formats .................................7
4.2 Message Header Fields ..........................................10 4.2 Message Header Fields ..........................................11
4.3 MIME Audio Content Descriptions ................................18 4.3 MIME Audio Content Descriptions ................................19
4.4 Voice Message Content Types ....................................20 4.4 Voice Message Content Types ....................................21
4.5 Other MIME Contents ............................................24 4.5 Other MIME Contents ............................................25
4.6 Delivery Status Notification (DSN) .............................26 4.6 Delivery Status Notification (DSN) .............................27
4.7 Message Disposition Notification (MDN) .........................27 4.7 Message Disposition Notification (MDN) .........................28
4.8 Forwarded Messages .............................................27 4.8 Forwarded Messages .............................................28
4.9 Reply Messages .................................................28 4.9 Reply Messages .................................................29
5. MESSAGE TRANSPORT PROTOCOL ........................................29 5. MESSAGE TRANSPORT PROTOCOL.......................................30
5.1 Base SMTP Protocol .............................................29 5.1 Base SMTP Protocol .............................................30
5.2 SMTP Service Extensions ........................................29 5.2 SMTP Service Extensions ........................................30
5.3 ESMTP - SMTP Downgrading .......................................31 5.3 ESMTP - SMTP Downgrading .......................................32
6. DIRECTORY ADDRESS RESOLUTION ......................................32 6. DIRECTORY ADDRESS RESOLUTION.....................................33
7. MANAGEMENT PROTOCOLS ..............................................32 7. MANAGEMENT PROTOCOLS.............................................33
7.1 Network Management .............................................32 7.1 Network Management .............................................33
8. CONFORMANCE REQUIREMENTS ..........................................33 8. CONFORMANCE REQUIREMENTS.........................................34
9. SECURITY CONSIDERATIONS ...........................................34 9. SECURITY CONSIDERATIONS..........................................35
9.1 General Directive ..............................................34 9.1 General Directive ..............................................35
9.2 Threats and Problems ...........................................34 9.2 Threats and Problems ...........................................35
9.3 Security Techniques ............................................35 9.3 Security Techniques ............................................36
10. REFERENCES.......................................................36 10. REFERENCES.......................................................37
11. ACKNOWLEDGMENTS..................................................39 11. ACKNOWLEDGMENTS..................................................40
12. COPYRIGHT NOTICE.................................................39 12. COPYRIGHT NOTICE.................................................40
13. AUTHORS' ADDRESSES...............................................40 13. AUTHORS' ADDRESSES...............................................41
14. APPENDIX A - VPIM REQUIREMENTS SUMMARY...........................41 14. APPENDIX A - VPIM REQUIREMENTS SUMMARY...........................42
15. APPENDIX B - EXAMPLE VOICE MESSAGES..............................48 15. APPENDIX B - EXAMPLE VOICE MESSAGES..............................49
16. APPENDIX C - EXAMPLE ERROR VOICE PROCESSING ERROR CODES..........54 16. APPENDIX C - EXAMPLE ERROR VOICE PROCESSING ERROR CODES..........55
17. APPENDIX D - EXAMPLE VOICE PROCESSING DISPOSITION TYPES..........56 17. APPENDIX D - EXAMPLE VOICE PROCESSING DISPOSITION TYPES..........57
18. APPENDIX E - IANA REGISTRATIONS..................................57 18. APPENDIX E - IANA REGISTRATIONS..................................58
18.1 Voice Content-Disposition Parameter Definition .................57 18.1 Voice Content-Disposition Parameter Definition ...............58
18.2 Multipart/Voice-Message MIME Media Type Definition .............58 18.2 Multipart/Voice-Message MIME Media Type Definition ...........59
19. APPENDIX F - CHANGE HISTORY: RFC 2421 (VPIM V2) TO THIS DOCUMENT.60 19. APPENDIX F - CHANGE HISTORY: RFC 2421 (VPIM V2) TO THIS DOCUMENT.61
1. Introduction 1. Introduction
MIME is the Internet multipurpose, multimedia-messaging standard. This MIME is the Internet multipurpose, multimedia-messaging standard. This
document explicitly recognizes its capabilities and provides a mechanism document explicitly recognizes its capabilities and provides a mechanism
for the exchange of various messaging technologies, primarily voice and for the exchange of various messaging technologies, primarily voice and
facsimile. facsimile.
Voice messaging evolved as telephone answering service into a full send, Voice messaging evolved as telephone answering service into a full send,
receive, and forward messaging paradigm with unique message features, receive, and forward messaging paradigm with unique message features,
semantics and usage patterns. Voice messaging was introduced on special semantics and usage patterns. Voice messaging was introduced on special
skipping to change at page 5, line 37 skipping to change at page 5, line 37
be required to originate conforming structures. be required to originate conforming structures.
It is expected that a system administrator who can perform TCP/IP It is expected that a system administrator who can perform TCP/IP
network configuration will manage a VPIM messaging system. When using network configuration will manage a VPIM messaging system. When using
facsimile or multiple voice encodings, it is suggested that the system facsimile or multiple voice encodings, it is suggested that the system
administrator maintain a list of the capabilities of the networked mail administrator maintain a list of the capabilities of the networked mail
machines to reduce the sending of undeliverable messages due to lack of machines to reduce the sending of undeliverable messages due to lack of
feature support. Configuration, implementation and management of these feature support. Configuration, implementation and management of these
directory-listing capabilities are local matters. directory-listing capabilities are local matters.
1.3 Applicability for VPIM
VPIM is intended for the exchange of voice messages between traditional
voice messaging systems and for systems that need to interoperate with
such systems. VPIM is intended connect voice-messaging systems into
special-purpose voice messaging networks. VPIM may also be used between
message store servers and VPIM-aware clients such as web servers, TUI,
and GUI clients. VPIM is not intended or optimized for downloading to,
or sending from commercial email clients.
Internet Voice Messaging, the subject of a separate standards
initiative, is intended to enable general-purpose email clients to send
and receive voice content through general-purpose message stores in an
interoperable way. IVM may also be a suitable format for downloading
voice messages from a VPIM server to a commercial email client. It may
also be a suitable format for submission of a voice message from a
general-purpose client into a VPIM system.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [REQ]. document are to be interpreted as described in [REQ].
3. Protocol Restrictions 3. Protocol Restrictions
This protocol does not limit the number of recipients per message. This protocol does not limit the number of recipients per message.
Where possible, server implementations should not restrict the number of Where possible, server implementations should not restrict the number of
skipping to change at page 36, line 14 skipping to change at page 37, line 14
10. References 10. References
[8BIT] Klensin, J., Freed, N., Rose, M., Stefferud, E., D. Crocker, "SMTP [8BIT] Klensin, J., Freed, N., Rose, M., Stefferud, E., D. Crocker, "SMTP
Service Extension for 8bit-MIMEtransport" RFC 1652, United Nations Service Extension for 8bit-MIMEtransport" RFC 1652, United Nations
University, Innosoft International, Inc., Dover Beach Consulting, Inc., University, Innosoft International, Inc., Dover Beach Consulting, Inc.,
Network Management Associates, Inc., The Branch Office, July 1994. Network Management Associates, Inc., The Branch Office, July 1994.
[ADPCM] G. Vaudreuil and G. Parsons, "Toll Quality Voice - 32 kbit/s ADPCM: [ADPCM] G. Vaudreuil and G. Parsons, "Toll Quality Voice - 32 kbit/s ADPCM:
MIME Sub-type Registration", RFC 2422, September 1998. Revised by: MIME Sub-type Registration", RFC 2422, September 1998. Revised by:
<draft-ietf-vpim-vpimv2r2-32k-02.txt>, October 2001. <draft-ietf-vpim-vpimv2r2-32k-03.txt>, February 2002.
[AMIS-A] Audio Messaging Interchange Specifications (AMIS) - Analog [AMIS-A] Audio Messaging Interchange Specifications (AMIS) - Analog
Protocol Version 1, Issue 2, February 1992. Protocol Version 1, Issue 2, February 1992.
[AMIS-D] Audio Messaging Interchange Specifications (AMIS) - Digital [AMIS-D] Audio Messaging Interchange Specifications (AMIS) - Digital
Protocol Version 1, Issue 3, August 1993. Protocol Version 1, Issue 3, August 1993.
[BINARY] Vaudreuil, G., "SMTP Service Extensions for Transmission of Large [BINARY] Vaudreuil, G., "SMTP Service Extensions for Transmission of Large
and Binary MIME Messages", RFC 3030, December 2000. and Binary MIME Messages", RFC 3030, December 2000.
skipping to change at page 36, line 42 skipping to change at page 37, line 42
Internet Messages: The Content-Disposition Header, RFC 2183, August Internet Messages: The Content-Disposition Header, RFC 2183, August
1997. 1997.
[DNS1] Mockapetris, P., "Domain names - implementation and specification", [DNS1] Mockapetris, P., "Domain names - implementation and specification",
RFC1035, Nov 1987. RFC1035, Nov 1987.
[DNS2] Mockapetris, P., "Domain names - concepts and facilities", RFC 1034, [DNS2] Mockapetris, P., "Domain names - concepts and facilities", RFC 1034,
Nov 1987. Nov 1987.
[DRPT] Moore, K. "SMTP Service Extensions for Delivery Status [DRPT] Moore, K. "SMTP Service Extensions for Delivery Status
Notifications", RFC 1891, January 1996. Notifications", RFC 1891, replaced by <draft-moore-rfc1891bis-00.txt>,
Work-in-Progress
[DSN] Moore, K., Vaudreuil, G., "An Extensible Message Format for Delivery [DSN] Moore, K., Vaudreuil, G., "An Extensible Message Format for Delivery
Status Notifications", RFC 1894, January 1996. Status Notifications", RFC 1894, replaced by <draft-vaudreuil-1894bis-
00>, January 1996.
[DUR] G. Parsons and G. Vaudreuil, "Content Duration MIME Header [DUR] G. Parsons and G. Vaudreuil, "Content Duration MIME Header
Definition", RFC 2424, September 1998. Revised by: <draft-ietf-vpim- Definition", RFC 2424, September 1998. Revised by: <draft-ietf-vpim-
vpimv2r2-dur-02.txt>, October 2001. vpimv2r2-dur-03.txt>, February 2002.
[E164] CCITT Recommendation E.164 (1991), Telephone Network and ISDN [E164] CCITT Recommendation E.164 (1991), Telephone Network and ISDN
Operation, Numbering, Routing and Mobile Service - Numbering Plan for Operation, Numbering, Routing and Mobile Service - Numbering Plan for
the ISDN Era. the ISDN Era.
[ESMTP] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker, [ESMTP] Klensin, J., Freed, N., Rose, M., Stefferud, E., and D. Crocker,
"SMTP Service Extensions" RFC 1869, United Nations University, Innosoft "SMTP Service Extensions" RFC 1869, United Nations University, Innosoft
International, Inc., Dover Beach Consulting, Inc., Network Management International, Inc., Dover Beach Consulting, Inc., Network Management
Associates, Inc., The Branch Office, November 1995. Associates, Inc., The Branch Office, November 1995.
[G726] CCITT Recommendation G.726 (1990), General Aspects of Digital [G726] CCITT Recommendation G.726 (1990), General Aspects of Digital
Transmission Systems, Terminal Equipment - 40, 32, 24,16 kbit/s Transmission Systems, Terminal Equipment - 40, 32, 24,16 kbit/s
Adaptive Differential Pulse Code Modulation (ADPCM). Adaptive Differential Pulse Code Modulation (ADPCM).
[HOSTREQ] Braden, R., "Requirements for Internet Hosts -- Application and [HOSTREQ] Braden, R., "Requirements for Internet Hosts -- Application and
Support", STD 3, RFC 1123, October 1989. Support", STD 3, RFC 1123, October 1989.
[LANG] Alvestrand,H., "Tags for the Identification of Languages", RFC 3066, [LANG] Alvestrand,H., "Tags for the Identification of Languages", RFC 3066,
January 2001. January 2001.
[MDN] Fajman, Roger, "An Extensible Message Format for Message Disposition [MDN] RFC 1891 updated by Vaudreuil, G, and Hansen, T, "An Extensible
Notifications" RFC 2298, March 1998. Message Format for Message Disposition Notifications", <draft-
vaudreuil-mdnbis-03.txt> Work-in-progress.
[MIB II] M. Rose, "Management Information Base for Network Management of [MIB II] M. Rose, "Management Information Base for Network Management of
TCP/IP-based internets: MIB-II", RFC 1213, March 1991. TCP/IP-based internets: MIB-II", RFC 1213, March 1991.
[MIME1] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions [MIME1] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part One: Format of Internet Message Bodies", RFC 2045, (MIME) Part One: Format of Internet Message Bodies", RFC 2045,
Innosoft, First Virtual, November 1996. Innosoft, First Virtual, November 1996.
[MIME2] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions [MIME2] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part Two: Media Types ", RFC 2046, Innosoft, First Virtual, (MIME) Part Two: Media Types ", RFC 2046, Innosoft, First Virtual,
skipping to change at page 37, line 50 skipping to change at page 39, line 6
Innosoft, MCI, ISI, November 1996. Innosoft, MCI, ISI, November 1996.
[MIME5] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions [MIME5] N. Freed and N. Borenstein, "Multipurpose Internet Mail Extensions
(MIME) Part Five: Conformance Criteria and Examples ", RFC 2049, (MIME) Part Five: Conformance Criteria and Examples ", RFC 2049,
Innosoft, First Virtual, November 1996. Innosoft, First Virtual, November 1996.
[PIPE] Freed, N., Cargille, A., "SMTP Service Extension for Command [PIPE] Freed, N., Cargille, A., "SMTP Service Extension for Command
Pipelining" RFC 2920, September 2000. Pipelining" RFC 2920, September 2000.
[REPORT] Vaudreuil, G., "The Multipart/Report Content Type for the [REPORT] Vaudreuil, G., "The Multipart/Report Content Type for the
Reporting of Mail System Administrative Messages", RFC 1892, Reporting of Mail System Administrative Messages", RFC 1892, replaced
01/15/1996. by <draft-vaudreuil-rfc1892bis-00.txt> work-in-progress.
[REQ] S. Bradner, "Key words for use in RFCs to Indicate Requirement [REQ] S. Bradner, "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997. Levels", RFC 2119, March 1997.
[RFC822] Crocker, D., "Standard for the Format of ARPA Internet Text [RFC822] Crocker, D., "Standard for the Format of ARPA Internet Text
Messages", STD 11, RFC 822, UDEL, August 1982. Messages", STD 11, RFC 822, UDEL, August 1982.
[SIZE] Klensin, J, Freed, N., Moore, K, "SMTP Service Extensions for [SIZE] Klensin, J, Freed, N., Moore, K, "SMTP Service Extensions for
Message Size Declaration" RFC 1870, United Nations University, Message Size Declaration" RFC 1870, United Nations University, Innosoft
Innosoft International, Inc., November 1995. International, Inc., November 1995.
[SMTP] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, [SMTP] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821,
USC/Information Sciences Institute, August 1982. USC/Information Sciences Institute, August 1982.
[STATUS] Freed, N. "SMTP Service Extension for Returning Enhanced Error [STATUS] Freed, N. "SMTP Service Extension for Returning Enhanced Error
Codes", RFC 2034, October 1996. Codes", RFC 2034, October 1996.
[TIFF-F] G. Parsons and J. Rafferty, "Tag Image File Format: Application [TIFF-F] G. Parsons and J. Rafferty, "Tag Image File Format: Application
F", RFC 2306 , March 1998. F", RFC 2306, March 1998.
[TIFFREG] G. Parsons, J. Rafferty & S. Zilles, "Tag Image File Format: [TIFFREG] G. Parsons, J. Rafferty & S. Zilles, "Tag Image File Format:
image/tiff - MIME sub-type registraion", RFC 2302, March 1998. image/tiff - MIME sub-type registraion", RFC 2302, March 1998.
[V-MSG] G. Vaudreuil and G. Parsons, "VPIM Voice Message MIME Sub-type [V-MSG] G. Vaudreuil and G. Parsons, "VPIM Voice Message MIME Sub-type
Registration", RFC 2423, September 1998. Registration", RFC 2423, September 1998.
[VCARD] Dawson, Frank, Howes, Tim, "vCard MIME Directory Profile" RFC 2426, [VCARD] Dawson, Frank, Howes, Tim, "vCard MIME Directory Profile" RFC 2426,
September 1998. September 1998.
skipping to change at page 39, line 15 skipping to change at page 40, line 15
11. Acknowledgments 11. Acknowledgments
The authors would like to offer a special thanks to the Electronic The authors would like to offer a special thanks to the Electronic
Messaging Association (EMA), especially the members of the Voice Messaging Association (EMA), especially the members of the Voice
Messaging Committee, and the IETF VPIM Work Group, for their support of Messaging Committee, and the IETF VPIM Work Group, for their support of
the VPIM specification and the efforts they have made to ensure its the VPIM specification and the efforts they have made to ensure its
success. success.
12. Copyright Notice 12. Copyright Notice
"Copyright (C) The Internet Society (2001). All Rights Reserved. "Copyright (C) The Internet Society (2002). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
 End of changes. 17 change blocks. 
61 lines changed or deleted 77 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/