< draft-ietf-ecrit-additional-data-27.txt		draft-ietf-ecrit-additional-data-28.txt >
	ECRIT R. Gellens		ECRIT R. Gellens
	Internet-Draft Qualcomm Technologies, Inc.		Internet-Draft Qualcomm Technologies, Inc.
	Intended status: Standards Track B. Rosen		Intended status: Standards Track B. Rosen
	Expires: June 18, 2015 NeuStar		Expires: August 8, 2015 NeuStar
	H. Tschofenig		H. Tschofenig
	(no affiliation)
	R. Marshall		R. Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	J. Winterbottom		J. Winterbottom
	(no affiliation)
	December 15, 2014		February 4, 2015
	Additional Data Related to an Emergency Call		Additional Data Related to an Emergency Call
	draft-ietf-ecrit-additional-data-27.txt		draft-ietf-ecrit-additional-data-28.txt
	Abstract		Abstract
	When an emergency call is sent to a Public Safety Answering Point		When an emergency call is sent to a Public Safety Answering Point
	(PSAP), the device that sends it, as well as any application service		(PSAP), the device that sends it, as well as any application service
	provider in the path of the call, or access network provider through		provider in the path of the call, or access network provider through
	which the call originated may have information about the call, the		which the call originated may have information about the call, the
	caller or the location which the PSAP may be able to use. This		caller or the location which the PSAP may be able to use. This
	document describes data structures and a mechanism to convey such		document describes data structures and a mechanism to convey such
	data to the PSAP. The mechanism uses a Uniform Resource Identifier		data to the PSAP. The mechanism uses a Uniform Resource Identifier
	skipping to change at page 2, line 4 ¶		skipping to change at page 2, line 4 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	This Internet-Draft will expire on June 18, 2015.		This Internet-Draft will expire on August 8, 2015.
	Copyright Notice		Copyright Notice
	Copyright (c) 2014 IETF Trust and the persons identified as the		Copyright (c) 2015 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	carefully, as they describe your rights and restrictions with respect		carefully, as they describe your rights and restrictions with respect
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Simplified BSD License text as described in Section 4.e of		include Simplified BSD License text as described in Section 4.e of
	the Trust Legal Provisions and are provided without warranty as		the Trust Legal Provisions and are provided without warranty as
	skipping to change at page 12, line 26 ¶		skipping to change at page 12, line 26 ¶
	4.1.7. xCard of Data Provider		4.1.7. xCard of Data Provider
	Data Element: xCard of Data Provider		Data Element: xCard of Data Provider
	Use: Optional		Use: Optional
	XML Element: <DataProviderContact>		XML Element: <DataProviderContact>
	Description: Per [RFC6351] the xcard structure is represented within		Description: Per [RFC6351] the xcard structure is represented within
	a <vcard> element, which is a child element of a <vcards> element.		a <vcard> element. Although multiple <vcard> elements may be
	The fact that a <vcard> element is contained within a <vcards>		contained in a structure only one <vcard> element SHOULD be
	element structurally permits multiple <vcard> elements, however,		provided. If more than one appears, the first SHOULD be used.
	only one <vcard> element SHOULD be provided. If more than one		There are many fields in the xCard and the creator of the data
	appears, the first SHOULD be used. There are many fields in the		structure is encouraged to provide as much information as they
	xCard and the creator of the data structure is encouraged to		have available. N, ORG, ADR, TEL, EMAIL are suggested at a
	provide as much information as they have available. N, ORG, ADR,		minimum. N SHOULD contain the name of the support group or device
	TEL, EMAIL are suggested at a minimum. N SHOULD contain the name		owner as appropriate. If more than one TEL property is provided,
	of the support group or device owner as appropriate. If more than		a parameter from the vCard Property Value registry MUST be
	one TEL property is provided, a parameter from the vCard Property		specified on each TEL. For encoding of the xCard this
	Value registry MUST be specified on each TEL. For encoding of the		specification uses the XML-based encoding specified in [RFC6351],
	xCard this specification uses the XML-based encoding specified in		referred to in this document as "xCard".
	[RFC6351], referred to in this document as "xCard".
	Reason for Need: Information needed to determine additional contact		Reason for Need: Information needed to determine additional contact
	information.		information.
	How Used by Call Taker: Assists the call taker by providing		How Used by Call Taker: Assists the call taker by providing
	additional contact information aside from what may be included in		additional contact information aside from what may be included in
	the SIP INVITE or the PIDF-LO.		the SIP INVITE or the PIDF-LO.
	4.1.8. Subcontractor Principal		4.1.8. Subcontractor Principal
	When the entity providing the data is a subcontractor, the Data		When the entity providing the data is a subcontractor, the Data
	Provider Type is set to that of the primary service provider and this		Provider Type is set to that of the primary service provider and this
	entry is supplied to provide information regarding the subcontracting		entry is supplied to provide information regarding the subcontracting
	entity.		entity.
	Data Element: Subcontractor Principal		Data Element: Subcontractor Principal
	Use: Conditional. This data is required if the entity providing the		Use: Conditional. This data is required if the entity providing the
	data is a subcontractor.		data is a subcontractor.
	XML Element: <SubcontratorPrincipal>		XML Element: <SubcontractorPrincipal>
	Description: Some providers outsource their obligations to handle		Description: Some providers outsource their obligations to handle
	aspects of emergency services to specialized providers. If the		aspects of emergency services to specialized providers. If the
	data provider is a subcontractor to another provider this element		data provider is a subcontractor to another provider this element
	contains the DataProviderString of the service provider to		contains the DataProviderString of the service provider to
	indicate which provider the subcontractor is working for.		indicate which provider the subcontractor is working for.
	Reason for Need: Identify the entity the subcontractor works for.		Reason for Need: Identify the entity the subcontractor works for.
	How Used by Call Taker: Allows the call taker to understand what the		How Used by Call Taker: Allows the call taker to understand what the
	skipping to change at page 14, line 16 ¶		skipping to change at page 14, line 13 ¶
	</ad:DataProviderReference>		</ad:DataProviderReference>
	<ad:DataProviderString>Example VoIP Provider		<ad:DataProviderString>Example VoIP Provider
	</ad:DataProviderString>		</ad:DataProviderString>
	<ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>		<ad:ProviderID>urn:nena:companyid:ID123</ad:ProviderID>
	<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>		<ad:ProviderIDSeries>NENA</ad:ProviderIDSeries>
	<ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider>		<ad:TypeOfProvider>Telecom Provider</ad:TypeOfProvider>
	<ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI>		<ad:ContactURI>tel:+1-201-555-0123</ad:ContactURI>
	<ad:Language>EN</ad:Language>		<ad:Language>EN</ad:Language>
	<ad:DataProviderContact		<ad:DataProviderContact
	xmlns="urn:ietf:params:xml:ns:vcard-4.0">		xmlns="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>
	<vcard>		<vcard>
	<fn><text>Hannes Tschofenig</text></fn>		<fn><text>Hannes Tschofenig</text></fn>
	<n>		<n>
	<surname>Hannes</surname>		<surname>Hannes</surname>
	<given>Tschofenig</given>		<given>Tschofenig</given>
	<additional/>		<additional/>
	<prefix/>		<prefix/>
	<suffix>Dipl. Ing.</suffix>		<suffix>Dipl. Ing.</suffix>
	</n>		</n>
	<bday><date>--0203</date></bday>		<bday><date>--0203</date></bday>
	skipping to change at page 15, line 47 ¶		skipping to change at page 15, line 43 ¶
	http://www.tschofenig.priv.at/key.asc		http://www.tschofenig.priv.at/key.asc
	</uri>		</uri>
	</key>		</key>
	<tz><text>Finland/Helsinki</text></tz>		<tz><text>Finland/Helsinki</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://www.tschofenig.priv.at</uri>		<uri>http://www.tschofenig.priv.at</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>
	</ad:DataProviderContact>		</ad:DataProviderContact>
	</ad:EmergencyCallData.ProviderInfo>		</ad:EmergencyCallData.ProviderInfo>
	Figure 2: EmergencyCallData.ProviderInfo Example.		Figure 2: EmergencyCallData.ProviderInfo Example.
	4.2. Service Information		4.2. Service Information
	This block describes the service that the service provider provides		This block describes the service that the service provider provides
	to the caller. It SHOULD be included by all SPs in the path of the		to the caller. It SHOULD be included by all SPs in the path of the
	call. The mime subtype is "application/		call. The mime subtype is "application/
	skipping to change at page 28, line 5 ¶		skipping to change at page 28, line 5 ¶
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<sub:EmergencyCallData.SubscriberInfo		<sub:EmergencyCallData.SubscriberInfo
	xmlns:sub=		xmlns:sub=
	"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"		"urn:ietf:params:xml:ns:EmergencyCallData:SubscriberInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	privacyRequested="false">		privacyRequested="false">
	<sub:DataProviderReference>FEABFECD901@example.org		<sub:DataProviderReference>FEABFECD901@example.org
	</sub:DataProviderReference>		</sub:DataProviderReference>
	<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">		<sub:SubscriberData xmlns="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>		<vcard>
	<vcard>
	<fn><text>Simon Perreault</text></fn>		<fn><text>Simon Perreault</text></fn>
	<n>		<n>
	<surname>Perreault</surname>		<surname>Perreault</surname>
	<given>Simon</given>		<given>Simon</given>
	<additional/>		<additional/>
	<prefix/>		<prefix/>
	<suffix>ing. jr</suffix>		<suffix>ing. jr</suffix>
	<suffix>M.Sc.</suffix>		<suffix>M.Sc.</suffix>
	</n>		</n>
	<bday><date>--0203</date></bday>		<bday><date>--0203</date></bday>
	skipping to change at page 29, line 48 ¶		skipping to change at page 29, line 47 ¶
	<uri>		<uri>
	http://www.viagenie.ca/simon.perreault/simon.asc		http://www.viagenie.ca/simon.perreault/simon.asc
	</uri>		</uri>
	</key>		</key>
	<tz><text>America/Montreal</text></tz>		<tz><text>America/Montreal</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://nomis80.org</uri>		<uri>http://nomis80.org</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>
	</sub:SubscriberData>		</sub:SubscriberData>
	</sub:EmergencyCallData.SubscriberInfo>		</sub:EmergencyCallData.SubscriberInfo>
	Figure 8: EmergencyCallData.SubscriberInfo Example.		Figure 8: EmergencyCallData.SubscriberInfo Example.
	4.5. Comment		4.5. Comment
	This block provides a mechanism for the data provider to supply		This block provides a mechanism for the data provider to supply
	extra, human readable information to the PSAP. It is not intended		extra, human readable information to the PSAP. It is not intended
	for a general purpose extension mechanism nor does it aim to provide		for a general purpose extension mechanism nor does it aim to provide
	machine-readable content. The mime subtype is "application/		machine-readable content. The mime subtype is "application/
	EmergencyCallData.Comment+xml"		EmergencyCallData.Comment+xml"
	skipping to change at page 39, line 10 ¶		skipping to change at page 39, line 10 ¶
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]		<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
	</pi:DataProviderReference>		</pi:DataProviderReference>
	<pi:DataProviderString>Hannes Tschofenig		<pi:DataProviderString>Hannes Tschofenig
	</pi:DataProviderString>		</pi:DataProviderString>
	<pi:TypeOfProvider>Other</pi:TypeOfProvider>		<pi:TypeOfProvider>Other</pi:TypeOfProvider>
	<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>		<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
	<pi:Language>EN</pi:Language>		<pi:Language>EN</pi:Language>
	<xc:DataProviderContact		<xc:DataProviderContact
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>
	<vcard>		<vcard>
	<fn><text>Hannes Tschofenig</text></fn>		<fn><text>Hannes Tschofenig</text></fn>
	<n>		<n>
	<surname>Hannes</surname>		<surname>Hannes</surname>
	<given>Tschofenig</given>		<given>Tschofenig</given>
	<additional/>		<additional/>
	<prefix/>		<prefix/>
	<suffix>Dipl. Ing.</suffix>		<suffix>Dipl. Ing.</suffix>
	</n>		</n>
	<bday><date>--0203</date></bday>		<bday><date>--0203</date></bday>
	skipping to change at page 40, line 37 ¶		skipping to change at page 40, line 36 ¶
	</uri>		</uri>
	</key>		</key>
	<tz><text>Finland/Helsinki</text></tz>		<tz><text>Finland/Helsinki</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://example.com/hannes.tschofenig		<uri>http://example.com/hannes.tschofenig
	</uri>		</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>
	</xc:DataProviderContact>		</xc:DataProviderContact>
	</pi:EmergencyCallData.ProviderInfo>		</pi:EmergencyCallData.ProviderInfo>
	--boundary1--		--boundary1--
	Figure 12: End Device sending SIP INVITE with Additional Data.		Figure 12: End Device sending SIP INVITE with Additional Data.
	In this example, information available to the access network provider		In this example, information available to the access network provider
	is included in the call setup message only indirectly via the use of		is included in the call setup message only indirectly via the use of
	the location reference. The PSAP has to retrieve it via a separate		the location reference. The PSAP has to retrieve it via a separate
	look-up step. Since the access network provider and the VoIP service		look-up step. Since the access network provider and the VoIP service
	skipping to change at page 42, line 4 ¶		skipping to change at page 41, line 49 ¶
	Contact: <sips:hannes@example.com>		Contact: <sips:hannes@example.com>
	Content-Type: multipart/mixed; boundary=boundary1		Content-Type: multipart/mixed; boundary=boundary1
	Content-Length: ...		Content-Length: ...
	--boundary1		--boundary1
	Content-Type: application/sdp		Content-Type: application/sdp
	...SDP goes here		...SDP goes here
	--boundary1--
			--boundary1--
	Content-Type: application/EmergencyCallData.DeviceInfo+xml		Content-Type: application/EmergencyCallData.DeviceInfo+xml
	Content-ID: <0123456789@atlanta.example.com>		Content-ID: <0123456789@atlanta.example.com>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<dev:EmergencyCallData.DeviceInfo		<dev:EmergencyCallData.DeviceInfo
	xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"		xmlns:dev="urn:ietf:params:xml:ns:EmergencyCallData:DeviceInfo"
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]		<dev:DataProviderReference>d4b3072df09876543@[93.184.216.119]
	</dev:DataProviderReference>		</dev:DataProviderReference>
	skipping to change at page 42, line 39 ¶		skipping to change at page 42, line 37 ¶
	xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">		xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]		<pi:DataProviderReference>d4b3072df09876543@[93.184.216.119]
	</pi:DataProviderReference>		</pi:DataProviderReference>
	<pi:DataProviderString>Hannes Tschofenig		<pi:DataProviderString>Hannes Tschofenig
	</pi:DataProviderString>		</pi:DataProviderString>
	<pi:TypeOfProvider>Other</pi:TypeOfProvider>		<pi:TypeOfProvider>Other</pi:TypeOfProvider>
	<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>		<pi:ContactURI>tel:+1-555-555-0123</pi:ContactURI>
	<pi:Language>EN</pi:Language>		<pi:Language>EN</pi:Language>
	<xc:DataProviderContact		<xc:DataProviderContact
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>
	<vcard>		<vcard>
	<fn><text>Hannes Tschofenig</text></fn>		<fn><text>Hannes Tschofenig</text></fn>
	<n>		<n>
	<surname>Hannes</surname>		<surname>Hannes</surname>
	<given>Tschofenig</given>		<given>Tschofenig</given>
	<additional/>		<additional/>
	<prefix/>		<prefix/>
	<suffix>Dipl. Ing.</suffix>		<suffix>Dipl. Ing.</suffix>
	</n>		</n>
	<bday><date>--0203</date></bday>		<bday><date>--0203</date></bday>
	skipping to change at page 44, line 18 ¶		skipping to change at page 44, line 15 ¶
	</uri>		</uri>
	</key>		</key>
	<tz><text>Finland/Helsinki</text></tz>		<tz><text>Finland/Helsinki</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://example.com/hannes.tschofenig		<uri>http://example.com/hannes.tschofenig
	</uri>		</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>
	</xc:DataProviderContact>		</xc:DataProviderContact>
	</pi:EmergencyCallData.ProviderInfo>		</pi:EmergencyCallData.ProviderInfo>
	--boundary1--		--boundary1--
	Content-Type: application/EmergencyCallData.ServiceInfo+xml		Content-Type: application/EmergencyCallData.ServiceInfo+xml
	Content-ID: <bloorpyhex@atlanta.example.com>		Content-ID: <bloorpyhex@atlanta.example.com>
	Content-Disposition: by-reference;handling=optional		Content-Disposition: by-reference;handling=optional
	<?xml version="1.0" encoding="UTF-8"?>		<?xml version="1.0" encoding="UTF-8"?>
	<svc:EmergencyCallData.ServiceInfo		<svc:EmergencyCallData.ServiceInfo
	skipping to change at page 45, line 10 ¶		skipping to change at page 45, line 6 ¶
	</pi:DataProviderReference>		</pi:DataProviderReference>
	<pi:DataProviderString>Example VoIP Provider		<pi:DataProviderString>Example VoIP Provider
	</pi:DataProviderString>		</pi:DataProviderString>
	<pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID>		<pi:ProviderID>urn:nena:companyid:ID123</pi:ProviderID>
	<pi:ProviderIDSeries>NENA</pi:ProviderIDSeries>		<pi:ProviderIDSeries>NENA</pi:ProviderIDSeries>
	<pi:TypeOfProvider>Service Provider</pi:TypeOfProvider>		<pi:TypeOfProvider>Service Provider</pi:TypeOfProvider>
	<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI>		<pi:ContactURI>sip:voip-provider@example.com</pi:ContactURI>
	<pi:Language>EN</pi:Language>		<pi:Language>EN</pi:Language>
	<xc:DataProviderContact		<xc:DataProviderContact
	xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">		xmlns:xc="urn:ietf:params:xml:ns:vcard-4.0">
	<vcards>
	<vcard>		<vcard>
	<fn><text>John Doe</text></fn>		<fn><text>John Doe</text></fn>
	<n>		<n>
	<surname>John</surname>		<surname>John</surname>
	<given>Doe</given>		<given>Doe</given>
	<additional/>		<additional/>
	<prefix/>		<prefix/>
	<suffix/>		<suffix/>
	</n>		</n>
	<bday><date>--0203</date></bday>		<bday><date>--0203</date></bday>
	skipping to change at page 46, line 28 ¶		skipping to change at page 46, line 23 ¶
	</parameters>		</parameters>
	<uri>geo:51.503396, 0.127640</uri>		<uri>geo:51.503396, 0.127640</uri>
	</geo>		</geo>
	<tz><text>Europe/London</text></tz>		<tz><text>Europe/London</text></tz>
	<url>		<url>
	<parameters><type><text>home</text></type>		<parameters><type><text>home</text></type>
	</parameters>		</parameters>
	<uri>http://www.example.com/john.doe</uri>		<uri>http://www.example.com/john.doe</uri>
	</url>		</url>
	</vcard>		</vcard>
	</vcards>
	</xc:DataProviderContact>		</xc:DataProviderContact>
	</pi:EmergencyCallData.ProviderInfo>		</pi:EmergencyCallData.ProviderInfo>
	Figure 13: VoIP Provider sending SIP INVITE with Additional Data.		Figure 13: VoIP Provider sending SIP INVITE with Additional Data.
	Finally, the PSAP requests location information from the access		Finally, the PSAP requests location information from the access
	network provider. The response is shown in Figure 14. Along with		network provider. The response is shown in Figure 14. Along with
	the location information, additional data is provided in the		the location information, additional data is provided in the
	<provided-by> element of the PIDF-LO. This request and response is		<provided-by> element of the PIDF-LO. This request and response is
	step #4.		step #4.
	skipping to change at page 49, line 37 ¶		skipping to change at page 49, line 31 ¶
	<xs:element name="TypeOfProvider"		<xs:element name="TypeOfProvider"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="ContactURI" type="xs:anyURI"		<xs:element name="ContactURI" type="xs:anyURI"
	minOccurs="1" maxOccurs="1"/>		minOccurs="1" maxOccurs="1"/>
	<xs:element name="Language" type="pi:iso3166a2"		<xs:element name="Language" type="pi:iso3166a2"
	minOccurs="1" maxOccurs="unbounded" />		minOccurs="1" maxOccurs="unbounded" />
	<xs:element name="DataProviderContact"		<xs:element name="DataProviderContact">
	type="xc:vcardType" minOccurs="0"		<xs:complexType>
	maxOccurs="1"/>		<xs:sequence>
			<xs:element minOccurs="0"
			maxOccurs="unbounded" ref="xc:vcard"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
	<xs:element name="SubcontratorPrincipal"		<xs:element name="SubcontractorPrincipal"
	type="xs:string" minOccurs="0" maxOccurs="1"/>		type="xs:string" minOccurs="0" maxOccurs="1"/>
	<xs:element name="SubcontractorPriority"		<xs:element name="SubcontractorPriority"
	type="pi:SubcontractorPriorityType"		type="pi:SubcontractorPriorityType"
	minOccurs="0" maxOccurs="1"/>		minOccurs="0" maxOccurs="1"/>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	</xs:complexType>		</xs:complexType>
	skipping to change at page 53, line 26 ¶		skipping to change at page 52, line 41 ¶
	<xs:import namespace="http://www.w3.org/XML/1998/namespace"		<xs:import namespace="http://www.w3.org/XML/1998/namespace"
	schemaLocation="http://www.w3.org/2001/xml.xsd"/>		schemaLocation="http://www.w3.org/2001/xml.xsd"/>
	<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>		<xs:import namespace="urn:ietf:params:xml:ns:vcard-4.0"/>
	<xs:element name="EmergencyCallData.SubscriberInfo"		<xs:element name="EmergencyCallData.SubscriberInfo"
	type="sub:SubscriberInfoType"/>		type="sub:SubscriberInfoType"/>
	<xs:complexType name="SubscriberInfoType">		<xs:complexType name="SubscriberInfoType">
	<xs:complexContent>		<xs:complexContent>
			<xs:restriction base="xs:anyType">
	<xs:sequence>		<xs:sequence>
	<xs:element name="DataProviderReference"		<xs:element name="DataProviderReference"
	type="xs:token" minOccurs="1" maxOccurs="1"/>		type="xs:token" minOccurs="1" maxOccurs="1"/>
	<xs:element name="SubscriberData"		<xs:element name="SubscriberData">
	type="xc:vcardType"		<xs:complexType>
	minOccurs="0" maxOccurs="1" />		<xs:sequence>
			<xs:element maxOccurs="unbounded"
			ref="xc:vcard"/>
			</xs:sequence>
			</xs:complexType>
			</xs:element>
	<xs:any namespace="##other" processContents="lax"		<xs:any namespace="##other" processContents="lax"
	minOccurs="0" maxOccurs="unbounded"/>		minOccurs="0" maxOccurs="unbounded"/>
	</xs:sequence>		</xs:sequence>
	<xs:attribute name="privacyRequested" type="xs:boolean"		<xs:attribute name="privacyRequested" type="xs:boolean"
	use="required"/>		use="required"/>
			</xs:restriction>
	</xs:complexContent>		</xs:complexContent>
	</xs:complexType>		</xs:complexType>
	</xs:schema>		</xs:schema>
	Figure 18: EmergencyCallData.SubscriberInfo XML Schema.		Figure 18: EmergencyCallData.SubscriberInfo XML Schema.
	7.5. EmergencyCallData.Comment XML Schema		7.5. EmergencyCallData.Comment XML Schema
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	skipping to change at page 79, line 42 ¶		skipping to change at page 79, line 42 ¶
	11. Acknowledgments		11. Acknowledgments
	This work was originally started in NENA and has benefitted from a		This work was originally started in NENA and has benefitted from a
	large number of participants in NENA standardization efforts,		large number of participants in NENA standardization efforts,
	originally in the Long Term Definition Working Group, the Data		originally in the Long Term Definition Working Group, the Data
	Technical Committee and most recently the Additional Data working		Technical Committee and most recently the Additional Data working
	group. The authors are grateful for the initial work and extended		group. The authors are grateful for the initial work and extended
	comments provided by many NENA participants, including Delaine		comments provided by many NENA participants, including Delaine
	Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James		Arnold, Marc Berryman, Guy Caron, Mark Fletcher, Brian Dupras, James
	Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra,		Leyerle, Kathy McMahon, Christian, Militeau, Ira Pyles, Matt Serra,
	and Robert (Bob) Sherry.		and Robert (Bob) Sherry. Amursana Khiyod, Robert Sherry, Frank
			Rahoi, Scott Ross, Tom Klepetka provided valuable feedback regarding
			the vCard/xCard use in this specification.
	We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin		We would also like to thank Paul Kyzivat, Gunnar Hellstrom, Martin
	Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris		Thomson, Keith Drage, Laura Liess, Chris Santer, Barbara Stark, Chris
	Santer, and Archie Cobbs for their review comments. Guy Caron		Santer, and Archie Cobbs for their review comments. Guy Caron
	deserves special mention for his detailed and extensive review		deserves special mention for his detailed and extensive review
	comments.		comments.
	12. References		12. References
	12.1. Normative References		12.1. Normative References
	skipping to change at page 105, line 25 ¶		skipping to change at page 105, line 25 ¶
	Brian Rosen		Brian Rosen
	NeuStar		NeuStar
	470 Conrad Dr.		470 Conrad Dr.
	Mars, PA 16046		Mars, PA 16046
	US		US
	Phone: +1 724 382 1051		Phone: +1 724 382 1051
	Email: br@brianrosen.net		Email: br@brianrosen.net
	Hannes Tschofenig		Hannes Tschofenig
	(no affiliation)		Hall in Tirol 6060
			Austria
	Email: Hannes.Tschofenig@gmx.net		Email: Hannes.tschofenig@gmx.net
	URI: http://www.tschofenig.priv.at		URI: http://www.tschofenig.priv.at
	Roger Marshall		Roger Marshall
	TeleCommunication Systems, Inc.		TeleCommunication Systems, Inc.
	2401 Elliott Avenue		2401 Elliott Avenue
	Seattle, WA 98121		Seattle, WA 98121
	US		US
	Phone: +1 206 792 2424		Phone: +1 206 792 2424
	Email: rmarshall@telecomsys.com		Email: rmarshall@telecomsys.com
	URI: http://www.telecomsys.com		URI: http://www.telecomsys.com
	James Winterbottom		James Winterbottom
	(no affiliation)
	AU		AU
	Email: a.james.winterbottom@gmail.com		Email: a.james.winterbottom@gmail.com
End of changes. 30 change blocks.
	45 lines changed or deleted		50 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/