Diff: draft-ietf-geopriv-pdif-lo-profile-10.txt - draft-ietf-geopriv-pdif-lo-profile-11.txt

	< draft-ietf-geopriv-pdif-lo-profile-10.txt	draft-ietf-geopriv-pdif-lo-profile-11.txt >

	Geopriv J. Winterbottom	Geopriv J. Winterbottom
	Internet-Draft M. Thomson	Internet-Draft M. Thomson
	Updates: 4119 (if approved) Andrew Corporation	Updates: 4119 (if approved) Andrew Corporation
	Intended status: Standards Track H. Tschofenig	Intended status: Standards Track H. Tschofenig

	Expires: April 12, 2008 Nokia Siemens Networks	Expires: August 23, 2008 Nokia Siemens Networks
	October 10, 2007	February 20, 2008

	GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations	GEOPRIV PIDF-LO Usage Clarification, Considerations and Recommendations

	draft-ietf-geopriv-pdif-lo-profile-10.txt	draft-ietf-geopriv-pdif-lo-profile-11.txt

	Status of this Memo	Status of this Memo

	By submitting this Internet-Draft, each author represents that any	By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware	applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes	have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.	aware will be disclosed, in accordance with Section 6 of BCP 79.

	Internet-Drafts are working documents of the Internet Engineering	Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that	Task Force (IETF), its areas, and its working groups. Note that

	skipping to change at page 1, line 36 ¶	skipping to change at page 1, line 36 ¶
	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."

	The list of current Internet-Drafts can be accessed at	The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.	http://www.ietf.org/ietf/1id-abstracts.txt.

	The list of Internet-Draft Shadow Directories can be accessed at	The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.	http://www.ietf.org/shadow.html.


	This Internet-Draft will expire on April 12, 2008.	This Internet-Draft will expire on August 23, 2008.

	Copyright Notice	Copyright Notice


	Copyright (C) The IETF Trust (2007).	Copyright (C) The IETF Trust (2008).

	Abstract	Abstract

	The Presence Information Data Format Location Object (PIDF-LO)	The Presence Information Data Format Location Object (PIDF-LO)
	specification provides a flexible and versatile means to represent	specification provides a flexible and versatile means to represent
	location information. There are, however, circumstances that arise	location information. There are, however, circumstances that arise
	when information needs to be constrained in how it is represented.	when information needs to be constrained in how it is represented.
	In these circumstances the range of options that need to be	In these circumstances the range of options that need to be
	implemented are reduced. There is growing interest in being able to	implemented are reduced. There is growing interest in being able to
	use location information contained in a PIDF-LO for routing	use location information contained in a PIDF-LO for routing

	skipping to change at page 3, line 26 ¶	skipping to change at page 3, line 26 ¶
	5.1. Polygon Restrictions . . . . . . . . . . . . . . . . . . . 15	5.1. Polygon Restrictions . . . . . . . . . . . . . . . . . . . 15
	5.2. Shape Examples . . . . . . . . . . . . . . . . . . . . . . 16	5.2. Shape Examples . . . . . . . . . . . . . . . . . . . . . . 16
	5.2.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 16	5.2.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 16
	5.2.2. Polygon . . . . . . . . . . . . . . . . . . . . . . . 17	5.2.2. Polygon . . . . . . . . . . . . . . . . . . . . . . . 17
	5.2.3. Circle . . . . . . . . . . . . . . . . . . . . . . . . 19	5.2.3. Circle . . . . . . . . . . . . . . . . . . . . . . . . 19
	5.2.4. Ellipse . . . . . . . . . . . . . . . . . . . . . . . 20	5.2.4. Ellipse . . . . . . . . . . . . . . . . . . . . . . . 20
	5.2.5. Arc Band . . . . . . . . . . . . . . . . . . . . . . . 21	5.2.5. Arc Band . . . . . . . . . . . . . . . . . . . . . . . 21
	5.2.6. Sphere . . . . . . . . . . . . . . . . . . . . . . . . 23	5.2.6. Sphere . . . . . . . . . . . . . . . . . . . . . . . . 23
	5.2.7. Ellipsoid . . . . . . . . . . . . . . . . . . . . . . 24	5.2.7. Ellipsoid . . . . . . . . . . . . . . . . . . . . . . 24
	5.2.8. Prism . . . . . . . . . . . . . . . . . . . . . . . . 26	5.2.8. Prism . . . . . . . . . . . . . . . . . . . . . . . . 26

	6. Security Considerations . . . . . . . . . . . . . . . . . . . 28	6. Security Considerations . . . . . . . . . . . . . . . . . . . 29
	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29	7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 30
	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 30	8. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 31
	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 31	9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32
	9.1. Normative references . . . . . . . . . . . . . . . . . . . 31	9.1. Normative references . . . . . . . . . . . . . . . . . . . 32
	9.2. Informative References . . . . . . . . . . . . . . . . . . 31	9.2. Informative References . . . . . . . . . . . . . . . . . . 32
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 32	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 33
	Intellectual Property and Copyright Statements . . . . . . . . . . 33	Intellectual Property and Copyright Statements . . . . . . . . . . 34

	1. Introduction	1. Introduction

	The Presence Information Data Format Location Object (PIDF-LO)	The Presence Information Data Format Location Object (PIDF-LO)
	[RFC4119] is the recommended way of encoding location information and	[RFC4119] is the recommended way of encoding location information and
	associated privacy policies. Location information in a PIDF-LO may	associated privacy policies. Location information in a PIDF-LO may
	be described in a geospatial manner based on a subset of GMLv3, or as	be described in a geospatial manner based on a subset of GMLv3, or as
	civic location information [I-D.ietf-geopriv-revised-civic-lo]. A	civic location information [I-D.ietf-geopriv-revised-civic-lo]. A
	GML profile for expressing geodetic shapes in a PIDF-LO is described	GML profile for expressing geodetic shapes in a PIDF-LO is described
	in [GeoShape]. Uses for PIDF-LO are envisioned in the context of	in [GeoShape]. Uses for PIDF-LO are envisioned in the context of

	skipping to change at page 10, line 24 ¶	skipping to change at page 10, line 24 ¶
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>
	<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">	<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
	<gml:pos>-43.5723 153.21760</gml:pos>	<gml:pos>-43.5723 153.21760</gml:pos>
	</gml:Point>	</gml:Point>
	<cl:civicAddress>	<cl:civicAddress>
	<cl:FLR>2</cl:FLR>	<cl:FLR>2</cl:FLR>
	</cl:civicAddress>	</cl:civicAddress>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	<dm:deviceID>mac:8asd7d7d70cf</dm:deviceID>	<dm:deviceID>mac:8asd7d7d70cf</dm:deviceID>
	</dm:device>	</dm:device>
	</presence>	</presence>

	Figure 2	Figure 2

	3.3. Manual/Automatic Configuration of Location Information	3.3. Manual/Automatic Configuration of Location Information

	skipping to change at page 11, line 25 ¶	skipping to change at page 11, line 25 ¶
	xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"	xmlns:dm="urn:ietf:params:xml:ns:pidf:data-model"
	xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"	xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
	xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"	xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
	xmlns:gml="http://www.opengis.net/gml"	xmlns:gml="http://www.opengis.net/gml"
	xmlns:gs="http://www.opengis.net/pidflo/1.0"	xmlns:gs="http://www.opengis.net/pidflo/1.0"
	entity="pres:ness@example.com">	entity="pres:ness@example.com">
	<dm:device id="nesspc-1">	<dm:device id="nesspc-1">
	<status>	<status>
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>

		<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
		<gml:pos>-34.410649 150.87651</gml:pos>
		<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
		30
		</gs:radius>
		</gs:Circle>
		</gp:location-info>
		<gp:usage-rules/>
		<method>GPS</method>
		</gp:geopriv>
		</status>
		<timestamp>2007-06-22T20:57:29Z</timestamp>
		<dm:deviceID>mac:1234567890ab</dm:deviceID>
		</dm:device>
		<dm:person id="ness">
		<status>
		<gp:geopriv>
		<gp:location-info>
	<civicAddress xml:lang="en-AU">	<civicAddress xml:lang="en-AU">
	<country>AU</country>	<country>AU</country>
	<A1>NSW</A1>	<A1>NSW</A1>
	<A3> Wollongong	<A3> Wollongong
	</A3><A4>North Wollongong	</A3><A4>North Wollongong
	</A4>	</A4>
	<RD>Flinders</RD><STS>Street</STS>	<RD>Flinders</RD><STS>Street</STS>
	<RDBR>Campbell Street</RDBR>	<RDBR>Campbell Street</RDBR>
	<LMK>	<LMK>
	Gilligan's Island	Gilligan's Island

	skipping to change at page 11, line 35 ¶	skipping to change at page 12, line 4 ¶
	<civicAddress xml:lang="en-AU">	<civicAddress xml:lang="en-AU">
	<country>AU</country>	<country>AU</country>
	<A1>NSW</A1>	<A1>NSW</A1>
	<A3> Wollongong	<A3> Wollongong
	</A3><A4>North Wollongong	</A3><A4>North Wollongong
	</A4>	</A4>
	<RD>Flinders</RD><STS>Street</STS>	<RD>Flinders</RD><STS>Street</STS>
	<RDBR>Campbell Street</RDBR>	<RDBR>Campbell Street</RDBR>
	<LMK>	<LMK>
	Gilligan's Island	Gilligan's Island


	</LMK> <LOC>Corner</LOC>	</LMK> <LOC>Corner</LOC>

	<NAM> Video Rental Store </NAM>	<NAM> Main Bank </NAM>
	<PC>2500</PC>	<PC>2500</PC>

	<ROOM> Westerns and Classics </ROOM>	<ROOM> 398 </ROOM>
	<PLC>store</PLC>	<PLC>store</PLC>
	<POBOX>Private Box 15</POBOX>	<POBOX>Private Box 15</POBOX>
	</civicAddress>	</civicAddress>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

	</gp:geopriv>	<method>Manual</method>
	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>
	<dm:deviceID>mac:1234567890ab</dm:deviceID>
	</dm:device>
	<dm:person id="ness">
	<status>
	<gp:geopriv>
	<gp:location-info>
	<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
	<gml:pos>-34.410649 150.87651</gml:pos>
	<gml:radius uom="urn:ogc:def:uom:EPSG::9001">
	30
	</gml:radius>
	</gs:Circle>
	</gp:location-info>
	<gp:usage-rules/>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-24T12:28:04Z</timestamp>	<timestamp>2007-06-24T12:28:04Z</timestamp>
	</dm:person>	</dm:person>
	</presence>	</presence>

	Figure 3	Figure 3

	4. Geodetic Coordinate Representation	4. Geodetic Coordinate Representation


	skipping to change at page 16, line 42 ¶	skipping to change at page 16, line 42 ¶
	entity="pres:point2d@example.com">	entity="pres:point2d@example.com">
	<dm:device id="point2d">	<dm:device id="point2d">
	<status>	<status>
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>
	<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">	<gml:Point srsName="urn:ogc:def:crs:EPSG::4326">
	<gml:pos>-34.407 150.883</gml:pos>	<gml:pos>-34.407 150.883</gml:pos>
	</gml:Point>	</gml:Point>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	<dm:deviceID>mac:1234567890ab</dm:deviceID>	<dm:deviceID>mac:1234567890ab</dm:deviceID>
	</dm:device>	</dm:device>
	</presence>	</presence>

	Figure 4	Figure 4

	Figure 5 shows a 3d point:	Figure 5 shows a 3d point:

	skipping to change at page 17, line 23 ¶	skipping to change at page 17, line 23 ¶
	<dm:device id="point3d">	<dm:device id="point3d">
	<status>	<status>
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>
	<gml:Point srsName="urn:ogc:def:crs:EPSG::4979"	<gml:Point srsName="urn:ogc:def:crs:EPSG::4979"
	xmlns:gml="http://www.opengis.net/gml">	xmlns:gml="http://www.opengis.net/gml">
	<gml:pos>-34.407 150.883 24.8</gml:pos>	<gml:pos>-34.407 150.883 24.8</gml:pos>
	</gml:Point>	</gml:Point>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	<dm:deviceID>mac:1234567890ab</dm:deviceID>	<dm:deviceID>mac:1234567890ab</dm:deviceID>
	</dm:device>	</dm:device>
	</presence>	</presence>

	Figure 5	Figure 5

	5.2.2. Polygon	5.2.2. Polygon

	skipping to change at page 18, line 29 ¶	skipping to change at page 18, line 29 ¶
	<gml:pos>43.111 -73.222</gml:pos> <!--C-->	<gml:pos>43.111 -73.222</gml:pos> <!--C-->
	<gml:pos>43.311 -73.122</gml:pos> <!--D-->	<gml:pos>43.311 -73.122</gml:pos> <!--D-->
	<gml:pos>43.411 -73.222</gml:pos> <!--E-->	<gml:pos>43.411 -73.222</gml:pos> <!--E-->
	<gml:pos>43.411 -73.322</gml:pos> <!--F-->	<gml:pos>43.411 -73.322</gml:pos> <!--F-->
	<gml:pos>43.311 -73.422</gml:pos> <!--A-->	<gml:pos>43.311 -73.422</gml:pos> <!--A-->
	</gml:LinearRing>	</gml:LinearRing>
	</gml:exterior>	</gml:exterior>
	</gml:Polygon>	</gml:Polygon>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 7	Figure 7

	In addition to the form shown in Figure 7 GML supports a posList	In addition to the form shown in Figure 7 GML supports a posList
	which provides a more compact representation for the coordinates of	which provides a more compact representation for the coordinates of

	skipping to change at page 19, line 28 ¶	skipping to change at page 19, line 28 ¶
	43.311 -73.422 43.111 -73.322	43.311 -73.422 43.111 -73.322
	43.111 -73.222 43.311 -73.122	43.111 -73.222 43.311 -73.122
	43.411 -73.222 43.411 -73.322	43.411 -73.222 43.411 -73.322
	43.311 -73.422	43.311 -73.422
	</gml:posList>	</gml:posList>
	</gml:LinearRing>	</gml:LinearRing>
	</gml:exterior>	</gml:exterior>
	</gml:Polygon>	</gml:Polygon>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 8	Figure 8

	5.2.3. Circle	5.2.3. Circle


	skipping to change at page 20, line 17 ¶	skipping to change at page 20, line 17 ¶
	xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"	xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
	xmlns:gml="http://www.opengis.net/gml"	xmlns:gml="http://www.opengis.net/gml"
	xmlns:gs="http://www.opengis.net/pidflo/1.0"	xmlns:gs="http://www.opengis.net/pidflo/1.0"
	entity="pres:circle@example.com">	entity="pres:circle@example.com">
	<tuple id="circle">	<tuple id="circle">
	<status>	<status>
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>
	<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">	<gs:Circle srsName="urn:ogc:def:crs:EPSG::4326">
	<gml:pos>42.5463 -73.2512</gml:pos>	<gml:pos>42.5463 -73.2512</gml:pos>

	<gml:radius uom="urn:ogc:def:uom:EPSG::9001">	<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
	850.24	850.24

	</gml:radius>	</gs:radius>
	</gs:Circle>	</gs:Circle>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>OTDOA</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 9	Figure 9

	5.2.4. Ellipse	5.2.4. Ellipse

	An elliptical area describes an ellipse in two dimensional space.	An elliptical area describes an ellipse in two dimensional space.

	skipping to change at page 21, line 29 ¶	skipping to change at page 21, line 29 ¶
	</gs:semiMajorAxis>	</gs:semiMajorAxis>
	<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">	<gs:semiMinorAxis uom="urn:ogc:def:uom:EPSG::9001">
	670	670
	</gs:semiMinorAxis>	</gs:semiMinorAxis>
	<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">	<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
	43.2	43.2
	</gs:orientation>	</gs:orientation>
	</gs:Ellipse>	</gs:Ellipse>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Device-Assisted_A-GPS</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 10	Figure 10

	The gml:pos element indicates the position of the center, or origin,	The gml:pos element indicates the position of the center, or origin,
	of the ellipse. The gs:semiMajorAxis and gs:semiMinorAxis elements	of the ellipse. The gs:semiMajorAxis and gs:semiMinorAxis elements

	skipping to change at page 23, line 32 ¶	skipping to change at page 23, line 32 ¶
	</gs:outerRadius>	</gs:outerRadius>
	<gs:startAngle uom="urn:ogc:def:uom:EPSG::9102">	<gs:startAngle uom="urn:ogc:def:uom:EPSG::9102">
	20	20
	</gs:startAngle>	</gs:startAngle>
	<gs:openingAngle uom="urn:ogc:def:uom:EPSG::9102">	<gs:openingAngle uom="urn:ogc:def:uom:EPSG::9102">
	20	20
	</gs:openingAngle>	</gs:openingAngle>
	</gs:ArcBand>	</gs:ArcBand>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>TA-NMR</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 12	Figure 12

	An important note to make on the arc band is that the center point	An important note to make on the arc band is that the center point
	used in the definition of the shape is not included in resulting	used in the definition of the shape is not included in resulting

	skipping to change at page 24, line 23 ¶	skipping to change at page 24, line 23 ¶
	<gp:geopriv>	<gp:geopriv>
	<gp:location-info>	<gp:location-info>
	<gs:Sphere srsName="urn:ogc:def:crs:EPSG::4979">	<gs:Sphere srsName="urn:ogc:def:crs:EPSG::4979">
	<gml:pos>42.5463 -73.2512 26.3</gml:pos>	<gml:pos>42.5463 -73.2512 26.3</gml:pos>
	<gs:radius uom="urn:ogc:def:uom:EPSG::9001">	<gs:radius uom="urn:ogc:def:uom:EPSG::9001">
	850.24	850.24
	</gs:radius>	</gs:radius>
	</gs:Sphere>	</gs:Sphere>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Device-Based_A-GPS</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 13	Figure 13

	5.2.7. Ellipsoid	5.2.7. Ellipsoid

	The ellipsoid is the volume most commonly produced by GPS systems.	The ellipsoid is the volume most commonly produced by GPS systems.

	skipping to change at page 25, line 47 ¶	skipping to change at page 26, line 32 ¶
	</gs:semiMinorAxis>	</gs:semiMinorAxis>
	<gs:verticalAxis uom="urn:ogc:def:uom:EPSG::9001">	<gs:verticalAxis uom="urn:ogc:def:uom:EPSG::9001">
	28.7	28.7
	</gs:verticalAxis>	</gs:verticalAxis>
	<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">	<gs:orientation uom="urn:ogc:def:uom:EPSG::9102">
	90	90
	</gs:orientation>	</gs:orientation>
	</gs:Ellipsoid>	</gs:Ellipsoid>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Hybrid_A-GPS</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>


	Figure 15	Figure 15

	5.2.8. Prism	5.2.8. Prism

	A prism may be used to represent a section of a building or range of	A prism may be used to represent a section of a building or range of
	floors of building. The prism extrudes a polygon by providing a	floors of building. The prism extrudes a polygon by providing a
	height element. It consists of a base made up of coplanar points	height element. It consists of a base made up of coplanar points
	defined in 3 dimensions all at the same altitude. The prism is then	defined in 3 dimensions all at the same altitude. The prism is then
	an extrusion from this base to the value specified in the height	an extrusion from this base to the value specified in the height
	element. If the height is negative, then the prism is extruded from	element. If the height is negative, then the prism is extruded from

	skipping to change at page 27, line 37 ¶	skipping to change at page 28, line 37 ¶
	</gml:LinearRing>	</gml:LinearRing>
	</gml:exterior>	</gml:exterior>
	</gml:Polygon>	</gml:Polygon>
	</gs:base>	</gs:base>
	<gs:height uom="urn:ogc:def:uom:EPSG::9001">	<gs:height uom="urn:ogc:def:uom:EPSG::9001">
	2.4	2.4
	</gs:height>	</gs:height>
	</gs:Prism>	</gs:Prism>
	</gp:location-info>	</gp:location-info>
	<gp:usage-rules/>	<gp:usage-rules/>

		<method>Wiremap</method>
	</gp:geopriv>	</gp:geopriv>
	</status>	</status>
	<timestamp>2007-06-22T20:57:29Z</timestamp>	<timestamp>2007-06-22T20:57:29Z</timestamp>
	</tuple>	</tuple>
	</presence>	</presence>

	Figure 17	Figure 17

	6. Security Considerations	6. Security Considerations


	skipping to change at page 31, line 5 ¶	skipping to change at page 31, line 14 ¶

	8. Acknowledgments	8. Acknowledgments

	The authors would like to thank the GEOPRIV working group for their	The authors would like to thank the GEOPRIV working group for their
	discussions in the context of PIDF-LO, in particular Carl Reed, Ron	discussions in the context of PIDF-LO, in particular Carl Reed, Ron
	Lake, James Polk, Henning Schulzrinne, Jerome Grenier, Roger Marshall	Lake, James Polk, Henning Schulzrinne, Jerome Grenier, Roger Marshall
	and Robert Sparks. Furthermore, we would like to thank Jon Peterson	and Robert Sparks. Furthermore, we would like to thank Jon Peterson
	as the author of PIDF-LO and Nadine Abbott for her constructive	as the author of PIDF-LO and Nadine Abbott for her constructive
	comments in clarifying some aspects of the document.	comments in clarifying some aspects of the document.


		Thanks to Karen Navas for pointing out some emissions in the
		examples.

	9. References	9. References

	9.1. Normative references	9.1. Normative references

	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.	Requirement Levels", BCP 14, RFC 2119, March 1997.

	[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object	[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
	Format", RFC 4119, December 2005.	Format", RFC 4119, December 2005.


	skipping to change at page 31, line 27 ¶	skipping to change at page 32, line 27 ¶

	[GeoShape]	[GeoShape]
	Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape	Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape
	Application Schema for use by the Internet Engineering	Application Schema for use by the Internet Engineering
	Task Force (IETF)", Candidate OpenGIS Implementation	Task Force (IETF)", Candidate OpenGIS Implementation
	Specification 06-142r1, Version: 1.0, April 2007.	Specification 06-142r1, Version: 1.0, April 2007.

	[I-D.ietf-geopriv-revised-civic-lo]	[I-D.ietf-geopriv-revised-civic-lo]
	Thomson, M. and J. Winterbottom, "Revised Civic Location	Thomson, M. and J. Winterbottom, "Revised Civic Location
	Format for PIDF-LO",	Format for PIDF-LO",

	draft-ietf-geopriv-revised-civic-lo-05 (work in progress),	draft-ietf-geopriv-revised-civic-lo-07 (work in progress),
	February 2007.	December 2007.

	9.2. Informative References	9.2. Informative References

	[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol	[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
	(DHCPv4 and DHCPv6) Option for Civic Addresses	(DHCPv4 and DHCPv6) Option for Civic Addresses
	Configuration Information", RFC 4776, November 2006.	Configuration Information", RFC 4776, November 2006.

	[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and	[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
	J. Polk, "Geopriv Requirements", RFC 3693, February 2004.	J. Polk, "Geopriv Requirements", RFC 3693, February 2004.


	skipping to change at page 33, line 7 ¶	skipping to change at page 34, line 7 ¶
	Nokia Siemens Networks	Nokia Siemens Networks
	Otto-Hahn-Ring 6	Otto-Hahn-Ring 6
	Munich, Bavaria 81739	Munich, Bavaria 81739
	Germany	Germany

	Email: Hannes.Tschofenig@nsn.com	Email: Hannes.Tschofenig@nsn.com
	URI: http://www.tschofenig.com	URI: http://www.tschofenig.com

	Full Copyright Statement	Full Copyright Statement


	Copyright (C) The IETF Trust (2007).	Copyright (C) The IETF Trust (2008).

	This document is subject to the rights, licenses and restrictions	This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors	contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.	retain all their rights.

	This document and the information contained herein are provided on an	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF

End of changes. 27 change blocks.
	37 lines changed or deleted	55 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/