< draft-ietf-geopriv-dhcp-civil-01.txt   draft-ietf-geopriv-dhcp-civil-02.txt >
GEOPRIV H. Schulzrinne GEOPRIV H. Schulzrinne
Internet-Draft Columbia U. Internet-Draft Columbia U.
Expires: August 8, 2004 February 8, 2004 Expires: September 18, 2004 March 20, 2004
DHCP Option for Civil Addresses Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for
draft-ietf-geopriv-dhcp-civil-01 Civic Addresses
draft-ietf-geopriv-dhcp-civil-02
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3667.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet-Drafts. groups may also distribute working documents as Internet-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 http:// The list of current Internet-Drafts can be accessed at http://
www.ietf.org/ietf/1id-abstracts.txt. 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 August 8, 2004. This Internet-Draft will expire on September 18, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
This document specifies a Dynamic Host Configuration Protocol (DHCP) This document specifies a Dynamic Host Configuration Protocol (DHCPv4
option for the civil (country, street and community) location of the and DHCPv6) option for the civic (country, community and street)
client. location of the client or the DHCP server.
Table of Contents Table of Contents
1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Format of the DHCP Civil Location Option . . . . . . . . . . . 5 3. Format of the DHCP Civic Location Option . . . . . . . . . . . 6
4. Civil Address Components . . . . . . . . . . . . . . . . . . . 6 3.1 Overall Format for DHCPv4 . . . . . . . . . . . . . . . . . . 6
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9 3.2 Overall Format for DHCPv6 . . . . . . . . . . . . . . . . . . 6
Normative References . . . . . . . . . . . . . . . . . . . . . 10 3.3 Element Format . . . . . . . . . . . . . . . . . . . . . . . . 7
Informative References . . . . . . . . . . . . . . . . . . . . 11 3.4 Civic Address Components . . . . . . . . . . . . . . . . . . . 7
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 11 4. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 12 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
Intellectual Property and Copyright Statements . . . . . . . . 13 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
Normative References . . . . . . . . . . . . . . . . . . . . . 14
Informative References . . . . . . . . . . . . . . . . . . . . 15
Author's Address . . . . . . . . . . . . . . . . . . . . . . . 15
A. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16
Intellectual Property and Copyright Statements . . . . . . . . 17
1. Terminology 1. Terminology
In this document, the key words "MUST", "MUSTNOT", "REQUIRED", In this document, the key words "MUST", "MUSTNOT", "REQUIRED",
"SHALL", "SHALLNOT", "SHOULD", "SHOULDNOT", "RECOMMENDED", "MAY", and "SHALL", "SHALLNOT", "SHOULD", "SHOULDNOT", "RECOMMENDED", "MAY", and
"OPTIONAL" are to be interpreted as described in RFC 2119 [1] and "OPTIONAL" are to be interpreted as described in RFC 2119 [1] and
indicate requirement levels for compliant implementations. indicate requirement levels for compliant implementations.
2. Introduction 2. Introduction
Many end system services can benefit by knowing the approximate Many end system services can benefit by knowing the approximate
location of the end device. In particular, IP telephony devices need location of the end device. In particular, IP telephony devices need
to know their location to contact the appropriate emergency response to know their location to contact the appropriate emergency response
agency and to be found by emergency responders. agency and to be found by emergency responders.
There are two common ways to identify the location of an object, There are two common ways to identify the location of an object,
either through geospatial coordinates or by so-called civil either through geospatial coordinates or by so-called civic address.
coordinates. Geospatial coordinates indicate longitude, latitude and Geospatial coordinates indicate longitude, latitude and altitude,
altitude, while civil coordinates indicate a street address. while civic addresses indicate a street address.
A related draft [6] describes a DHCP [2] option for conveying A related draft [13] describes a DHCPv4 [2] option for conveying
geospatial information to a device. This draft describes how DHCP geospatial information to a device. This draft describes how DHCPv4
can be used to convey the civil location to devices. Both can be and DHCPv6 [5] can be used to convey the civic location to devices.
used simultaneously, increasing the chance to deliver accurate and Both can be used simultaneously, increasing the chance to deliver
timely location information to emergency responders. accurate and timely location information to emergency responders.
End systems that obtain location information via the mechanism End systems that obtain location information via the mechanism
described here then use other protocol mechanisms to communicate this described here then use other protocol mechanisms to communicate this
information to the emergency call center. information to the emergency call center or to convey it as part of
presence information.
Civil information is useful since it often provides additional, Civic information is useful since it often provides additional,
human-usable information particularly within buildings. Also, human-usable information particularly within buildings. Also,
compared to geospatial information, it is readily obtained for most compared to geospatial information, it is readily obtained for most
occupied structures and can often be interpreted even if incomplete. occupied structures and can often be interpreted even if incomplete.
For example, for many large university or corporate campuses, For example, for many large university or corporate campuses,
geocoding information to building and room granularity may not be geocoding information to building and room granularity may not be
readily available. readily available.
Unlike geospatial information, the format for civil information Unlike geospatial information, the format for civic information
differs from country to country. Thus, this draft establishes an differs from country to country. Thus, this draft establishes an
IANA registry for civil location data fields. The initial set of IANA registry for civic location data fields. The initial set of
data fields is derived from standards published by the United States data fields is derived from standards published by the United States
National Emergency Numbering Association (NENA) [8]. It is National Emergency Number Association (NENA) [15]. It is anticipated
anticipated that other countries can reuse many of the data elements. that other countries can reuse many of the data elements.
3. Format of the DHCP Civil Location Option The same civic address information can often be rendered in multiple
languages and scripts. For example, Korean addresses are often shown
in Hangul, Latin and Kanji, while some older cities have multiple
language variants (Munich, Muenchen and Monaco, for example). Since
DHCPv4 and DHCPv6 do not currently support a mechanism to query for a
specific script or language, the DHCP server SHOULD provide all
common renderings to the client and MUST provide at least the
rendering in the language and script appropriate to the location
indicated. For example, for use in presence information, the target
may be visiting from a foreign country and want to convey the
information in a format suitable for watchers in its home country.
For emergency services, the rendering in the local language is likely
to be most appropriate. To provide multiple renderings, the client
repeats sequences of address elements, prefixing each with 'language'
and/or 'script' element (see Section 3.3). The language and script
remain in effect for subsequent elements until overridden by another
language or script element.
0 1 2 3 The DHCP long-options mechanism described in RFC 3396 [8] MUST be
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 used if the civic address option exceeds the maximum DHCP option size
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ of 255 octets.
| Code TBD | N | Countrycode |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| What | civil address elements ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Each civil address element has the following format: 3. Format of the DHCP Civic Location Option
3.1 Overall Format for DHCPv4
0 1 2 3 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 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 | N | Countrycode |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| What | civic address elements ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Code TBD: The code for this DHCP option is TBD by IANA. Code TBD: The code for this DHCP option is TBD by IANA.
N: The length of this option is variable. N: The length of this option is variable.
Countrycode: The two-letter ISO 3166 country code in capital ASCII Countrycode: The two-letter ISO 3166 country code in capital ASCII
letters, e.g., DE or US. letters, e.g., DE or US.
What: The 'what' element describes which location the DHCP refers to. What: The 'what' element describes which location the DHCP refers to.
Currently, three options are defined: the location of the DHCP Currently, three options are defined: the location of the DHCP
server (0), the location of the network element believed to be server (a value of 0), the location of the network element
closest to the client (1) or the location of the client (2). believed to be closest to the client (1) or the location of the
Option (2) SHOULD be used, but may not be known. Options (1) and client (2). Option (2) SHOULD be used, but may not be known.
(2) SHOULDNOT be used unless it is known that the DHCP client is Options (1) and (2) SHOULD NOT be used unless it is known that the
in close physical proximity to the server or network element. DHCP client is in close physical proximity to the server or
network element.
CAtype: A one-octet descriptor of the data civil address value. Civic address element: Zero or more elements comprising the civic
address, with the format described below (Section 3.3).
3.2 Overall Format for DHCPv6
The DHCPv6 [5] civic address option refers generally to the client as
a whole.
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| OPTION_CIVIC_ADDRESS | option-len |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Countrycode | what | elements ...
| civic address elements |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
option-code: OPTION_CIVIC_ADDRESS (TBD)
option-len: Length of the Countrycode, 'what' and civic address
elements.
Countrycode: See above (Section 3.1).
What: See above (Section 3.1).
Civic address element: See above (Section 3.1).
3.3 Element Format
For both DHCPv4 and DHCPv6, each civic 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 ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
CAtype: A one-octet descriptor of the data civic address value.
CAlength: The length, in octets, of the CAvalue, not including the CAlength: The length, in octets, of the CAvalue, not including the
CAlength field itself. Data SHOULD be encoded in uppercase. CAlength field itself. Data SHOULD be encoded in mixed case,
following the customary spelling.
CAvalue: The civil address value, encoded as UTF-8, and written in CAvalue: The civic address value, encoded as UTF-8 [6], and written
uppercase letters where applicable. in uppercase letters where applicable. The script indication is
written in mixed-case, with the first letter a capital letter.
4. Civil Address Components Elements SHOULD be included in numeric order from lowest to highest
of their CAtype if the server only provides one language and script
rendition. In general, an element is labeled in its language and
script by the most recent 'language tag' (CAtype = 0) element
preceding it. Since not all elements depend on the script and
language, a client accumulates the elements by CAtype and then
selects the most desirable language and script rendition if there are
multiple elements for the same CAtype.
3.4 Civic Address Components
Since each country has different administrative hierarchies, with Since each country has different administrative hierarchies, with
often the same (English) names, this specification adopts a simple often the same (English) names, this specification adopts a simple
hierarchical notation that is then instantiated for each country. We hierarchical notation that is then instantiated for each country. We
assume that five levels are sufficient for sub-national divisions assume that five levels are sufficient for sub-national divisions
above the street level. above the street level.
All elements are OPTIONAL and can appear in any order. Abbreviations All elements are OPTIONAL and can appear in any order. Abbreviations
do not need a trailing period. do not need a trailing period.
skipping to change at page 6, line 46 skipping to change at page 8, line 39
| 5 | A5 | neighborhood, block | | 5 | A5 | neighborhood, block |
| | | | | | | |
| 6 | A6 | street | | 6 | A6 | street |
+----------------------+----------------------+---------------------+ +----------------------+----------------------+---------------------+
Table 1 Table 1
For specific countries, the administrative sub-divisions are For specific countries, the administrative sub-divisions are
described below. described below.
US (United States): 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 [7], Appendix B; A2=county (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 (Canada): The mapping to NENA designations is shown in CA (Canada): The mapping to NENA designations is shown in
parentheses. A1=province (STA), A2=county (CNA), A3=city or town parentheses. A1=province (STA); A2=county (CNA); A3=city or town
(MCN). (MCN); A6=street (STN).
DE (Germany): A1=state (Bundesstaat); A2=county (Regierungsbezirk);
A3=city (Stadt, Gemeinde); A6=street (Strasse). Street suffixes
(STS) are used only for designations that are a separate word
(e.g., Marienthaler Strasse).
JP (Japan): A1=metropolis (To, Fu) or prefecture (Ken, Do); A2=city JP (Japan): A1=metropolis (To, Fu) or prefecture (Ken, Do); A2=city
(Shi) or rural area (Gun); A3=ward (Ku) or village (Mura); A4=town (Shi) or rural area (Gun); A3=ward (Ku) or village (Mura); A4=town
(Chou or Machi); A5=city district (Choume); A6=block (Banchi or (Chou or Machi); A5=city district (Choume); A6=block (Banchi or
Ban). Ban).
DE (Germany): A1=state (Bundesstaat); A2=county (Kreis); A3=city KR (Korea): A1=province (Do); A2=county (gun); A3=city or village
(Stadt, Gemeinde); A6=street (Strasse). (ri); A4=urban district (gu); A5=neighborhood (dong); A6=street
(no, ro, ga or gil).
US (United States): 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 [14], Appendix B; A2=county (CNA); A3=civic
community name (city or town) (MCN); A6=street (STN). A4 and A5
are not used. The civic community name (MCN) reflects the
political boundaries. These may differ from postal delivery
assignments for historical or practical reasons.
Additional CA types appear in many countries and are simply omitted Additional CA types appear in many countries and are simply omitted
where they are not needed: where they are not needed or known:
+----------------+----------------+----------------+----------------+ +----------------+----------------+----------------+----------------+
| CAtypej | NENA | Description | Examples | | CAtype | NENA | Description | Examples |
+----------------+----------------+----------------+----------------+ +----------------+----------------+----------------+----------------+
| 0 | | language | i-default [3] |
| | | | |
| 16 | PRD | leading street | N | | 16 | PRD | leading street | N |
| | | direction | | | | | direction | |
| | | | | | | | | |
| 17 | POD | trailing | SW | | 17 | POD | trailing | SW |
| | | street suffix | | | | | street suffix | |
| | | | | | | | | |
| 18 | STS | street suffix | AVE, PLATZ | | 18 | STS | street suffix | AVE, PLATZ |
| | | | | | | | | |
| 19 | HNO | house number | 123 | | 19 | HNO | house number | 123 |
| | | | | | | | | |
skipping to change at page 8, line 4 skipping to change at page 10, line 5
| | | information | | | | | information | |
| | | | | | | | | |
| 23 | NAM | name | JOE'S | | 23 | NAM | name | JOE'S |
| | | (residence and | BARBERSHOP | | | | (residence and | BARBERSHOP |
| | | office | | | | | office | |
| | | occupant) | | | | | occupant) | |
| | | | | | | | | |
| 24 | ZIP | postal/zip | 10027-1234 | | 24 | ZIP | postal/zip | 10027-1234 |
| | | code | | | | | code | |
| | | | | | | | | |
| 25 | | type of place | | | 25 | | placetype | office |
| | | | | | | | | |
| 26 | | floor | | | 26 | | floor | 4 |
| | | | | | | | | |
| 27 | | room number | | | 27 | | room number | 450F |
| | | | |
| 128 | | script | Latn |
| | | | |
| 255 | | reserved | |
+----------------+----------------+----------------+----------------+ +----------------+----------------+----------------+----------------+
The CA types labeled in the second column correspond to items from The CA types labeled in the second column correspond to items from
the NENA "Recommended Formats & Protocols For ALI Data Exchange, ALI the NENA "Recommended Formats & Protocols For ALI Data Exchange, ALI
Response & GIS Mapping" [8], but are applicable to most countries. Response & GIS Mapping" [15], but are applicable to most countries.
The "NENA" column refers to the data dictionary name in Exhibit 18 of The "NENA" column refers to the data dictionary name in Exhibit 18 of
[8]. [15].
The "language" item (CAtype 0) optionally identifies the language
used for presenting the address information, drawing from the tags
for identifying languages in [7]. If omitted, the default value for
this tag is "i-default" [3].
The "script" item (CAtype 128) optionally identifies the script used
for presenting the address information, drawing from the tags for
identifying scripts in ISO 15924 [11]. If omitted, the default value
for this tag is "Latn".
The NAM object is used to aid user location ("Joe Miller" "Alice's The NAM object is used to aid user location ("Joe Miller" "Alice's
Dry Cleaning"). It does not identify the person using a Dry Cleaning"). It does not identify the person using a
communications device, but rather the person or organization communications device, but rather the person or organization
associated with the address. associated with the address.
For POD and PRD, in English-speaking countries, the abbreviations N, For POD and PRD, in English-speaking countries, the abbreviations N,
E, S, W, and NE, NW, SE, SW should be used. E, S, W, and NE, NW, SE, SW should be used.
STS designates a street suffix. In the United States (US), the STS designates a street suffix. In the United States (US), the
abbreviations recommended by the United States Postal Service abbreviations recommended by the United States Postal Service
Publication 28 [7], Appendix C, SHOULD be used. Publication 28 [14], Appendix C, SHOULD be used.
The "type of place" item indicates whether the location is a 'home',
'office' or 'public', using text strings. Additional text strings
can be registered with IANA and correspond to the "placetype" element
in [9].
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 The "type of place" item (CAtype 25) describes the type of place
communications. described by the civic coordinates. For example, it describes
whether it is a home, office, street or other public space. The
values are drawn from the items in the rich presence [16] document.
This information makes it easy, for example, for the DHCP client to
then populate the presence information. Since this is an
IANA-registered token, the language and script designations do not
apply for this element.
quiet: The location is a place such as a library, restaurant, 4. Example
place-of-worship, or theater that discourages noise, conversation
and other distractions.
Additional string values can be registered with IANA using the Rather than showing the precise byte layout of a DHCP option, we show
registry established in [9]. a symbolic example below, representing the civic address of the
Munich city hall in Bavaria, Germany. The city and state name are
also conveyed in English and Italian in addition to German; the other
items are assumed to be common across all languages. All languages
use the latin script.
The DHCP long-options mechanism described in RFC 3396 [3] MUST be +--------+---------------+
used if the civil address option exceeds the maximum DHCP option size | CAtype | CAvalue |
of 255 octets. +--------+---------------+
| 0 | de |
| | |
| 128 | Latn |
| | |
| 1 | Bayern |
| | |
| 2 | Oberbayern |
| | |
| 3 | M=U+00FCnchen |
| | |
| 6 | Marienplatz |
| | |
| 19 | 8 |
| | |
| 21 | Rathaus |
| | |
| 24 | 80331 |
| | |
| 25 | public |
| | |
| 0 | en |
| | |
| 1 | Bavaria |
| | |
| 3 | Munich |
| | |
| 0 | it |
| | |
| 1 | Baviera |
| | |
| 3 | Monaco |
+--------+---------------+
5. Security Considerations 5. Security Considerations
The information in this option may be used for a variety of tasks. In 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. some cases, integrity of the information may be of great importance.
In such cases, DHCP authentication in RFC3118 [4] SHOULD be used to In such cases, DHCP authentication in RFC3118 [4] SHOULD be used to
protect the integrity of the DHCP options. protect the integrity of the DHCP options.
6. IANA Considerations
This document requests that IANA register a new DHCPv4 and DHCPv6
option code for the Civic Address .
This document establishes a new IANA registry for CAtypes designating
civic address components. According to RFC 2434 [12], this registry
operates under the "Specification Required" rules. The IANA
registration needs to include the following information:
CAType: Numeric identifier, assigned by IANA.
Brief description: Short description identifying the meaning of the
element.
Reference to published specification: A stable reference to an RFC or
other permanent and readily available reference, in sufficient
detail so that interoperability between independent
implementations is possible.
Country-specific considerations: If applicable, notes whether the
element is only applicable or defined for certain countries.
Normative References 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] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131, [2] Droms, R., "Dynamic Host Configuration Protocol", RFC 2131,
March 1997. March 1997.
[3] Lemon, T. and S. Cheshire, "Encoding Long Options in the Dynamic [3] Alvestrand, H., "IETF Policy on Character Sets and Languages",
Host Configuration Protocol (DHCPv4)", RFC 3396, November 2002. BCP 18, RFC 2277, January 1998.
[4] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages", [4] Droms, R. and W. Arbaugh, "Authentication for DHCP Messages",
RFC 3118, June 2001. RFC 3118, June 2001.
[5] Sugano, H. and S. Fujimoto, "Presence Information Data Format [5] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C. and M.
(PIDF)", draft-ietf-impp-cpim-pidf-08 (work in progress), May Carney, "Dynamic Host Configuration Protocol for IPv6
2003. (DHCPv6)", RFC 3315, July 2003.
[6] Yergeau, F., "UTF-8, a transformation format of ISO 10646", STD
63, RFC 3629, November 2003.
[7] Alvestrand, H., "Tags for the Identification of Languages", BCP
47, RFC 3066, January 2001.
[8] Lemon, T. and S. Cheshire, "Encoding Long Options in the
Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
November 2002.
[9] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004.
[10] Sugano, H. and S. Fujimoto, "Presence Information Data Format
(PIDF)", draft-ietf-impp-cpim-pidf-08 (work in progress), May
2003.
[11] International Organization for Standardization, ISO.,
"Information and documentation - Codes for the representation
of names of scripts", February 2004.
Informative References Informative References
[6] Polk, J., Schnizlein, J. and M. Linsner, "Dynamic Host [12] Narten, T. and H. Alvestrand, "Guidelines for Writing an IANA
Configuration Protocol Option for Coordinate-based Location Considerations Section in RFCs", BCP 26, RFC 2434, October
Configuration Information", 1998.
draft-ietf-geopriv-dhcp-lci-option-03 (work in progress),
December 2003.
[7] United States Postal Service, "Postal Addressing Standards", [13] Polk, J., Schnizlein, J. and M. Linsner, "Dynamic Host
November 2000. Configuration Protocol Option for Coordinate-based Location
Configuration Information",
draft-ietf-geopriv-dhcp-lci-option-03 (work in progress),
December 2003.
[8] National Emergency Number Assocation, "NENA Recommended Formats [14] United States Postal Service, "Postal Addressing Standards",
and Protocols For ALI Data Exchange, ALI Response and GIS November 2000.
Mapping", NENA NENA-02-010, January 2002.
[9] Schulzrinne, H., "RPID -- Rich Presence Information Data [15] National Emergency Number Assocation, "NENA Recommended Formats
Format", draft-ietf-simple-rpid-00 (work in progress), July and Protocols For ALI Data Exchange, ALI Response and GIS
2003. Mapping", NENA NENA-02-010, January 2002.
[16] Schulzrinne, H., Gurbani, V., Kyzivat, P. and J. Rosenberg,
"RPID: Rich Presence: Extensions to the Presence Information
Data Format (PIDF)", draft-ietf-simple-rpid-02 (work in
progress), March 2004.
Author's Address Author's Address
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
US US
Phone: +1 212 939 7042 Phone: +1 212 939 7042
EMail: hgs+simple@cs.columbia.edu EMail: hgs+simple@cs.columbia.edu
URI: http://www.cs.columbia.edu URI: http://www.cs.columbia.edu
Appendix A. Acknowledgments Appendix A. Acknowledgments
Rohan Mahy and Stefan Berger provided helpful comments. Harald Alvestrand, Stefan Berger and Rohan Mahy provided helpful
comments.
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 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; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the IETF's procedures with respect to rights in IETF Documents can
standards-related documentation can be found in BCP-11. Copies of be found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
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 which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
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 Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
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.
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. 56 change blocks. 
155 lines changed or deleted 324 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/