Internet Engineering Task Force
Internet Draft H. Schulzrinne
Columbia U.
draft-ietf-geopriv-dhcp-civil-00.txt
June 27, 2003
Expires: December 2003
DHCP Option for Civil Location
STATUS OF THIS MEMO
This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026.
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
http://www.ietf.org/ietf/1id-abstracts.txt
To view the list Internet-Draft Shadow Directories, see
http://www.ietf.org/shadow.html.
H. Schulzrinne [Page 1]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
Abstract
This document specifies a Dynamic Host Configuration Protocol option
for the civil (country, street and community) location of the client.
1 Terminology
In this document, the key words "MUST", "MUST NOT", "REQUIRED",
"SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY",
and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations.
2 Introduction
Many end system services can benefit by knowing the approximate
location of the end device. In particular, IP telephony devices need
to know their location to contact the appropriate emergency response
agency and to be found by emergency responders.
There are two common ways to identify the location of an object,
either through geospatial coordinates or by so-called civil
coordinates. Geospatial coordinates indicate longitude, latitude and
altitude, while civil coordinates indicate a street address.
This is commonly, but not necessearily, closely related to
the postal address, used by the local postal service to
deliver mail. However, not all postal addresses correspond
to street addresses. For example, the author's address is a
postal address that does not appear on any street or
building sign. Naturally, post office boxes would be
unsuitable for the purposes described here.
A related draft [8] describes a DHCP [2] option for conveying
geospatial information to a device. This draft describes how DHCP can
be used to convey the civil location to devices. Both can be used
simultaneously, increasing the chance to deliver accurate and timely
location information to emergency responders.
End systems that obtain location information via the mechanism
described here then use other protocol mechanisms to communicate this
information to the emergency call center.
Civil information is useful since it often provides additional,
human-usable information particularly within buildings. Also,
compared to geospatial information, it is readily obtained for most
occupied structures and can often be interpreted even if incomplete.
H. Schulzrinne [Page 2]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
For example, for many large university or corporate campuses,
geocoding information to building and room granularity may not be
readily available.
Unlike geospatial information, the format for civil information
differs from country to country. Thus, this draft establishes an IANA
registry for civil location data fields. The initial set of data
fields is derived from standards published by the United States
National Emergency Numbering Association (NENA) [3]. It is
anticipated that other countries can reuse many of the data elements.
3 Format of the DHCP Civil Location Option
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Code TBD | N | Countrycode |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| What | civil address elements ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Each civil address element has the following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CAtype | CAlength | CAvalue ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Code TBD: The code for this DHCP option is TBD by IANA.
N: The length of this option is variable.
Countrycode: The two-letter ISO country code in capital ASCII
letter, e.g., DE or US.
What: The 'what' element describes which location the DHCP
refers to. Currently, three options are defined: the
location of the DHCP server (0), the location of the
network element believed to be closest to the client (1) or
the location of the client (2). Option (2) SHOULD be used,
but may not be known. Options (1) and (2) SHOULD NOT be
H. Schulzrinne [Page 3]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
used unless it is known that the DHCP client is in close
physical proximity to the server or network element.
In some cases, the local wiring plant makes it
difficult to ascertain the device location with
certainty. In that case, it is still preferable to
indicate the DHCP server, Ethernet switch or router,
but indicate the uncertainty. This avoids that the
emergency responders try to break into the LAN closet.
CAtype: A one-octet descriptor of the data civil address value.
CAlength: The length, in octets, of the CAvalue, not including
the CAlength field itself. Data SHOULD be encoded in
uppercase.
CAvalue: The civil address value, encoded as UTF-8, and written
in uppercase letters where applicable.
4 Civil Address Components
Since each country has different administrative hierarchies, with
often the same (English) names, this specification adopts a simple
hierarchical notation that is then instantiated for each country. We
assume that five levels are sufficient for sub-national divisions
above the street level.
All elements are OPTIONAL and can appear in any order. Abbreviations
do not need a trailing period.
CAtype label description
___________________________________________________________________________
1 A1 national subdivisions (state, region, province, prefecture)
2 A2 county, parish, gun (JP), district (IN)
3 A3 city, township, shi (JP)
4 A4 city division, borough, city district, ward, chou (JP)
5 A5 neighborhood, block
6 A6 street
For specific countries, the administrative sub-divisions are
described below.
US: The mapping to NENA designations is shown in parentheses.
A1=state (STA), using the the two-letter state and
possession abbreviations recommended by the United States
Postal Service Publication 28 [4], Appendix B; A2=county
H. Schulzrinne [Page 4]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
(CNA); A3=civil community name (city or town) (MCN);
A6=street (STN). A4 and A5 are not used. The civil
community name (MCN) reflects the political boundaries.
These may differ from postal delivery assignments for
historical or practical reasons.
CA: The mapping to NENA designations is shown in parentheses.
A1=province (STA), A2=county (CNA), A3=city or town (MCN).
JP: A1=metropolis (To, Fu) or prefecture (Ken, Do); A2=city
(Shi) or rural area (Gun); A3=ward (Ku) or village (Mura);
A4=town (Chou or Machi); A5=city district (Choume);
A6=block (Banchi or Ban).
DE: A1=state (Bundesstaat); A2=county (Kreis); A3=city (Stadt,
Gemeinde); A6=street (Strasse).
Additional CA types appear in many countries and are simply omitted
where they are not used:
CAtype NENA description examples
___________________________________________________________________________
16 PRD leading street direction N
17 POD trailing street suffix SW
18 STS street suffix AVE, PLATZ
19 HNO house number 123
20 HNS house number suffix A, 1/2
21 LMK landmark or vanity address SHADELAND CRESCENT APTS
22 LOC additional location information APT 17
23 NAM name (residence and office occupant) JOE'S BARBERSHOP
24 ZIP postal/zip code 10027-1234
25 type of place
26 privacy
The CA types labeled in the second column correspond to items from
the NENA "Recommended Formats & Protocols For ALI Data Exchange, ALI
Response & GIS Mapping" [3], but are applicable to most countries.
The "NENA" column refers to the data dictionary name in Exhibit 18 of
[3].
The NAM object is used to aid user location ("Joe Miller" "Alice's
Dry Cleaning"). It does not identify the person using a
communications device, but rather the person or organization
associated with the address.
For POD and PRD, in English-speaking countries, the abbreviations N,
E, S, W, and NE, NW, SE, SW should be used.
H. Schulzrinne [Page 5]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
STS designates a street suffix. In the United States (US), the
abbreviations recommended by the United States Postal Service
Publication 28 [4], Appendix C, SHOULD be used.
The "type of place" item indicates whether the location is a 'home',
be registered with IANA and correspond to the "placetype" element in
[5].
The "privacy" object can have the string values
public: Others may be able to see or hear the communications.
private: Inappropriate individuals are not likely to see or hear
the communications.
quiet: The location is a place such as a library, restaurant,
place-of-worship, or theater that discourages noise,
conversation and other distractions.
Additional string values can be registered with IANA using the
registry established in [5].
The DHCP long-options mechanism described in RFC 3396 [6] MUST be
used if the civil address option exceeds the maximum DHCP option size
of 255 octets.
5 Security Considerations
The information in this option may be used for a variety of tasks. In
some cases, integrity of the information may be of great importance.
In such cases, DHCP authentication in [7] SHOULD be used to protect
the integrity of the DHCP options.
6 Acknowledgments
Rohan Mahy and Stefan Berger provided helpful comments.
7 References
8 Normative References
[1] S. Bradner, "Key words for use in RFCs to indicate requirement
levels," RFC 2119, Internet Engineering Task Force, Mar. 1997.
[2] R. E. Droms, "Dynamic host configuration protocol," RFC 2131,
Internet Engineering Task Force, Mar. 1997.
[3] National Emergency Number Assocation (NE, "NENA recommended
H. Schulzrinne [Page 6]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
formats & protocols for ALI data exchange, ALI response & GIS
mapping," Standard NENA-02-010, NENA, Washington, DC, Jan. 2002.
[4] U. S. P. Service, "Postal addressing standards," Publication 28,
USPS, Washington, DC, Nov. 2000.
[5] H. Schulzrinne et al., "RPIDS -- rich presence information data
format for presence based on the session initiation protocol (SIP),"
internet draft, Internet Engineering Task Force, Feb. 2003. Work in
progress.
[6] T. Lemon and S. Cheshire, "Encoding long options in the dynamic
host configuration protocol (dhcpv4)," RFC 3396, Internet Engineering
Task Force, Nov. 2002.
[7] R. E. Droms and W. Arbaugh, eds., "Authentication for DHCP
messages," RFC 3118, Internet Engineering Task Force, June 2001.
9 Informative References
[8] J. Polk et al., "DHCP option for geographic location," Internet
Draft, Internet Engineering Task Force, Oct. 2002. Work in progress.
10 Authors' Addresses
Henning Schulzrinne
Dept. of Computer Science
Columbia University
1214 Amsterdam Avenue
New York, NY 10027
USA
electronic mail: schulzrinne@cs.columbia.edu
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
H. Schulzrinne [Page 7]
Internet Draft DHCP Option for Civil Addresses June 27, 2003
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS 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.
H. Schulzrinne [Page 8]
Table of Contents
1 Terminology ......................................... 2
2 Introduction ........................................ 2
3 Format of the DHCP Civil Location Option ............ 3
4 Civil Address Components ............................ 4
5 Security Considerations ............................. 6
6 Acknowledgments ..................................... 6
7 References .......................................... 6
8 Normative References ................................ 6
9 Informative References .............................. 7
10 Authors' Addresses .................................. 7
H. Schulzrinne [Page 1]
