<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-ecrit-additional-data" target="https://datatracker.ietf.org/doc/html/draft-ietf-ecrit-additional-data-38">
   <front>
      <title>Additional Data Related to an Emergency Call</title>
      <author initials="R." surname="Gellens" fullname="Randall Gellens">
         </author>
      <author initials="B." surname="Rosen" fullname="Brian Rosen">
         <organization>NeuStar</organization>
      </author>
      <author initials="H." surname="Tschofenig" fullname="Hannes Tschofenig">
         </author>
      <author initials="R." surname="Marshall" fullname="Roger Marshall">
         <organization>TeleCommunication Systems</organization>
      </author>
      <author initials="J." surname="Winterbottom" fullname="James Winterbottom">
         <organization>Winterb Consulting Services</organization>
      </author>
      <date month="April" day="5" year="2016" />
      <abstract>
	 <t>When an emergency call is sent to a Public Safety Answering Point (PSAP), the originating device, the access network provider to which the device is connected, and all service providers in the path of the call have information about the call, the caller, or the location, which is helpful for the PSAP to have in handling the emergency. This document describes data structures and mechanisms to convey such data to the PSAP. The intent is that every emergency call carry as much of the information described here as possible using the mechanisms described here.

 The mechanisms permit the data to be conveyed by reference (as an external resource) or by value (within the body of a SIP message or a location object). This follows the tradition of prior emergency services standardization work where data can be conveyed by value within the call signaling (i.e., in the body of the SIP message) or by reference.
	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-ecrit-additional-data-38" />
   
</reference>
