draft-ietf-geopriv-civic-address-recommendations-01.txt   draft-ietf-geopriv-civic-address-recommendations-02.txt 
GEOPRIV K. Wolf GEOPRIV K. Wolf
Internet-Draft A. Mayrhofer Internet-Draft A. Mayrhofer
Intended status: BCP nic.at Intended status: BCP nic.at
Expires: July 13, 2009 Jan 09, 2009 Expires: August 22, 2009 Feb 18, 2009
Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA
Registry Definition Registry Definition
draft-ietf-geopriv-civic-address-recommendations-01 draft-ietf-geopriv-civic-address-recommendations-02
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 33 skipping to change at page 1, line 33
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 July 13, 2009. This Internet-Draft will expire on August 22, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 25 skipping to change at page 3, line 25
4.2. Guidelines for Individual Elements . . . . . . . . . . . . 8 4.2. Guidelines for Individual Elements . . . . . . . . . . . . 8
4.2.1. Country . . . . . . . . . . . . . . . . . . . . . . . 8 4.2.1. Country . . . . . . . . . . . . . . . . . . . . . . . 8
4.2.2. Country Subdivisions A1-A6 . . . . . . . . . . . . . . 9 4.2.2. Country Subdivisions A1-A6 . . . . . . . . . . . . . . 9
4.2.3. Road and Street Names . . . . . . . . . . . . . . . . 9 4.2.3. Road and Street Names . . . . . . . . . . . . . . . . 9
4.2.4. House Numbers . . . . . . . . . . . . . . . . . . . . 10 4.2.4. House Numbers . . . . . . . . . . . . . . . . . . . . 10
4.2.5. Local Names . . . . . . . . . . . . . . . . . . . . . 11 4.2.5. Local Names . . . . . . . . . . . . . . . . . . . . . 11
4.2.6. Floors . . . . . . . . . . . . . . . . . . . . . . . . 11 4.2.6. Floors . . . . . . . . . . . . . . . . . . . . . . . . 11
4.2.7. Address Codes . . . . . . . . . . . . . . . . . . . . 12 4.2.7. Address Codes . . . . . . . . . . . . . . . . . . . . 12
4.2.8. Other Elements . . . . . . . . . . . . . . . . . . . . 13 4.2.8. Other Elements . . . . . . . . . . . . . . . . . . . . 13
5. Security & Privacy Considerations . . . . . . . . . . . . . . 13 5. Security Considerations . . . . . . . . . . . . . . . . . . . 13
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
6.1. PIDF-LO Civic Address Consideration Registry . . . . . . . 14 6.1. PIDF-LO Civic Address Consideration Registry . . . . . . . 14
6.1.1. Structure . . . . . . . . . . . . . . . . . . . . . . 14 6.1.1. Structure . . . . . . . . . . . . . . . . . . . . . . 14
6.1.2. Registration Template . . . . . . . . . . . . . . . . 15 6.1.2. Registration Template . . . . . . . . . . . . . . . . 15
6.1.3. Registry Location . . . . . . . . . . . . . . . . . . 15 6.1.3. Registry Location . . . . . . . . . . . . . . . . . . 15
6.1.4. Registration Procedure . . . . . . . . . . . . . . . . 16 6.1.4. Registration Procedure . . . . . . . . . . . . . . . . 16
6.2. Registration Request for Austria . . . . . . . . . . . . . 16 6.2. Registration Request for Austria . . . . . . . . . . . . . 16
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 16
skipping to change at page 13, line 47 skipping to change at page 13, line 47
the definition in the PIDF-LO base documents. the definition in the PIDF-LO base documents.
It is RECOMMENDED that the elements SEAT, UNIT and ROOM remain to be It is RECOMMENDED that the elements SEAT, UNIT and ROOM remain to be
used for identifying a location inside a building. They MAY be used used for identifying a location inside a building. They MAY be used
by the owner of the respective building if a considerations document by the owner of the respective building if a considerations document
does not restrict their use. For example, an airport could decide to does not restrict their use. For example, an airport could decide to
place the gate number in the UNIT element, and a location recipient place the gate number in the UNIT element, and a location recipient
could identify that PIDF-LO by the value of the PLC Element. The could identify that PIDF-LO by the value of the PLC Element. The
name of the airport could be placed in NAM. name of the airport could be placed in NAM.
5. Security & Privacy Considerations 5. Security Considerations
RFC 4119 contains general security considerations for handling PIDF- RFC 4119 contains general security considerations for handling PIDF-
LOs. In addition to that, it has to be considered that data from LOs. In addition to that, it has to be considered that data from
certain data sources (on which the described mapping process is certain data sources (on which the described mapping process is
based) are possibly not public, so restrictions as imposed on the based) are possibly not public, so restrictions as imposed on the
original data set MUST also be imposed on the resulting PIDF-LO original data set MUST also be imposed on the resulting PIDF-LO
document. The considerations document SHOULD note such restrictions document. The considerations document SHOULD note such restrictions
in its Security Considerations section. in its Security Considerations section.
6. IANA Considerations 6. IANA Considerations
skipping to change at page 16, line 25 skipping to change at page 16, line 25
6.2. Registration Request for Austria 6.2. Registration Request for Austria
This document requests registration of the Civic Address This document requests registration of the Civic Address
Considerations for addresses form the official Austrian Building an Considerations for addresses form the official Austrian Building an
Habitation registry, according to the registration procedure Habitation registry, according to the registration procedure
described above. The required information is contained in Appendix A described above. The required information is contained in Appendix A
7. Acknowledgements 7. Acknowledgements
The authors wish to thank Gregor Jaenin for contributing insights The authors would like to thank Martin Thomson and Richard Barnes for
reviewing the document, and Gregor Jaenin for contributing insights
into the Austrian civic address data format. into the Austrian civic address data format.
Appendix A. Civic Address Considerations Registration for the Austrian Appendix A. Civic Address Considerations Registration for the Austrian
building and habitation registry building and habitation registry
The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and
habitation registry law) is the legal basis for the obligation to habitation registry law) is the legal basis for the obligation to
provide a registry of civic addresses, buildings and their usable provide a registry of civic addresses, buildings and their usable
units (subdivisions of buildings). The registry is operated by units (subdivisions of buildings). The registry is operated by
"Statistik Austria GmbH", a fully governmental owned company. "Statistik Austria GmbH", a fully governmental owned company.
skipping to change at page 20, line 45 skipping to change at page 20, line 45
According to Statistik Austria [refs.adrwarten], 81.5% of Austrian According to Statistik Austria [refs.adrwarten], 81.5% of Austrian
addresses are of the simple type Musterstrasse 1 (Musterstrasse is an addresses are of the simple type Musterstrasse 1 (Musterstrasse is an
example street name). 5% of all addresses have an additional example street name). 5% of all addresses have an additional
character, like Musterstrasse 1b. 1% of Austrian addresses look like character, like Musterstrasse 1b. 1% of Austrian addresses look like
Musterstrasse 21A - 23A. For 8% of addresses, an additional separator Musterstrasse 21A - 23A. For 8% of addresses, an additional separator
is necessary, like Musterstrasse 10 Haus 1 Stiege 2 or Musterstrasse is necessary, like Musterstrasse 10 Haus 1 Stiege 2 or Musterstrasse
20 Gruppe A Reihe 1 Parzelle 13 or Musterstrasse 30 Weg 1 Parzelle 20 Gruppe A Reihe 1 Parzelle 13 or Musterstrasse 30 Weg 1 Parzelle
10. Very seldom, there are so called special addresses (0.03%), for 10. Very seldom, there are so called special addresses (0.03%), for
example Musterstrasse gegenueber 3a, meaning this address is actually example Musterstrasse gegenueber 3a, meaning this address is actually
vis-a-vis of house number 3A. Rather surprisingly, 4.47% of Austrian opposite of house number 3A. Rather surprisingly, 4.47% of Austrian
addresses contain the identifier of the estate since no house number addresses contain the identifier of the estate since no house number
is assigned at all, for example: Musterstrasse GNR 1234, or is assigned at all, for example: Musterstrasse GNR 1234, or
Musterstrasse GNR .12/4 Kirche (this type of addresses is common for Musterstrasse GNR .12/4 Kirche (this type of addresses is common for
churches) or a real example in Stockerau: Kolomaniwoerth GNR 1583. churches) or a real example in Stockerau: Kolomaniwoerth GNR 1583.
This identifier is stored by Statistik Austria as Hausnummerntext. This identifier is stored by Statistik Austria as Hausnummerntext.
Otherwise one could misinterpret this number as a house number, what Otherwise one could misinterpret this number as a house number, what
would be definitely wrong. would be definitely wrong.
A.2. Sample Addresses A.2. Sample Addresses
skipping to change at page 29, line 5 skipping to change at page 29, line 5
Strasse: Lazarettgasse Strasse: Lazarettgasse
Hausnummer - 1. Teil - Nummer: 13 Hausnummer - 1. Teil - Nummer: 13
Hausnummer - 1. Teil - Buchstabe: A Hausnummer - 1. Teil - Buchstabe: A
Hausnummer - Verbindungszeichen Teil 1-Bis: - Hausnummer - Verbindungszeichen Teil 1-Bis: -
Hausnummer - Bis-Nummer: 13 Hausnummer - Bis-Nummer: 13
Hausnummer - Bis-Buchstabe: C Hausnummer - Bis-Buchstabe: C
Postleitzahl: 1090 Postleitzahl: 1090
PIDF-LO: PIDF-LO:
<?xml version="1.0" lang="de" encoding="UTF-8"?> <?xml version="1.0" encoding="UTF-8" ?>
<presence xmlns="urn:ietf:params:xml:ns:pidf" <presence xmlns="urn:ietf:params:xml:ns:pidf"
xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10" xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr" xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
entity="pres:123@examplehost"> entity="pres:123@examplehost">
<tuple id="123456"> <tuple id="abcd123456">
<status> <status>
<gp:geopriv> <gp:geopriv>
<gp:location-info> <gp:location-info>
<cl:civicAddress> <cl:civicAddress>
<cl:country>AT</country> <cl:country>AT</cl:country>
<cl:A1>Wien</A1> <cl:A1>Wien</cl:A1>
<cl:A2>Wien</A2> <cl:A2>Wien</cl:A2>
<cl:A3>Wien</A3> <cl:A3>Wien</cl:A3>
<cl:A4>9</A4> <cl:A4>9</cl:A4>
<cl:RD>Lazarettgasse</RD> <cl:RD>Lazarettgasse</cl:RD>
<cl:HNO>;13;A;-;13;C;;;;;;;;;;;;</HNO> <cl:HNO>;13;A;-;13;C;;;;;;;;;;;;</cl:HNO>
<cl:PC>1090<PC> <cl:PC>1090</cl:PC>
</cl:civicAddress> </cl:civicAddress>
</gp:location-info> </gp:location-info>
<gp:usage-rules> <gp:usage-rules>
<gp:retransmission-allowed>yes</gp:retransmission-allowed> <gp:retransmission-allowed>yes</gp:retransmission-allowed>
<gp:retention-expiry>2009-11-10T12:00:00Z</gp:retention-expiry> <gp:retention-expiry>2009-11-10T12:00:00Z</gp:retention-expiry>
</gp:usage-rules> </gp:usage-rules>
</gp:geopriv> </gp:geopriv>
</status> </status>
<timestamp>2009-02-09T12:00:00Z</timestamp> <timestamp>2009-02-09T12:00:00Z</timestamp>
</tuple> </tuple>
 End of changes. 10 change blocks. 
17 lines changed or deleted 18 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/