draft-ietf-geopriv-location-types-registry-00.txt   draft-ietf-geopriv-location-types-registry-01.txt 
Geopriv H. Schulzrinne Geopriv H. Schulzrinne
Internet-Draft Columbia U. Internet-Draft Columbia U.
Expires: May 29, 2005 H. Tschofenig Expires: January 6, 2006 H. Tschofenig
Siemens Siemens
November 28, 2004 July 5, 2005
Location Types Registry Location Types Registry
draft-ietf-geopriv-location-types-registry-00.txt draft-ietf-geopriv-location-types-registry-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is subject to all provisions By submitting this Internet-Draft, each author represents that any
of section 3 of RFC 3667. By submitting this Internet-Draft, each applicable patent or other IPR claims of which he or she is aware
author represents that any applicable patent or other IPR claims of have been or will be disclosed, and any of which he or she becomes
which he or she is aware have been or will be disclosed, and any of aware will be disclosed, in accordance with Section 6 of BCP 79.
which he or she become aware will be disclosed, in accordance with
RFC 3668.
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
other groups may also distribute working documents as other groups may also distribute working documents as Internet-
Internet-Drafts. Drafts.
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."
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 May 29, 2005. This Internet-Draft will expire on January 6, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). Copyright (C) The Internet Society (2005).
Abstract Abstract
This document creates a registry for location types. This document creates a registry for location types. The place types
'aircraft', 'airport', 'bus', 'car', home', 'hotel', 'industrial',
'library', 'mall', 'office', 'restaurant', 'school', 'ship',
'station', 'street', 'theater', 'hospital', 'train', 'truck',
'public' and 'public-transport' are created with this document.
Additional place types can be added on a 'First Come First Served'
policy.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 5 3. Location Types . . . . . . . . . . . . . . . . . . . . . . . . 5
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1 Normative References . . . . . . . . . . . . . . . . . . . . 11 7.1 Normative References . . . . . . . . . . . . . . . . . . . 11
7.2 Informative References . . . . . . . . . . . . . . . . . . . 11 7.2 Informative References . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 11
Intellectual Property and Copyright Statements . . . . . . . . 12 Intellectual Property and Copyright Statements . . . . . . . . 12
1. Introduction 1. Introduction
This document creates a registry for location types, such as bus, This document creates a registry for location types, such as bus,
airport or hotel. airport or hotel.
2. Terminology 2. Terminology
skipping to change at page 8, line 16 skipping to change at page 8, line 16
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
'public-transport' . 'public-transport' .
Following the policies outline in RFC 2434 [2], these tokens are Following the policies outline in RFC 2434 [2], these tokens are
assigned on a 'First Come First Served' policy. Each registration assigned on a 'First Come First Served' policy. Each registration
must include the name of the token and a brief description similar to must include the name of the token and a brief description similar to
the ones offered in for the initial registrations contained this the ones offered in for the initial registrations contained this
document: document:
XML Schema Name Data Type:
Token Identifier:
Identifier of the token Identifier of the token
Description: Description:
Brief description indicating the meaning of the token. Brief description indicating the meaning of the token.
Usage of these tokens is not limited to XML. However, it is expected Note that the usage of these tokens is not limited to XML and the
that XML imposes the most restrictions on the allowable syntax and 'Token Identifier' is the XML element content and not the XML element
thus all tokens must conform to the rules for XML Names. name.
5. Security Considerations 5. 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.
6. Acknowledgements 6. Acknowledgements
We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for We would like to thank V. Gurbani, P. Kyzivat and J. Rosenberg for
their work on RPID [3] which lead to the location types listed in their work on RPID [3] which lead to the location types listed in
this document. this document. Many thanks to Allison Mankin for her guidance.
7. References 7. References
7.1 Normative References 7.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", March 1997. Levels", 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.
7.2 Informative References 7.2 Informative References
[3] Schulzrinne, H., Gurbani, V., Kyzivat, P. and J. Rosenberg, [3] Schulzrinne, H., "RPID: Rich Presence Extensions to the Presence
"RPID: Rich Presence: Extensions to the Presence Information Information Data Format (PIDF)", draft-ietf-simple-rpid-07
Data Format (PIDF)", draft-ietf-simple-rpid-04 (work in (work in progress), June 2005.
progress), October 2004.
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 Intellectual Property Statement
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
skipping to change at page 12, line 41 skipping to change at page 12, line 41
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Copyright Statement Copyright Statement
Copyright (C) The Internet Society (2004). This document is subject Copyright (C) The Internet Society (2005). This document is subject
to the rights, licenses and restrictions contained in BCP 78, and to the rights, licenses and restrictions contained in BCP 78, and
except as set forth therein, the authors retain all their rights. except as set forth therein, the authors retain all their rights.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.24, available from http://www.levkowetz.com/ietf/tools/rfcdiff/