Internet DRAFT - draft-barnes-atoca-cap-mime
draft-barnes-atoca-cap-mime
Network Working Group R. Barnes
Internet-Draft BBN Technologies
Intended status: Standards Track B. Rosen
Expires: April 9, 2012 Neustar
H. Tschofenig
Nokia Siemens Networks
October 7, 2011
Media Type Registration for Common Alerting Protocol
draft-barnes-atoca-cap-mime-01
Abstract
This document registers the media type "application/cap+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 9, 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
Barnes, et al. Expires April 9, 2012 [Page 1]
Internet-Draft CAP MIME registration October 2011
publication of this document. Please review these documents
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 . . . . . . . . . . . . . . . . . . . . 6
4. Normative References . . . . . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
Barnes, et al. Expires April 9, 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 full specification for
CAP can be found at the following URL:
<http://www.oasis-open.org/committees/download.php/15135/
emergency-CAPv1.1-Corrected_DOM.pdf>
The following is an example of a CAP message for a severe
thunderstorm warning:
Barnes, et al. Expires April 9, 2012 [Page 3]
Internet-Draft CAP MIME registration October 2011
<?xml version="1.0" encoding="UTF-8"?>
<alert xmlns="urn:oasis:names:tc:emergency:cap:1.1">
<identifier>KSTO1055887203</identifier>
<sender>KSTO@NWS.NOAA.GOV</sender>
<sent>2003-06-17T14:57:00-07:00</sent>
<status>Actual</status>
<msgType>Alert</msgType>
<scope>Public</scope>
<info>
<category>Met</category>
<event>SEVERE THUNDERSTORM</event>
<urgency>Severe</urgency>
<certainty>Likely</certainty>
<senderName>NATIONAL WEATHER SERVICE SACRAMENTO</senderName>
<headline>SEVERE THUNDERSTORM WARNING</headline>
<description> 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 </description>
<instruction> TAKE COVER IN A SUBSTANTIAL SHELTER
UNTIL THE STORM PASSES </instruction>
<contact>BARUFFALDI/JUSKIE</contact>
<area>
<areaDesc> EXTREME NORTH CENTRAL TUOLUMNE COUNTY
IN CALIFORNIA, EXTREME NORTHEASTERN
CALAVERAS COUNTY IN CALIFORNIA, SOUTHWESTERN
ALPINE COUNTY IN CALIFORNIA </areaDesc>
<polygon> 38.47,-120.14 38.34,-119.95 38.52,-119.74
38.62,-119.89 38.47,-120.14 </polygon>
</area>
</info>
</alert>
2. IANA Considerations
2.1. Registration of the 'application/common-alerting-protocol+xml'
media type
Barnes, et al. Expires April 9, 2012 [Page 4]
Internet-Draft CAP MIME registration October 2011
To: ietf-types@iana.org
Subject: Registration of media type application/cap+xml
Type name: application
Subtype name: cap+xml
Required parameters: (none)
Optional parameters: charset; Indicates the character encoding of
the enclosed XML. Default is UTF-8 [RFC3629].
Encoding considerations: Uses XML, which can employ 8-bit
characters, depending on the character encoding used. See RFC
3023 [RFC3023], Section 3.2.
Security considerations: Transmission of CAP payloads does not
introduce new security risks
Interoperability considerations: CAP is widely used for emergency
management.
Published specification: RFC XXXX [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:
Magic number: (none)
File extension: .cap
Macintosh file type code: 'TEXT'
Person & email address to contact for further information: Hannes
Tschofenig, hannes.tschofenig@nsn.com
Intended usage: Limited use
Restrictions on usage: (none)
Author: The CAP format was originally standardized by OASIS [CAP].
This document was developed by the IETF ATOCA working group.
Barnes, et al. Expires April 9, 2012 [Page 5]
Internet-Draft CAP MIME registration October 2011
Change controller: The IESG <iesg@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/cap+xml.
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, "Common 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
1300 N 17th St
Arlington, VA 22209
US
Email: rbarnes@bbn.com
Barnes, et al. Expires April 9, 2012 [Page 6]
Internet-Draft CAP MIME registration October 2011
Brian Rosen
Neustar
470 Conrad Dr.
Mars, PA 16046
US
Email: br@brianrosen.net
Hannes Tschofenig
Nokia Siemens Networks
Linnoitustie 6
Espoo 02600
Finland
Phone: +358 (50) 4871445
Email: Hannes.Tschofenig@gmx.net
Barnes, et al. Expires April 9, 2012 [Page 7]
