SIMPLE G. Garcia Internet-Draft J. Martin Intended status: Standards Track Telefonica I+D Expires: August 16, 2009 February 12, 2009 Attention Request (POKE) for Instant Messaging draft-garcia-simple-poke-01 Status of this Memo This Internet-Draft is submitted to IETF in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 16, 2009. Copyright Notice Copyright (c) 2009 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Abstract This document specifies a message content type and XML format to request attention from a targeted user. This feature is usually Garcia & Martin Expires August 16, 2009 [Page 1] Internet-Draft POKE February 2009 known as poke, nudge or buzz in existing messaging platforms. Its primary use is as an additional instant messaging capability that can be sent in the middle of a instant messaging session or in a standalone message at any time. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3 2. Message Content . . . . . . . . . . . . . . . . . . . . . . . . 3 3. XML Document Format . . . . . . . . . . . . . . . . . . . . . . 4 4. Security Considerations . . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 5.1. Content-Type Registration for 'application/im-poke+xml' . . 4 5.2. URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:im-poke' . . . . . . . . . . . . . 5 5.3. Schema registration . . . . . . . . . . . . . . . . . . . . 6 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 7 7.1. Normative References . . . . . . . . . . . . . . . . . . . 7 7.2. Informative References . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 7 Garcia & Martin Expires August 16, 2009 [Page 2] Internet-Draft POKE February 2009 1. Introduction Some existing messaging platforms include the capability to send a message to a user requesting his attention (e.g. XMPP [XEP-0224]). This feature is usually known as poke, nudge or buzz, and in desktop applications the notification is usually implemented using a combination of sound and the vibration of chat windows. This document describes the XML message format to encode this attention request. This message can be used inside an instant messaging session (for example a MSRP session) or as a standalone message (for example in a SIP MESSAGE). In session mode, the poke message is sent as part of the messaging stream and its usage is negotiated just like any other media type in that stream, with details depending on the session mode protocol. The receiver of this message can present it to the user in different ways depending on the device capabilities and the user preferences. The message format does not include support to specify sender preferences for the realization of the attention request. 1.1. Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2. Message Content The only XML element of the message is the poke element. This is the root element of the message and doesn't define any additional attribute. The schema (Section 3) should be consulted for the normative message format. In order to include additional functionality, the XML schema can be extended in future documents. Additional elements MUST use their own namespaces and MUST be designed such that receivers can safely ignore such extensions. Adding elements to the namespace defined in this document is not permitted. This is the example of a poke message: Garcia & Martin Expires August 16, 2009 [Page 3] Internet-Draft POKE February 2009 3. XML Document Format 4. Security Considerations The poke message is a specialized type of instant messaging, all the security considerations for the instant messages also applies to the poke messages. Pokes rate MUST be controlled and limited in the receiving side to minify the effect of malicious nodes sending these messages too often (the limit is an implementor decission). 5. IANA Considerations 5.1. Content-Type Registration for 'application/im-poke+xml' Garcia & Martin Expires August 16, 2009 [Page 4] Internet-Draft POKE February 2009 To: ietf-types@iana.org Subject: Registration of MIME media type application/ im-poke+xml MIME media type name: application MIME subtype name: im-poke+xml Required parameters: (none) Optional parameters: charset; Indicates the character encoding of enclosed XML. Default is UTF-8. Encoding considerations: Uses XML, which can employ 8-bit characters, depending on the character encoding used. See [RFC3023], section 3.2. Security considerations: This content type is designed to carry information about current user activity, which may be considered private information. Appropriate precautions should be adopted to limit disclosure of this information. Interoperability considerations: This content type provides a common format for sending attention requests. Published specification: RFC XXXX Applications which use this media type: Instant messaging systems. Additional information: none Person & email address to contact for further information: Gustavo Garcia, ggb@tid.es Intended usage: LIMITED USE Author/Change controller: This specification is a work item of the IETF SIMPLE working group, with the mailing list address simple@ietf.org. Other information: This media type is a specialization of application/xml [RFC3023], and many of the considerations described there also apply to application/im-poke+xml. 5.2. URN Sub-Namespace Registration for 'urn:ietf:params:xml:ns:im-poke' Garcia & Martin Expires August 16, 2009 [Page 5] Internet-Draft POKE February 2009 URI: urn:ietf:params:xml:ns:im-poke Description: This is the XML namespace for XML elements defined by [RFC XXXX] to describe attention request by an instant messaging client using the application/im-poke+xml content type. Registrant Contact: IETF, SIMPLE working group, simple@ietf.org, Gustavo Garcia, ggb@tid.es XML: BEGIN Attention Request (POKE) for Instant Messaging

Namespace for SIMPLE poke extension

urn:ietf:params:xml:ns:im-poke

See [RFCXXXX].

END 5.3. Schema registration This section registers a new XML schema per the procedures in [RFC3688]. URI: urn:ietf:params:xml:schema:im-poke Registrant Contact: IETF, SIMPLE working group, (simple@ietf.org), Gustavo Garcia (ggb@tid.es). The XML for this schema can be found as the sole content of Section 3. 6. Acknowledgements We would like to acknowledge the valuable ideas and support given by Guido Garcia and the useful comments received from Jose Luis Urien. 7. References Garcia & Martin Expires August 16, 2009 [Page 6] Internet-Draft POKE February 2009 7.1. Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media Types", RFC 3023, January 2001. [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, January 2004. 7.2. Informative References [XEP-0224] Monitzer, A., "XEP-0224: Attention", august 2008. Authors' Addresses Gustavo Garcia Telefonica I+D Emilio Vargas Madrid, Madrid Spain Phone: +34 913129826 Email: ggb@tid.es Jose-Luis Martin Telefonica I+D Parque Tecnologico de Boecillo Boecillo, Valladolid Spain Phone: +34 983367902 Email: jlmp@tid.es Garcia & Martin Expires August 16, 2009 [Page 7]