One document matched: draft-barnes-atoca-cap-mime-00.xml

<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd">
<?rfc toc="yes"?>
<?rfc tocompact="yes"?>
<?rfc tocdepth="3"?>
<?rfc tocindent="yes"?>
<?rfc symrefs="yes"?>
<?rfc sortrefs="yes"?>
<?rfc comments="yes"?>
<?rfc inline="yes"?>
<?rfc compact="yes"?>
<?rfc subcompact="no"?>
<rfc category="std" docName="draft-barnes-atoca-cap-mime-00" ipr="trust200902">
  <front>
    <title abbrev="CAP MIME registration">Media Type Registration for Common
    Alerting Protocol</title>

    <author fullname="Richard Barnes" initials="R.L." surname="Barnes">
      <organization>BBN Technologies</organization>

      <address>
        <postal>
          <street>9861 Broken Land Parkway</street>

          <city>Columbia</city>

          <region>MD</region>

          <code>21046</code>

          <country>US</country>
        </postal>

        <phone>+1 410 290 6169</phone>
      </address>
    </author>

    <author fullname="Brian Rosen" initials="B." surname="Rosen">
      <organization>Neustar</organization>

      <address>
        <postal>
          <street></street>

          <city></city>

          <region></region>

          <code></code>

          <country></country>
        </postal>

        <phone></phone>

        <facsimile></facsimile>

        <email></email>

        <uri></uri>
      </address>
    </author>

    <date month="October" year="2011" />

    <abstract>
      <t>This document registers the media type
      "application/common-alerting-protocol+xml" for Common Alerting Protocol
      (CAP) format .</t>
    </abstract>

    <note title="Requirements Language">
      <t>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 <xref
      target="RFC2119">RFC 2119</xref>.</t>
    </note>
  </front>

  <middle>
    <section title="Introduction">
      <t>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:</t>

      <figure>
        <artwork><![CDATA[   <?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>

]]></artwork>
      </figure>
    </section>

    <section anchor="IANA" title="IANA Considerations">
      <t></t>

      <section title="Registration of the 'application/common-alerting-protocol+xml' media type">
        <t><list style="hanging">
            <t hangText="To: ">ietf-types@iana.org</t>

            <t hangText="Subject: ">Registration of MIME media type
            application/ common- alerting-protocol+xml</t>

            <t hangText="MIME media type name: ">application</t>

            <t hangText="MIME subtype name: ">common-alerting-protocol+xml</t>

            <t hangText="Required parameters: ">(none)</t>

            <t hangText="Optional parameters: ">charset; Indicates the
            character encoding of the enclosed XML. Default is UTF-8 <xref
            target="RFC3629"></xref>.</t>

            <t hangText="Security considerations: ">Transmission of CAP
            payloads does not introduce new security risks</t>

            <t hangText="Interoperability considerations: ">CAP is widely used
            for emergency management.</t>

            <t hangText="Published specification: ">RFC XXX [Replace by the
            RFC number of this specification].</t>

            <t
            hangText="Applications which use this media type: ">Applications
            that convey alerts and early warnings according to the CAP
            standard.</t>

            <t hangText="Additional information: ">OASIS has published the
            Common Alerting Protocol specification <xref
            target="CAP"></xref>.</t>

            <t
            hangText="Person & email address to contact for further information: ">Hannes
            Tschofenig, hannes.tschofenig@nsn.com</t>

            <t hangText="Intended usage: ">Limited use</t>

            <t hangText="Author/Change controller: ">IETF ATOCA working
            group</t>

            <t hangText="Other information: ">This media type is a
            specialization of application/xml <xref target="RFC3023"></xref>,
            and many of the considerations described there also apply to
            application/ common-alerting-protocol+xml.</t>
          </list></t>
      </section>
    </section>

    <section anchor="Security" title="Security Considerations">
      <t>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.</t>
    </section>
  </middle>

  <back>
    <references title="Normative References">
      <?rfc ?>

      <reference anchor="CAP">
        <front>
          <title>ommon Alerting Protocol v1.1</title>

          <author fullname="" initials="A" surname="Botterell">
            <organization></organization>
          </author>

          <author initials="E." surname="Jones">
            <organization>J</organization>

            <address>
              <postal>
                <street></street>

                <city></city>

                <region></region>

                <code></code>

                <country></country>
              </postal>

              <phone></phone>

              <facsimile></facsimile>

              <email></email>

              <uri></uri>
            </address>
          </author>

          <date month="October" year="2005" />
        </front>
      </reference>

      <?rfc include="reference.RFC.2119"?>

      <?rfc include="reference.RFC.3023"?>

      <?rfc include="reference.RFC.3629"?>
    </references>
  </back>
</rfc>