Network Working Group R. Barnes Internet-Draft BBN Technologies Intended status: Standards Track B. Rosen Expires: April 8, 2012 Neustar October 6, 2011 Media Type Registration for Common Alerting Protocol draft-barnes-atoca-cap-mime-00 Abstract This document registers the media type "application/ common-alerting-protocol+xml" for Common Alerting Protocol (CAP) format . 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 RFC 2119 [RFC2119]. Status of this Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. 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." This Internet-Draft will expire on April 8, 2012. Copyright Notice Copyright (c) 2011 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 Barnes & Rosen Expires April 8, 2012 [Page 1] Internet-Draft CAP MIME registration October 2011 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Registration of the 'application/common-alerting-protocol+xml' media type . . . 4 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 4. Normative References . . . . . . . . . . . . . . . . . . . . . 5 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 Barnes & Rosen Expires April 8, 2012 [Page 2] Internet-Draft CAP MIME registration October 2011 1. Introduction The Common Alerting Protocol (CAP) [cap] is an XML document format for exchanging emergency alerts and public warnings. This document registers a media type for CAP documents. The following is an example of a CAP message for a severe thunderstorm warning: KSTO1055887203 KSTO@NWS.NOAA.GOV 2003-06-17T14:57:00-07:00 Actual Alert Public Met SEVERE THUNDERSTORM Severe Likely NATIONAL WEATHER SERVICE SACRAMENTO SEVERE THUNDERSTORM WARNING AT 254 PM PDT... NATIONAL WEATHER SERVICE DOPPLER RADAR INDICATED A SEVERE THUNDERSTORM OVER SOUTH CENTRAL ALPINE COUNTY... OR ABOUT 18 MILES SOUTHEAST OF KIRKWOOD... MOVING SOUTHWEST AT 5 MPH. HAIL... INTENSE RAIN AND STRONG DAMAGING WINDS ARE LIKELY WITH THIS STORM TAKE COVER IN A SUBSTANTIAL SHELTER UNTIL THE STORM PASSES BARUFFALDI/JUSKIE EXTREME NORTH CENTRAL TUOLUMNE COUNTY IN CALIFORNIA, EXTREME NORTHEASTERN CALAVERAS COUNTY IN CALIFORNIA, SOUTHWESTERN ALPINE COUNTY IN CALIFORNIA 38.47,-120.14 38.34,-119.95 38.52,-119.74 38.62,-119.89 38.47,-120.14 Barnes & Rosen Expires April 8, 2012 [Page 3] Internet-Draft CAP MIME registration October 2011 2. IANA Considerations 2.1. Registration of the 'application/common-alerting-protocol+xml' media type To: ietf-types@iana.org Subject: Registration of MIME media type application/ common- alerting-protocol+xml MIME media type name: application MIME subtype name: common-alerting-protocol+xml Required parameters: (none) Optional parameters: charset; Indicates the character encoding of the enclosed XML. Default is UTF-8 [RFC3629]. Security considerations: Transmission of CAP payloads does not introduce new security risks Interoperability considerations: CAP is widely used for emergency management. Published specification: RFC XXX [Replace by the RFC number of this specification]. Applications which use this media type: Applications that convey alerts and early warnings according to the CAP standard. Additional information: OASIS has published the Common Alerting Protocol specification [CAP]. Person & email address to contact for further information: Hannes Tschofenig, hannes.tschofenig@nsn.com Intended usage: Limited use Author/Change controller: IETF ATOCA working group Other information: This media type is a specialization of application/xml [RFC3023], and many of the considerations described there also apply to application/ common-alerting- protocol+xml. Barnes & Rosen Expires April 8, 2012 [Page 4] Internet-Draft CAP MIME registration October 2011 3. Security Considerations The introduction of the CAP MIME type does not present any new risks in itself. CAP messages are used to encode emergency alerts, which means that false CAP messages can have significant negative effects, such as the unnecessary evacuation of an area. Systems that process CAP messages will need to have mechanisms for integrity protection and origin authentication, in order to ensure either that end alert recipients do not receive false alerts or that they can distinguish valid alerts from false alerts. 4. Normative References [CAP] Botterell, A. and E. Jones, "ommon Alerting Protocol v1.1", October 2005. [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. [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD 63, RFC 3629, November 2003. Authors' Addresses Richard Barnes BBN Technologies 9861 Broken Land Parkway Columbia, MD 21046 US Phone: +1 410 290 6169 Brian Rosen Neustar Phone: Fax: Email: URI: Barnes & Rosen Expires April 8, 2012 [Page 5]