< draft-ietf-geopriv-relative-location-01.txt		draft-ietf-geopriv-relative-location-02.txt >
	GEOPRIV M. Thomson		GEOPRIV M. Thomson
	Internet-Draft Andrew Corporation		Internet-Draft Andrew Corporation
	Intended status: Standards Track B. Rosen		Intended status: Standards Track B. Rosen
	Expires: September 29, 2011 Neustar		Expires: May 3, 2012 Neustar
	D. Stanley		D. Stanley
	Aruba Networks		Aruba Networks
	G. Bajko		G. Bajko
	Nokia		Nokia
	A. Thomson		A. Thomson
	Cisco Systems, Inc.		Cisco Systems, Inc.
	March 28, 2011		October 31, 2011
	Relative Location Representation		Relative Location Representation
	draft-ietf-geopriv-relative-location-01		draft-ietf-geopriv-relative-location-02
	Abstract		Abstract
	This document defines an extension to PIDF-LO (RFC4119) for the		This document defines an extension to PIDF-LO (RFC4119) for the
	expression of location information that is defined relative to a		expression of location information that is defined relative to a
	reference point. The reference point may be expressed as a geodetic		reference point. The reference point may be expressed as a geodetic
	or civic location, and the relative offset may be one of several		or civic location, and the relative offset may be one of several
	shapes. Optionally, a reference to a secondary document (such as a		shapes. Optionally, a reference to a secondary document (such as a
	map image) can be included, along with the relationship of the map		map image) can be included, along with the relationship of the map
	coordinate system to the reference/offset coordinate system to allow		coordinate system to the reference/offset coordinate system to allow
	skipping to change at page 1, line 47 ¶		skipping to change at page 1, line 47 ¶
	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 September 29, 2011.		This Internet-Draft will expire on May 3, 2012.
	Copyright Notice		Copyright Notice
	Copyright (c) 2011 IETF Trust and the persons identified as the		Copyright (c) 2011 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
	skipping to change at page 3, line 19 ¶		skipping to change at page 3, line 19 ¶
	3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4		3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
	4. Relative Location . . . . . . . . . . . . . . . . . . . . . . 7		4. Relative Location . . . . . . . . . . . . . . . . . . . . . . 7
	4.1. Relative Coordinate System . . . . . . . . . . . . . . . . 7		4.1. Relative Coordinate System . . . . . . . . . . . . . . . . 7
	4.2. Placement of XML Elements . . . . . . . . . . . . . . . . 7		4.2. Placement of XML Elements . . . . . . . . . . . . . . . . 7
	4.3. Binary Format . . . . . . . . . . . . . . . . . . . . . . 8		4.3. Binary Format . . . . . . . . . . . . . . . . . . . . . . 8
	4.4. Distances and Angles . . . . . . . . . . . . . . . . . . . 8		4.4. Distances and Angles . . . . . . . . . . . . . . . . . . . 8
	4.5. Value Encoding . . . . . . . . . . . . . . . . . . . . . . 9		4.5. Value Encoding . . . . . . . . . . . . . . . . . . . . . . 9
	4.6. Relative Location Restrictions . . . . . . . . . . . . . . 9		4.6. Relative Location Restrictions . . . . . . . . . . . . . . 9
	4.7. Baseline TLVs . . . . . . . . . . . . . . . . . . . . . . 9		4.7. Baseline TLVs . . . . . . . . . . . . . . . . . . . . . . 9
	4.8. Reference TLV . . . . . . . . . . . . . . . . . . . . . . 9		4.8. Reference TLV . . . . . . . . . . . . . . . . . . . . . . 9
	4.9. Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . 10		4.9. Shapes . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	4.9.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 10		4.9.1. Point . . . . . . . . . . . . . . . . . . . . . . . . 10
	4.9.2. Circle or Sphere Shape . . . . . . . . . . . . . . . . 11		4.9.2. Circle or Sphere Shape . . . . . . . . . . . . . . . . 11
	4.9.3. Ellipse or Ellipsoid Shape . . . . . . . . . . . . . . 12		4.9.3. Ellipse or Ellipsoid Shape . . . . . . . . . . . . . . 12
	4.9.4. Polygon or Prism Shape . . . . . . . . . . . . . . . . 14		4.9.4. Polygon or Prism Shape . . . . . . . . . . . . . . . . 14
	4.9.5. Arc-Band Shape . . . . . . . . . . . . . . . . . . . . 17		4.9.5. Arc-Band Shape . . . . . . . . . . . . . . . . . . . . 17
	4.10. Secondary Map Metadata . . . . . . . . . . . . . . . . . . 18		4.10. Dynamic Location TLVs . . . . . . . . . . . . . . . . . . 18
	4.10.1. Map URL . . . . . . . . . . . . . . . . . . . . . . . 19		4.10.1. Orientation . . . . . . . . . . . . . . . . . . . . . 19
	4.10.2. Map Coordinate Reference System . . . . . . . . . . . 19		4.10.2. Speed . . . . . . . . . . . . . . . . . . . . . . . . 19
	4.10.3. Map Example . . . . . . . . . . . . . . . . . . . . . 21		4.10.3. Heading . . . . . . . . . . . . . . . . . . . . . . . 19
	5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 22		4.11. Secondary Map Metadata . . . . . . . . . . . . . . . . . . 19
	5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . . 22		4.11.1. Map URL . . . . . . . . . . . . . . . . . . . . . . . 20
	5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 23		4.11.2. Map Coordinate Reference System . . . . . . . . . . . 20
	5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 25		4.11.3. Map Example . . . . . . . . . . . . . . . . . . . . . 22
	6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 25		5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
	7. Security Considerations . . . . . . . . . . . . . . . . . . . 28		5.1. Civic PIDF with Polygon Offset . . . . . . . . . . . . . . 23
	8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 28		5.2. Geo PIDF with Circle Offset . . . . . . . . . . . . . . . 24
	8.1. Relative Location Registry . . . . . . . . . . . . . . . . 28		5.3. Civic TLV with Point Offset . . . . . . . . . . . . . . . 26
	8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 29		6. Schema Definition . . . . . . . . . . . . . . . . . . . . . . 26
	8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 30		7. Security Considerations . . . . . . . . . . . . . . . . . . . 29
	8.4. CRS public identifier registration . . . . . . . . . . . . 30		8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 29
	9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 32		8.1. Relative Location Registry . . . . . . . . . . . . . . . . 29
	10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 32		8.2. URN Sub-Namespace Registration . . . . . . . . . . . . . . 30
	10.1. Normative References . . . . . . . . . . . . . . . . . . . 32		8.3. XML Schema Registration . . . . . . . . . . . . . . . . . 31
	10.2. Informative References . . . . . . . . . . . . . . . . . . 33		8.4. CRS public identifier registration . . . . . . . . . . . . 31
			8.5. CAtype Registration . . . . . . . . . . . . . . . . . . . 33
			9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 33
			10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
			10.1. Normative References . . . . . . . . . . . . . . . . . . . 33
			10.2. Informative References . . . . . . . . . . . . . . . . . . 35
	1. Introduction		1. Introduction
	This document describes a format for the expression of relative		This document describes a format for the expression of relative
	location information.		location information.
	A relative location is formed of a reference location, plus a		A relative location is formed of a reference location, plus a
	relative offset from that reference location. The reference location		relative offset from that reference location. The reference location
	can be represented in either civic or geodetic form. The reference		can be represented in either civic or geodetic form. The reference
	location can also have dynamic components such as velocity. The		location can also have dynamic components such as velocity. The
	skipping to change at page 7, line 51 ¶		skipping to change at page 7, line 51 ¶
	along the direction described by the <orientation> element. The		along the direction described by the <orientation> element. The
	coordinate system also moves as described by the <speed> and		coordinate system also moves as described by the <speed> and
	<heading> elements.		<heading> elements.
	4.2. Placement of XML Elements		4.2. Placement of XML Elements
	The baseline of the reference location is represented as <location-		The baseline of the reference location is represented as <location-
	info> like a normal PIDF-LO. Relative location adds a new <relative-		info> like a normal PIDF-LO. Relative location adds a new <relative-
	location> element to <location-info> Within <relative-location>		location> element to <location-info> Within <relative-location>
	<reference> and <offset> elements are described. Within <offset> are		<reference> and <offset> elements are described. Within <offset> are
	shape elements described below.		shape elements described below. This document extends PIDF-LO as
			described in [I-D.ietf-geopriv-local-civic].
	4.3. Binary Format		4.3. Binary Format
	This document describes a way to encode the relative location in a		This document describes a way to encode the relative location in a
	binary TLV form for use in other protocols that use TLVs to represent		binary TLV form for use in other protocols that use TLVs to represent
	location.		location.
	A type-length-value encoding is used.		A type-length-value encoding is used.
	+------+------+------+------+------+------+------+		+------+------+------+------+------+------+------+
	skipping to change at page 9, line 30 ¶		skipping to change at page 9, line 30 ¶
	or TLV encoding of location for a given reference point.		or TLV encoding of location for a given reference point.
	Any error in the reference point transfers to the location described		Any error in the reference point transfers to the location described
	by the relative location. Any errors arising from an implementation		by the relative location. Any errors arising from an implementation
	not supporting or understanding elements of the reference point		not supporting or understanding elements of the reference point
	directly increases the error (or uncertainty) in the resulting		directly increases the error (or uncertainty) in the resulting
	location.		location.
	4.7. Baseline TLVs		4.7. Baseline TLVs
	Baseline TLVs are defined in [RFC3825].		Baseline locations is described using the formats defined in
			[RFC4776] or [RFC6225].
	4.8. Reference TLV		4.8. Reference TLV
	When a reference is encoded in binary form, the baseline and		When a reference is encoded in binary form, the baseline and
	reference locations are combined in a reference TLV. This TLV		reference locations are combined in a reference TLV. This TLV
	contains civic address TLVs (if the baseline was a civic) or geo TLVs		contains civic address TLVs (if the baseline was a civic) or geo TLVs
	(if the baseline was a geo).		(if the baseline was a geo).
	+------+------+------+------+------+------+		+------+------+------+------+------+------+
	| 111 |Length| Reference TLVs |		| 111 |Length| Reference TLVs |
	+------+------+------+------+------+------+		+------+------+------+------+------+------+
	Reference TLV		Reference TLV
	If this TLV contains the reference location, then we need to
	explicitly say that the shape TLVs in here use WGS84; and when the
	shapes are outside of this, they use the relative:2d or relative:3d
	forms.
	TBD - Need TLVs for dynamic objects (orientation - multiple angles,
	speed - single scalar, heading - multiple angles)
	4.9. Shapes		4.9. Shapes
	Shape data is used to represent regions of uncertainty for the		Shape data is used to represent regions of uncertainty for the
	reference and relative locations. Shape data in the reference		reference and relative locations. Shape data in the reference
	location uses a WGS84 [WGS84] CRS. Shape data in the relative		location uses a [WGS84] CRS. Shape data in the relative location
	location uses a relative CRS.		uses a relative CRS.
	The XML form for shapes uses Geography Markup Language (GML)		The XML form for shapes uses Geography Markup Language (GML)
	[OGC.GML-3.1.1], consistent with the rules in target="RFC5491"/>.		[OGC.GML-3.1.1], consistent with the rules in [RFC5491]. Reference
	Reference locations use the CRS URNs specified in [RFC5491]; relative		locations use the CRS URNs specified in [RFC5491]; relative locations
	locations use either a 2D CRS (urn:ietf:params:geopriv:relative:2d),		use either a 2D CRS (urn:ietf:params:geopriv:relative:2d), or a 3D
	or a 3D (urn:ietf:params:geopriv:relative:3d), depending on the shape		(urn:ietf:params:geopriv:relative:3d), depending on the shape type.
	type.
	The binary form of each shape uses a different shape types for 2d and		The binary form of each shape uses a different shape types for 2d and
	3d shapes.		3d shapes.
	Nine shape type codes are defined.		Nine shape type codes are defined.
	4.9.1. Point		4.9.1. Point
	A point "shape" describes a single point with unknown uncertainty.		A point "shape" describes a single point with unknown uncertainty.
	It consists of a single set of coordinates.		It consists of a single set of coordinates.
	skipping to change at page 18, line 48 ¶		skipping to change at page 18, line 48 ¶
	+------+------+------+------+		+------+------+------+------+
	| Coordinate |		| Coordinate |
	+------+------+------+------+------+------+------+------+		+------+------+------+------+------+------+------+------+
	| Inner Radius | Outer Radius |		| Inner Radius | Outer Radius |
	+------+------+------+------+------+------+------+------+		+------+------+------+------+------+------+------+------+
	| Start Angle | Opening Angle |		| Start Angle | Opening Angle |
	+------+------+------+------+------+------+------+------+		+------+------+------+------+------+------+------+------+
	Arc-Band Encoding		Arc-Band Encoding
	4.10. Secondary Map Metadata		4.10. Dynamic Location TLVs
			Dynamic location elements use the definitions in [RFC5962].
			4.10.1. Orientation
			The orientation of the target is described using one or two angles.
			+------+------+
			| 123 |Length|
			+------+------+------+------+
			| Angle |
			+------+------+------+------+
			| (Optional) Angle |
			+------+------+------+------+
			Dynamic Orientation TLVs
			4.10.2. Speed
			The speed of the target is a scalar value in meters per second.
			+------+------+
			| 124 |Length|
			+------+------+------+------+
			| Length |
			+------+------+------+------+
			| Speed |
			+------+------+------+------+
			Dynamic Speed TLVs
			4.10.3. Heading
			The heading, or direction of travel, is described using one or two
			angles.
			+------+------+
			| 125 |Length|
			+------+------+------+------+
			| Angle |
			+------+------+------+------+
			| (Optional) Angle |
			+------+------+------+------+
			Dynamic Heading TLVs
			4.11. Secondary Map Metadata
	The optional "map" URL can be used to provide a user of relative		The optional "map" URL can be used to provide a user of relative
	location with a visual reference for the location information. This		location with a visual reference for the location information. This
	document does not describe how the recipient uses the map nor how it		document does not describe how the recipient uses the map nor how it
	locates the reference or offset within the map. Maps can be simple		locates the reference or offset within the map. Maps can be simple
	images, vector files, 2-D or 3-D geospatial databases, or any other		images, vector files, 2-D or 3-D geospatial databases, or any other
	form of representation understood by both the sender and recipient.		form of representation understood by both the sender and recipient.
	4.10.1. Map URL		4.11.1. Map URL
	In XML, the map is a <map> element defined within <relative-location>		In XML, the map is a <map> element defined within <relative-location>
	and contains the URL. The URL is encoded as a UTF-8 encoded string.		and contains the URL. The URL is encoded as a UTF-8 encoded string.
	An "http:" or "https:" URL MUST be used unless the entity creating		An "http:" or "https:" URL MUST be used unless the entity creating
	the PIDF-LO is able to ensure that authorized recipients of this data		the PIDF-LO is able to ensure that authorized recipients of this data
	are able to use other URI schemes. A "type" attribute MUST be		are able to use other URI schemes. A "type" attribute MUST be
	present and specifies the kind of map the URL points to. Map types		present and specifies the kind of map the URL points to. Map types
	are specified as mime media types as recorded in the IANA Media Types		are specified as mime media types as recorded in the IANA Media Types
	registry. For example <map type="image/png">https://www.example.com/		registry. For example <map type="image/png">https://www.example.com/
	floorplans/123South/floor-2</map>. In binary, the map type is a		floorplans/123South/floor-2</map>. In binary, the map type is a
	separate TLV from the map URL:		separate TLV from the map URL:
	+------+------+------+------+------+-- --+------+		+------+------+------+------+------+-- --+------+
	| 123 |Length| Map Media Type ...		| 126 |Length| Map Media Type ...
	+------+------+------+------+------+-- --+------+		+------+------+------+------+------+-- --+------+
	| 124 |Length| Map Image URL ...		| 127 |Length| Map Image URL ...
	+------+------+------+------+------+-- --+------+		+------+------+------+------+------+-- --+------+
	Map URL TLVs		Map URL TLVs
	4.10.2. Map Coordinate Reference System		4.11.2. Map Coordinate Reference System
	The CRS used by the map depends on the type of map. For example, a		The CRS used by the map depends on the type of map. For example, a
	map described by a 3-D geometric model of the building may contain a		map described by a 3-D geometric model of the building may contain a
	complete CRS description in it. For some kinds of maps, typically		complete CRS description in it. For some kinds of maps, typically
	described as images, the CRS used within the map must define the		described as images, the CRS used within the map must define the
	following:		following:
	o The CRS origin		o The CRS origin
	o The CRS axes used and their orientation		o The CRS axes used and their orientation
	o The unit of measure used		o The unit of measure used
	This document provides elements that allow for a mapping between the		This document provides elements that allow for a mapping between the
	local coordinate reference system used for the relative location and		local coordinate reference system used for the relative location and
	the coordinate reference system used for the map where they are not		the coordinate reference system used for the map where they are not
	the same.		the same.
	4.10.2.1. Map Reference Point Offset		4.11.2.1. Map Reference Point Offset
	This optional element identifies the coordinates of the reference		This optional element identifies the coordinates of the reference
	point as it appears in the map. This value is measured in a map-type		point as it appears in the map. This value is measured in a map-type
	dependent manner, using the coordinate system of the map.		dependent manner, using the coordinate system of the map.
	For image maps, coordinates start from the upper left corner and		For image maps, coordinates start from the upper left corner and
	coordinates are first counted by column with positive values to the		coordinates are first counted by column with positive values to the
	right; then rows are counted with positive values toward the bottom		right; then rows are counted with positive values toward the bottom
	of the image. For such an image, the first item is columns, the		of the image. For such an image, the first item is columns, the
	second rows and any third value applies to any third dimension used		second rows and any third value applies to any third dimension used
	in the image coordinate space.		in the image coordinate space.
	The <offset> element contains 2 (or 3) coordinates similar to a GML		The <offset> element contains 2 (or 3) coordinates similar to a GML
	"pos", For example:		"pos", For example:
	<offset> 2670.0 1124.0 1022.0</offset>		<offset> 2670.0 1124.0 1022.0</offset>
	Map Reference Point Example XML		Map Reference Point Example XML
	+------+------+		+------+------+
	| 125 |Length|		| 128 |Length|
	+------+------+------+------+		+------+------+------+------+
	| Coordinate-1 |		| Coordinate-1 |
	+------+------+------+------+		+------+------+------+------+
	| Coordinate-2 |		| Coordinate-2 |
	+------+------+------+------+		+------+------+------+------+
	| (3D-only) Coordinate-3 |		| (3D-only) Coordinate-3 |
	+------+------+------+------+		+------+------+------+------+
	Map Reference Point Coordinates TLV		Map Reference Point Coordinates TLV
	If omitted, a value containing all zeros is assumed. If the		If omitted, a value containing all zeros is assumed. If the
	coordinates provided contain fewer values than are needed, the first		coordinates provided contain fewer values than are needed, the first
	value from the set is applied in place of any missing values.		value from the set is applied in place of any missing values.
	4.10.2.2. Map Orientation		4.11.2.2. Map Orientation
	The map orientation includes the orientation of the map direction in		The map orientation includes the orientation of the map direction in
	relation to the Earth. Map orientation is expressed relative to the		relation to the Earth. Map orientation is expressed relative to the
	orientation of the relative coordinate system. This means that map		orientation of the relative coordinate system. This means that map
	orientation with respect to WGS84 North is the sum of th orientation		orientation with respect to WGS84 North is the sum of th orientation
	field, plus any orientation included in a dynamic portion of the		field, plus any orientation included in a dynamic portion of the
	reference location. Both values default to zero if no value is		reference location. Both values default to zero if no value is
	specified.		specified.
	This type uses a single precision floating point value of degrees		This type uses a single precision floating point value of degrees
	relative to North.		relative to North.
	In XML, the <orientation> element contains a single floating point		In XML, the <orientation> element contains a single floating point
	value, example <orientation>67.00</orientation>. In TLV form:		value, example <orientation>67.00</orientation>. In TLV form:
	+------+------+------+------+------+------+		+------+------+------+------+------+------+
	| 126 |Length| Angle |		| 129 |Length| Angle |
	+------+------+------+------+------+------+		+------+------+------+------+------+------+
	Map Orientation TLV		Map Orientation TLV
	4.10.2.3. Map Scale		4.11.2.3. Map Scale
	The optional map scale describes the relationship between the units		The optional map scale describes the relationship between the units
	of measure used in the map, relative to the meters unit used in the		of measure used in the map, relative to the meters unit used in the
	relative coordinate system.		relative coordinate system.
	This type uses a sequence of IEEE 754 [IEEE.754] single precision		This type uses a sequence of IEEE 754 [IEEE.754] single precision
	floating point values to represent scale as a sequence of numeric		floating point values to represent scale as a sequence of numeric
	values. The units of these values is dependent on the type of map,		values. The units of these values is dependent on the type of map,
	and could for example be pixels per meter for an image.		and could for example be pixels per meter for an image.
	skipping to change at page 21, line 42 ¶		skipping to change at page 22, line 42 ¶
	handed coordinate system. A negative value for the y/rows-axis		handed coordinate system. A negative value for the y/rows-axis
	scaling value can be used to account for any change in direction		scaling value can be used to account for any change in direction
	between the y-axis used in the relative coordinate system and the		between the y-axis used in the relative coordinate system and the
	rows axis of the image coordinate system.		rows axis of the image coordinate system.
	In XML, the <scale> element may contain the single scale value, or		In XML, the <scale> element may contain the single scale value, or
	may contain 2 (or 3) values similar to a GML "pos" with separate		may contain 2 (or 3) values similar to a GML "pos" with separate
	scale values. In TLV form:		scale values. In TLV form:
	+------+------+------+------+------+		+------+------+------+------+------+
	| 127 |Length| Scales ...		| 130 |Length| Scales ...
	+------+------+------+------+------+		+------+------+------+------+------+
	Map Scale TLV		Map Scale TLV
	4.10.3. Map Example		4.11.3. Map Example
	An example of expressing a map is:		An example of expressing a map is:
	<rel:map>		<rel:map>
	<rel:url type="image/jpeg">		<rel:url type="image/jpeg">
	http://example.com/map.jpg		http://example.com/map.jpg
	</rel:url>		</rel:url>
	<rel:offset>200 210</rel:offset>		<rel:offset>200 210</rel:offset>
	<rel:orientation>68</rel:orientation>		<rel:orientation>68</rel:orientation>
	<rel:scale>2.90 -2.90</rel:scale>		<rel:scale>2.90 -2.90</rel:scale>
	skipping to change at page 25, line 34 ¶		skipping to change at page 26, line 34 ¶
	| 40 | BBuilding|A |		| 40 | BBuilding|A |
	| | |		| | |
	| 40 | AFloor|6th |		| 40 | AFloor|6th |
	| | |		| | |
	| 40 | BSuite|213 |		| 40 | BSuite|213 |
	| | |		| | |
	| 40 | ADoor|Front |		| 40 | ADoor|Front |
	| | |		| | |
	| 115 | 100 70 |		| 115 | 100 70 |
	| | |		| | |
	| 123 | image/png |		| 126 | image/png |
	| | |		| | |
	| 124 | http://maps.example.com/3400Wacker/A6 |		| 127 | http://maps.example.com/3400Wacker/A6 |
	| | |		| | |
	| 125 | 0.0 4120.0 |		| 128 | 0.0 4120.0 |
	| | |		| | |
	| 126 | 113.0 |		| 129 | 113.0 |
	| | |		| | |
	| 127 | 10.6 |		| 130 | 10.6 |
	+--------+-------------------------------------------------+		+--------+-------------------------------------------------+
	6. Schema Definition		6. Schema Definition
	<?xml version="1.0"?>		<?xml version="1.0"?>
	<xs:schema		<xs:schema
	xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"		xmlns:rel="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
	xmlns:xs="http://www.w3.org/2001/XMLSchema"		xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:gml="http://www.opengis.net/gml"		xmlns:gml="http://www.opengis.net/gml"
	targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:relative"		targetNamespace="urn:ietf:params:xml:ns:pidf:geopriv10:relative"
	skipping to change at page 29, line 22 ¶		skipping to change at page 30, line 22 ¶
	| RLtype | description | Reference |		| RLtype | description | Reference |
	+--------+-------+--------------------------------+-----------+		+--------+-------+--------------------------------+-----------+
	| 111 | relative location reference | this RFC |		| 111 | relative location reference | this RFC |
	| 112 | relative location angle | this RFC |		| 112 | relative location angle | this RFC |
	| 113 | relative location shape 2D point | this RFC |		| 113 | relative location shape 2D point | this RFC |
	| 114 | relative location shape 3D point | this RFC |		| 114 | relative location shape 3D point | this RFC |
	| 115 | relative location shape circular | this RFC |		| 115 | relative location shape circular | this RFC |
	| 116 | relative location shape spherical | this RFC |		| 116 | relative location shape spherical | this RFC |
	| 117 | relative location shape elliptical | this RFC |		| 117 | relative location shape elliptical | this RFC |
	| 118 | relative location shape ellipsoid | this RFC |		| 118 | relative location shape ellipsoid | this RFC |
	| 119 | relative location shape arc-band | this RFC |		| 119 | relative location shape 2D polygon | this RFC |
	| 120 | relative location shape 2D polygon | this RFC |		| 120 | relative location shape 3D polygon | this RFC |
	| 121 | relative location shape 3D polygon | this RFC |
	| 121 | relative location shape prism | this RFC |		| 121 | relative location shape prism | this RFC |
	| 122 | relative location map type | this RFC |		| 122 | relative location shape arc-band | this RFC |
	| 123 | relative location map URI | this RFC |		| 123 | relative location dynamic orientation | this RFC |
	| 124 | relative location map coordinates | this RFC |		| 124 | relative location dynamic speed | this RFC |
	| 125 | relative location map angle | this RFC |		| 125 | relative location dynamic heading | this RFC |
	| 126 | relative location map scale | this RFC |		| 126 | relative location map type | this RFC |
			| 127 | relative location map URI | this RFC |
			| 128 | relative location map coordinates | this RFC |
			| 129 | relative location map angle | this RFC |
			| 130 | relative location map scale | this RFC |
	+--------+-------+--------------------------------+-----------+		+--------+-------+--------------------------------+-----------+
	8.2. URN Sub-Namespace Registration		8.2. URN Sub-Namespace Registration
	This document registers a new XML namespace, as per the guidelines in		This document registers a new XML namespace, as per the guidelines in
	[RFC3688]) that has been registered with IANA.		[RFC3688]) that has been registered with IANA.
	URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative		URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative
	Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),		Registrant Contact: IETF, GEOPRIV working group (geopriv@ietf.org),
	skipping to change at page 32, line 8 ¶		skipping to change at page 33, line 8 ¶
	<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d</h2>		<h2>urn:ietf:params:xml:ns:pidf:geopriv10:relative:3d</h2>
	<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">		<p>See <a href="http://www.rfc-editor.org/rfc/rfcXXXX.txt">
	RFCXXXX</a>.</p>		RFCXXXX</a>.</p>
	</body>		</body>
	</html>		</html>
	<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX		<!-- [[NOTE TO RFC-EDITOR: Please replace all instances of RFCXXXX
	with the number of the published		with the number of the published
	document and remove this note.]] -->		document and remove this note.]] -->
	END		END
			8.5. CAtype Registration
			This section adds a new entry to the CAtype registry defined by
			[I-D.ietf-geopriv-local-civic].
			Namespace URI: urn:ietf:params:xml:ns:pidf:geopriv10:relative
			Local Name: REL
			Description: Relative location from a reference point
			Contact: The IESG (iesg@ietf.org); the GEOPRIV working group
			(geopriv@ietf.org).
			Specification: RFCXXXX
			Schema: urn:ietf:params:xml:schema:pidf:geopriv10:relativeLocation
			Type: A
	9. Acknowledgements		9. Acknowledgements
	This is the product of a design team on relative location. Besides		This is the product of a design team on relative location. Besides
	the authors, this team included: Marc Linsner, James Polk, and James		the authors, this team included: Marc Linsner, James Polk, and James
	Winterbottom.		Winterbottom.
	10. References		10. References
	10.1. Normative References		10.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in
	Requirement Levels", BCP 14, RFC 2119, March 1997.		RFCs to Indicate Requirement Levels",
			BCP 14, RFC 2119, March 1997.
	[RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic		[RFC4119] Peterson, J., "A Presence-based
	Host Configuration Protocol Option for Coordinate-		GEOPRIV Location Object Format",
	based Location Configuration Information", RFC 3825,		RFC 4119, December 2005.
	July 2004.
	[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location		[RFC4776] Schulzrinne, H., "Dynamic Host
	Object Format", RFC 4119, December 2005.		Configuration Protocol (DHCPv4 and
			DHCPv6) Option for Civic Addresses
			Configuration Information", RFC 4776,
			November 2006.
	[RFC4776] Schulzrinne, H., "Dynamic Host Configuration		[RFC5139] Thomson, M. and J. Winterbottom,
	Protocol (DHCPv4 and DHCPv6) Option for Civic		"Revised Civic Location Format for
	Addresses Configuration Information", RFC 4776,		Presence Information Data Format
	November 2006.		Location Object (PIDF-LO)", RFC 5139,
			February 2008.
	[RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic		[RFC5226] Narten, T. and H. Alvestrand,
	Location Format for Presence Information Data Format		"Guidelines for Writing an IANA
	Location Object (PIDF-LO)", RFC 5139, February 2008.		Considerations Section in RFCs",
			BCP 26, RFC 5226, May 2008.
	[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for		[RFC5491] Winterbottom, J., Thomson, M., and H.
	Writing an IANA Considerations Section in RFCs",		Tschofenig, "GEOPRIV Presence
	BCP 26, RFC 5226, May 2008.		Information Data Format Location
			Object (PIDF-LO) Usage Clarification,
			Considerations, and Recommendations",
			RFC 5491, March 2009.
	[RFC5491] Winterbottom, J., Thomson, M., and H. Tschofenig,		[RFC5962] Schulzrinne, H., Singh, V.,
	"GEOPRIV Presence Information Data Format Location		Tschofenig, H., and M. Thomson,
	Object (PIDF-LO) Usage Clarification,		"Dynamic Extensions to the Presence
	Considerations, and Recommendations", RFC 5491,		Information Data Format Location
	March 2009.		Object (PIDF-LO)", RFC 5962,
			September 2010.
	[RFC5962] Schulzrinne, H., Singh, V., Tschofenig, H., and M.		[RFC6225] Polk, J., Linsner, M., Thomson, M.,
	Thomson, "Dynamic Extensions to the Presence		and B. Aboba, "Dynamic Host
	Information Data Format Location Object (PIDF-LO)",		Configuration Protocol Options for
	RFC 5962, September 2010.		Coordinate-Based Location
			Configuration Information", RFC 6225,
			July 2011.
	[OGC.GML-3.1.1] Cox, S., Daisey, P., Lake, R., Portele, C., and A.		[I-D.ietf-geopriv-local-civic] Winterbottom, J., Thomson, M.,
	Whiteside, "Geographic information - Geography		Barnes, R., Rosen, B., and R. George,
	Markup Language (GML)", OpenGIS 03-105r1,		"Specifying Civic Address Extensions
	April 2004, <http://portal.opengeospatial.org/files/		in PIDF-LO",
	?artifact_id=4700>.		draft-ietf-geopriv-local-civic-02
			(work in progress), October 2011.
	[OGC.GeoShape] Thomson, M. and C. Reed, "GML 3.1.1 PIDF-LO Shape		[OGC.GML-3.1.1] Cox, S., Daisey, P., Lake, R.,
	Application Schema for use by the Internet		Portele, C., and A. Whiteside,
	Engineering Task Force (IETF)", OGC Best		"Geographic information - Geography
	Practice 06-142r1, Version: 1.0, April 2007.		Markup Language (GML)", OpenGIS 03-
			105r1, April 2004, <http://
			portal.opengeospatial.org/files/
			?artifact_id=4700>.
	[IEEE.754] IEEE, "IEEE Standard for Binary Floating-Point		[OGC.GeoShape] Thomson, M. and C. Reed, "GML 3.1.1
	Arithmetic", IEEE Standard 754-1985, January 2003.		PIDF-LO Shape Application Schema for
			use by the Internet Engineering Task
			Force (IETF)", OGC Best Practice 06-
			142r1, Version: 1.0, April 2007.
	[Clinger1990] Clinger, W., "How to Read Floating Point Numbers		[IEEE.754] IEEE, "IEEE Standard for Binary
	Accurately", Proceedings of Conference on		Floating-Point Arithmetic", IEEE
	Programming Language Design and Implementation pp.		Standard 754-1985, January 2003.
	92-101, 1990,
	<ftp://ftp.ccs.neu.edu/pub/people/will/		[Clinger1990] Clinger, W., "How to Read Floating
	howtoread.ps>.		Point Numbers Accurately",
			Proceedings of Conference on
			Programming Language Design and
			Implementation pp. 92-101, 1990, <ftp
			://ftp.ccs.neu.edu/pub/people/will/
			howtoread.ps>.
	10.2. Informative References		10.2. Informative References
	[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81,		[RFC3688] Mealling, M., "The IETF XML
	RFC 3688, January 2004.		Registry", BCP 81, RFC 3688,
			January 2004.
	[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter,		[RFC3986] Berners-Lee, T., Fielding, R., and L.
	"Uniform Resource Identifier (URI): Generic Syntax",		Masinter, "Uniform Resource
	STD 66, RFC 3986, January 2005.		Identifier (URI): Generic Syntax",
			STD 66, RFC 3986, January 2005.
	Authors' Addresses		Authors' Addresses
	Martin Thomson		Martin Thomson
	Andrew Corporation		Andrew Corporation
	Andrew Building (39)		Andrew Building (39)
	Wollongong University Campus		Wollongong University Campus
	Northfields Avenue		Northfields Avenue
	Wollongong, NSW 2522		Wollongong, NSW 2522
	AU		AU
End of changes. 45 change blocks.
	115 lines changed or deleted		208 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/