< draft-ietf-geopriv-location-types-registry-05.txt		draft-ietf-geopriv-location-types-registry-06.txt >
	Geopriv H. Schulzrinne		Geopriv H. Schulzrinne
	Internet-Draft Columbia U.		Internet-Draft Columbia U.
	Expires: September 7, 2006 H. Tschofenig		Expires: November 22, 2006 H. Tschofenig
	Siemens		Siemens
	March 6, 2006		May 21, 2006
	Location Types Registry		Location Types Registry
	draft-ietf-geopriv-location-types-registry-05		draft-ietf-geopriv-location-types-registry-06
	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 35 ¶		skipping to change at page 1, line 35 ¶
	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 September 7, 2006.		This Internet-Draft will expire on November 22, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document creates a registry for describing the types of places a		This document creates a registry for describing the types of places a
	human or end system might be found. The registry is then referenced		human or end system might be found. The registry is then referenced
	by other protocols that need a common set of location terms as		by other protocols that need a common set of location terms as
	protocol constants. Examples of location terms defined in this		protocol constants. Examples of location terms defined in this
	document include aircraft, office and train station.		document include aircraft, office and train station.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5		2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
	3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 6		3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 6
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9		4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
	5. Internationalization Considerations . . . . . . . . . . . . . 10		5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
	6. Security Considerations . . . . . . . . . . . . . . . . . . . 11		5.1 Registering Tokens . . . . . . . . . . . . . . . . . . . . 11
	7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 12		5.2 URN Sub-Namespace Registration for
	8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13		'urn:ietf:params:xml:ns:location-type' . . . . . . . . . . 12
	8.1 Normative References . . . . . . . . . . . . . . . . . . . 13		5.3 Schema Registration for Schema
	8.2 Informative References . . . . . . . . . . . . . . . . . . 13		urn:ietf:params:xml:ns:location-type . . . . . . . . . . . 12
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 13		6. Internationalization Considerations . . . . . . . . . . . . . 13
	Intellectual Property and Copyright Statements . . . . . . . . 15		7. Security Considerations . . . . . . . . . . . . . . . . . . . 14
			8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15
			9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16
			9.1 Normative References . . . . . . . . . . . . . . . . . . . 16
			9.2 Informative References . . . . . . . . . . . . . . . . . . 16
			Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 16
			Intellectual Property and Copyright Statements . . . . . . . . 18
	1. Introduction		1. Introduction
	This document creates a registry for location type tokens. We		This document creates a registry for location type tokens. We
	anticipate that the network, through configuration or management		anticipate that the network, through configuration or management
	protocols, tells a mobile device what kind of location it finds		protocols, tells a mobile device what kind of location it finds
	itself in. The device and associated software can then tailor its		itself in. The device and associated software can then tailor its
	behavior to the environment. For example, this document defines the		behavior to the environment. For example, this document defines the
	terms "classroom", "place-of-worship" and "theater". A considerate		terms "classroom", "place-of-worship" and "theater". A considerate
	owner of a cell phone might program the device to switch from ringer		owner of a cell phone might program the device to switch from ringer
	skipping to change at page 9, line 5 ¶		skipping to change at page 9, line 5 ¶
	unknown: The type of place is unknown.		unknown: The type of place is unknown.
	warehouse: Place in which goods or merchandise are stored, such as a		warehouse: Place in which goods or merchandise are stored, such as a
	storehouse or self-storage facility.		storehouse or self-storage facility.
	water: In, on or above bodies of water, such as an ocean, lake,		water: In, on or above bodies of water, such as an ocean, lake,
	river, canal or other waterway.		river, canal or other waterway.
	watercraft: On a vessel for travel on water such as a boat or ship.		watercraft: On a vessel for travel on water such as a boat or ship.
	4. IANA Considerations		4. Schema
			This registry can be used in two ways, first,as a list of tokens, to
			be referenced by appropriate protocols that accept textual tokens and
			secondly as a schema, with its own namespace, referenced by other
			schema, either explicity or via namespace="##other".
			<?xml version="1.0" encoding="UTF-8"?>
			<xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type"
			xmlns="urn:ietf:params:xml:ns:location-type"
			xmlns:xs="http://www.w3.org/2001/XMLSchema"
			elementFormDefault="qualified"
			attributeFormDefault="unqualified">
			<xs:complexType name="empty"/>
			<xs:element name="aircraft" type="empty" />
			<xs:element name="airport" type="empty" />
			<xs:element name="arena" type="empty" />
			<xs:element name="automobile" type="empty" />
			<xs:element name="bank" type="empty" />
			<xs:element name="bar" type="empty" />
			<xs:element name="bus" type="empty" />
			<xs:element name="bicyle" type="empty" />
			<xs:element name="bus-station" type="empty" />
			<xs:element name="cafe" type="empty" />
			<xs:element name="classroom" type="empty" />
			<xs:element name="club" type="empty" />
			<xs:element name="construction" type="empty" />
			<xs:element name="convention-center" type="empty" />
			<xs:element name="government" type="empty" />
			<xs:element name="hospital" type="empty" />
			<xs:element name="hotel" type="empty" />
			<xs:element name="industrial" type="empty" />
			<xs:element name="library" type="empty" />
			<xs:element name="motorcyle" type="empty" />
			<xs:element name="office" type="empty" />
			<xs:element name="outdoors" type="empty" />
			<xs:element name="parking" type="empty" />
			<xs:element name="place-of-worship" type="empty" />
			<xs:element name="prison" type="empty" />
			<xs:element name="public" type="empty" />
			<xs:element name="public-transport" type="empty" />
			<xs:element name="residence" type="empty" />
			<xs:element name="restaurant" type="empty" />
			<xs:element name="school" type="empty" />
			<xs:element name="shopping-area" type="empty" />
			<xs:element name="stadium" type="empty" />
			<xs:element name="store" type="empty" />
			<xs:element name="street" type="empty" />
			<xs:element name="theater" type="empty" />
			<xs:element name="train" type="empty" />
			<xs:element name="train-station" type="empty" />
			<xs:element name="truck" type="empty" />
			<xs:element name="underway" type="empty" />
			<xs:element name="unknown" type="empty" />
			<xs:element name="warehouse" type="empty" />
			<xs:element name="water" type="empty" />
			<xs:element name="watercraft" type="empty" />
			</xs:schema>
			5. IANA Considerations
			5.1 Registering Tokens
	This document creates new IANA registries for location types as		This document creates new IANA registries for location types as
	listed in Section 3 starting with 'aircraft' and finishing with		listed in Section 3 starting with 'aircraft' and finishing with
	'watercraft'.		'watercraft'.
			IANA will maintain this registry both in the form of an XML schema
			and a list of tokens, with the same content.
	Following the policies outline in RFC 2434 [2], new tokens are		Following the policies outline in RFC 2434 [2], new tokens are
	assigned after Expert Review by the IETF GEOPRIV working group or its		assigned after Expert Review by the Expert Reviewer appointed by the
	designated successor. The same procedure applies to updates of		IESG. The same procedure applies to updates of tokens within the
	tokens within the registry and to deleting tokens from the registry.		registry and to deleting tokens from the registry.
	There are no restrictions regarding the update of location-type
	values in the registry.
	The expert review should be guided by a few common-sense		The expert review should be guided by a few common-sense
	considerations. For example, tokens should not be specific to a		considerations. For example, tokens should not be specific to a
	country, region, organization or company, should be well-defined and		country, region, organization or company, should be well-defined and
	should be widely recognized.		should be widely recognized. The Expert's support of IANA will
			include providing IANA with the new token(s) when the update is
			provided only in the form of a schema, and providing IANA with the
			new schema element(s) when the update is provided only in the form of
			a token.
	To ensure widespread usability across protocols, tokens MUST follow		To ensure widespread usability across protocols, tokens MUST follow
	the character set restrictions for XML Names [3].		the character set restrictions for XML Names [3].
	Each registration must include the name of the token and a brief		Each registration must include the name of the token and a brief
	description similar to the ones offered in for the initial		description similar to the ones offered in for the initial
	registrations contained this document:		registrations contained this document:
	Token Identifier: Identifier of the token.		Token Identifier: Identifier of the token.
	Description: Brief description indicating the meaning of the token,		Description: Brief description indicating the meaning of the token,
	including one or more examples where the term encompasses several		including one or more examples where the term encompasses several
	more precise terms.		more precise terms.
			XML namespace: Tokens MAY be used as elements within other
			appropriate XML documents. Each token lists the namespace it is
			part of, typically urn:ietf:params:xml:ns:location-type:ext, where
			'ext' is the name of the extension.
	Note that the usage of these tokens is not limited to XML and the		Note that the usage of these tokens is not limited to XML and the
	'Token Identifier' is the XML element content and not the XML element		'Token Identifier' is the XML element content and not the XML element
	name.		name.
	5. Internationalization Considerations		5.2 URN Sub-Namespace Registration for
			'urn:ietf:params:xml:ns:location-type'
			URI: urn:ietf:params:xml:ns:location-type
			Description: This is the XML namespace for XML elements defined by
			RFCXXXX [RFC editor: replace with RFC number] to describe
			location types within XML documents.
			Registrant Contact: IETF, GEOPRIV working group, geopriv@ietf.org,
			Henning Schulzrinne, hgs@cs.columbia.edu
			XML:
			BEGIN
			<?xml version="1.0"?>
			<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
			"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
			<html xmlns="http://www.w3.org/1999/xhtml
			<head>
			<meta http-equiv="content-type"
			content="text/html;charset=iso-8859-1"/>
			<title>Location Types Registry</title>
			</head>
			<body>
			<h1>Namespace for Location Types</h1>
			<h2>urn:ietf:params:xml:ns:location-type</h2>
			<p>See <a href="URL of published RFC">RFC&rfc.number; [RFC
			editor: replace with RFC number]</a>.</p>
			</body>
			</html>
			END
			5.3 Schema Registration for Schema urn:ietf:params:xml:ns:location-type
			URI: please assign
			Registrant Contact: IESG
			XML: See Section 4
			6. Internationalization Considerations
	The location-type values listed in this document MUST NOT be		The location-type values listed in this document MUST NOT be
	presented to the user. The values therefore have the characteristic		presented to the user. The values therefore have the characteristic
	of tokens or tags and no internationalization support is required.		of tokens or tags and no internationalization support is required.
	6. Security Considerations		7. Security Considerations
	This document defines a registry for location types and as such does		This document defines a registry for location types and as such does
	not raise security issues.		not raise security issues.
	7. Acknowledgements		8. Acknowledgements
	We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for
	their work on RPID [6] which lead to the location types listed in
	this document. Many thanks to Allison Mankin for her guidance. Rick
	Jones pointed us to the Global Justice XML work (see
	http://it.ojp.gov/jxdm/) that helped us to add more values to the
	location registry.
	During the IETF last call, Harald Tveit Alvestrand, Frank Ellermann		Vijay Gurbani, Paul Kyzivat and Jonathan Rosenberg contributed to
	and Sam Hartman provided useful feedback. David Kessens helped to		RPID [6], which lead to the location types listed in this document.
	tighten up many of the defintions.		Many thanks to Harald Alvestrand, Frank Ellermann, Bill Fenner, Ted
			Hardie, David Kessens, Allison Mankin, Jon Peterson and Sam Hartman
			for their suggestions. Rick Jones pointed us to the Global Justice
			XML work (see http://it.ojp.gov/jxdm/) that helped us to add more
			values to the location registry.
	Some of the definitions are derived from the Merriam-Webster Online		Some of the definitions are derived from the Merriam-Webster Online
	Dictionary.		Dictionary.
	8. References		9. References
	8.1 Normative References		9.1 Normative References
	[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement		[1] Bradner, S., "Key words for use in RFCs to Indicate Requirement
	Levels", BCP 14, RFC 2119, March 1997.		Levels", BCP 14, RFC 2119, March 1997.
	[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA		[2] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
	Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.		Considerations Section in RFCs", BCP 26, RFC 2434, October 1998.
	[3] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E.		[3] Yergeau, F., Paoli, J., Sperberg-McQueen, C., Bray, T., and E.
	Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)",		Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)",
	W3C REC REC-xml-20040204, February 2004.		W3C REC REC-xml-20040204, February 2004.
	8.2 Informative References		9.2 Informative References
	[4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4		[4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
	and DHCPv6) Option for Civic Addresses Configuration		and DHCPv6) Option for Civic Addresses Configuration
	Information", draft-ietf-geopriv-dhcp-civil-09 (work in		Information", draft-ietf-geopriv-dhcp-civil-09 (work in
	progress), January 2006.		progress), January 2006.
	[5] Tschofenig, H., "Carrying Location Objects in RADIUS",		[5] Tschofenig, H., "Carrying Location Objects in RADIUS",
	draft-ietf-geopriv-radius-lo-05 (work in progress),		draft-ietf-geopriv-radius-lo-06 (work in progress), March 2006.
	February 2006.
	[6] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence		[6] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence
	Information Data Format (PIDF)", draft-ietf-simple-rpid-10		Information Data Format (PIDF)", draft-ietf-simple-rpid-10
	(work in progress), December 2005.		(work in progress), December 2005.
	Authors' Addresses		Authors' Addresses
	Henning Schulzrinne		Henning Schulzrinne
	Columbia University		Columbia University
	Department of Computer Science		Department of Computer Science
End of changes. 18 change blocks.
	38 lines changed or deleted		154 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/