draft-ietf-geopriv-location-types-registry-06.txt   rfc4589.txt 
Geopriv H. Schulzrinne Network Working Group H. Schulzrinne
Internet-Draft Columbia U. Request for Comments: 4589 Columbia U.
Expires: November 22, 2006 H. Tschofenig Category: Standards Track H. Tschofenig
Siemens Siemens
May 21, 2006
Location Types Registry Location Types Registry
draft-ietf-geopriv-location-types-registry-06
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at Status of This Memo
http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 22, 2006. This document specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
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 ....................................................2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology .....................................................3
3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 6 3. Location Types ..................................................3
4. Schema . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 4. Schema ..........................................................6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. IANA Considerations .............................................7
5.1 Registering Tokens . . . . . . . . . . . . . . . . . . . . 11 5.1. Registering Tokens .........................................7
5.2 URN Sub-Namespace Registration for 5.2. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:location-type' . . . . . . . . . . 12 urn:ietf:params:xml:ns:location-type .......................8
5.3 Schema Registration for Schema 5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type . . . . . . . . . . . 12 urn:ietf:params:xml:ns:location-type .......................9
6. Internationalization Considerations . . . . . . . . . . . . . 13 6. Internationalization Considerations .............................9
7. Security Considerations . . . . . . . . . . . . . . . . . . . 14 7. Security Considerations .........................................9
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 15 8. Acknowledgements ................................................9
9. References . . . . . . . . . . . . . . . . . . . . . . . . . . 16 9. References .....................................................10
9.1 Normative References . . . . . . . . . . . . . . . . . . . 16 9.1. Normative References ......................................10
9.2 Informative References . . . . . . . . . . . . . . . . . . 16 9.2. Informative References ....................................10
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
to vibrate mode in such environments. Just knowing the geographic to vibrate mode in such environments. Just knowing the geographic
location, be it as civic (street address) or geospatial coordinates location, be it as civic (street address) or geospatial coordinates,
would generally not allow the device to make a similar decision. would generally not allow the device to make a similar decision.
Naturally, the number of descriptive terms for physical environments Naturally, the number of descriptive terms for physical environments
is almost unbounded. This registry tries to identify common terms is almost unbounded. This registry tries to identify common terms
that are likely to be useful for communications devices and for that are likely to be useful for communications devices and for
controlling and guiding communication behavior. The terms roughly controlling and guiding communications behavior. The terms roughly
correspond to the level of details of location descriptions and icons correspond to the level of details of location descriptions and icons
found on geographic maps, for example, and are meant to be in common found on geographic maps, for example, and are meant to be in common
use across a variety of cultures and countries. The registration use across a variety of cultures and countries. The registration
process described in the IANA Considerations section allows to extend process described in the IANA Considerations section allows this list
this list as needed, while aiming to prevent an unnecessary explosion to be extended as needed, while aiming to prevent an unnecessary
in the registry. explosion in the registry.
The use of tokens, i.e., protocol constants, makes it easier to build The use of tokens (i.e., protocol constants) makes it easier to build
systems across multiple languages. A user interface can readily systems across multiple languages. A user interface can readily
translate a finite set of tokens to user-appropriate textual or translate a finite set of tokens to user-appropriate textual or
iconic representations. Protocols using this registry are encouraged iconic representations. Protocols using this registry are encouraged
to provide additional mechanisms to accommodate location types not to provide additional mechanisms to accommodate location types not
currently registered via free-text fields with appropriate language currently registered via free-text fields with appropriate language
and character set labeling. and character set labeling.
The terms defined in this registry do not attempt to provide a The terms defined in this registry do not attempt to provide a
hierarchy of location descriptions, except in certain special cases. hierarchy of location descriptions, except in certain special cases.
For example, the term "restaurant" is defined to include the term For example, the term "restaurant" is defined to include the term
"cafe" and the term "public" encompasses a range of descriptors, as "cafe", and the term "public" encompasses a range of descriptors, as
noted below. The registry makes these more generic terms available noted below. The registry makes these more generic terms available
as often the more detailed distinctions may not be available, or as often the more detailed distinctions may not be available, or
privacy concerns suggest the use of less precise terms that are still privacy concerns suggest the use of less precise terms that are still
sufficient to guide communications behavior or evaluate the source of sufficient to guide communications behavior or evaluate the source of
a phone call or message, say. a phone call or message, say.
In many cases, a location might be described by multiple terms that In many cases, a location might be described by multiple terms that
apply at the same time. For example, the combination of "restaurant" apply at the same time. For example, the combination of "restaurant"
and "airport" is immediately recognizable. This registry makes no and "airport" is immediately recognizable. This registry makes no
attempt to limit the number of terms that can be used to describe a attempt to limit the number of terms that can be used to describe a
single place or to restrict what combinations are allowed, given that single place or to restrict what combinations are allowed, given that
there are few combinations that are physically impossible. Common there are few combinations that are physically impossible. Common
sense is probably a better guide here; the authors would not want to sense is probably a better guide here; the authors would not want to
rule out creative business models such as combinations of "parking" rule out creative business models such as combinations of "parking"
and "restaurant" or "bar" and "hospital". The number of terms that and "restaurant" or "bar" and "hospital". The number of terms that
can be used within the same protocol element is left to the protocol can be used within the same protocol element is left to the protocol
description. description.
This document does not describe how the values of the registry are to This document does not describe how the values of the registry are to
be used, as this description is provided by other documents. For be used, as this description is provided by other documents. For
example, [4], describes a options for carrying civic address example, [5] describes options for carrying civic address
information, including the place-type attributes listed in this information, including the place type attributes listed in this
document, using the Dynamic Host Configuration Protocol (DHCPv4 and document, using the Dynamic Host Configuration Protocol (DHCPv4 and
DHCPv6). A usage for RADIUS is described in [5], where this DHCPv6). A usage for Remote Authentication Dial-In User Service
information is conveyed from the RADIUS client to the RADIUS server. (RADIUS) is described in [6], where this information is conveyed from
Rich presence (RPID [6]) also utilizes the values of the location the RADIUS client to the RADIUS server. Rich presence (RPID [4])
type registry. also utilizes the values of the location types registry.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [1]. document are to be interpreted as described in [1].
3. Location Types 3. Location Types
This section describes types of location where an entity is located. This section describes types of locations where an entity is located.
The entity is not further specified and can be a person or an object The entity is not further specified and can be a person or an object
such as a network access point or end system. such as a network access point or end system.
aircraft: A device that is used or intended to be used for flight in aircraft: A device that is used or intended to be used for flight in
the air, such as an airplane, helicopter, gyroplane, glider or the air, such as an airplane, helicopter, gyroplane, glider, or
lighter-than-air devices like a balloon. lighter-than-air devices like a balloon.
airport: A place from which aircraft operate, such as an airport or airport: A place from which aircrafts operate, such as an airport or
heliport. heliport.
arena: Enclosed area used for sports events. arena: Enclosed area used for sports events.
automobile: A usually four-wheeled automotive vehicle designed for automobile: An automotive vehicle, usually four-wheeled, designed
passenger transportation, such as a car. for passenger transportation, such as a car.
bank: Business establishment in which money is kept for saving or bank: Business establishment in which money is kept for saving,
commercial purposes or is invested, supplied for loans, or commercial purposes, is invested, supplied for loans, or
exchanged. exchanged.
bar: A bar or saloon. bar: A bar or saloon.
bus: A large motor vehicle designed to carry passengers.
bicycle: A vehicle with two wheels tandem, a steering handle, a bicycle: A vehicle with two wheels tandem, a steering handle, a
saddle seat, and pedals by which it is propelled. saddle seat, and pedals by which it is propelled.
bus-station: Terminal that serves bus passengers, such as a bus depot bus: A large motor vehicle designed to carry passengers.
or bus terminal.
cafe: Usually small and informal establishment serving various bus-station: Terminal that serves bus passengers, such as a bus
depot or bus terminal.
cafe: Usually a small and informal establishment that serves various
refreshments (such as coffee); coffee shop. refreshments (such as coffee); coffee shop.
classroom: Academic classroom or lecture hall. classroom: Academic classroom or lecture hall.
club: Dance club, nightclub or discotheque. club: Dance club, nightclub, or discotheque.
construction: Construction site. construction: Construction site.
convention-center: Convention center or exhibition hall. convention-center: Convention center or exhibition hall.
government: Government building, such as those used by the government: Government building, such as those used by the
legislative, executive, or judicial branches of governments, legislative, executive, or judicial branches of governments,
including court houses, police stations and military including court houses, police stations, and military
installations. installations.
hospital: Hospital, hospice, medical clinic, mental institution, or hospital: Hospital, hospice, medical clinic, mental institution, or
doctor's office. doctor's office.
hotel: Hotel, motel, inn or other lodging establishment. hotel: Hotel, motel, inn, or other lodging establishment.
industrial: Industrial setting, such as a manufacturing floor or industrial: Industrial setting, such as a manufacturing floor or
power plant. power plant.
library: Library or other public place in which literary and artistic library: Library or other public place in which literary and
materials, such as books, music, periodicals, newspapers, artistic materials, such as books, music, periodicals, newspapers,
pamphlets, prints, records, and tapes, are kept for reading, pamphlets, prints, records, and tapes, are kept for reading,
reference, or lending. reference, or lending.
motorcycle: A two-wheeled automotive vehicle, including a scooter. motorcycle: A two-wheeled automotive vehicle, including a scooter.
office: Business setting, such as an office. office: Business setting, such as an office.
other: A place without a registered place type representation. other: A place without a registered place type representation.
outdoors: Outside a building, in or into the open air, such as a park outdoors: Outside a building, in or into the open air, such as a
or city streets. park or city streets.
parking: A parking lot or parking garage. parking: A parking lot or parking garage.
place-of-worship: A religious site where congregations gather for place-of-worship: A religious site where congregations gather for
religious observances, such as a church, chapel, meetinghouse, religious observances, such as a church, chapel, meetinghouse,
mosque, shrine, synagogue, or temple. mosque, shrine, synagogue, or temple.
prison: Correctional institution where persons are confined while on prison: Correctional institution where persons are confined while on
trial or for punishment, such as a prison, penitentiary, jail, trial or for punishment, such as a prison, penitentiary, jail,
brig. brig.
public: Public area such as a shopping mall, street, park, public public: Public area such as a shopping mall, street, park, public
building, train station, airport or in public conveyance such as a building, train station, or airport or in public conveyance such
bus, train, plane or ship. This general description encompasses as a bus, train, plane, or ship. This general description
the more precise descriptors 'street', 'public-transport', encompasses the more precise descriptors 'street', 'public-
'aircraft', 'bus', 'bus-station', 'train', 'train-station', transport', 'aircraft', 'bus', 'bus-station', 'train', 'train-
'airport', 'shopping-area', 'outdoors', and 'watercraft'. station', 'airport', 'shopping-area', 'outdoors', and
'watercraft'.
public-transport: Any form of public transport, including aircraft, public-transport: Any form of public transport, including aircraft,
bus, train or ship. bus, train, or ship.
residence: A private or residential setting, not necessarily the residence: A private or residential setting, not necessarily the
personal residence of the entity, e.g., including a friend's home. personal residence of the entity, e.g., including a friend's home.
restaurant: Restaurant, coffee shop or other public dining restaurant: Restaurant, coffee shop, or other public dining
establishment. establishment.
school: School or university property, but not necessarily a school: School or university property, but not necessarily a
classroom or library. classroom or library.
shopping-area: Shopping mall or shopping area. This area is a large, shopping-area: Shopping mall or shopping area. This area is a
often enclosed shopping complex containing various stores, large, often enclosed, shopping complex containing various stores,
businesses, and restaurants usually accessible by common businesses, and restaurants usually accessible by common
passageways. passageways.
stadium: Large, usually open structure for sports events, including a stadium: Large, usually open structure for sports events, including
racetrack. a racetrack.
store: Place where merchandise is offered for sale, such as a shop. store: Place where merchandise is offered for sale, such as a shop.
street: A public thoroughfare, such as a avenue, street, alley, lane, street: A public thoroughfare, such as an avenue, street, alley,
road, including any sidewalks. lane, or road, including any sidewalks.
theater: Theater, lecture hall, auditorium, class room, movie theater theater: Theater, lecture hall, auditorium, classroom, movie
or similar facility designed for presentations, talks, plays, theater, or similar facility designed for presentations, talks,
music performances and other events involving an audience. plays, music performances, and other events involving an audience.
train: Train, monorail, maglev, cable car or similar conveyance. train: Train, monorail, maglev, cable car, or similar conveyance.
train-station: Terminal where trains load or unload passengers or train-station: Terminal where trains load or unload passengers or
goods; railway station, railroad station, railroad terminal, train goods; railway station, railroad station, railroad terminal, train
depot. depot.
truck: An automotive vehicle suitable for hauling, used primarily to truck: An automotive vehicle suitable for hauling, used primarily to
carry goods rather than people. carry goods rather than people.
underway: In a land, water, or air craft which is underway (in underway: In a land-, water-, or aircraft that is underway (in
motion). motion).
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. Schema 4. Schema
This registry can be used in two ways, first,as a list of tokens, to 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 be referenced by appropriate protocols that accept textual tokens,
secondly as a schema, with its own namespace, referenced by other and second, as a schema, with its own namespace, referenced by other
schema, either explicity or via namespace="##other". schema, either explicitly or via namespace="##other".
<?xml version="1.0" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8"?>
<xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type" <xs:schema targetNamespace="urn:ietf:params:xml:ns:location-type"
xmlns="urn:ietf:params:xml:ns:location-type" xmlns="urn:ietf:params:xml:ns:location-type"
xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xs="http://www.w3.org/2001/XMLSchema"
elementFormDefault="qualified" elementFormDefault="qualified"
attributeFormDefault="unqualified"> attributeFormDefault="unqualified">
<xs:complexType name="empty"/> <xs:complexType name="empty"/>
<xs:complexType name="Note_t">
<xs:simpleContent>
<xs:extension base="xs:string">
<xs:attribute ref="xml:lang"/>
</xs:extension>
</xs:simpleContent>
</xs:complexType>
<xs:element name="aircraft" type="empty" /> <xs:element name="aircraft" type="empty" />
<xs:element name="airport" type="empty" /> <xs:element name="airport" type="empty" />
<xs:element name="arena" type="empty" /> <xs:element name="arena" type="empty" />
<xs:element name="automobile" type="empty" /> <xs:element name="automobile" type="empty" />
<xs:element name="bank" type="empty" /> <xs:element name="bank" type="empty" />
<xs:element name="bar" type="empty" /> <xs:element name="bar" type="empty" />
<xs:element name="bus" type="empty" />
<xs:element name="bicyle" type="empty" /> <xs:element name="bicyle" type="empty" />
<xs:element name="bus" type="empty" />
<xs:element name="bus-station" type="empty" /> <xs:element name="bus-station" type="empty" />
<xs:element name="cafe" type="empty" /> <xs:element name="cafe" type="empty" />
<xs:element name="classroom" type="empty" /> <xs:element name="classroom" type="empty" />
<xs:element name="club" type="empty" /> <xs:element name="club" type="empty" />
<xs:element name="construction" type="empty" /> <xs:element name="construction" type="empty" />
<xs:element name="convention-center" type="empty" /> <xs:element name="convention-center" type="empty" />
<xs:element name="government" type="empty" /> <xs:element name="government" type="empty" />
<xs:element name="hospital" type="empty" /> <xs:element name="hospital" type="empty" />
<xs:element name="hotel" type="empty" /> <xs:element name="hotel" type="empty" />
<xs:element name="industrial" type="empty" /> <xs:element name="industrial" type="empty" />
<xs:element name="library" type="empty" /> <xs:element name="library" type="empty" />
<xs:element name="motorcyle" type="empty" /> <xs:element name="motorcycle" type="empty" />
<xs:element name="office" type="empty" /> <xs:element name="office" type="empty" />
<xs:element name="other" type="Note_t"/>
<xs:element name="outdoors" type="empty" /> <xs:element name="outdoors" type="empty" />
<xs:element name="parking" type="empty" /> <xs:element name="parking" type="empty" />
<xs:element name="place-of-worship" type="empty" /> <xs:element name="place-of-worship" type="empty" />
<xs:element name="prison" type="empty" /> <xs:element name="prison" type="empty" />
<xs:element name="public" type="empty" /> <xs:element name="public" type="empty" />
<xs:element name="public-transport" type="empty" /> <xs:element name="public-transport" type="empty" />
<xs:element name="residence" type="empty" /> <xs:element name="residence" type="empty" />
<xs:element name="restaurant" type="empty" /> <xs:element name="restaurant" type="empty" />
<xs:element name="school" type="empty" /> <xs:element name="school" type="empty" />
<xs:element name="shopping-area" type="empty" /> <xs:element name="shopping-area" type="empty" />
skipping to change at page 11, line 7 skipping to change at page 7, line 44
<xs:element name="truck" type="empty" /> <xs:element name="truck" type="empty" />
<xs:element name="underway" type="empty" /> <xs:element name="underway" type="empty" />
<xs:element name="unknown" type="empty" /> <xs:element name="unknown" type="empty" />
<xs:element name="warehouse" type="empty" /> <xs:element name="warehouse" type="empty" />
<xs:element name="water" type="empty" /> <xs:element name="water" type="empty" />
<xs:element name="watercraft" type="empty" /> <xs:element name="watercraft" type="empty" />
</xs:schema> </xs:schema>
5. IANA Considerations 5. IANA Considerations
5.1 Registering Tokens 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 IANA will maintain this registry both in the form of an XML schema
and a list of tokens, with the same content. 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 Expert Reviewer appointed by the assigned after Expert Review. The Expert Reviewer will generally
IESG. The same procedure applies to updates of tokens within the consult the IETF GeoPRIV working group mailing list or its designated
registry and to deleting tokens from the registry. successor. Updates or deletions of tokens from the registration
follow the same procedures.
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; they should be well-
should be widely recognized. The Expert's support of IANA will defined and widely recognized. The expert's support of IANA will
include providing IANA with the new token(s) when the update is 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 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 new schema element(s) when the update is provided only in the form of
a token. 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 herein 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 XML namespace: Tokens MAY be used as elements within other
appropriate XML documents. Each token lists the namespace it is appropriate XML documents. Each token lists the namespace it is
part of, typically urn:ietf:params:xml:ns:location-type:ext, where part of, typically urn:ietf:params:xml:ns:location-type:ext, where
'ext' is the name of the extension. '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.2 URN Sub-Namespace Registration for 5.2. URN Sub-Namespace Registration for
'urn:ietf:params:xml:ns:location-type' urn:ietf:params:xml:ns:location-type
URI: 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 Description: This is the XML namespace for XML elements defined by
RFCXXXX [RFC editor: replace with RFC number] to describe RFC4589 to describe location types within XML documents.
location types within XML documents.
Registrant Contact: IETF, GEOPRIV working group, geopriv@ietf.org, Registrant Contact: IETF, GEOPRIV working group, geopriv@ietf.org,
Henning Schulzrinne, hgs@cs.columbia.edu Henning Schulzrinne, hgs@cs.columbia.edu
XML: XML:
BEGIN BEGIN
<?xml version="1.0"?> <?xml version="1.0"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN" <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML Basic 1.0//EN"
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml <html xmlns="http://www.w3.org/1999/xhtml
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
skipping to change at page 12, line 32 skipping to change at page 9, line 19
"http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd"> "http://www.w3.org/TR/xhtml-basic/xhtml-basic10.dtd">
<html xmlns="http://www.w3.org/1999/xhtml <html xmlns="http://www.w3.org/1999/xhtml
<head> <head>
<meta http-equiv="content-type" <meta http-equiv="content-type"
content="text/html;charset=iso-8859-1"/> content="text/html;charset=iso-8859-1"/>
<title>Location Types Registry</title> <title>Location Types Registry</title>
</head> </head>
<body> <body>
<h1>Namespace for Location Types</h1> <h1>Namespace for Location Types</h1>
<h2>urn:ietf:params:xml:ns:location-type</h2> <h2>urn:ietf:params:xml:ns:location-type</h2>
<p>See <a href="URL of published RFC">RFC&rfc.number; [RFC <p>See <a href="ftp://ftp.rfc-editor.org/in-notes/rfc4589.txt">
editor: replace with RFC number]</a>.</p> RFC4589</a>.</p>
</body> </body>
</html> </html>
END END
5.3 Schema Registration for Schema urn:ietf:params:xml:ns:location-type 5.3. Schema Registration for Schema
urn:ietf:params:xml:ns:location-type
URI: please assign URI: urn:ietf:params:xml:ns:location-type
Registrant Contact: IESG Registrant Contact: IESG
XML: See Section 4 XML: See Section 4
6. Internationalization Considerations 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.
7. 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.
8. Acknowledgements 8. Acknowledgements
Vijay Gurbani, Paul Kyzivat and Jonathan Rosenberg contributed to Vijay Gurbani, Paul Kyzivat, and Jonathan Rosenberg contributed to
RPID [6], which lead to the location types listed in this document. RPID [4], which led to the location types listed in this document.
Many thanks to Harald Alvestrand, Frank Ellermann, Bill Fenner, Ted Many thanks to Harald Alvestrand, Frank Ellermann, Bill Fenner, Ted
Hardie, David Kessens, Allison Mankin, Jon Peterson and Sam Hartman Hardie, David Kessens, Allison Mankin, Jon Peterson, and Sam Hartman
for their suggestions. Rick Jones pointed us to the Global Justice 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 XML work (see http://it.ojp.gov/jxdm/) that helped us to add more
values to the location registry. 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.
9. References 9. References
9.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] Sperberg-McQueen, C., Maler, E., Bray, T., Paoli, J., and F.
Maler, "Extensible Markup Language (XML) 1.0 (Third Edition)", Yergeau, "Extensible Markup Language (XML) 1.0 (Third Edition)",
W3C REC REC-xml-20040204, February 2004. World Wide Web Consortium
Recommendation http://www.w3.org/TR/2004/REC-xml-20040204,
February 2004.
9.2 Informative References 9.2. Informative References
[4] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4 [4] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence
and DHCPv6) Option for Civic Addresses Configuration Information Data Format (PIDF)", Work in Progress,
Information", draft-ietf-geopriv-dhcp-civil-09 (work in December 2005.
progress), January 2006.
[5] Tschofenig, H., "Carrying Location Objects in RADIUS", [5] Schulzrinne, H., "Dynamic Host Configuration Protocol (DHCPv4
draft-ietf-geopriv-radius-lo-06 (work in progress), March 2006. and DHCPv6) Option for Civic Addresses Configuration
Information", Work in Progress, January 2006.
[6] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence [6] Tschofenig, H., "Carrying Location Objects in RADIUS", Work in
Information Data Format (PIDF)", draft-ietf-simple-rpid-10 Progress, March 2006.
(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
450 Computer Science Building 450 Computer Science Building
New York, NY 10027 New York, NY 10027
USA USA
Phone: +1 212 939 7042 Phone: +1 212 939 7042
Email: schulzrinne@cs.columbia.edu EMail: schulzrinne@cs.columbia.edu
URI: http://www.cs.columbia.edu/~hgs URI: http://www.cs.columbia.edu/~hgs
Hannes Tschofenig Hannes Tschofenig
Siemens Siemens
Otto-Hahn-Ring 6 Otto-Hahn-Ring 6
Munich, Bavaria 81739 Munich, Bavaria 81739
Germany Germany
Email: Hannes.Tschofenig@siemens.com EMail: Hannes.Tschofenig@siemens.com
URI: http://www.tschofenig.com URI: http://www.tschofenig.com
Intellectual Property Statement Full Copyright Statement
Copyright (C) The Internet Society (2006).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79. found in BCP 78 and BCP 79.
skipping to change at page 18, line 29 skipping to change at page 12, line 45
such proprietary rights by implementers or users of this such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr. http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at this standard. Please address the information to the IETF at
ietf-ipr@ietf.org. ietf-ipr@ietf.org.
Disclaimer of Validity Acknowledgement
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement
Copyright (C) The Internet Society (2006). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights.
Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is provided by the IETF
Internet Society. Administrative Support Activity (IASA).
 End of changes. 71 change blocks. 
162 lines changed or deleted 152 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/