draft-ietf-geopriv-revised-civic-lo-00.txt   draft-ietf-geopriv-revised-civic-lo-01.txt 
GEOPRIV WG M. Thomson GEOPRIV WG M. Thomson
Internet-Draft J. Winterbottom Internet-Draft J. Winterbottom
Expires: June 18, 2006 Andrew Expires: July 7, 2006 Andrew
December 15, 2005 January 3, 2006
Revised Civic Location Format for PIDF-LO Revised Civic Location Format for PIDF-LO
draft-ietf-geopriv-revised-civic-lo-00.txt draft-ietf-geopriv-revised-civic-lo-01.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 June 18, 2006. This Internet-Draft will expire on July 7, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2005). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines an XML format for the representation of civic This document defines an XML format for the representation of civic
location. This format is designed for use with PIDF Location Object location. This format is designed for use with PIDF Location Object
(PIDF-LO) documents. The format is based on the civic address (PIDF-LO) documents. The format is based on the civic address
definition in PIDF-LO, but adds several new elements based on the definition in PIDF-LO, but adds several new elements based on the
civic types defined for DHCP, and adds a hierarchy to address complex civic types defined for DHCP, and adds a hierarchy to address complex
road identity schemes. The format also includes support for the xml: road identity schemes. The format also includes support for the
lang language tag and restricts the types of elements where xml:lang language tag and restricts the types of elements where
appropriate. appropriate.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Changes from PIDF-LO . . . . . . . . . . . . . . . . . . . . . 5 3. Changes from PIDF-LO . . . . . . . . . . . . . . . . . . . . . 5
3.1. Additional Civic Address Types . . . . . . . . . . . . . . 5 3.1. Additional Civic Address Types . . . . . . . . . . . . . . 5
3.2. New Thoroughfare Elements . . . . . . . . . . . . . . . . 7 3.2. New Thoroughfare Elements . . . . . . . . . . . . . . . . 7
3.2.1. Street Numbering . . . . . . . . . . . . . . . . . . . 8 3.2.1. Street Numbering . . . . . . . . . . . . . . . . . . . 8
skipping to change at page 2, line 24 skipping to change at page 2, line 24
3.3. Country Element . . . . . . . . . . . . . . . . . . . . . 9 3.3. Country Element . . . . . . . . . . . . . . . . . . . . . 9
3.4. Languages and Scripts . . . . . . . . . . . . . . . . . . 9 3.4. Languages and Scripts . . . . . . . . . . . . . . . . . . 9
3.5. Whitespace . . . . . . . . . . . . . . . . . . . . . . . . 9 3.5. Whitespace . . . . . . . . . . . . . . . . . . . . . . . . 9
4. Civic Address Schema . . . . . . . . . . . . . . . . . . . . . 10 4. Civic Address Schema . . . . . . . . . . . . . . . . . . . . . 10
5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 5. Example . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
6. Security Considerations . . . . . . . . . . . . . . . . . . . 13 6. Security Considerations . . . . . . . . . . . . . . . . . . . 13
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
7.1. URN sub-namespace registration for 7.1. URN sub-namespace registration for
'urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr' . . . . 14 'urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr' . . . . 14
7.2. XML Schema Registration . . . . . . . . . . . . . . . . . 14 7.2. XML Schema Registration . . . . . . . . . . . . . . . . . 14
7.3. CAtype registration . . . . . . . . . . . . . . . . . . . 15 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15
7.3.1. Primary Thoroughfare CAtype . . . . . . . . . . . . . 15 8.1. Normative References . . . . . . . . . . . . . . . . . . . 15
7.3.2. Thoroughfare Section CAtype . . . . . . . . . . . . . 15 8.2. Informative References . . . . . . . . . . . . . . . . . . 15
7.3.3. Thoroughfare Branch CAtype . . . . . . . . . . . . . . 15 Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 16
7.3.4. Thoroughfare Sub-Branch CAtype . . . . . . . . . . . . 16 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 17
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Intellectual Property and Copyright Statements . . . . . . . . . . 18
8.1. Normative References . . . . . . . . . . . . . . . . . . . 17
8.2. Informative References . . . . . . . . . . . . . . . . . . 17
Appendix A. Acknowledgements . . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 19
Intellectual Property and Copyright Statements . . . . . . . . . . 20
1. Introduction 1. Introduction
Since the publication of the original PIDF-LO civic specification, in Since the publication of the original PIDF-LO civic specification, in
[I-D.ietf-geopriv-pidf-lo], it has been found that the specification [I-D.ietf-geopriv-pidf-lo], it has been found that the specification
is lacking a number of additional parameters that can be used to more is lacking a number of additional parameters that can be used to more
precisely specify a civic location. These additional parameters have precisely specify a civic location. These additional parameters have
been largely captured in [I-D.ietf-geopriv-dhcp-civil]. been largely captured in [I-D.ietf-geopriv-dhcp-civil].
This document revises the GEOPRIV civic form to include the This document revises the GEOPRIV civic form to include the
skipping to change at page 4, line 13 skipping to change at page 4, line 13
in specifying a civic location. in specifying a civic location.
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 [RFC2119]. document are to be interpreted as described in [RFC2119].
The term "thoroughfare" is used in this document to describe a road The term "thoroughfare" is used in this document to describe a road
or part of a road or other access route along which a final point is or part of a road or other access route along which a final point is
identified. This is consistent with the definition used in [S42]. identified. This is consistent with the definition used in [UPU-
S42].
3. Changes from PIDF-LO 3. Changes from PIDF-LO
3.1. Additional Civic Address Types 3.1. Additional Civic Address Types
[I-D.ietf-geopriv-dhcp-civil] provides a full set of parameters that [I-D.ietf-geopriv-dhcp-civil] provides a full set of parameters that
may used to describe a civic location. Specifically [I-D.ietf- may used to describe a civic location. Specifically [I-D.ietf-
geopriv-dhcp-civil] lists several civic address types (CAtypes) that geopriv-dhcp-civil] lists several civic address types (CAtypes) that
require support in the formal PIDF-LO definition that are not in require support in the formal PIDF-LO definition that are not in
[I-D.ietf-geopriv-pidf-lo]. Additional CAtypes are registered in [I-D.ietf-geopriv-pidf-lo].
Section 7.3.
These changes include and new elements that are required to support These changes include and new elements that are required to support
more complex structures for naming street addresses, this is more complex structures for naming street addresses, this is
described in more detail in Section 3.2. described in more detail in Section 3.2.
+--------------+--------+-----------------------------+-------------+ +--------------+--------+-----------------------------+-------------+
| New Civic | CAtype | Description | Example | | New Civic | CAtype | Description | Example |
| Field | | | | | Field | | | |
+--------------+--------+-----------------------------+-------------+ +--------------+--------+-----------------------------+-------------+
| BLD | 24 | Building (structure) | Hope | | BLD | 24 | Building (structure) | Hope |
| | | | Theatre | | | | | Theatre |
| | | | | | | | | |
| UNIT | 26 | Unit (apartment, suite) | 12a | | UNIT | 26 | Unit (apartment, suite) | 12a |
| | | | | | | | | |
| ROOM | 28 | Room | 450F | | ROOM | 28 | Room | 450F |
| | | | | | | | | |
| SEAT | 33 | Seat (desk, cubicle, | WS 181 |
| | | workstation) | |
| | | | |
| PLC | 29 | Place-type | office | | PLC | 29 | Place-type | office |
| | | | | | | | | |
| POBOX | 31 | Post office box (P.O. box) | U40 | | POBOX | 31 | Post office box (P.O. box) | U40 |
| | | | | | | | | |
| ADDCODE | 32 | Additional Code | 13203000003 | | ADDCODE | 32 | Additional Code | 13203000003 |
| | | | | | | | | |
| RD | TBA | Primary road or street | Broadway | | SEAT | 33 | Seat (desk, cubicle, | WS 181 |
| | | workstation) | |
| | | | | | | | | |
| RDSEC | TBA | Road section | 14 | | RD | 34 | Primary road or street | Broadway |
| | | | | | | | | |
| RDBR | TBA | Road branch | Lane 7 | | RDSEC | 35 | Road section | 14 |
| | | | | | | | | |
| RDSUBBR | TBA | Road sub-branch | Alley 8 | | RDBR | 36 | Road branch | Lane 7 |
| | | | |
| RDSUBBR | 37 | Road sub-branch | Alley 8 |
| | | | |
| PRM | 38 | Road pre-modifier | Old |
| | | | |
| POM | 39 | Road post-modifier | Extended |
+--------------+--------+-----------------------------+-------------+ +--------------+--------+-----------------------------+-------------+
Table 1: New Civic PIDF-LO Types Table 1: New Civic PIDF-LO Types
Building: The "building" (BLD) conveys the name of a single building Building: The "building" (BLD) conveys the name of a single building
if the street address includes more than one building or the if the street address includes more than one building or the
building name is helpful in identifying the location. (For building name is helpful in identifying the location. (For
example, on university campuses, the house number is often not example, on university campuses, the house number is often not
displayed on buildings, while the building name is prominently displayed on buildings, while the building name is prominently
shown.) shown.)
Unit: The "unit" (UNIT) contains the name or number of a part of a Unit: The "unit" (UNIT) contains the name or number of a part of a
structure where there are separate administrative units, owners or structure where there are separate administrative units, owners or
tenants, such as separate companies or families who occupy that tenants, such as separate companies or families who occupy that
structure. Common examples include suite or apartment structure. Common examples include suite or apartment
designations. designations.
Room: A "room" (ROOM) is the smallest identifiable subdivision of a Room: A "room" (ROOM) is the smallest identifiable subdivision of a
structure. structure.
Seat: The "seat" element (SEAT) describes a single place where a
person might sit. Common examples include a seat in a theatre and
a cubicle in a cube farm.
Place type: The "type of place" element (PLC) describes the type of Place type: The "type of place" element (PLC) describes the type of
place described by the civic coordinates. For example, it place described by the civic coordinates. For example, it
describes whether it is a home, office, street or other public describes whether it is a home, office, street or other public
space. The values are drawn from the items in the location types space. The values are drawn from the items in the location types
registry [I-D.ietf-geopriv-location-types-registry]. This registry [I-D.ietf-geopriv-location-types-registry]. This
information makes it easy, for example, for the DHCP client to information makes it easy, for example, for the DHCP client to
then populate the presence information. then populate the presence information.
Post office box: The "post office box" element (POBOX) describes a Post office box: The "post office box" element (POBOX) describes a
container, such as a pigeon hole, at a central mailing location, container, such as a pigeon hole, at a central mailing location,
where mail is held. where mail is held.
Additional code: The "additional code" item (ADDCODE) provides an Additional code: The "additional code" item (ADDCODE) provides an
additional, country-specific code identifying the location. For additional, country-specific code identifying the location. For
example, for Japan, it contains the Japan Industry Standard (JIS) example, for Japan, it contains the Japan Industry Standard (JIS)
address code. The JIS address code provides a unique address address code. The JIS address code provides a unique address
inside of Japan, down to the level of indicating the floor of the inside of Japan, down to the level of indicating the floor of the
building. building.
Seat: The "seat" element (SEAT) describes a single place where a
person might sit. Common examples include a seat in a theatre and
a cubicle in a cube farm.
Primary Road Name: The "primary road name" item (RD) is the name Primary Road Name: The "primary road name" item (RD) is the name
given to the root road or street associated with the address. In given to the root road or street associated with the address. In
many cases this will the name of the road or street on which an many cases this will the name of the road or street on which an
office or house exists, in some cases it will be the name of road office or house exists, in some cases it will be the name of road
or street from which more granular information stems. In most or street from which more granular information stems. In most
countries, this field should be used in preference to the "A6" countries, this field should be used in preference to the "A6"
element, which was previously used for street information. element, which was previously used for street information.
Road Section: The "road section" item (RDSEC) is an identifier that Road Section: The "road section" item (RDSEC) is an identifier that
represents a specific section or stretch of a primary road. This represents a specific section or stretch of a primary road. This
skipping to change at page 7, line 29 skipping to change at page 7, line 29
suburb. suburb.
Sub-Branch Road Name: The "sub-branch road name" item (RDSUBBR) Sub-Branch Road Name: The "sub-branch road name" item (RDSUBBR)
represents the name or identifier of a road/street that intersects represents the name or identifier of a road/street that intersects
or is associated with a branch road (RDBR). The road sub-branch or is associated with a branch road (RDBR). The road sub-branch
is a new thoroughfare element and is envisaged being used where is a new thoroughfare element and is envisaged being used where
sub-branch roads reuse names and there is no way, other than the sub-branch roads reuse names and there is no way, other than the
road section (RDSEC) identifier, to discern a difference between road section (RDSEC) identifier, to discern a difference between
them, such as a change in municipality or suburb. them, such as a change in municipality or suburb.
Road Pre-Modifier: The "road pre-modifier" item (PRM) is an optional
element of the complete street name. It is a word or phrase that
precedes all other elements of the street name and modifies it,
but is separated from the street name by a street name pre-
directional. An example is "Old" in "Old North First Street".
Road Post-Modifier: The "road post-modifier" item (POM) is an
optional element of the complete street name. It is a word or
phrase that follows all other elements of the street name and
modifies it, but is separated from the street name by a street
name post-directional and/or street suffix. An example is
"Extended" in "East End Avenue Extended".
3.2. New Thoroughfare Elements 3.2. New Thoroughfare Elements
In some countries a thoroughfare can be broken up into sections, and In some countries a thoroughfare can be broken up into sections, and
it is not uncommon for street numbers to be repeated between it is not uncommon for street numbers to be repeated between
sections. A road section identifier is required to ensure that an sections. A road section identifier is required to ensure that an
address is unique. For example, "West Alice Parade" has 5 sections, address is unique. For example, "West Alice Parade" has 5 sections,
each numbered from 1; unless the section is specified "7 West Alice each numbered from 1; unless the section is specified "7 West Alice
Parade" could exist in 5 different places. The "RDSEC" element is Parade" could exist in 5 different places. The "RDSEC" element is
used to specify the section. used to specify the section.
skipping to change at page 8, line 32 skipping to change at page 8, line 45
3.2.1. Street Numbering 3.2.1. Street Numbering
The introduction of new thoroughfare elements affects the The introduction of new thoroughfare elements affects the
interpretation of several of more specific civic address data. In interpretation of several of more specific civic address data. In
particular, street numbering (the "HNO" element) applies to the most particular, street numbering (the "HNO" element) applies to the most
specific road element specified. That is, the first specified specific road element specified. That is, the first specified
element from: "RDSUBBR", "RDBR", "RDSEC", or "RD". element from: "RDSUBBR", "RDBR", "RDSEC", or "RD".
3.2.2. Directionals and other Qualifiers 3.2.2. Directionals and other Qualifiers
The "PRD", "POD" and "STS" elements always apply to the value of the The "PRM", "POM", "PRD", "POD" and "STS" elements always apply to the
"RD" element only. If road branches or sub-branches require street value of the "RD" element only. If road branches or sub-branches
suffixes or qualifiers, they MUST be included in the "RDBR" or require street suffixes or qualifiers, they MUST be included in the
"RDSUBBR" element text. "RDBR" or "RDSUBBR" element text.
In PIDF-LO [I-D.ietf-geopriv-pidf-lo], examples and descriptions for
the "PRD" and "POD" elements focussed on these qualifiers being
directionals, for example North, South etc. This derives from their
use in North America, where the name is derived from (pre-directional
and post-directional respectively). However in quite a number of
cities and countries around the world a street prefix may be
something other than a directional, for example "Little" or "Lower".
The Universal Postal Union (UPU) standard [S42] refers to these items
as "thoroughfare qualifiers" and allows any value for these fields.
This specification extends the allowed values for the "PRD" and "POD"
elements to include any value.
To avoid confusion it is RECOMMENDED that where the "PRD" and "POD"
elements are used to represent something other than a directional
that the values be explicit such as "Little" and not an abbreviation
such as "Lt".
3.3. Country Element 3.3. Country Element
The "country" element differs from that defined in [I-D.ietf-geopriv- The "country" element differs from that defined in [I-D.ietf-geopriv-
pidf-lo] in that it now restricts the value space of the element to pidf-lo] in that it now restricts the value space of the element to
two upper case characters, which more closely matches the definition two upper case characters, which more closely matches the definition
in [ISO.3166.1988]. in [ISO.3166.1988].
3.4. Languages and Scripts 3.4. Languages and Scripts
skipping to change at page 10, line 42 skipping to change at page 10, line 42
<xs:element name="civicAddress" type="ca:civicAddress"/> <xs:element name="civicAddress" type="ca:civicAddress"/>
<xs:complexType name="civicAddress"> <xs:complexType name="civicAddress">
<xs:sequence> <xs:sequence>
<xs:element name="country" type="ca:iso3166" minOccurs="0"/> <xs:element name="country" type="ca:iso3166" minOccurs="0"/>
<xs:element name="A1" type="ca:caType" minOccurs="0"/> <xs:element name="A1" type="ca:caType" minOccurs="0"/>
<xs:element name="A2" type="ca:caType" minOccurs="0"/> <xs:element name="A2" type="ca:caType" minOccurs="0"/>
<xs:element name="A3" type="ca:caType" minOccurs="0"/> <xs:element name="A3" type="ca:caType" minOccurs="0"/>
<xs:element name="A4" type="ca:caType" minOccurs="0"/> <xs:element name="A4" type="ca:caType" minOccurs="0"/>
<xs:element name="A5" type="ca:caType" minOccurs="0"/> <xs:element name="A5" type="ca:caType" minOccurs="0"/>
<xs:element name="A6" type="ca:caType" minOccurs="0"/> <xs:element name="A6" type="ca:caType" minOccurs="0"/>
<xs:element name="PRM" type="ca:caType" minOccurs="0"/>
<xs:element name="PRD" type="ca:caType" minOccurs="0"/> <xs:element name="PRD" type="ca:caType" minOccurs="0"/>
<xs:element name="RD" type="ca:caType" minOccurs="0"/> <xs:element name="RD" type="ca:caType" minOccurs="0"/>
<xs:element name="STS" type="ca:caType" minOccurs="0"/> <xs:element name="STS" type="ca:caType" minOccurs="0"/>
<xs:element name="POD" type="ca:caType" minOccurs="0"/> <xs:element name="POD" type="ca:caType" minOccurs="0"/>
<xs:element name="POM" type="ca:caType" minOccurs="0"/>
<xs:element name="RDSEC" type="ca:caType" minOccurs="0"/> <xs:element name="RDSEC" type="ca:caType" minOccurs="0"/>
<xs:element name="RDBR" type="ca:caType" minOccurs="0"/> <xs:element name="RDBR" type="ca:caType" minOccurs="0"/>
<xs:element name="RDSUBBR" type="ca:caType" minOccurs="0"/> <xs:element name="RDSUBBR" type="ca:caType" minOccurs="0"/>
<xs:element name="HNO" type="ca:caType" minOccurs="0"/> <xs:element name="HNO" type="ca:caType" minOccurs="0"/>
<xs:element name="HNS" type="ca:caType" minOccurs="0"/> <xs:element name="HNS" type="ca:caType" minOccurs="0"/>
<xs:element name="LMK" type="ca:caType" minOccurs="0"/> <xs:element name="LMK" type="ca:caType" minOccurs="0"/>
<xs:element name="LOC" type="ca:caType" minOccurs="0"/> <xs:element name="LOC" type="ca:caType" minOccurs="0"/>
<xs:element name="FLR" type="ca:caType" minOccurs="0"/> <xs:element name="FLR" type="ca:caType" minOccurs="0"/>
<xs:element name="NAM" type="ca:caType" minOccurs="0"/> <xs:element name="NAM" type="ca:caType" minOccurs="0"/>
<xs:element name="PC" type="ca:caType" minOccurs="0"/> <xs:element name="PC" type="ca:caType" minOccurs="0"/>
skipping to change at page 12, line 15 skipping to change at page 12, line 15
5. Example 5. Example
<?xml version="1.0"?> <?xml version="1.0"?>
<civicAddress xml:lang="en-AU" <civicAddress xml:lang="en-AU"
xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"> xmlns="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr">
<country>AU</country> <country>AU</country>
<A1> New South Wales </A1> <A1> New South Wales </A1>
<A3> Wollongong <A3> Wollongong
</A3><A4>North Wollongong </A3><A4>North Wollongong
</A4> </A4>
<PRD>Corner</PRD><RD>Flinders</RD><STS>Street</STS> <RD>Flinders</RD><STS>Street</STS>
<RDBR>Campbell Street</RDBR> <RDBR>Campbell Street</RDBR>
<LMK> <LMK>
Gilligan's Island Gilligan's Island
</LMK> </LMK> <LOC>Corner</LOC>
<NAM> Video Rental Store </NAM> <NAM> Video Rental Store </NAM>
<PC>2500</PC> <PC>2500</PC>
<ROOM> Westerns and Classics </ROOM> <ROOM> Westerns and Classics </ROOM>
<PLC>store</PLC> <PLC>store</PLC>
<POBOX>Private Box 15</POBOX> <POBOX>Private Box 15</POBOX>
</civicAddress> </civicAddress>
6. Security Considerations 6. Security Considerations
The XML representation described in this document is designed for The XML representation described in this document is designed for
skipping to change at page 15, line 5 skipping to change at page 15, line 5
[RFC3688]. [RFC3688].
URI: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr URI: urn:ietf:params:xml:schema:pidf:geopriv10:civicAddr
Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org), Registrant Contact: IETF, GEOPRIV working group, (geopriv@ietf.org),
Martin Thomson (martin.thomson@andrew.com). Martin Thomson (martin.thomson@andrew.com).
The XML for this schema can be found as the entirety of Section 4 The XML for this schema can be found as the entirety of Section 4
of this document. of this document.
7.3. CAtype registration
This section registers CAtype codes in accordance with [I-D.ietf-
geopriv-dhcp-civil].
7.3.1. Primary Thoroughfare CAtype
This section registers the primary thoroughfare CAtype (RD).
CAtype: TBA
Brief description: The name of a primary thoroughfare, not including
any qualifiers.
Reference to published specification: Please refer to RFCXXXX [[NOTE
TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number for
this specification.]]
Country-specific considerations: None
7.3.2. Thoroughfare Section CAtype
This section registers the thoroughfare section CAtype (RDSEC).
CAtype: TBA
Brief description: An identifier identifying a specific section or
stretch of a primary thoroughfare.
Reference to published specification: Please refer to RFCXXXX [[NOTE
TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number for
this specification.]]
Country-specific considerations: None
7.3.3. Thoroughfare Branch CAtype
This section registers the thoroughfare branch CAtype (RDBR).
CAtype: TBA
Brief description: The name of a secondary thoroughfare or
thoroughfare branch.
Reference to published specification: Please refer to RFCXXXX [[NOTE
TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number for
this specification.]]
Country-specific considerations: None
7.3.4. Thoroughfare Sub-Branch CAtype
This section registers the thoroughfare sub-branch CAtype (RDSUBBR).
CAtype: TBA
Brief description: The name of a tertiary thoroughfare or
thoroughfare sub-branch.
Reference to published specification: Please refer to RFCXXXX [[NOTE
TO IANA/RFC-EDITOR: Please replace XXXX with the RFC number for
this specification.]]
Country-specific considerations: None
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[W3C.REC-xmlschema-2-20041028] [W3C.REC-xmlschema-2-20041028]
Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes Malhotra, A. and P. Biron, "XML Schema Part 2: Datatypes
Second Edition", W3C REC REC-xmlschema-2-20041028, Second Edition", W3C REC REC-xmlschema-2-20041028,
October 2004. October 2004.
[I-D.ietf-geopriv-dhcp-civil] [I-D.ietf-geopriv-dhcp-civil]
Schulzrinne, H., "Dynamic Host Configuration Protocol Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses (DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", Configuration Information",
draft-ietf-geopriv-dhcp-civil-07 (work in progress), draft-ietf-geopriv-dhcp-civil-08 (work in progress),
September 2005. December 2005.
[I-D.ietf-geopriv-location-types-registry] [I-D.ietf-geopriv-location-types-registry]
Schulzrinne, H. and H. Tschofenig, "Location Types Schulzrinne, H. and H. Tschofenig, "Location Types
Registry", draft-ietf-geopriv-location-types-registry-03 Registry", draft-ietf-geopriv-location-types-registry-03
(work in progress), August 2005. (work in progress), August 2005.
[ISO.3166.1988] [ISO.3166.1988]
International Organization for Standardization, "Codes for International Organization for Standardization, "Codes for
the representation of names of countries, 3rd edition", the representation of names of countries, 3rd edition",
ISO Standard 3166, August 1988. ISO Standard 3166, August 1988.
skipping to change at page 17, line 44 skipping to change at page 15, line 44
8.2. Informative References 8.2. Informative References
[RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688,
January 2004. January 2004.
[I-D.ietf-geopriv-pidf-lo] [I-D.ietf-geopriv-pidf-lo]
Peterson, J., "A Presence-based GEOPRIV Location Object Peterson, J., "A Presence-based GEOPRIV Location Object
Format", draft-ietf-geopriv-pidf-lo-03 (work in progress), Format", draft-ietf-geopriv-pidf-lo-03 (work in progress),
September 2004. September 2004.
[S42] Universal Postal Union (UPU), "International Postal [UPU-S42] Universal Postal Union (UPU), "International Postal
Address Components and Templates", UPS SB42-4, July 2004. Address Components and Templates", UPS SB42-4, July 2004.
Appendix A. Acknowledgements Appendix A. Acknowledgements
The authors would like to thank Henning Schulzrinne for his The authors would like to thank Henning Schulzrinne for his
assistance in defining the additional civic address types, assistance in defining the additional civic address types,
particularly his research into different addressing schemes that lead particularly his research into different addressing schemes that lead
to the introduction of the thoroughfare elements. In addition we to the introduction of the thoroughfare elements. In addition we
would like to thank Jon Peterson for his work in defining the would like to thank Jon Peterson for his work in defining the
PIDF-LO. PIDF-LO.
skipping to change at page 20, line 41 skipping to change at page 18, 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 (2005). This document is subject Copyright (C) The Internet Society (2006). 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. 25 change blocks. 
123 lines changed or deleted 56 lines changed or added

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