Media Type Registration for Common
Alerting ProtocolBBN Technologies1300 N 17th StArlingtonVA22209USrbarnes@bbn.comNeustar470 Conrad Dr.MarsPA16046USbr@brianrosen.netNokia Siemens NetworksLinnoitustie 6Espoo02600Finland+358 (50) 4871445Hannes.Tschofenig@gmx.netThis document registers the media type "application/cap+xml" for
Common Alerting Protocol (CAP) format .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.The Common Alerting Protocol (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:ietf-types@iana.orgRegistration of media type
application/cap+xmlapplicationcap+xml(none)charset; Indicates the
character encoding of the enclosed XML. Default is UTF-8 .Uses XML, which can employ
8-bit characters, depending on the character encoding used. See
RFC 3023 , Section 3.2.Transmission of CAP
payloads does not introduce new security risksCAP is widely used
for emergency management.RFC XXXX [Replace by the
RFC number of this specification].Applications
that convey alerts and early warnings according to the CAP
standard.(none).cap'TEXT'Hannes
Tschofenig, hannes.tschofenig@nsn.comLimited use(none)The CAP format was originally standardized
by OASIS . This document was developed
by the IETF ATOCA working group.The IESG
<iesg@ietf.org>This media type is a
specialization of application/xml ,
and many of the considerations described there also apply to
application/cap+xml.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.Common Alerting Protocol v1.1J