< draft-ietf-impp-cpim-msgfmt-07.txt   draft-ietf-impp-cpim-msgfmt-08.txt >
Network Working Group D. Atkins, IHTFP Consulting Network Working Group D. Atkins, IHTFP Consulting
Internet Draft G. Klyne, Clearswift Internet Draft G. Klyne, Nine by Nine
16 October 2002 9 January 2003
Expires: April 2003 Expires: July 2003
Common Presence and Instant Messaging: Message Format Common Presence and Instant Messaging: Message Format
<draft-ietf-impp-cpim-msgfmt-07.txt> <draft-ietf-impp-cpim-msgfmt-08.txt>
Status of this memo Status of this memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress". material or to cite them other than as "work in progress".
The list of current Internet-Drafts can be accessed at To view the entire list of current Internet-Drafts, please check the
http://www.ietf.org/1id-abstracts.html "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
The list of Internet-Draft Shadow Directories can be accessed at Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
http://www.ietf.org/shadow.html Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society 2002. All Rights Reserved. Copyright (C) The Internet Society 2003. All Rights Reserved.
Abstract Abstract
This memo defines the mime type 'Message/CPIM', a message format for This memo defines the mime type 'Message/CPIM', a message format for
protocols that conform to the Common Profile for Instant Messaging protocols that conform to the Common Profile for Instant Messaging
(CPIM) specification. (CPIM) specification.
Discussion of this document Discussion of this document
Please send comments to: <impp@iastate.edu>. To subscribe: send a Please send comments to: <impp@iastate.edu>. To subscribe: send a
skipping to change at page 2, line 43 skipping to change at page 2, line 43
5.1 An example Message/CPIM message 5.1 An example Message/CPIM message
5.2 An example using MIME multipart/signed 5.2 An example using MIME multipart/signed
6. APPLICATION DESIGN CONSIDERATIONS 6. APPLICATION DESIGN CONSIDERATIONS
7. IANA CONSIDERATIONS 7. IANA CONSIDERATIONS
7.1 Registration for Message/CPIM content type 7.1 Registration for Message/CPIM content type
7.2 Registration for urn:ietf:params:cpim-headers: 7.2 Registration for urn:ietf:params:cpim-headers:
8. INTERNATIONALIZATION CONSIDERATIONS 8. INTERNATIONALIZATION CONSIDERATIONS
9. SECURITY CONSIDERATIONS 9. SECURITY CONSIDERATIONS
10. ACKNOWLEDGEMENTS 10. ACKNOWLEDGEMENTS
11. REFERENCES 11. REFERENCES
11.1 Normative references
11.2 Informative references
12. AUTHORS' ADDRESSES 12. AUTHORS' ADDRESSES
Full copyright statement Full copyright statement
1. INTRODUCTION 1. INTRODUCTION
This memo defines the mime content-type 'Message/CPIM'. This is a This memo defines the mime content-type 'Message/CPIM'. This is a
common message format for CPIM-compliant messaging protocols [14]. common message format for CPIM-compliant messaging protocols [14].
While being prepared for CPIM, this format is quite general and may While being prepared for CPIM, this format is quite general and may
be reused by other applications with similar requirements. be reused by other applications with similar requirements.
skipping to change at page 24, line 26 skipping to change at page 24, line 26
Instant messaging Instant messaging
Additional information: Additional information:
The default namespace URI associated with this content-type is The default namespace URI associated with this content-type is
'urn:ietf:params:cpim-headers:'. (See RFC XXXX [this document] 'urn:ietf:params:cpim-headers:'. (See RFC XXXX [this document]
for further details.) for further details.)
See also the Common Profile for Instant Messaging (CPIM) [14] See also the Common Profile for Instant Messaging (CPIM) [14]
Person & email address to contact for further information: Person & email address to contact for further information:
G. Klyne, GK@ACM.ORG G. Klyne, GK-IETF@ninebynine.org
Intended usage: Intended usage:
LIMITED USE LIMITED USE
Author/Change controller: Author/Change controller:
IETF IETF
7.2 Registration for urn:ietf:params:cpim-headers: 7.2 Registration for urn:ietf:params:cpim-headers:
Registry name: Registry name:
skipping to change at page 26, line 8 skipping to change at page 26, line 8
and unencapsulated at the receiving end of the tunnel. and unencapsulated at the receiving end of the tunnel.
The resulting message must have no data loss due to the encoding and The resulting message must have no data loss due to the encoding and
unencoding of the message. For example, an application may choose to unencoding of the message. For example, an application may choose to
apply the MIME base64 content-transfer-encoding to the Message/CPIM apply the MIME base64 content-transfer-encoding to the Message/CPIM
object to meet this requirement. object to meet this requirement.
10. ACKNOWLEDGEMENTS 10. ACKNOWLEDGEMENTS
The authors thank the following for their helpful comments: Harald The authors thank the following for their helpful comments: Harald
Alvestrand, Walter Houser, Leslie Daigle, Mark Day, Brian Raymor, Alvestrand, Walter Houser, Leslie Daigle, Mark Day, Brian Raymor.
[[[...]]]
11. REFERENCES 11. REFERENCES
11.1 Normative references
[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement [1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", RFC 2119, March 1997. Levels", RFC 2119, March 1997.
[2] Resnick, P., "Internet Message Format", RFC 2822, April 2001. [2] Resnick, P., "Internet Message Format", RFC 2822, April 2001.
[3] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [3] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part One: Format of Internet Message Bodies", Extensions (MIME) Part One: Format of Internet Message Bodies",
RFC 2045, November 1996. RFC 2045, November 1996.
[4] Freed, N. and N. Borenstein, "Multipurpose Internet Mail [4] Freed, N. and N. Borenstein, "Multipurpose Internet Mail
Extensions (MIME) Part Two: Media Types", RFC 2046 November Extensions (MIME) Part Two: Media Types", RFC 2046 November
1996. 1996.
[5] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet [5] Freed, N., Klensin, J., and J. Postel, "Multipurpose Internet
Mail Extensions (MIME) Part Four: Registration Procedures", RFC Mail Extensions (MIME) Part Four: Registration Procedures", RFC
2048, BCP 13, November 1996. 2048, BCP 13, November 1996.
[7] Alvestrand, H., "Tags for the Identification of Languages", RFC
3066, January 2001. (Defines Content-language header.)
[10] Berners-Lee, T., Fielding, R.T. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August
1998.
[17] D. Crocker, P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[19] Alvestrand, H, "IETF Policy on Character Sets and Languages",
RFC 2277, BCP 18, January 1998.
[21] F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC
2279 January 1998.
[22] M. Mealling, L. Masinter, T. Hardie, G. Klyne, "An IETF URN Sub-
namespace for Registered Protocol Parameters", draft-mealling-
iana-urn-02.txt (work in progress), October 2001
[23] C. Newman, G. Klyne, "Date and Time on the Internet:
Timestamps", RFC 3339, July 2002.
[24] R. Moats, "URN Syntax", RFC 2141, May 1997.
11.2 Informative references
[6] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson, [6] Weider, C., Preston, C., Simonsen, K., Alvestrand, H., Atkinson,
R., Crispin, M., Svanberg, P., "Report from the IAB Character R., Crispin, M., Svanberg, P., "Report from the IAB Character
Set Workshop", RFC 2130, April 1997. Set Workshop", RFC 2130, April 1997.
[7] Alvestrand, H., "Tags for the Identification of Languages", RFC
3066, January 2001. (Defines Content-language header.)
[8] Ramsdell, B., "S/MIME Version 3 Message Specification", RFC [8] Ramsdell, B., "S/MIME Version 3 Message Specification", RFC
2633, June 1999. 2633, June 1999.
[9] Callas, J., Donnerhacke, L., Finney, H. and R. Thayer, "OpenPGP [9] Callas, J., Donnerhacke, L., Finney, H. and R. Thayer, "OpenPGP
Message Format", RFC 2440, November 1998. Message Format", RFC 2440, November 1998.
[10] Berners-Lee, T., Fielding, R.T. and L. Masinter, "Uniform
Resource Identifiers (URI): Generic Syntax", RFC 2396, August
1998.
[11] Tim Bray, Jean Paoli, and C. M. Sperberg-McQueen, "Extensible [11] Tim Bray, Jean Paoli, and C. M. Sperberg-McQueen, "Extensible
Markup Language (XML) 1.0", W3C recommendation: Markup Language (XML) 1.0", W3C recommendation:
<http://www.w3.org/TR/REC-xml>, 10 February 1998. <http://www.w3.org/TR/REC-xml>, 10 February 1998.
[12] Tim Bray, Dave Hollander, and Andrew Layman, "Namespaces in [12] Tim Bray, Dave Hollander, and Andrew Layman, "Namespaces in
XML", W3C recommendation: <http://www.w3.org/TR/REC-xml-names>, XML", W3C recommendation: <http://www.w3.org/TR/REC-xml-names>,
14 January 1999. 14 January 1999.
[13] "Data elements and interchange formats - Information interchange [13] "Data elements and interchange formats - Information interchange
- Representation of dates and times", ISO 8601:1988(E), - Representation of dates and times", ISO 8601:1988(E),
skipping to change at page 27, line 26 skipping to change at page 27, line 47
common-00 (work in progress), August 2000. common-00 (work in progress), August 2000.
[15] Day, M., Aggarwal, S., Mohr, G., and J. Vincent, "Instant [15] Day, M., Aggarwal, S., Mohr, G., and J. Vincent, "Instant
Messaging / Presence Protocol Requirements", RFC 2779, February Messaging / Presence Protocol Requirements", RFC 2779, February
2000. 2000.
[16] N. Freed, K. Moore, "MIME Parameter Value and Encoded Word [16] N. Freed, K. Moore, "MIME Parameter Value and Encoded Word
Extensions: Character Sets, Languages, and Continuations", RFC Extensions: Character Sets, Languages, and Continuations", RFC
2231, November 1997. 2231, November 1997.
[17] D. Crocker, P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", RFC 2234, November 1997.
[18] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P. [18] R. Fielding, J. Gettys, J. Mogul, H. Frystyk, L. Masinter, P.
Leach, T. Berners-Lee, "Hypertext Transfer Protocol -- Leach, T. Berners-Lee, "Hypertext Transfer Protocol --
HTTP/1.1", RFC 2616, June 1999. HTTP/1.1", RFC 2616, June 1999.
[19] Alvestrand, H, "IETF Policy on Character Sets and Languages",
RFC 2277, BCP 18, January 1998.
[20] Freed, N., and J. Postel, "IANA Charset Registration [20] Freed, N., and J. Postel, "IANA Charset Registration
Procedures", BCP 19, RFC 2278, January 1998. Procedures", BCP 19, RFC 2278, January 1998.
[21] F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC
2279 January 1998.
[22] M. Mealling, L. Masinter, T. Hardie, G. Klyne, "An IETF URN Sub-
namespace for Registered Protocol Parameters", draft-mealling-
iana-urn-02.txt (work in progress), October 2001
[23] C. Newman, G. Klyne, "Date and Time on the Internet:
Timestamps", RFC 3339, July 2002.
[24] R. Moats, "URN Syntax", RFC 2141, May 1997.
12. AUTHORS' ADDRESSES 12. AUTHORS' ADDRESSES
Derek Atkins Derek Atkins
IHTFP Consulting IHTFP Consulting
6 Farragut Ave 6 Farragut Ave
Somerville, MA 02144 Somerville, MA 02144
USA. USA.
Telephone: +1 617 623 3745 Telephone: +1 617 623 3745
E-mail: warlord@ihtfp.com E-mail: derek@ihtfp.com
E-mail: warlord@alum.mit.edu E-mail: warlord@alum.mit.edu
Graham Klyne Graham Klyne
Clearswift, Nine by Nine
1310 Waterside, 14 Chambrai Close
Arlington Business Park Appleford
Theale Abingdon
Reading, RG7 4SA OX14 4NT
United Kingdom. UK
Telephone: +44 118 903 8000 Telephone: +44 1235 848491
Facsimile: +44 118 903 9000 E-mail: GK-IETF@ninebynine.org
E-mail: GK@ACM.ORG
Appendix A: Amendment history Appendix A: Amendment history
[[[RFC editor: please remove this appendix on publication.]]] [[[RFC editor: please remove this appendix on publication.]]]
00a 01-Feb-2001 Memo initially created. 00a 01-Feb-2001 Memo initially created.
00b 06-Feb-2001 Editorial review. Reworked namespace framework 00b 06-Feb-2001 Editorial review. Reworked namespace framework
description. Deferred specification of mandatory description. Deferred specification of mandatory
headers to the application specification, allowing headers to the application specification, allowing
skipping to change at page 29, line 46 skipping to change at page 29, line 46
06a 20-Feb-2002 Fix definition in section 3.6 of NAMECHAR characters 06a 20-Feb-2002 Fix definition in section 3.6 of NAMECHAR characters
to include apostrophe 0x27 (following RFC 2822). Fix to include apostrophe 0x27 (following RFC 2822). Fix
error in sect 3.1 definition of SEPARATORS. error in sect 3.1 definition of SEPARATORS.
07a 28-Aug-2002 Fix description of 'require' header in section 4.7. 07a 28-Aug-2002 Fix description of 'require' header in section 4.7.
07b 16-Oct-2002 Change author affiliation details. Update document 07b 16-Oct-2002 Change author affiliation details. Update document
and expiry dates, for re-realease of I-D. Update and expiry dates, for re-realease of I-D. Update
date-time reference to RFC3339. date-time reference to RFC3339.
08a 09-Jan-2003 Change author affiliation and email details. Update
document and expiry dates, for re-realease of I-D
post-last-call. Separate normative and informative
references.
TODO: TODO:
o Replace XXXX with assigned RFC numbers. (Note that this memo o Replace XXXX with assigned RFC numbers. (Note that this memo
depends on [22] progressing to RFC status.) depends on [22] progressing to RFC status.)
o Update references to other CPIM documents. o Update references to other CPIM documents.
o Separate normative and non-normative references. o Delete reference [14]?
o Renumber references?
REVIEW CHECKLIST: REVIEW CHECKLIST:
(Points to be checked or considered more widely on or before final (Points to be checked or considered more widely on or before final
review.) review.)
o The desirability of a completely rigid syntax. o The desirability of a completely rigid syntax.
o Escape mechanism details. o Escape mechanism details.
 End of changes. 18 change blocks. 
49 lines changed or deleted 60 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/