< draft-ietf-ecrit-similar-location-14.txt		draft-ietf-ecrit-similar-location-15.txt >
	ECRIT B. Rosen		ECRIT B. Rosen
	Internet-Draft		Internet-Draft
	Updates: 5222 (if approved) R. Marshall		Updates: 5222 (if approved) R. Marshall
	Intended status: Standards Track J. Martin		Intended status: Standards Track J. Martin
	Expires: 2 June 2022 Comtech TCS		Expires: 15 July 2022 Comtech TCS
	29 November 2021		11 January 2022
	A LoST extension to return complete and similar location info		A LoST extension to return complete and similar location info
	draft-ietf-ecrit-similar-location-14		draft-ietf-ecrit-similar-location-15
	Abstract		Abstract
	This document introduces a new way to provide returned location		This document introduces a new way to provide returned location
	information in LoST responses that is either of a completed or		information in LoST responses that is either of a completed or
	similar form to the original input civic location, based on whether		similar form to the original input civic location, based on whether
	valid or invalid civic address elements are returned within the		valid or invalid civic address elements are returned within the
	<findServiceResponse> message. This document defines a new extension		<findServiceResponse> message. This document defines a new extension
	to the <findServiceResponse> message within the LoST protocol		to the <findServiceResponse> message within the LoST protocol
	[RFC5222] that enables the LoST protocol to return in a response a		(RFC5222) that enables the LoST protocol to return in a response a
	completed civic address element set for a valid location response,		completed civic address element set for a valid location response,
	and one or more suggested sets of similar location information for an		and one or more suggested sets of similar location information for an
	invalid location. These two types of civic addresses are referred to		invalid location. These two types of civic addresses are referred to
	as either "complete location" or "similar location", and are included		as either "complete location" or "similar location", and are included
	as a compilation of CAtype xml elements within the existing LoST		as a compilation of CAtype xml elements within the existing LoST
	<findServiceResponse> message structure.		<findServiceResponse> message structure.
	Status of This Memo		Status of This Memo
	This Internet-Draft is submitted in full conformance with the		This Internet-Draft is submitted in full conformance with the
	skipping to change at page 1, line 44 ¶		skipping to change at page 1, line 44 ¶
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 2 June 2022.		This Internet-Draft will expire on 15 July 2022.
	Copyright Notice		Copyright Notice
	Copyright (c) 2021 IETF Trust and the persons identified as the		Copyright (c) 2022 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 (https://trustee.ietf.org/		Provisions Relating to IETF Documents (https://trustee.ietf.org/
	license-info) in effect on the date of publication of this document.		license-info) in effect on the date of publication of this document.
	Please review these documents carefully, as they describe your rights		Please review these documents carefully, as they describe your rights
	and restrictions with respect to this document. Code Components		and restrictions with respect to this document. Code Components
	extracted from this document must include Revised BSD License text as		extracted from this document must include Revised BSD License text as
	described in Section 4.e of the Trust Legal Provisions and are		described in Section 4.e of the Trust Legal Provisions and are
	provided without warranty as described in the Revised BSD License.		provided without warranty as described in the Revised BSD License.
	skipping to change at page 2, line 35 ¶		skipping to change at page 2, line 35 ¶
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16
	8.1. XML Schema Registration . . . . . . . . . . . . . . . . . 16		8.1. XML Schema Registration . . . . . . . . . . . . . . . . . 16
	8.2. LoST-RLI Namespace Registration . . . . . . . . . . . . . 16		8.2. LoST-RLI Namespace Registration . . . . . . . . . . . . . 16
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17		9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
	9.1. Normative References . . . . . . . . . . . . . . . . . . 17		9.1. Normative References . . . . . . . . . . . . . . . . . . 17
	9.2. Informative References . . . . . . . . . . . . . . . . . 18		9.2. Informative References . . . . . . . . . . . . . . . . . 18
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
	1. Introduction		1. Introduction
	The LoST protcol [RFC5222] supports the validation of civic location		The LoST protocol [RFC5222] supports the validation of civic location
	information sent in a <findService> request, by providing a set of		information sent in a <findService> request, by providing a set of
	validation result status indicators in the response. The current		validation result status indicators in the response. The current
	usefulness of the supported xml elements <valid>, <invalid>, and		usefulness of the supported xml elements <valid>, <invalid>, and
	<unchecked> is limited. They each provide an indication of validity		<unchecked> is limited. They each provide an indication of validity
	for any one location element as a part of the whole civic address,		for any one location element as a part of the whole civic address,
	but this is insufficient in providing either the complete set of		but this is insufficient in providing either the complete set of
	civic address elements that the LoST server contains, or of providing		civic address elements that the LoST server contains, or of providing
	alternate suggestions (hints) as to which civic address is intended		alternate suggestions (hints) as to which civic address is intended
	for use.		for use.
	skipping to change at page 11, line 4 ¶		skipping to change at page 11, line 4 ¶
	<HNO>6000</HNO>		<HNO>6000</HNO>
	</civicAddress>		</civicAddress>
	</location>		</location>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	</findService>		</findService>
	<!-- =====Response================================== -->		<!-- =====Response================================== -->
	<findServiceResponse >		<findServiceResponse
	xmlns="urn:ietf:params:xml:ns:lost1"		xmlns="urn:ietf:params:xml:ns:lost1"
	xmlns:rli="urn:ietf:params:xml:ns:lost-rli1">		xmlns:rli="urn:ietf:params:xml:ns:lost-rli1"
	xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">		xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	<mapping		<mapping
	expires="NO-CACHE"		expires="NO-CACHE"
	lastUpdated="2006-11-01T01:00:00Z"		lastUpdated="2006-11-01T01:00:00Z"
	source="authoritative.example"		source="authoritative.example"
	sourceId="8799e346000098aa3e">		sourceId="8799e346000098aa3e">
	<displayName xml:lang="en">Leets 911</displayName>		<displayName xml:lang="en">Leets 911</displayName>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	skipping to change at page 12, line 46 ¶		skipping to change at page 12, line 46 ¶
	</civicAddress>		</civicAddress>
	</location>		</location>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	</findService>		</findService>
	<!-- =====Response=================================== -->		<!-- =====Response=================================== -->
	<findServiceResponse>		<findServiceResponse
	xmlns="urn:ietf:params:xml:ns:lost1"		xmlns="urn:ietf:params:xml:ns:lost1"
	xmlns:rli="urn:ietf:params:xml:ns:lost-rli1">		xmlns:rli="urn:ietf:params:xml:ns:lost-rli1"
	xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">		xmlns:ca="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
	<mapping		<mapping
	expires="NO-CACHE"		expires="NO-CACHE"
	lastUpdated="2006-11-01T01:00:00Z"		lastUpdated="2006-11-01T01:00:00Z"
	source="authoritative.example"		source="authoritative.example"
	sourceId="8799e346000098aa3e">		sourceId="8799e346000098aa3e">
	<displayName xml:lang="en">Leets 911</displayName>		<displayName xml:lang="en">Leets 911</displayName>
	<service>urn:service:sos</service>		<service>urn:service:sos</service>
	<uri>sip:leets-911@example.com</uri>		<uri>sip:leets-911@example.com</uri>
	skipping to change at page 15, line 36 ¶		skipping to change at page 15, line 36 ¶
	<!-- extend locationValidation by placing the following		<!-- extend locationValidation by placing the following
	at the extensionPoint -->		at the extensionPoint -->
	<xs:group>		<xs:group>
	<xs:choice minOccurs="0">		<xs:choice minOccurs="0">
	<xs:element name="similarLocation"		<xs:element name="similarLocation"
	type="lost1:locationInformation"		type="lost1:locationInformation"
	minOccurs="1" maxOccurs="unbounded" />		minOccurs="1" maxOccurs="unbounded" />
	<xs:element name="completeLocation"		<xs:element name="completeLocation"
	type="lost1:locationInformation"/>		type="lost1:locationInformation"/>
	</xs:choice>		</xs:choice>
	</group>		</xs:group>
	<!-- and also at the locationValidation extensionPoint -->		<!-- and also at the locationValidation extensionPoint -->
	<xs:attribute name="similarLocationsLimited" use="optional">		<xs:attribute name="similarLocationsLimited" use="optional">
	<xs:simpleType>		<xs:simpleType>
	<xs:restriction base="xs:integer">		<xs:restriction base="xs:integer">
	<xs:minInclusive value="1">		<xs:minInclusive value="1"/>
	</xs:restriction>		</xs:restriction>
	</xs:simpleType>		</xs:simpleType>
	</xs:attribute>		</xs:attribute>
	</xs:schema>		</xs:schema>
	7. Security Considerations		7. Security Considerations
	Whether the input to the LoST server is a Valid or Invalid Location,		Whether the input to the LoST server is a Valid or Invalid Location,
	the LoST server ultimately determines what it considers to be a Valid		the LoST server ultimately determines what it considers to be a Valid
	skipping to change at page 16, line 43 ¶		skipping to change at page 16, line 43 ¶
	8. IANA Considerations		8. IANA Considerations
	8.1. XML Schema Registration		8.1. XML Schema Registration
	URI: urn:ietf:params:xml:schema:lost-rli1		URI: urn:ietf:params:xml:schema:lost-rli1
	Registrant Contact: IETF ECRIT Working Group, Brian Rosen		Registrant Contact: IETF ECRIT Working Group, Brian Rosen
	(br@brianrosen.net).		(br@brianrosen.net).
	XML Schema: The XML schema to be registered is contained		XML Schema: The XML schema to be registered is contained
	in Section 7.		in <xref target="XMLSchema"/>.
	8.2. LoST-RLI Namespace Registration		8.2. LoST-RLI Namespace Registration
	URI: urn:ietf:params:xml:ns:lost-rli1		URI: urn:ietf:params:xml:ns:lost-rli1
	Registrant Contact: IETF ECRIT Working Group, Brian Rosen		Registrant Contact: IETF ECRIT Working Group, Brian Rosen
	(br@brianrosen.net).		(br@brianrosen.net).
	XML:		XML:
	BEGIN		BEGIN
End of changes. 13 change blocks.
	14 lines changed or deleted		14 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/