<pre>Internet Engineering Task Force (IETF)                           K. Wolf
Request for Comments: 5774                                  A. Mayrhofer
BCP: 154                                                          nic.at
Updates: <a href="./rfc4776">4776</a>                                                 March 2010
Category: Best Current Practice
ISSN: 2070-1721


               <span class="h1">Considerations for Civic Addresses in the</span>
      <span class="h1">Presence Information Data Format Location Object (PIDF-LO):</span>
                <span class="h1">Guidelines and IANA Registry Definition</span>

Abstract

   This document provides a guideline for creating civic address
   considerations documents for individual countries, as required by <a href="./rfc4776">RFC</a>
   <a href="./rfc4776">4776</a>.  Furthermore, this document also creates an IANA Registry
   referring to such address considerations documents and registers such
   address considerations for Austria.

Status of This Memo

   This memo documents an Internet Best Current Practice.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   BCPs is available in <a href="./rfc5741#section-2">Section&nbsp;2 of RFC 5741</a>.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   <a href="http://www.rfc-editor.org/info/rfc5774">http://www.rfc-editor.org/info/rfc5774</a>.

Copyright Notice

   Copyright (c) 2010 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 1]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


Table of Contents

   <a href="#section-1">1</a>. Introduction ....................................................<a href="#page-3">3</a>
   <a href="#section-2">2</a>. Terminology .....................................................<a href="#page-4">4</a>
   <a href="#section-3">3</a>. Requirements ....................................................<a href="#page-4">4</a>
   <a href="#section-4">4</a>. Specifying PIDF-LO Element Usage ................................<a href="#page-5">5</a>
      <a href="#section-4.1">4.1</a>. General Considerations and Workflow ........................<a href="#page-5">5</a>
      <a href="#section-4.2">4.2</a>. Guidelines for Individual Elements .........................<a href="#page-7">7</a>
           <a href="#section-4.2.1">4.2.1</a>. Country .............................................<a href="#page-7">7</a>
           <a href="#section-4.2.2">4.2.2</a>. Country Subdivisions A1-A6 ..........................<a href="#page-7">7</a>
           <a href="#section-4.2.3">4.2.3</a>. Road and Street Names ...............................<a href="#page-8">8</a>
           <a href="#section-4.2.4">4.2.4</a>. House Numbers .......................................<a href="#page-8">8</a>
           <a href="#section-4.2.5">4.2.5</a>. Local Names .........................................<a href="#page-9">9</a>
           <a href="#section-4.2.6">4.2.6</a>. Floors .............................................<a href="#page-10">10</a>
           <a href="#section-4.2.7">4.2.7</a>. Address Codes ......................................<a href="#page-10">10</a>
           <a href="#section-4.2.8">4.2.8</a>. Other Elements .....................................<a href="#page-11">11</a>
   <a href="#section-5">5</a>. Security Considerations ........................................<a href="#page-12">12</a>
   <a href="#section-6">6</a>. IANA Considerations ............................................<a href="#page-12">12</a>
      <a href="#section-6.1">6.1</a>. PIDF-LO Civic Address Considerations Registry .............<a href="#page-12">12</a>
           <a href="#section-6.1.1">6.1.1</a>. Structure ..........................................<a href="#page-12">12</a>
           <a href="#section-6.1.2">6.1.2</a>. Registration Template ..............................<a href="#page-13">13</a>
           <a href="#section-6.1.3">6.1.3</a>. Registry Location ..................................<a href="#page-14">14</a>
           <a href="#section-6.1.4">6.1.4</a>. Registration Procedure .............................<a href="#page-14">14</a>
      <a href="#section-6.2">6.2</a>. Registration Request for Austria ..........................<a href="#page-14">14</a>
      6.3. Registration of the Considerations in <a href="./rfc4776">RFC 4776</a> as
           Obsolete ..................................................<a href="#page-14">14</a>
   <a href="#section-7">7</a>. Acknowledgements ...............................................<a href="#page-17">17</a>
   <a href="#appendix-A">Appendix A</a>. Civic Address Considerations Registration for
           the Austrian Building and Habitation Registry .............<a href="#page-18">18</a>
      <a href="#appendix-A.1">A.1</a>. Civic Address Format in Austria ...........................<a href="#page-18">18</a>
      <a href="#appendix-A.2">A.2</a>. Sample Addresses ..........................................<a href="#page-22">22</a>
      <a href="#appendix-A.3">A.3</a>. Address Codes in Austria ..................................<a href="#page-23">23</a>
      <a href="#appendix-A.4">A.4</a>. Austrian Addresses in PIDF-LO .............................<a href="#page-23">23</a>
           <a href="#appendix-A.4.1">A.4.1</a>. Country ............................................<a href="#page-23">23</a>
           <a href="#appendix-A.4.2">A.4.2</a>. Country Subdivisions A1-A6 .........................<a href="#page-24">24</a>
           <a href="#appendix-A.4.3">A.4.3</a>. Road and Street Names ..............................<a href="#page-27">27</a>
           <a href="#appendix-A.4.4">A.4.4</a>. House Numbers ......................................<a href="#page-27">27</a>
           <a href="#appendix-A.4.5">A.4.5</a>. Local Names ........................................<a href="#page-28">28</a>
           <a href="#appendix-A.4.6">A.4.6</a>. Floors .............................................<a href="#page-28">28</a>
           <a href="#appendix-A.4.7">A.4.7</a>. Additional Code Element ............................<a href="#page-28">28</a>
           <a href="#appendix-A.4.8">A.4.8</a>. Other Elements .....................................<a href="#page-29">29</a>
           <a href="#appendix-A.4.9">A.4.9</a>. Elements Not to Be Used ............................<a href="#page-29">29</a>
      <a href="#appendix-A.5">A.5</a>. Example ...................................................<a href="#page-29">29</a>
      <a href="#appendix-A.6">A.6</a>. IANA Registration Record ..................................<a href="#page-30">30</a>
   Normative References ..............................................<a href="#page-31">31</a>
   Informative References ............................................<a href="#page-32">32</a>





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 2]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>.  Introduction</span>

   The Presence Information Data Format Location Object (PIDF-LO)
   [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>] is an object format for carrying geographical information
   on the Internet.  PIDF-LO can contain civic address information and
   supports a range of "civic address types" (CAtypes) to hold the
   individual attributes of such addresses (see <a href="./rfc4119#section-2.2.1">Section&nbsp;2.2.1 of
   [RFC4119]</a> and <a href="./rfc5139#section-3.1">Section&nbsp;3.1 of [RFC5139]</a>).

   In many use cases, PIDF-LOs are populated with data from long-
   established sources, like postal and governmental building registers,
   line information databases and yellow/white pages of infrastructure
   providers, or official residents registers.  The structure and format
   of data from such sources is almost always different from PIDF-LO's
   CAtypes definition -- additionally, the structure and format of those
   sources differ from country to country.

   To make use of such existing data sources, transposing that data into
   PIDF-LO format is required.  With no guidelines available on how to
   map source Fields into CAtype Elements, different creators of PIDF-LO
   documents might end up with different results, even when using the
   same data source, which reduces interoperability and increases the
   risk of misinterpretation by recipients.

   Therefore, civic address considerations are necessary to ensure
   uniform usage of PIDF-LO Elements for such data sources.  [<a href="./rfc4776" title="&quot;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information&quot;">RFC4776</a>]
   explicitly requests such documents to be provided, but defines
   neither their structure nor a way to publish them.  This memo
   provides documentation on how to create such civic address
   considerations, and IANA has created a registry to store references
   to such documents.  Furthermore, civic address considerations for
   Austria are provided in <a href="#appendix-A">Appendix A</a> and have been registered in the
   IANA registry.

   <a href="./rfc4776#section-3.4">Section&nbsp;3.4 of [RFC4776]</a> contains some example considerations
   regarding the use of administrative subdivision Elements for Canada,
   Germany, Japan, Korea, and the United States.  This document
   registers these examples with IANA as "obsolete" (see <a href="#section-6.3">Section 6.3</a>).

   <a href="./rfc4776#section-3.4">Section&nbsp;3.4 of [RFC4776]</a> also contains instructions on the creation
   of civic address considerations documents on page 8.  This document
   updates that section and replaces said instructions with Sections <a href="#section-4">4</a>
   and 5 of this memo.

   The guidelines in this document have been created with a focus on
   formal application of PIDF-LO (such as conveying location during an
   emergency call).  It is not intended to forbid other, more informal
   uses of PIDF-LO that may not follow any formal mapping



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 3]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   specifications.  An example use case of such informal usage may be
   the transmission of PIDF-LO documents during an instant-messaging
   session between humans.  Such use may, however, imply some drawbacks,
   like prohibiting automatic processing of civic addresses from such a
   PIDF-LO.

<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>.  Terminology</span>

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in <a href="./rfc2119">RFC 2119</a> [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC2119</a>].

   In addition, this document uses "Field" to refer to a field of a
   civic address data source, and "Element" to refer to a CAtype Element
   of a PIDF-LO.

<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>.  Requirements</span>

   The following requirements apply to defining civic-address mapping
   considerations:

   o  The considerations document MUST identify the data source to which
      the definitions apply.  A brief description of its structure
      SHOULD be provided as well.

   o  For any data source, just one active mapping definition should
      exist in order to reduce the risk of ambiguous interpretation.

   o  The document MUST include instructions for any Field that occurs
      in the data.  For any of the Fields, the document MUST describe
      whether the Field is required, optional, or must not be used in
      the mapping procedure.

   o  Instructions MUST be included for any CAtype Element that is
      registered by the time the document is created.  Those
      instructions MUST include information regarding whether an Element
      is required, optional, or must not be used in that mapping.  In
      case the set of CAtypes is revised by the IETF, the address
      considerations document SHOULD be updated.  Until an update is
      approved, the existing mapping procedure MUST be used.

   o  Address mapping procedures SHOULD be reversible so that location
      recipients can identify the corresponding record in the original
      data source (given they have access to that source).

   o  For any source data Field that is required or optional, at least
      one example mapping MUST be provided.




<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 4]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   o  In many cases, data sources used in the mapping process might be
      subject to access restrictions.  Such restrictions (as imposed on
      the original data) MUST also be imposed on the resulting PIDF-LO
      documents.  The considerations document SHOULD note such
      restrictions in its Security Considerations section.

   Although the mapping is defined in a national way and the actual
   meaning of several PIDF-LO Elements may not be clear to an outsider,
   at least the country Element tells in what context this PIDF-LO was
   created.  In case of emergency calls, a PIDF-LO would just be passed
   to a Public Safety Answering Point (PSAP) in the same country as the
   location generator anyway.  However, in a border region there might
   be exceptions and the PIDF-LO could be sent to a neighboring country.
   The PIDF-LO can still be passed on to a PSAP in the right country
   (based on the country Element), or the PSAP might be aware of the
   mapping scheme used in the neighboring country.

   A consistent mapping is also very important for checking if two PIDF-
   LO documents describe the same location.  When civic address Fields
   are put into different PIDF-LO Elements, it may be difficult to
   identify whether or not two PIDF-LOs describe identical addresses.

<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>.  Specifying PIDF-LO Element Usage</span>

   The purpose of the civic address considerations for an individual
   data source is to create interoperability by specifying a common list
   of PIDF-LO Elements to be used and by defining the mapping between
   these Elements and the Fields of the respective data source.

<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a>.  General Considerations and Workflow</span>

   The workflow for creating an address considerations document is as
   follows:

   1.  Describe the data source to which the address considerations
       document applies.

   2.  Identify all Fields from the data source and decide, for each of
       the Fields, whether or not it is to be used for the purpose of
       creating PIDF-LO documents.  The considerations document must
       list all Fields (or at least state which Fields are considered in
       the mapping and clearly state that the other Fields MUST NOT be
       used).

   3.  For each of the Fields that are required or optional, specify a
       clear mapping instruction according to the guidelines below.





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 5]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   4.  Provide a list of all CAtypes registered and describe their level
       of usage in this mapping (or combine it with the list of Fields
       above and clearly list which Elements are not used for the
       mapping procedure).  For Elements that are not described in
       detail, state whether they MUST NOT be used at all or whether
       they may be used without further restriction.

   5.  Provide examples of source data and mapping results.

   Civic address Elements are designed to be generic containers.  In
   some cases, Fields clearly correspond to such a container; however,
   in some other cases, identifying the correct container might require
   some approximation.  For example, in some countries the RD (road)
   Element might also be appropriate for other thoroughfares, like
   waterways or tunnels.

   Fields that are identified to have the same meaning as one of the
   CAtypes SHOULD be directly mapped to that CAtype Element.

   Where CAtype usage diverges from the original specification, the
   mapping definition of Fields that are mapped to that Element SHOULD
   include a discussion of the differences.

   Fields that do not fit into an existing CAtype:

      Even though the list of CAtypes could be extended, it is not
      feasible to add new Elements for every new Field in every data
      source in every country.  Therefore, unless new generic CAtypes
      are specified by the IETF, only existing Elements can be used,
      which leaves the following options:

      1.  Concatenate several civic address Fields into a single PIDF-LO
          Element (define delimiters if applicable and make sure the
          separate civic address parts can be retrieved again).

      2.  Use a PIDF-LO Element that is unused so far.

      Note: Obviously, the first option is required if the number of
      Fields that are used in the mapping procedure is greater than the
      number of existing CAtype Elements.

   Note that the xml:lang attribute should be present in PIDF-LO XML
   [<a href="#ref-W3C.REC-xml-20060816">W3C.REC-xml-20060816</a>] documents, according to <a href="./rfc5139">RFC 5139</a>.








<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 6]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a>.  Guidelines for Individual Elements</span>

   The following sections discuss individual PIDF-LO Elements and
   describe what to consider for each Element when defining civic
   address considerations.  It is RECOMMENDED to follow a similar
   structure for considerations documents.

<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>.  Country</span>

   The country Element must hold the alpha-2 codes from ISO 3166-1
   [<a href="#ref-ISO3166-1" title="&quot;Codes for the representation of names of countries and their subdivisions - Part 1: Country codes&quot;">ISO3166-1</a>] in uppercase characters, as clarified in <a href="./rfc5139#section-3.3">Section&nbsp;3.3 of
   RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>].

   This Element cannot be redefined on a national basis since it
   identifies the country itself.  This Element is used to identify
   which national mapping for civic addresses has been used in a
   specific PIDF-LO.

   Example for Austria: &lt;country&gt;AT&lt;/country&gt;

<span class="h4"><a class="selflink" id="section-4.2.2" href="#section-4.2.2">4.2.2</a>.  Country Subdivisions A1-A6</span>

   The Elements A1 to A6 are used to hold national subdivision
   identifiers, with A1 holding the top-level subdivision identifier.
   A1 may either contain the second part of ISO 3166-2 [<a href="#ref-ISO3166-2" title="&quot;Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code&quot;">ISO3166-2</a>] (see
   <a href="./rfc5139#section-3.4">Section&nbsp;3.4 of RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]) or other values as described in
   the particular address considerations document.  Elements "A2" to
   "A6" may contain additional levels of subdivisions (see <a href="./rfc4119#section-2.2.1">Section&nbsp;2.2.1
   of RFC 4119</a>).

   For A1, an address considerations document MUST state whether ISO
   3166-2 codes are to be used exclusively; alternatively, it should
   define a list of values to be used (for example, subdivision names).
   In either case, A1 MUST NOT be redefined for any other use than
   describing top-level subdivisions.

   For each of the A2 - A6 Elements that are required or optional, the
   document SHOULD define the set of allowed values, either by listing
   them or by referring to such a list.

   Example for Austria:

   A1 province (Bundesland)
   A2 political district (politischer Bezirk) name or identifier
   A3 commune (Gemeinde) name or identifier
   A4 village (Ortschaft) name or identifier
   A5 cadastral municipality (Katastralgemeinde) name or identifier




<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 7]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   A6 must not be used.  For more details, see the example in <a href="#appendix-A.4.2">Appendix</a>
   <a href="#appendix-A.4.2">A.4.2</a>.

<span class="h4"><a class="selflink" id="section-4.2.3" href="#section-4.2.3">4.2.3</a>.  Road and Street Names</span>

   PIDF-LO contains the following Elements related to road names: RD,
   RDSEC, RDBR, RDSUBADDR, PRM, POM (Sections <a href="#section-3.1">3.1</a> and <a href="#section-3.2">3.2</a> of <a href="./rfc5139">RFC 5139</a>
   [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]) and PRD, POD, STS (Sections <a href="#section-3.4">3.4</a> of [<a href="./rfc4776" title="&quot;Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information&quot;">RFC4776</a>]).  Note: the
   use of the A6 Element for street names is not valid any more (<a href="./rfc5139#section-3.2">Section</a>
   <a href="./rfc5139#section-3.2">3.2 of RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>]).

   Besides the basic specification of which of those Elements are
   required, optional, or not to be used, an address considerations
   document may also describe more complicated dependencies (for
   example, "RD is optional, but required if any other road name Element
   is used").

   For any required or optional Element, the relation of those Elements
   to Fields of the data source used MUST be described, as should
   special considerations (like concatenation of Fields into an
   Element), if they apply.  The usage of the Element STS (street
   suffix) SHOULD be consistent.  In case no suffixes are known in a
   data source, or it is common to write the street name and the suffix
   together, the STS Element SHOULD be left out completely.  If suffixes
   may be abbreviated, the common abbreviations SHOULD be defined.

   Example for Austria:

   RD: street name

   All other road Elements must not be used.  Street suffixes are
   already included in the "street name" Field and must not be
   abbreviated.

<span class="h4"><a class="selflink" id="section-4.2.4" href="#section-4.2.4">4.2.4</a>.  House Numbers</span>

   PIDF-LO specifies two Elements related to house numbers: HNO ("house
   number", numeric part only) and HNS ("house number suffix") (see
   <a href="./rfc4776#section-3.4">Section&nbsp;3.4 of RFC 4776</a>).  However, in many countries house numbers
   have a more complex format.  In any case, a clear definition is
   REQUIRED to minimize the potential for confusion.

   An address considerations document should provide the following
   information with regards to house numbers: if the structure of house
   numbers fits the HNO/HNS structure, the document MUST mandate to use
   those Elements as described in <a href="./rfc4776">RFC 4776</a>.  If the structure of house
   numbers does not directly fit into those two Elements, the document




<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 8]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   MUST define strategies on how to map source Fields into Elements.
   Besides HNO and HNS, LOC and BLD could be considered for carrying
   house number information.

   The document SHOULD describe whether or not abbreviations of house
   number information is valid.  If abbreviations are used, they MUST be
   clearly defined.  If house numbers consist of more than one number,
   or if multiple prefixes and suffixes may coexist, a delimiter symbol
   and a clear rule on how to concatenate all this data into the HNO and
   HNS Element might be necessary.  Whenever concatenating data into one
   Element, keep in mind that the location recipient might want to
   separate the data again.

   Example from Austria:

   HNO: concatenate all the data Fields of Austrian house numbers into
        this single PIDF-LO Element in a defined order with delimiter
        symbols (see <a href="#appendix-A.4.4">Appendix A.4.4</a> for the complete definition).

   HNS: usage not allowed since there may be multiple suffixes for the
        different parts of the house number.

   LOC and BLD are not to be used to reflect house number information.

<span class="h4"><a class="selflink" id="section-4.2.5" href="#section-4.2.5">4.2.5</a>.  Local Names</span>

   PIDF-LO contains three Elements to reflect local names: LMK, LOC, and
   NAM (<a href="./rfc4776#section-3.4">Section&nbsp;3.4 of RFC 4776</a>).  Such local names may be of importance
   for the identification of a location and may either coexist with a
   valid civic address or (in some cases) have no address assigned, in
   which case the local name, itself, identifies the location.  In rural
   regions, for example, a farm name may be more common than a street
   address to identify a location.  Landmarks typically don't have any
   civic address information assigned.  Therefore, local names may
   assist in finding a "street name" type address, but they might also
   be the authoritative (and only) civic location information.

   For any required or optional Element out of LMK, LOC, or NAM, the
   considerations document should state potential values (source data)
   for the Element.  In the case that multiple values for an Element may
   occur, a concatenation/selection strategy should be described.
   Concatenation using ";" as a separator is recommended, unless this
   character also appears in the source Fields.

   If local name information and "common" address information is both
   available and used, the document SHOULD discuss the relationship
   between those two address information types and the expected behavior
   of location recipients.



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                 [Page 9]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Example from Austria:

   NAM: contains the "Vulgoname" (local name); multiple local names are
        separated by a semicolon (if applicable).

   LMK: contains the farm name (just one name possible) (if applicable).

   LOC: can be used without restriction for additional location
        information (as per <a href="./rfc4119">RFC 4119</a>).

   The "Vulgoname" is useful to identify the location within its
   locality, since official addresses (especially in rural regions)
   might not be well known.

<span class="h4"><a class="selflink" id="section-4.2.6" href="#section-4.2.6">4.2.6</a>.  Floors</span>

   PIDF-LO defines the Element FLR to hold floor information but does
   not further specify its content.  <a href="./rfc3825#section-2.1">Section&nbsp;2.1 of RFC 3825</a> provides
   guidance about floor numbering but is not directly related to PIDF-
   LO.

   An address considerations document SHOULD clearly specify how to
   express floors using the FLR Element.  Following the above-mentioned
   guidance is RECOMMENDED; however, local nomenclature might require a
   completely different system.  The document SHOULD specify whether
   only numbers, text, or both are allowed in the FLR Element.  If there
   are standard values for certain floors, they SHOULD be listed.
   Abbreviations SHOULD be avoided, unless they are the primary (well-
   known) way of identifying floors.

   Example from Austria:

   If floor numbers are to be mapped, the FLR Element MUST be used.
   Numbers and text are both allowed.  The first floor (&lt;FLR&gt;1&lt;/FLR&gt;) is
   the first "full" floor above the floor at street level.  The floor at
   street level is &lt;FLR&gt;EG&lt;/FLR&gt; or &lt;FLR&gt;0&lt;/FLR&gt;.  There might be
   intermediate floors, especially between the floor at street level and
   the "first floor".  Such intermediate floors have names like
   "Mezzanine", "Erster Halbstock" ("first half floor"), or "Zweiter
   Halbstock" ("second half floor"), and have local meanings.

<span class="h4"><a class="selflink" id="section-4.2.7" href="#section-4.2.7">4.2.7</a>.  Address Codes</span>

   Address codes are available in several countries in different forms
   (for estates, buildings, or usable units for example).  These codes
   identify an address record and MAY be placed in the ADDCODE Element
   in PIDF-LO.  Address codes can help the location recipient to
   determine the location and to identify the original record in the



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 10]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   data source.  Depending on the type of code, the code alone (without
   any other Elements) may even be sufficient to fully identify an
   address within a country.

   In such cases, a PIDF-LO containing just the country and ADDCODE
   Elements might provide enough information to retrieve a civic
   address, given the location recipient has access to the respective
   source database.

   A civic address considerations document SHOULD specify whether and in
   which applications the use of the ADDCODE Element is allowed.  If
   ADDCODE is used, its relation to the remaining Elements MUST be
   clearly stated.  If several namespaces for address codes exist in a
   country, a mechanism to distinguish the different code spaces MUST be
   described.

   Examples from Austria:

   Statistik Austria provides 4 codes: Adresscode (AdrCD), Adresssubcode
   (AdrsubCD), Objektnummer (ObjNr), and Nutzungseinheitenlaufnummer
   (NtzLnr).

   The following format SHOULD be used:

        &lt;ADDCODE&gt;AdrCD=1234567;AdrsubCD=123;
        ObjNr=2333211;NtzLnr=0001&lt;/ADDCODE&gt;

<span class="h4"><a class="selflink" id="section-4.2.8" href="#section-4.2.8">4.2.8</a>.  Other Elements</span>

   This section lists all PIDF-LO Elements that have not been discussed
   so far.

   To specify the location inside a building, the following Elements can
   be useful:

   o  UNIT
   o  ROOM
   o  SEAT

   The following Elements are to be used for the representation of
   postal codes:

   o  PC
   o  PCN
   o  POBOX






<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 11]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   To describe the place-type or the building, the following Elements
   are available:

   o  PLC - Place-type (for allowed values, refer to the IANA registry
      defined in [<a href="./rfc4589" title="&quot;Location Types Registry&quot;">RFC4589</a>])

   o  BLD - Building (structure)

   For any of those Elements that are required or optional in a mapping,
   the semantics of its contents must be described if it differs from
   the definition in the PIDF-LO base documents.

   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
   by the owner of the respective building if a considerations document
   does not restrict their use.  For example, an airport could decide to
   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
   name of the airport could be placed in NAM.

<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>.  Security Considerations</span>

   <a href="./rfc4119">RFC 4119</a> contains general security considerations for handling PIDF-
   LOs.

<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>.  IANA Considerations</span>

   IANA has created the registry "PIDF-LO Civic Address Considerations
   Registry", according to the following definitions.  Furthermore, this
   document registers a civic address considerations document for
   Austrian addresses, as provided in the Appendix of this document, and
   also registers the considerations of <a href="./rfc4776">RFC 4776</a> as obsolete.

<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>.  PIDF-LO Civic Address Considerations Registry</span>

<span class="h4"><a class="selflink" id="section-6.1.1" href="#section-6.1.1">6.1.1</a>.  Structure</span>

   The IANA registry contains the following fields:

   o  Country-Code: either the ISO 3166 alpha-two code of the country to
      which the consideration applies or "other" in case the
      considerations document is not specific to a particular country.
      This field is to be defined by the requestor.

   o  Serial Number: a number that uniquely identifies a considerations
      document within a certain "Country-Code" field value.  Serial
      Numbers are sequentially assigned by IANA per Country-Code value,
      start at zero, and are never reused.



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 12]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   o  Reference to specification: this field contains a reference to the
      considerations document.  The xref type "rfc" should be used for
      referencing to RFCs, while other documents should use the "uri"
      type.

   o  Requestor: the author of the document.

   o  Status: one of either "active" or "obsolete".  When the document
      is registered by IANA, the status is first set to "active" by
      IANA.  Experts may later request changing the status to
      "obsolete", especially if there is an updated version of the
      considerations document available.  Authors of considerations
      documents must contact the experts if they wish to change the
      status of the document.

   Note: the combination of Country-Code and Serial Number fields
   uniquely identifies a considerations document in the registry (for
   example, "AT-0", "US-0", "US-1", or "other-0").

<span class="h4"><a class="selflink" id="section-6.1.2" href="#section-6.1.2">6.1.2</a>.  Registration Template</span>

   For registration of address considerations documents in the registry,
   requesters SHOULD use the following template.  The template SHOULD be
   contained in the considerations document itself.

           &lt;record&gt;
             &lt;country&gt; &lt;!-- Country-Code --&gt; &lt;/country&gt;
             &lt;serial&gt; &lt;!-- assigned by IANA --&gt; &lt;/serial&gt;

             &lt;!-- reference to document --&gt;
             &lt;xref type="uri" data="http://www.example.org/civicaddr/"/&gt;

             &lt;!-- record requesters --&gt;
             &lt;xref type="person" data="John_Doe"/&gt;
             &lt;xref type="person" data="Jane_Dale"/&gt;

             &lt;status&gt; &lt;!-- assigned by IANA --&gt; &lt;/status&gt;
           &lt;/record&gt;

          &lt;people&gt;
            &lt;person id="John_Doe"&gt;
              &lt;name&gt; &lt;!-- Firstname Lastname --&gt; &lt;/name&gt;
              &lt;org&gt; &lt;!-- Organization Name --&gt; &lt;/org&gt;
              &lt;uri&gt; &lt;!-- mailto: or http: URI --&gt; &lt;/uri&gt;
              &lt;updated&gt; &lt;!-- date format YYYY-MM-DD --&gt; &lt;/updated&gt;
            &lt;/person&gt;
            &lt;!-- repeat person section for each person --&gt;
          &lt;/people&gt;



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 13]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h4"><a class="selflink" id="section-6.1.3" href="#section-6.1.3">6.1.3</a>.  Registry Location</span>

   Approved registrations are published in the IANA registry named
   "PIDF-LO Civic Address Considerations Registry", which is available
   from <a href="http://www.iana.org">http://www.iana.org</a>.

   Registrations are sorted by ascending order by the Country-Code and
   by Serial Number within Country-Code values.  Registrations with
   Country-Code of "other" are put at the end of the list.

<span class="h4"><a class="selflink" id="section-6.1.4" href="#section-6.1.4">6.1.4</a>.  Registration Procedure</span>

   Following the policies outlined in [<a href="./rfc5226" title="">RFC5226</a>], new address
   considerations are added to the registry after Expert Review (see
   <a href="./rfc5226#section-4.1">Section&nbsp;4.1 in RFC 5226</a>).  The Expert will generally check if the
   submitted address considerations conform to the civic address
   guidelines in this document (see <a href="#section-4">Section 4</a>).  If in doubt, the Expert
   SHOULD consult the GEOPRIV mailing list or its dedicated successor.
   If possible, the Experts SHOULD check the available documentation on
   which the address consideration is based.

<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>.  Registration Request for Austria</span>

   This document registers the civic address considerations for
   addresses from the official Austrian Building and Habitation
   registry, according to the registration procedure described above.
   The required information is contained in <a href="#appendix-A">Appendix A</a>.

<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a>.  Registration of the Considerations in <a href="./rfc4776">RFC 4776</a> as Obsolete</span>

   Since this document updates <a href="./rfc4776">RFC 4776</a>, the considerations on the
   subdivision Elements in <a href="./rfc4776#section-3.4">Section&nbsp;3.4 of RFC 4776</a> for Canada, Germany,
   Japan, Korea, and the United States are obsolete.  The following IANA
   registration records register them in the IANA registry as obsolete.

















<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 14]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Canada:
              &lt;record&gt;
                &lt;country&gt;CA&lt;/country&gt;
                &lt;serial&gt;0&lt;/serial&gt;
                &lt;xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/&gt;
                &lt;xref type="person" data="Henning_Schulzrinne"/&gt;
                &lt;status&gt;obsolete&lt;/status&gt;
              &lt;/record&gt;

             &lt;people&gt;
               &lt;person id="Henning_Schulzrinne"&gt;
                 &lt;name&gt;Henning Schulzrinne&lt;/name&gt;
                 &lt;org&gt;Columbia University&lt;/org&gt;
                 &lt;uri&gt;mailto:hgs+geopriv@cs.columbia.edu&lt;/uri&gt;
                 &lt;updated&gt;2009-01-09&lt;/updated&gt;
               &lt;/person&gt;
             &lt;/people&gt;

   Germany:
              &lt;record&gt;
                &lt;country&gt;DE&lt;/country&gt;
                &lt;serial&gt;0&lt;/serial&gt;
                &lt;xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/&gt;
                &lt;xref type="person" data="Henning_Schulzrinne"/&gt;
                &lt;status&gt;obsolete&lt;/status&gt;
              &lt;/record&gt;

             &lt;people&gt;
               &lt;person id="Henning_Schulzrinne"&gt;
                 &lt;name&gt;Henning Schulzrinne&lt;/name&gt;
                 &lt;org&gt;Columbia University&lt;/org&gt;
                 &lt;uri&gt;mailto:hgs+geopriv@cs.columbia.edu&lt;/uri&gt;
                 &lt;updated&gt;2009-01-09&lt;/updated&gt;
               &lt;/person&gt;
             &lt;/people&gt;
















<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 15]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Japan:
              &lt;record&gt;
                &lt;country&gt;JP&lt;/country&gt;
                &lt;serial&gt;0&lt;/serial&gt;
                &lt;xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/&gt;
                &lt;xref type="person" data="Henning_Schulzrinne"/&gt;
                &lt;status&gt;obsolete&lt;/status&gt;
              &lt;/record&gt;

             &lt;people&gt;
               &lt;person id="Henning_Schulzrinne"&gt;
                 &lt;name&gt;Henning Schulzrinne&lt;/name&gt;
                 &lt;org&gt;Columbia University&lt;/org&gt;
                 &lt;uri&gt;mailto:hgs+geopriv@cs.columbia.edu&lt;/uri&gt;
                 &lt;updated&gt;2009-01-09&lt;/updated&gt;
               &lt;/person&gt;
             &lt;/people&gt;

   Korea:
              &lt;record&gt;
                &lt;country&gt;KR&lt;/country&gt;
                &lt;serial&gt;0&lt;/serial&gt;
                &lt;xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/&gt;
                &lt;xref type="person" data="Henning_Schulzrinne"/&gt;
                &lt;status&gt;obsolete&lt;/status&gt;
              &lt;/record&gt;

             &lt;people&gt;
               &lt;person id="Henning_Schulzrinne"&gt;
                 &lt;name&gt;Henning Schulzrinne&lt;/name&gt;
                 &lt;org&gt;Columbia University&lt;/org&gt;
                 &lt;uri&gt;mailto:hgs+geopriv@cs.columbia.edu&lt;/uri&gt;
                 &lt;updated&gt;2009-01-09&lt;/updated&gt;
               &lt;/person&gt;
             &lt;/people&gt;
















<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 16]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   United States:
              &lt;record&gt;
                &lt;country&gt;US&lt;/country&gt;
                &lt;serial&gt;0&lt;/serial&gt;
                &lt;xref type="rfc" data="<a href="./rfc4776">rfc4776</a>"/&gt;
                &lt;xref type="person" data="Henning_Schulzrinne"/&gt;
                &lt;status&gt;obsolete&lt;/status&gt;
              &lt;/record&gt;

             &lt;people&gt;
               &lt;person id="Henning_Schulzrinne"&gt;
                 &lt;name&gt;Henning Schulzrinne&lt;/name&gt;
                 &lt;org&gt;Columbia University&lt;/org&gt;
                 &lt;uri&gt;mailto:hgs+geopriv@cs.columbia.edu&lt;/uri&gt;
                 &lt;updated&gt;2009-01-09&lt;/updated&gt;
               &lt;/person&gt;
             &lt;/people&gt;

<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>.  Acknowledgements</span>

   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.




























<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 17]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>.  Civic Address Considerations Registration for the Austrian</span>
             Building and Habitation Registry

   The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and
   habitation registry law) is the legal basis for the obligation to
   provide a registry of civic addresses, buildings, and their usable
   units (subdivisions of buildings).  The registry is operated by
   "Statistik Austria GmbH", a fully governmentally owned company.  The
   local administrations of individual townships are responsible for
   keeping records in the registry up to date.

   The data format definition for the individual records is publicly
   available (data access itself is, however, restricted).  Hence, a
   uniform address database for the whole of Austria is available.  A
   detailed description of the Statistik Austria civic address data
   format is contained in <a href="#appendix-A.1">Appendix A.1</a>.

<span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>.  Civic Address Format in Austria</span>

   Statistik Austria data describes estates, buildings, and usable units
   [<a href="#ref-merkmalskatalog">merkmalskatalog</a>].  On a single estate there may be any number of
   buildings.  Apartment houses that have more than one staircase are
   split up in separate buildings at every staircase.  In every
   building, there may be several usable units.  For example, an
   apartment house may have several apartments, counting as separate
   usable units.  Moreover, one building may have more than one address
   but will have at least one address.  Below, the address Fields for
   estates (Table 1), buildings (Table 2), and usable units (Table 3)
   are shown.

   The ADDCODE, A5, and PCN Elements are optional, and the other
   Elements MUST be used if the data source contains their corresponding
   Fields.  The Elements A1 and A2 (not listed in the tables) SHOULD
   also be used if data is available.  Exception: when using the address
   codes only (access to the codes is necessary for the creator and
   recipient of the location information), just the ADDCODE and country
   Elements are mandatory; the other Elements can be used optionally, of
   course.













<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 18]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   +-------------------------+-------------------------------+---------+
   |  Statistik Austria name |          Explanation          | PIDF-LO |
   |                         |                               | Element |
   +-------------------------+-------------------------------+---------+
   |        Adresscode       |       address identifier      | ADDCODE |
   |                         |                               |         |
   |      Gemeindename,      |  commune name and identifier  |    A3   |
   |    Gemeindekennziffer   |                               |         |
   |                         |                               |         |
   |     Ortschaftsname,     |  village name and identifier  |    A4   |
   |   Ortschaftskennziffer  |                               |         |
   |                         |                               |         |
   |      Strassenname,      |   street name and identifier  |    RD   |
   |    Strassenkennziffer   |                               |         |
   |                         |                               |         |
   |  Katastralgemeindename, |   cadastral municipality and  |    A5   |
   | Katastralgemeindenummer |           identifier          |         |
   |                         |                               |         |
   |     Hausnummerntext     |   text in front of the house  |   HNO   |
   |                         |             number            |         |
   |                         |                               |         |
   | Hausnummer - 1.  Teil - |    first part of the house    |   HNO   |
   |          Nummer         |        number, numeric        |         |
   |                         |                               |         |
   | Hausnummer - 1.  Teil - |    first part of the house    |   HNO   |
   |        Buchstabe        |       number, character       |         |
   |                         |                               |         |
   |       Hausnummer -      |  links first and Bis part of  |   HNO   |
   | Verbindungszeichen Teil |          house number         |         |
   |         1 -&gt; Bis        |                               |         |
   |                         |                               |         |
   | Hausnummer - Bis-Nummer |  number of Bis part of house  |   HNO   |
   |                         |             number            |         |
   |                         |                               |         |
   |       Hausnummer -      |    character of Bis part of   |   HNO   |
   |      Bis-Buchstabe      |          house number         |         |
   |                         |                               |         |
   |    Hausnummernbereich   |     indicates if all house    |   HNO   |
   |                         | numbers specified or just odd |         |
   |                         |   or even numbers are stated  |         |
   |                         |                               |         |
   |       Postleitzahl      |          postal code          |    PC   |
   |                         |                               |         |
   |   Postleitzahlengebiet  |     postal community code     |   PCN   |
   |                         |                               |         |






<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 19]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   |        Vulgoname        |           local name          |   NAM   |
   |                         |                               |         |
   |         Hofname         |           farm name           |   LMK   |
   +-------------------------+-------------------------------+---------+

                 Table 1: Civic Address Fields for Estates

   +------------------------+--------------------------------+---------+
   | Statistik Austria name |           Explanation          | PIDF-LO |
   |                        |                                | Element |
   +------------------------+--------------------------------+---------+
   |      Adresssubcode     |         address subcode        | ADDCODE |
   |                        |                                |         |
   |      Objektnummer      |           object code          | ADDCODE |
   |                        |                                |         |
   |      Hausnummer -      |  links Bis and second part of  |   HNO   |
   |   Verbindungszeichen   |          house number          |         |
   |   Teil Bis -&gt; Teil 2   |                                |         |
   |                        |                                |         |
   |  Hausnummer - 2.  Teil |    second part of the house    |   HNO   |
   |        - Nummer        |         number, numeric        |         |
   |                        |                                |         |
   |  Hausnummer - 2.  Teil |    second part of the house    |   HNO   |
   |       - Buchstabe      |        number, character       |         |
   |                        |                                |         |
   |      Hausnummer -      | links second and third part of |   HNO   |
   |   Verbindungszeichen   |          house number          |         |
   |     Teil 2-&gt; Teil 3    |                                |         |
   |                        |                                |         |
   |  Hausnummer - 3.  Teil |     third part of the house    |   HNO   |
   |        - Nummer        |         number, numeric        |         |
   |                        |                                |         |
   |  Hausnummer - 3.  Teil |     third part of the house    |   HNO   |
   |       - Buchstabe      |        number, character       |         |
   |                        |                                |         |
   | Gebaeudeunterscheidung |     for differentiation of     |   HNO   |
   |                        |  buildings, e.g.  Maierweg 27  |         |
   |                        |      Hotel vs. Maierweg 27     |         |
   |                        |         Appartmenthaus         |         |
   |                        |                                |         |
   +------------------------+--------------------------------+---------+

          Table 2: Additional Civic Address Fields for Buildings








<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 20]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   +-----------------------------+---------------------------+---------+
   |    Statistik Austria name   |        Explanation        | PIDF-LO |
   |                             |                           | Element |
   +-----------------------------+---------------------------+---------+
   | Nutzungseinheitenlaufnummer |      usable unit code     | ADDCODE |
   |                             |                           |         |
   |          Tuernummer         |        door number        |   HNO   |
   |                             |                           |         |
   |          Topnummer          |        unit number        |   HNO   |
   |                             |                           |         |
   |       Lagebeschreibung      |   for verbal description  |   HNO   |
   |                             |                           |         |
   |             Lage            |  describes if the usable  |   FLR   |
   |                             |  unit is in the basement, |         |
   |                             |  mezzanine, attic floor,  |         |
   |                             |   ... (but not the floor  |         |
   |                             |          number)          |         |
   |                             |                           |         |
   |          Stockwerk          |           floor           |   FLR   |
   |                             |                           |         |
   +-----------------------------+---------------------------+---------+

         Table 3: Additional Civic Address Fields for Usable Units

   Note: "floors" in Austria (as in most parts of Europe) are counted
   differently compared to the US.  The "1st floor" in Austria is
   actually the floor above the floor at street level (2nd floor in US)
   -- not considering the fact that, in old buildings, there might be
   even more floors between street level and 1st floor, like "mezzanine"
   and "2nd mezzanine".  So, an Austrian "1st floor" could well be the
   "4th floor" according to US nomenclature.

   According to Statistik Austria [<a href="#ref-adrwarten" title="&quot;Handbuch Adress-GWR-Online Teil A Theoretisches Handbuch Kapitel 2 Warten von Adressen im Adress-GWR-Online&quot;">adrwarten</a>], 81.5% of Austrian
   addresses are of the simple type Musterstrasse 1 (Musterstrasse is an
   example street name). 5% of all addresses have an additional
   character, like Musterstrasse 1b. 1% of Austrian addresses look like
   Musterstrasse 21A - 23A.  For 8% of addresses, an additional
   separator is necessary -- like Musterstrasse 10 Haus 1 Stiege 2, or
   Musterstrasse 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 example, Musterstrasse gegenueber 3A,
   meaning this address is actually opposite of house number 3A.  Rather
   surprisingly, 4.47% of Austrian addresses contain the identifier of
   the estate since no house number is assigned at all -- for example,
   Musterstrasse GNR 1234, or Musterstrasse GNR .12/4 Kirche (this type
   of addresses is common for churches), or a real example in Stockerau:





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 21]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Kolomaniwoerth GNR 1583.  This identifier is stored by Statistik
   Austria as Hausnummerntext.  Otherwise, one could misinterpret this
   number as a house number, which would be definitely wrong.

<span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>.  Sample Addresses</span>

   In order to clarify the Austrian civic address format, this section
   provides some exemplary addresses:

   1234 Musterstadt, Hauptstrasse 1a - 5a Block 1b Haus 2c Stiege 1
   Postleitzahl: 1234
   Stadt: Musterstadt
   Strasse: Hauptstrasse
   Hausnummer - 1.  Teil - Nummer: 1
   Hausnummer - 1.  Teil - Buchstabe: a
   Hausnummer - Verbindungszeichen Teil 1 -&gt; Bis: -
   Hausnummer - 2.  Teil - Nummer: 5
   Hausnummer - 2.  Teil - Buchstabe: a
   Hausnummer - Verbindungszeichen Teil Bis -&gt; Teil 2: Block
   Hausnummer - 2.  Teil - Nummer: 1
   Hausnummer - 2.  Teil - Buchstabe: b
   Hausnummer - Verbindungszeichen Teil 2-&gt; Teil 3: Haus
   Hausnummer - 3.  Teil - Nummer: 2
   Hausnummer - 3.  Teil - Buchstabe: c
   Gebaeudeunterscheidung: Stiege 1

   1234 Musterstadt, Musterstrasse 13 Hotel
   Postleitzahl: 1234
   Stadt: Musterstadt
   Strasse: Musterstrasse
   Hausnummer - 1. Teil - Nummer: 13
   Gebaeudeunterscheidung: Hotel

   6020 Innsbruck, Anichstrasse vor 35
   Postleitzahl: 6020
   Stadt: Innsbruck
   Strasse: Anichstrasse
   Hausnummerntext: vor ("in front of")
   Hausnummer: 35

   6173 Oberperfuss, Riedl 3097 (Pfarrkirche)
   Postleitzahl: 6173
   Stadt: Oberperfuss
   Strasse: Riedl
   Hausnummerntext: 3097
   (since the estate identifier is 81305 3097, where 81305 is the





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 22]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Katastralgemeindenummer (cadastral municipality), and no house
   number is assigned)
   Vulgoname: Pfarrkirche

<span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>.  Address Codes in Austria</span>

   Statistik Austria registers 4 codes: Adresscode, Adresssubcode,
   Objektnummer, and the Nutzungseinheitenlaufnummer.  The Adresscode (7
   digits) is a unique code for an address in Austria.  The
   Adressregister maps the Adresscode to the civic address.  If there is
   a building located at an address, there is also an Adresssubcode (3
   digits) assigned.  Every building at an address has its own
   Adresssubcode (assigned sequentially starting with 001, 002, 003, and
   so on) in order to distinguish between buildings at the same address.
   Furthermore, every building located in Austria has its own unique
   code, the Objektnummer (7 digits).  This code identifies the building
   independent of the Adresscode.  That's because addresses are subject
   to change while the building may persist.  To differentiate multiple
   usable units inside a building, the Nutzungseinheitenlaufnummer (4
   digits) is used.  This code is also assigned in sequential order for
   each building.

   Besides, every address and building is geocoded by Statistik Austria.
   Hence, if every PIDF-LO would carry data in the format of Statistik
   Austria and if every PSAP would use the database of Statistik Austria
   for mapping, a time-saving, definite mapping without irregularities
   could be achieved.

   Besides these codes, Statistik Austria maintains reference numbers
   for communes, localities, or streets, to mention just a few.

<span class="h3"><a class="selflink" id="appendix-A.4" href="#appendix-A.4">A.4</a>.  Austrian Addresses in PIDF-LO</span>

   The following subsections define the mapping procedure.

<span class="h4"><a class="selflink" id="appendix-A.4.1" href="#appendix-A.4.1">A.4.1</a>.  Country</span>

   The country Element for Austria must be set to AT, since this is the
   ISO 3166-1 [<a href="#ref-ISO3166-1" title="&quot;Codes for the representation of names of countries and their subdivisions - Part 1: Country codes&quot;">ISO3166-1</a>] alpha-2 code for Austria.

   &lt;country&gt;AT&lt;/country&gt;

   The usage of the ISO 3166 code is demanded by <a href="./rfc4119">RFC 4119</a> [<a href="./rfc4119" title="&quot;A Presence-based GEOPRIV Location Object Format&quot;">RFC4119</a>], and
   <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>] proposes to use uppercase characters only.







<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 23]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h4"><a class="selflink" id="appendix-A.4.2" href="#appendix-A.4.2">A.4.2</a>.  Country Subdivisions A1-A6</span>

   A1 province (Bundesland), Section A.4.2.1
   A2 political district name or identifier (politischer Bezirk),
      Section A.4.2.2
   A3 commune name or identifier (Gemeinde), Section A.4.2.3
   A4 village name or identifier (Ortschaft), Section A.4.2.4
   A5 cadastral municipality name or identifier (Katastralgemeindename
      or Katastralgemeindenummer), Section A.4.2.5

   Element A6 must not be used.

   Last, there is an exception to mention that concerns the Austrian
   capital, Vienna (Wien).  The city of Vienna is equal to its political
   district and even the province is called Vienna.  Nevertheless,
   Vienna is separated in 23 districts within the same political
   district.  Consequently, an address in Vienna would look like:

   &lt;country&gt;AT&lt;/country&gt;
   &lt;A1&gt;Wien&lt;/A1&gt;
   &lt;A2&gt;Wien&lt;/A2&gt;
   &lt;A3&gt;Wien&lt;/A3&gt;
   &lt;A4&gt;Favoriten&lt;/A4&gt; or &lt;A4&gt;10&lt;A4&gt;
   &lt;A5&gt;Inzersdorf Stadt&lt;A5&gt;

   The Element A4, holding the city division, can hold the name or the
   number of the district.

<span class="h5"><a class="selflink" id="appendix-A.4.2.1" href="#appendix-A.4.2.1">A.4.2.1</a>.  A1 Element</span>

   As proposed in <a href="./rfc5139">RFC 5139</a> [<a href="./rfc5139" title="&quot;Revised Civic Location Format for Presence Information Data Format Location Object (PIDF-LO)&quot;">RFC5139</a>], for the PIDF-LO Element A1, the
   second part of ISO 3166-2 [<a href="#ref-ISO3166-2" title="&quot;Codes for the representation of names of countries and their subdivisions - Part 2: Country subdivision code&quot;">ISO3166-2</a>] can be used.  However, in
   Austria it is also common to write out the names of the states.
   Table 4 shows the possible values of the A1 Element for Austrian
   states.
















<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 24]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


        +------------------------+--------------------------------+
        |       Bundesland       | second part of ISO 3166-2 code |
        +------------------------+--------------------------------+
        |       Burgenland       |                1               |
        |                        |                                |
        |      K=U+00E4rnten     |                2               |
        |                        |                                |
        | Nieder=U+00F6sterreich |                3               |
        |                        |                                |
        |  Ober=U+00F6sterreich  |                4               |
        |                        |                                |
        |        Salzburg        |                5               |
        |                        |                                |
        |       Steiermark       |                6               |
        |                        |                                |
        |          Tirol         |                7               |
        |                        |                                |
        |       Vorarlberg       |                8               |
        |                        |                                |
        |          Wien          |                9               |
        +------------------------+--------------------------------+

                  Table 4: A1 Element Format for Austria
   (Note: values are shown in UTF-8, which is recommended to be used for
   PIDF-LO.)

<span class="h5"><a class="selflink" id="appendix-A.4.2.2" href="#appendix-A.4.2.2">A.4.2.2</a>.  A2 Element</span>

   Names of the Austrian political districts are available at Statistik
   Austria [<a href="#ref-bezirke" title="&quot;Politische Bezirke, Gebietsstand 2008&quot;">bezirke</a>].  These names, the unique code for the political
   district, or both can be used for the A2 Element.  If the content of
   the A2 Element is numeric, obviously the code is provided (there is
   no political district in Austria with a number in its name).  In case
   both the name and the code are provided, they are separated by a
   semicolon and the name must be listed first.

   The district of "Bruck an der Leitha" could be represented by:

   &lt;A2&gt;Bruck an der Leitha&lt;A2&gt;

   or
   &lt;A2&gt;307&lt;/A2&gt;

   or
   &lt;A2&gt;Bruck an der Leitha;307&lt;/A2&gt;






<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 25]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-26" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


<span class="h5"><a class="selflink" id="appendix-A.4.2.3" href="#appendix-A.4.2.3">A.4.2.3</a>.  A3 Element</span>

   The Element A3 holds the Gemeindename (commune name), the identifier
   of the Gemeinde, or both separated by a semicolon (the name must be
   listed first).  If the content of the A3 Element consists of a number
   only, it is obvious that just the identifier is provided.  Statistik
   Austria maintains a table with the Gemeindenamen and identifiers
   [<a href="#ref-gemeinden" title="&quot;Gemeindeliste sortiert nach Gemeindekennziffer, Gebietsstand 2008&quot;">gemeinden</a>], which must be used as the content for the A3 Element; no
   other spelling is allowed.

   Sample:

   &lt;A3&gt;Neusiedl am See&lt;/A3&gt;

   or
   &lt;A3&gt;10713&lt;/A3&gt;

   or
   &lt;A3&gt;Neusiedl am See;10713&lt;/A3&gt;

<span class="h5"><a class="selflink" id="appendix-A.4.2.4" href="#appendix-A.4.2.4">A.4.2.4</a>.  A4 Element</span>

   The Element A4 holds the Ortschaftsname (village name), the
   Ortschaftskennziffer (the identifier), or both separated by a
   semicolon (the name must be listed first).  If the content of the A4
   Element consists of a number only, it is obvious that just the
   identifier is provided, since there are no Ortschaftsnamen in Austria
   that contain a number.  Statistik Austria maintains a table with the
   Ortschaftsnamen and identifiers [<a href="#ref-ortschaften" title="&quot;Gemeinden mit Ortschaften und Postleitzahlen, Gebietsstand 2008&quot;">ortschaften</a>], which must be used as
   the content for the A4 Element; no other spelling is allowed.

   Sample:

   &lt;A4&gt;Wilfleinsdorf&lt;/A4&gt;

   or
   &lt;A4&gt;03448&lt;/A4&gt;

   or
   &lt;A4&gt;Wilfleinsdorf;03448&lt;/A4&gt;

<span class="h5"><a class="selflink" id="appendix-A.4.2.5" href="#appendix-A.4.2.5">A.4.2.5</a>.  A5 Element</span>

   The Element A5 holds the Katastralgemeindename (cadastral
   municipality), the Katastralgemeindenummer (the identifier), or both
   separated by a semicolon (the name must be listed first).  If the





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 26]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-27" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   content of the A5 Element consists of a number only, it is obvious
   that just the identifier is provided, since there are no
   Katastralgemeindenamen in Austria that contain a number.

   Sample (Vienna, Fuenfhaus):

   &lt;A5&gt;Oberbaumgarten&lt;/A5&gt;

   or
   &lt;A5&gt;1208&lt;/A5&gt;

   or
   &lt;A5&gt;Oberbaumgarten;1208&lt;/A5&gt;

<span class="h4"><a class="selflink" id="appendix-A.4.3" href="#appendix-A.4.3">A.4.3</a>.  Road and Street Names</span>

   The PIDF-LO Element RD holds the complete street name, including the
   street suffix.  No abbreviations are allowed.  No other Elements are
   needed for streets and must not be used.

<span class="h4"><a class="selflink" id="appendix-A.4.4" href="#appendix-A.4.4">A.4.4</a>.  House Numbers</span>

   Statistik Austria lists 14 data Fields related to the house number of
   a building plus another 5 Fields for distinction of different usable
   units inside a building (including the floor, which has a separate
   Element in PIDF-LO).  Unfortunately, PIDF-LO only defines a single
   house number Element (HNO, numeric part only) and house number suffix
   Element (HNS).  Therefore, this section defines a mapping in order to
   accommodate all data: all house number data is concatenated into a
   single HNO Element, even though it is expected to hold numeric part
   only.

   In order to allow automatic procession of the HNO Element, it is
   necessary to use a semicolon as a delimiter symbol (Austrian house
   numbers do not contain semicolons).  The house number parts MUST be
   provided in the order in which they are listed by the Statistik
   Austria document [<a href="#ref-merkmalskatalog">merkmalskatalog</a>].  For user-interface
   representation, the semicolon-separated format can be transformed by
   replacing semicolons by spaces (multiple spaces should be combined)
   and no space should be present between a numeric part of a house
   number and its related character.

   It is not allowed to use the HNS Element for Austrian addresses,
   since there are addresses that do not have just a single suffix.







<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 27]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-28" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   The house number "vor 1 - 1A" (consisting of a house number text
   "vor", first part of the house number numeric "1", "-" as the link of
   the first and Bis part, "1" as house number Bis part numeric, "A" as
   character of the Bis part) would be mapped to:

   &lt;HNO&gt;vor;1;;-;1;A;;;;;;;;;;;&lt;/HNO&gt;

<span class="h4"><a class="selflink" id="appendix-A.4.5" href="#appendix-A.4.5">A.4.5</a>.  Local Names</span>

   NAM: contains the Vulgoname (local name); multiple local names are
        separated by a semicolon (if applicable).

   LMK: contains the farm name (just one name possible) (if applicable).

   LOC: can be used without restriction for additional location
        information (as per <a href="./rfc4119">RFC 4119</a>).

<span class="h4"><a class="selflink" id="appendix-A.4.6" href="#appendix-A.4.6">A.4.6</a>.  Floors</span>

   The floor Element may contain numbers or text describing the floor.
   The first floor (&lt;FLR&gt;1&lt;/FLR&gt;) is the floor above the floor at street
   level.  The floor at street level is &lt;FLR&gt;EG&lt;/FLR&gt; or &lt;FLR&gt;0&lt;/FLR&gt;.
   Other floors may have names like mezzanine, for example.  The
   Statistik Austria data Fields Lage and Stockwerk are concatenated if
   necessary.

<span class="h4"><a class="selflink" id="appendix-A.4.7" href="#appendix-A.4.7">A.4.7</a>.  Additional Code Element</span>

   The Element additional code may be used to hold the codes provided by
   Statistik Austria.  There is an Adresscode, Adresssubcode,
   Objektnummer, and a Nutzungseinheitenlaufnummer.  These unique codes
   identify the location.  Actually, these codes alone would be enough
   but require that the location recipient has access to the database of
   Statistik Austria.

   If the additional code in a PIDF-LO document is going to hold the
   codes from Statistik Austria, the following format should be used:

   &lt;ADDCODE&gt;AdrCD=1234567;AdrsubCD=123;
   ObjNr=2333211;NtzLnr=0001&lt;/ADDCODE&gt;

   It is not necessary to provide all codes, but there are some
   restrictions: the Adresssubcode cannot be used without an Adresscode.
   More restrictions are defined by Statistik Austria.  By setting the
   country Element to AT (see <a href="#section-4.2.1">Section 4.2.1</a>), indicating an Austrian
   address, the Additional Code Element is expected to hold codes from





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 28]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-29" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Statistik Austria only.  When creating PIDF-LO documents using
   address codes by Statistik Austria, the country and ADDCODE Elements
   are mandatory.

<span class="h4"><a class="selflink" id="appendix-A.4.8" href="#appendix-A.4.8">A.4.8</a>.  Other Elements</span>

   The Elements PC and PCN can hold the data form Statistik Austria, the
   POBOX can be used if the post assigned a post office box.  At least
   the PC Element should be present.

   PC:    Postleitzahl (postal code)

   PCN:   Postleitzahlengebiet (postal community name)

   POBOX: Postfach

   The Elements UNIT, ROOM, SEAT, PLC, and BLD may be used without
   further restriction.

<span class="h4"><a class="selflink" id="appendix-A.4.9" href="#appendix-A.4.9">A.4.9</a>.  Elements Not to Be Used</span>

   A6
   STS
   HNS
   PRD
   POD
   RDBR
   RDSUBBR
   PRM
   POM

<span class="h3"><a class="selflink" id="appendix-A.5" href="#appendix-A.5">A.5</a>.  Example</span>

   This section shows an example mapping of an Austrian address to
   PIDF-LO.

   Address:

   Bundesland: Wien
   Politischer Bezirk: Wien
   Gemeindename: Wien
   9. Bezirk
   Strasse: Lazarettgasse
   Hausnummer - 1. Teil - Nummer: 13
   Hausnummer - 1. Teil - Buchstabe: A
   Hausnummer - Verbindungszeichen Teil 1-Bis: -





<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 29]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-30" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


   Hausnummer - Bis-Nummer: 13
   Hausnummer - Bis-Buchstabe: C
   Postleitzahl: 1090

   PIDF-LO:

   &lt;?xml version="1.0" encoding="UTF-8" ?&gt;
     &lt;presence xmlns="urn:ietf:params:xml:ns:pidf"
        xmlns:gp="urn:ietf:params:xml:ns:pidf:geopriv10"
        xmlns:cl="urn:ietf:params:xml:ns:pidf:geopriv10:civicAddr"
        entity="pres:123@examplehost"&gt;
      &lt;tuple id="abcd123456"&gt;
       &lt;status&gt;
        &lt;gp:geopriv&gt;
          &lt;gp:location-info&gt;
            &lt;cl:civicAddress xml:lang="de"&gt;
              &lt;cl:country&gt;AT&lt;/cl:country&gt;
              &lt;cl:A1&gt;Wien&lt;/cl:A1&gt;
              &lt;cl:A2&gt;Wien&lt;/cl:A2&gt;
              &lt;cl:A3&gt;Wien&lt;/cl:A3&gt;
              &lt;cl:A4&gt;9&lt;/cl:A4&gt;
              &lt;cl:RD&gt;Lazarettgasse&lt;/cl:RD&gt;
              &lt;cl:HNO&gt;;13;A;-;13;C;;;;;;;;;;;;&lt;/cl:HNO&gt;
              &lt;cl:PC&gt;1090&lt;/cl:PC&gt;
            &lt;/cl:civicAddress&gt;
          &lt;/gp:location-info&gt;
         &lt;gp:usage-rules&gt;
         &lt;gp:retransmission-allowed&gt;yes&lt;/gp:retransmission-allowed&gt;
         &lt;gp:retention-expiry&gt;2009-11-10T12:00:00Z&lt;/gp:retention-expiry&gt;
         &lt;/gp:usage-rules&gt;
        &lt;/gp:geopriv&gt;
       &lt;/status&gt;
       &lt;timestamp&gt;2009-02-09T12:00:00Z&lt;/timestamp&gt;
      &lt;/tuple&gt;
     &lt;/presence&gt;

<span class="h3"><a class="selflink" id="appendix-A.6" href="#appendix-A.6">A.6</a>.  IANA Registration Record</span>

       &lt;record&gt;
         &lt;country&gt;AT&lt;/country&gt;
         &lt;serial&gt;0&lt;/serial&gt;

         &lt;!-- reference to document --&gt;
         &lt;xref type="rfc" data="<a href="./rfc5774">rfc5774</a>"/&gt;

         &lt;!-- record requesters --&gt;
         &lt;xref type="person" data="Alexander_Mayrhofer"/&gt;
         &lt;xref type="person" data="Karl_Heinz_Wolf"/&gt;



<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 30]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-31" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


         &lt;status&gt;active&lt;/status&gt;
       &lt;/record&gt;

      &lt;people&gt;
        &lt;person id="Alexander_Mayrhofer"&gt;
          &lt;name&gt;Alexander Mayrhofer&lt;/name&gt;
          &lt;org&gt;nic.at GmbH&lt;/org&gt;
          &lt;uri&gt;mailto:alexander.mayrhofer@nic.at&lt;/uri&gt;
          &lt;updated&gt;2009-01-09&lt;/updated&gt;
        &lt;/person&gt;
        &lt;person id="Karl_Heinz_Wolf"&gt;
          &lt;name&gt;Karl Heinz Wolf&lt;/name&gt;
          &lt;org&gt;nic.at GmbH&lt;/org&gt;
          &lt;uri&gt;mailto:karlheinz.wolf@nic.at&lt;/uri&gt;
          &lt;updated&gt;2009-01-09&lt;/updated&gt;
        &lt;/person&gt;
      &lt;/people&gt;

Normative References

   [<a id="ref-RFC2119">RFC2119</a>]     Bradner, S., "Key words for use in RFCs to Indicate
                 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.

   [<a id="ref-RFC4119">RFC4119</a>]     Peterson, J., "A Presence-based GEOPRIV Location Object
                 Format", <a href="./rfc4119">RFC 4119</a>, December 2005.

   [<a id="ref-RFC4589">RFC4589</a>]     Schulzrinne, H. and H. Tschofenig, "Location Types
                 Registry", <a href="./rfc4589">RFC 4589</a>, July 2006.

   [<a id="ref-RFC4776">RFC4776</a>]     Schulzrinne, H., "Dynamic Host Configuration Protocol
                 (DHCPv4 and DHCPv6) Option for Civic Addresses
                 Configuration Information", <a href="./rfc4776">RFC 4776</a>, November 2006.

   [<a id="ref-RFC5139">RFC5139</a>]     Thomson, M. and J. Winterbottom, "Revised Civic
                 Location Format for Presence Information Data Format
                 Location Object (PIDF-LO)", <a href="./rfc5139">RFC 5139</a>, February 2008.

   [<a id="ref-RFC5226">RFC5226</a>]     Narten, T. and H. Alvestrand, "Guidelines for Writing
                 an IANA Considerations Section in RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc5226">RFC</a>
                 <a href="./rfc5226">5226</a>, May 2008.

   [<a id="ref-W3C.REC-xml-20060816">W3C.REC-xml-20060816</a>]
                 W3C, "Extensible Markup Language (XML) 1.0 (Fourth
                 Edition)", Recommendation REC-xml-20060816, August
                 2006, &lt;<a href="http://www.w3.org/TR/2006/REC-xml-20060816">http://www.w3.org/TR/2006/REC-xml-20060816</a>&gt;.






<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 31]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-32" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


Informative References

   [<a id="ref-adrwarten">adrwarten</a>]   Statistik Austria, "Handbuch Adress-GWR-Online Teil A
                 Theoretisches Handbuch Kapitel 2 Warten von Adressen im
                 Adress-GWR-Online", Jan 2005.

   [<a id="ref-merkmalskatalog">merkmalskatalog</a>]
                 Statistik Austria, "Handbuch Adress-GWR-Online Teil C
                 Anhang 2 Merkmalskatalog", Sept 2004.

   [<a id="ref-ISO3166-1">ISO3166-1</a>]   International Organization for Standardization, "Codes
                 for the representation of names of countries and their
                 subdivisions - Part 1: Country codes", ISO Standard
                 3166-1:1997, 1997.

   [<a id="ref-ISO3166-2">ISO3166-2</a>]   International Organization for Standardization, "Codes
                 for the representation of names of countries and their
                 subdivisions - Part 2: Country subdivision code", ISO
                 Standard 3166-2:1998, 1998.

   [<a id="ref-bezirke">bezirke</a>]     Statistik Austria, "Politische Bezirke, Gebietsstand
                 2008", Feb 2008.

   [<a id="ref-gemeinden">gemeinden</a>]   Statistik Austria, "Gemeindeliste sortiert nach
                 Gemeindekennziffer, Gebietsstand 2008", Feb 2008.

   [<a id="ref-ortschaften">ortschaften</a>] Statistik Austria, "Gemeinden mit Ortschaften und
                 Postleitzahlen, Gebietsstand 2008", Feb 2008.























<span class="grey">Wolf &amp; Mayrhofer          Best Current Practice                [Page 32]</span></pre>
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-33" ></span>
<span class="grey"><a href="./rfc5774">RFC 5774</a>              Civic Address Considerations            March 2010</span>


Authors' Addresses

   Karl Heinz Wolf
   nic.at GmbH
   Karlsplatz 1/2/9
   Wien  A-1010
   Austria

   Phone: +43 1 5056416 37
   EMail: karlheinz.wolf@nic.at
   URI:   <a href="http://www.nic.at/">http://www.nic.at/</a>


   Alexander Mayrhofer
   nic.at GmbH
   Karlsplatz 1/2/9
   Wien  A-1010
   Austria

   Phone: +43 1 5056416 34
   EMail: alexander.mayrhofer@nic.at
   URI:   <a href="http://www.nic.at/">http://www.nic.at/</a>





























Wolf &amp; Mayrhofer          Best Current Practice                [Page 33]
</pre>