idnits 2.17.00 (12 Aug 2021) /tmp/idnits15402/draft-barnes-atoca-cap-mime-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- The document date (October 6, 2011) is 3879 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. 'CAP' ** Obsolete normative reference: RFC 3023 (Obsoleted by RFC 7303) Summary: 1 error (**), 0 flaws (~~), 2 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group R. Barnes 3 Internet-Draft BBN Technologies 4 Intended status: Standards Track B. Rosen 5 Expires: April 8, 2012 Neustar 6 October 6, 2011 8 Media Type Registration for Common Alerting Protocol 9 draft-barnes-atoca-cap-mime-00 11 Abstract 13 This document registers the media type "application/ 14 common-alerting-protocol+xml" for Common Alerting Protocol (CAP) 15 format . 17 Requirements Language 19 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 21 document are to be interpreted as described in RFC 2119 [RFC2119]. 23 Status of this Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at http://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on April 8, 2012. 40 Copyright Notice 42 Copyright (c) 2011 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (http://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 58 2. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4 59 2.1. Registration of the 60 'application/common-alerting-protocol+xml' media type . . . 4 61 3. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 62 4. Normative References . . . . . . . . . . . . . . . . . . . . . 5 63 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 5 65 1. Introduction 67 The Common Alerting Protocol (CAP) [cap] is an XML document format 68 for exchanging emergency alerts and public warnings. This document 69 registers a media type for CAP documents. The following is an 70 example of a CAP message for a severe thunderstorm warning: 71 73 74 KSTO1055887203 75 KSTO@NWS.NOAA.GOV 76 2003-06-17T14:57:00-07:00 77 Actual 78 Alert 79 Public 80 81 Met 82 SEVERE THUNDERSTORM 83 Severe 84 Likely 85 NATIONAL WEATHER SERVICE SACRAMENTO 86 SEVERE THUNDERSTORM WARNING 87 AT 254 PM PDT... 88 NATIONAL WEATHER SERVICE 89 DOPPLER RADAR INDICATED A SEVERE 90 THUNDERSTORM OVER SOUTH CENTRAL ALPINE COUNTY... 91 OR ABOUT 18 MILES SOUTHEAST OF 92 KIRKWOOD... MOVING SOUTHWEST AT 5 MPH. HAIL... 93 INTENSE RAIN AND STRONG DAMAGING WINDS 94 ARE LIKELY WITH THIS STORM 95 TAKE COVER IN A SUBSTANTIAL SHELTER 96 UNTIL THE STORM PASSES 97 BARUFFALDI/JUSKIE 98 99 EXTREME NORTH CENTRAL TUOLUMNE COUNTY 100 IN CALIFORNIA, EXTREME NORTHEASTERN 101 CALAVERAS COUNTY IN CALIFORNIA, SOUTHWESTERN 102 ALPINE COUNTY IN CALIFORNIA 103 38.47,-120.14 38.34,-119.95 38.52,-119.74 104 38.62,-119.89 38.47,-120.14 105 106 107 109 2. IANA Considerations 111 2.1. Registration of the 'application/common-alerting-protocol+xml' 112 media type 114 To: ietf-types@iana.org 116 Subject: Registration of MIME media type application/ common- 117 alerting-protocol+xml 119 MIME media type name: application 121 MIME subtype name: common-alerting-protocol+xml 123 Required parameters: (none) 125 Optional parameters: charset; Indicates the character encoding of 126 the enclosed XML. Default is UTF-8 [RFC3629]. 128 Security considerations: Transmission of CAP payloads does not 129 introduce new security risks 131 Interoperability considerations: CAP is widely used for emergency 132 management. 134 Published specification: RFC XXX [Replace by the RFC number of this 135 specification]. 137 Applications which use this media type: Applications that convey 138 alerts and early warnings according to the CAP standard. 140 Additional information: OASIS has published the Common Alerting 141 Protocol specification [CAP]. 143 Person & email address to contact for further information: Hannes 144 Tschofenig, hannes.tschofenig@nsn.com 146 Intended usage: Limited use 148 Author/Change controller: IETF ATOCA working group 150 Other information: This media type is a specialization of 151 application/xml [RFC3023], and many of the considerations 152 described there also apply to application/ common-alerting- 153 protocol+xml. 155 3. Security Considerations 157 The introduction of the CAP MIME type does not present any new risks 158 in itself. CAP messages are used to encode emergency alerts, which 159 means that false CAP messages can have significant negative effects, 160 such as the unnecessary evacuation of an area. Systems that process 161 CAP messages will need to have mechanisms for integrity protection 162 and origin authentication, in order to ensure either that end alert 163 recipients do not receive false alerts or that they can distinguish 164 valid alerts from false alerts. 166 4. Normative References 168 [CAP] Botterell, A. and E. Jones, "ommon Alerting Protocol 169 v1.1", October 2005. 171 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 172 Requirement Levels", BCP 14, RFC 2119, March 1997. 174 [RFC3023] Murata, M., St. Laurent, S., and D. Kohn, "XML Media 175 Types", RFC 3023, January 2001. 177 [RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO 178 10646", STD 63, RFC 3629, November 2003. 180 Authors' Addresses 182 Richard Barnes 183 BBN Technologies 184 9861 Broken Land Parkway 185 Columbia, MD 21046 186 US 188 Phone: +1 410 290 6169 190 Brian Rosen 191 Neustar 193 Phone: 194 Fax: 195 Email: 196 URI: