idnits 2.17.1
draft-ietf-geopriv-civic-address-recommendations-03.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** The document seems to lack a License Notice according IETF Trust
Provisions of 28 Dec 2009, Section 6.b.i or Provisions of 12 Sep 2009
Section 6.b -- however, there's a paragraph with a matching beginning.
Boilerplate error?
(You're using the IETF Trust Provisions' Section 6.b License Notice from
12 Feb 2009 rather than one of the newer Notices. See
https://trustee.ietf.org/license-info/.)
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
No issues found here.
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
-- The draft header indicates that this document updates RFC4776, but the
abstract doesn't seem to directly say this. It does mention RFC4776
though, so this could be OK.
Miscellaneous warnings:
----------------------------------------------------------------------------
== The copyright year in the IETF Trust and authors Copyright Line does not
match the current year
(Using the creation date from RFC4776, updated by this document, for
RFC5378 checks: 2006-11-17)
-- The document seems to lack a disclaimer for pre-RFC5378 work, but may
have content which was first submitted before 10 November 2008. If you
have contacted all the original authors and they are all willing to grant
the BCP78 rights to the IETF Trust, then this is fine, and you can ignore
this comment. If not, you may need to add the pre-RFC5378 disclaimer.
(See the Legal Provisions document at
https://trustee.ietf.org/license-info for more information.)
-- The document date (July 9, 2009) is 5404 days in the past. Is this
intentional?
Checking references for intended status: Best Current Practice
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
** Obsolete normative reference: RFC 5226 (Obsoleted by RFC 8126)
Summary: 2 errors (**), 0 flaws (~~), 1 warning (==), 3 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
2 GEOPRIV K. Wolf
3 Internet-Draft A. Mayrhofer
4 Updates: 4776 (if approved) nic.at
5 Intended status: BCP July 9, 2009
6 Expires: January 10, 2010
8 Considerations for Civic Addresses in PIDF-LO - Guidelines and IANA
9 Registry Definition
10 draft-ietf-geopriv-civic-address-recommendations-03
12 Status of this Memo
14 This Internet-Draft is submitted to IETF in full conformance with the
15 provisions of BCP 78 and BCP 79.
17 Internet-Drafts are working documents of the Internet Engineering
18 Task Force (IETF), its areas, and its working groups. Note that
19 other groups may also distribute working documents as Internet-
20 Drafts.
22 Internet-Drafts are draft documents valid for a maximum of six months
23 and may be updated, replaced, or obsoleted by other documents at any
24 time. It is inappropriate to use Internet-Drafts as reference
25 material or to cite them other than as "work in progress."
27 The list of current Internet-Drafts can be accessed at
28 http://www.ietf.org/ietf/1id-abstracts.txt.
30 The list of Internet-Draft Shadow Directories can be accessed at
31 http://www.ietf.org/shadow.html.
33 This Internet-Draft will expire on January 10, 2010.
35 Copyright Notice
37 Copyright (c) 2009 IETF Trust and the persons identified as the
38 document authors. All rights reserved.
40 This document is subject to BCP 78 and the IETF Trust's Legal
41 Provisions Relating to IETF Documents in effect on the date of
42 publication of this document (http://trustee.ietf.org/license-info).
43 Please review these documents carefully, as they describe your rights
44 and restrictions with respect to this document.
46 Abstract
48 This document provides a guideline for creating civic address
49 consideration documents for individual countries, as required by RFC
50 4776. Furthermore, this document also creates an IANA Registry
51 referring to such address consideration documents and registers such
52 an address consideration for Austria.
54 Table of Contents
56 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 5
58 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 6
60 3. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . 6
62 4. Specifying PIDF-LO Element Usage . . . . . . . . . . . . . . . 7
63 4.1. General Considerations and Workflow . . . . . . . . . . . 7
64 4.2. Guidelines for Individual Elements . . . . . . . . . . . . 8
65 4.2.1. Country . . . . . . . . . . . . . . . . . . . . . . . 9
66 4.2.2. Country Subdivisions A1-A6 . . . . . . . . . . . . . . 9
67 4.2.3. Road and Street Names . . . . . . . . . . . . . . . . 9
68 4.2.4. House Numbers . . . . . . . . . . . . . . . . . . . . 10
69 4.2.5. Local Names . . . . . . . . . . . . . . . . . . . . . 11
70 4.2.6. Floors . . . . . . . . . . . . . . . . . . . . . . . . 12
71 4.2.7. Address Codes . . . . . . . . . . . . . . . . . . . . 12
72 4.2.8. Other Elements . . . . . . . . . . . . . . . . . . . . 13
74 5. Security Considerations . . . . . . . . . . . . . . . . . . . 14
76 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
77 6.1. PIDF-LO Civic Address Consideration Registry . . . . . . . 14
78 6.1.1. Structure . . . . . . . . . . . . . . . . . . . . . . 14
79 6.1.2. Registration Template . . . . . . . . . . . . . . . . 15
80 6.1.3. Registry Location . . . . . . . . . . . . . . . . . . 16
81 6.1.4. Registration Procedure . . . . . . . . . . . . . . . . 16
82 6.2. Registration Request for Austria . . . . . . . . . . . . . 16
83 6.3. Registration of the considerations in RFC 4776 as
84 obsolete . . . . . . . . . . . . . . . . . . . . . . . . . 16
86 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19
88 Appendix A. Civic Address Considerations Registration for the
89 Austrian building and habitation registry . . . . . . 19
90 A.1. Civic Address Format in Austria . . . . . . . . . . . . . 20
91 A.2. Sample Addresses . . . . . . . . . . . . . . . . . . . . . 24
92 A.3. Address Codes in Austria . . . . . . . . . . . . . . . . . 25
93 A.4. Austrian Addresses in PIDF-LO . . . . . . . . . . . . . . 25
94 A.4.1. Country . . . . . . . . . . . . . . . . . . . . . . . 25
95 A.4.2. Country Subdivisions A1-A6 . . . . . . . . . . . . . . 25
96 A.4.3. Road and Street Names . . . . . . . . . . . . . . . . 28
97 A.4.4. House Numbers . . . . . . . . . . . . . . . . . . . . 29
98 A.4.5. Local Names . . . . . . . . . . . . . . . . . . . . . 29
99 A.4.6. Floors . . . . . . . . . . . . . . . . . . . . . . . . 29
100 A.4.7. Additional Code Element . . . . . . . . . . . . . . . 30
101 A.4.8. Other Elements . . . . . . . . . . . . . . . . . . . . 30
102 A.4.9. Elements not to be used . . . . . . . . . . . . . . . 30
103 A.5. Example . . . . . . . . . . . . . . . . . . . . . . . . . 31
104 A.6. IANA Registration Record . . . . . . . . . . . . . . . . . 32
106 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 33
107 8.1. Normative References . . . . . . . . . . . . . . . . . . . 33
108 8.2. Informative References . . . . . . . . . . . . . . . . . . 34
110 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 35
112 1. Introduction
114 The "Presence Information Data Format Location Object" (PIDF-LO)
115 [RFC4119] is an object format for carrying geographical information
116 on the Internet. PIDF-LO can contain civic address information, and
117 supports a range of "civic address types" (CATypes) to hold
118 individual attributes of such addresses (see Section 2.2.1 of
119 [RFC4119] and Section 3.1 of [RFC5139]).
121 In many use cases, PIDF-LOs are populated with data from long-
122 established sources, like postal or governmental building registers,
123 line information databases and yellow / white pages of infrastructure
124 providers, or official residents registers. The structure and format
125 of data from such sources is almost always different from PIDF-LO's
126 CAtypes definition - additionally, structure and format of those
127 sources differs from country to country.
129 To make use of such existing data sources, transposing that data into
130 PIDF-LO format is required. With no guidelines available on how to
131 map source Fields into CAtype Elements, different creators of PIDF-LO
132 documents might end up with different results, even when using the
133 same data source - which reduces interoperability and increases the
134 risk of misinterpretation by receivers.
136 Therefore, civic address considerations are necessary to ensure
137 uniform usage of PIDF-LO Elements for such data sources. [RFC4776]
138 explicitly requests such documents to be provided, but does neither
139 define their structure nor a way to publish them. This memo provides
140 documentation on how to create such civic address considerations, and
141 requests the creation of an IANA Registry to store references to such
142 documents. Furthermore, a civic address consideration for Austria is
143 provided in Appendix A to be registered in the IANA Registry.
145 Section 3.4 of [RFC4776] contains some example considerations
146 regarding the use of administrative sub-division elements for Canada,
147 Germany, Japan, Korea and the United States. This document IANA
148 registers these examples as "obsolete" (see Section 6.3).
150 Section 3.4 of [RFC4776] also contains instructions on the creation
151 of Civic Address Consideration documents on page 8. This document
152 updates this section, and replaces said instructions with Section 4
153 and 5 of this memo.
155 The guidelines in this document have been created with a focus on
156 formal application of PIDF-LO (such as conveying location during an
157 emergency call). It is not intended to forbid other, more informal
158 uses of PIDF-LO that may not follow any formal mapping
159 specifications. An example usecase of such informal usage may be the
160 transmission of PIDF-LO documents during an instant messaging session
161 between humans. Such use may, however, imply some drawbacks like
162 prohibiting automatic processing of civic addresses from such a
163 PIDF-LO.
165 2. Terminology
167 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
168 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
169 document are to be interpreted as described in RFC 2119 [RFC2119].
171 In addition, this document uses "Field" to refer to a field of a
172 civic address data source, and "Element" to refer to a CAType element
173 of a PIDF-LO.
175 3. Requirements
177 The following requirements apply to defining civic address mapping
178 considerations:
180 o The considerations document MUST identify the data source to which
181 the definitions apply. A brief description of its structure
182 SHOULD be provided as well.
184 o For any data source, just one active mapping definition should
185 exist in order to reduce the risk of ambiguous interpretation.
187 o The document MUST include instructions for any Field that occurs
188 in the data. For any of the Fields, the document MUST describe
189 whether the Field is required, optional, or must not be used in
190 the mapping procedure.
192 o Instructions MUST be included for any CAtype Element that is
193 registered by the time the document is created. Those
194 instructions MUST include information whether an Element is
195 required, optional, or must not be used in that mapping. In case
196 the set of CAtypes is revised by the IETF, the address
197 consideration document SHOULD be updated. Until an update is
198 approved, the existing mapping procedure MUST be used.
200 o Address mapping procedures SHOULD be reversible, so that location
201 recipients can identify the corresponding record in the original
202 data source (given they have access to that source).
204 o For any source data Field that is required or optional, at least
205 one example mapping MUST be provided.
207 o In many cases, data sources used in the mapping process might be
208 subject to access restrictions. Such restrictions (as imposed on
209 the original data) MUST also be imposed on the resulting PIDF-LO
210 documents. The considerations document SHOULD note such
211 restrictions in its Security Considerations section.
213 Although the mapping is defined in a national way and the actual
214 meaning of several PIDF-LO Elements may not be clear to an outsider,
215 at least the country element tells in what context this PIDF-LO was
216 created. In case of emergency calls, a PIDF-LO would just be passed
217 to a PSAP in the same country as the location generator anyway.
218 However, in a border region there might be exceptions and the PIDF-LO
219 could be sent to a neighboring country. The PIDF-LO can still be
220 passed on to a PSAP in the right country (based on the country
221 element), or the PSAP might be aware of the mapping scheme used in
222 the neighboring country.
224 A consistent mapping is also very important for checking if two
225 PIDF-LO documents describe the same location. When civic address
226 Fields are put into different PIDF-LO Elements, it may be difficult
227 to identify whether or not two PIDF-LOs describe identical addresses.
229 4. Specifying PIDF-LO Element Usage
231 The purpose of the civic address considerations for an individual
232 data source is to create interoperability by specifying a common list
233 of PIDF-LO Elements to be used, and by defining the mapping between
234 these Elements and the Fields of the respective data source.
236 4.1. General Considerations and Workflow
238 The workflow for creating an address considerations document is as
239 follows:
241 1. Describe the data source to which the address considerations
242 document applies.
243 2. Identify all Fields from the data source, and decide for each of
244 the Fields whether or not it is to be used for the purpose of
245 creating PIDF-LO documents. In the considerations document, all
246 Fields must be listed (or at least state which Fields are
247 considered in the mapping and clearly state that the other Fields
248 MUST NOT be used).
250 3. For each of the Fields that is required or optional, specify a
251 clear mapping instruction according to the guidelines below.
252 4. Provide a list of all CAtypes registered, and describe their
253 level of usage in this mapping (or combine it with the list of
254 Fields above and clearly list which Elements are not used for the
255 mapping procedure). For Elements that are not described in
256 detail state whether they MUST NOT be used at all or they may be
257 used without further restriction.
258 5. Provide examples of source data and mapping results
260 Civic address fields are designed to be generic containers. In some
261 cases, Fields clearly correspond to such a container; however, in
262 some other cases, identifying the correct container might require
263 some approximation. For example, in some countries the RD (road)
264 Element might also be appropriate for other thoroughfares, like
265 waterways or tunnels.
267 Fields that are identified to have the same meaning as one of the
268 CAtypes SHOULD be directly mapped to that CAtype Element.
270 Where CAtype usage diverges from the original specification, the
271 mapping definition of Fields that are mapped to that Element SHOULD
272 include a discussion of the differences.
274 Fields that do not fit into an existing CAtype: Even though the list
275 of CAtypes could be extended, it is not feasible to add new elements
276 for every new Field in every data source in every country.
277 Therefore, unless new generic CAtypes are specified by the IETF, only
278 existing elements can be used, which leaves the following options:
280 1. Concatenate several civic address fields into a single PIDF-LO
281 element (define delimiters if applicable and make sure the
282 separate civic address parts can be retrieved again)
283 2. Use a PIDF-LO element that is unused so far
285 Note: Obviously, the first option is required if the number of Fields
286 that are used in the mapping procedure is greater than the number of
287 existing CAtype Elements.
289 Note that the xml:lang attribute should be present in PIDF-LO XML
290 documents according to RFC 5139.
292 4.2. Guidelines for Individual Elements
294 The following sections discuss individual PIDF-LO Elements and
295 describe what to consider for each Element when defining civic
296 address considerations. It is RECOMMENDED to follow a similar
297 structure for considerations documents.
299 4.2.1. Country
301 The country element must hold the alpha-2 codes from ISO 3166-1
302 [refs.ISO3166-1] in upper case characters as clarified in Section 3.3
303 of RFC 5139 [RFC5139].
305 This element cannot be redefined on a national basis since it
306 identifies the country itself. This element is used to identify
307 which national mapping for civic addresses has been used in a
308 specific PIDF-LO.
310 Example for Austria: AT
312 4.2.2. Country Subdivisions A1-A6
314 The elements A1 to A6 are used to hold national subdivision
315 identifiers, with A1 holding the top-level subdivision identifier.
316 A1 may either contain the second part of ISO 3166-2 [refs.ISO3166-2]
317 (see section 3.4 of RFC 5139 [RFC5139]), or values as described in
318 the address consideration document. Elements "A2" to "A6" may
319 contain additional levels of subdivisions (see section 2.2.1 of RFC
320 4119).
322 For A1, an address consideration document MUST state whether ISO
323 3166-2 codes are to be used exclusively; alternatively it should
324 define a list of values to be used (for example, subdivision names).
325 In either case, A1 MUST NOT be redefined for any other use than
326 describing top level subdivisions.
328 For each of the A2 - A6 Elements that is required or optional, the
329 document SHOULD define the set of allowed values, either by listing
330 them, or by referring to such a list.
332 Example for Austria:
334 A1 province (Bundesland)
335 A2 political district (politischer Bezirk) name or identifier
336 A3 commune (Gemeinde) name or identifier
337 A4 village (Ortschaft) name or identifier
338 A5 cadastral municipality (Katastralgemeinde) name or identifier
340 A6 must not be used. For more details see the example in
341 Appendix A.4.2.
343 4.2.3. Road and Street Names
345 PIDF-LO contains the following Elements related to road names: RD,
346 RDSEC, RDBR, RDSUBADDR, PRM, POM (section 3.1 and 3.2 of RFC 5139
348 [RFC5139]) and PRD, POD, STS (section 3.4 of [RFC4776]). Note: The
349 use of the A6 Element for street names is not valid any more (Section
350 3.2 of RFC 5139 [RFC5139]).
352 Besides the basic specification of which of those Elements are
353 required, optional or not to be used, an address considerations
354 document may also describe more complicated dependencies (for
355 example, "RD is optional, but required if any other road name Element
356 is used").
358 For any required or optional element, the relation of those Elements
359 to Fields of the data source used MUST be described, as well as
360 special considerations (like concatenation of Fields into an Element)
361 if they apply. The usage of the Element STS (street suffix) SHOULD
362 be consistent. In case no suffixes are known in a data source, or it
363 is common to write the street name and the suffix together, the STS
364 Element SHOULD be left out completely. If suffixes may be
365 abbreviated the common abbreviations SHOULD be defined.
367 Example for Austria:
369 RD: street name
371 All other road Elements must not be used. Street suffixes are
372 already included in the "street name" Field, and must not be
373 abbreviated.
375 4.2.4. House Numbers
377 PIDF-LO specifies two Elements related to house numbers: HNO ("house
378 number", numeric part only) and HNS ("house number suffix") (see
379 section 3.4 of RFC 4776). However, in many countries house numbers
380 have a more complex format. In any case, a clear definition is
381 REQUIRED to minimize confusion potential.
383 An address considerations document should provide the following
384 information with regards to house numbers: If the structure of house
385 numbers fits the HNO/HNS structure, the document MUST mandate to use
386 those fields as described in RFC 4776. If the structure of house
387 numbers does not directly fit into those two Elements, the document
388 MUST define strategies on how to map source Fields into Elements.
389 Besides HNO and HNS, LOC and BLD could be considered for carrying
390 house number information.
392 The document SHOULD describe whether abbreviations of house number
393 information is valid or not. If abbreviations are used, they MUST be
394 clearly defined. If house number consists of more than one number,
395 or multiple prefixes and suffixes may coexist, a delimiter symbol and
396 a clear rule on how to concatenate all this data into the HNO and HNS
397 element might be necessary. Whenever concatenating data into one
398 Element, keep in mind that the location recipient might want to
399 separate the data again.
401 Example from Austria:
403 HNO: concatenate all the data elements of Austrian house numbers into
404 this single PIDF-LO Element in a defined order with delimiter symbols
405 (see Appendix A.4.4 for the complete definition).
407 HNS: Usage not allowed since there may be multiple suffixes for the
408 different parts of the house number.
410 LOC and BLD are not to be used to reflect house number information.
412 4.2.5. Local Names
414 PIDF-LO contains three elements to reflect local names: LMK, LOC, NAM
415 (section 3.4 of RFC 4776). Such local names may be of importance for
416 the identification of a location, and may either coexist with a valid
417 civic address or (in some cases) no address may be assigned so that
418 the local names itself identifies the location. In rural regions for
419 example, a farm name may be more common than a street address to
420 identify a location. Landmarks typically don't have any civic
421 address information assigned. Therefore, local names may assist in
422 finding a "street name" type address, but they might also be the
423 authoritative (and only) civic location information.
425 For any required or optional Element out of LMK, LOC, NAM the
426 considerations document should state potential values (source data)
427 for the element. In the case that multiple values for an Element may
428 occur, a concatenation / selection strategy should be described.
429 Concatenation using ";" as separator is recommended, unless this
430 character also appears in the source Fields.
432 If local name information and "common" address information is both
433 available and used, the document SHOULD discuss the relation between
434 those two address information types, and expected behaviour of
435 location recipients.
437 Example from Austria:
439 NAM: contains the "Vulgoname" (local name), multiple local names are
440 separated by a semicolon (if applicable)
442 LMK: contains the farm name (just one name possible) (if applicable)
443 LOC: can be used without restriction for additional location
444 information (as per RFC 4119)
446 The "Vulgoname" is useful to identify the location within its
447 locality, since official addresses especially in rural regions might
448 not be well known.
450 4.2.6. Floors
452 PIDF-LO defines the element FLR to hold floor information, but does
453 not further specify its content. Section 2.1 of RFC 3825 provides
454 guidance about floor numbering, but is not directly related to
455 PIDF-LO.
457 An address considerations document SHOULD clearly specify how to
458 express floors using the FLR element. Following the above mentioned
459 guidance is RECOMMENDED; however, local nomenclature might require a
460 completely different system. The document SHOULD specify whether
461 only numbers, text, or both are allowed in the FLR element. If there
462 are standard values for certain floors, they SHOULD be listed.
463 Abbreviations SHOULD be avoided, unless they are the primary (well
464 known) way of identifying floors.
466 Example from Austria:
468 If floor numbers are to be mapped, the FLR Element MUST be used.
469 Numbers and text are both allowed. The first floor (1) is
470 the first "full" floor above the floor at street level. The floor at
471 street level is EG or 0. There might be
472 intermediate floors, especially between the floor at street level and
473 the "first floor". Such intermediate floors have names like
474 "Mezzanine", "Erster Halbstock" ("first half floor"), "Zweiter
475 Halbstock" ("second half floor"), and have local meanings.
477 4.2.7. Address Codes
479 Address codes are available in several countries in different forms
480 (for estates, buildings or usable units for example). These codes
481 identify an address record, and MAY be placed in the ADDCODE element
482 in PIDF-LO. Address codes can help the location recipient to
483 determine the location, and to identify the original record in the
484 data source. Depending on the type of code, the code alone (without
485 any other Elements) may even be sufficient to fully identify an
486 address within a country.
488 In such cases, a PIDF-LO containing just the country and ADDCODE
489 elements might provide enough information to retrieve a civic
490 address, given the location recipient has access to the respective
491 source database.
493 A civic address considerations document SHOULD specify whether and in
494 which applications the use of the ADDCODE Element is allowed. If
495 ADDCODE is used, its relation to the remaining Elements MUST be
496 clearly stated. If several namespaces for address codes exist in a
497 country, a mechanism to distinguish the different code spaces MUST be
498 described.
500 Examples from Austria:
502 Statistik Austria provides 4 codes: Adresscode (AdrCD), Adresssubcode
503 (AdrsubCD), Objektnummer (ObjNr) and Nutzungseinheitenlaufnummer
504 (NtzLnr).
506 The following format SHOULD be used:
508 AdrCD=1234567;AdrsubCD=123;
509 ObjNr=2333211;NtzLnr=0001
511 4.2.8. Other Elements
513 This section lists all PIDF-LO Elements that have not been discussed
514 so far.
516 To specify the location inside a building, the following Elements can
517 be useful:
519 o UNIT
520 o ROOM
521 o SEAT
523 The following Elements are to be used for the representation of
524 postal codes:
526 o PC
527 o PCN
528 o POBOX
530 To describe the place-type or the building, the following Elements
531 are available:
533 o PLC - Place-type (see [RFC4589])
534 o BLD - Building (structure)
536 For any of those Elements that are required or optional in a mapping,
537 the semantics of its contents must be described, if it differs from
538 the definition in the PIDF-LO base documents.
540 It is RECOMMENDED that the elements SEAT, UNIT and ROOM remain to be
541 used for identifying a location inside a building. They MAY be used
542 by the owner of the respective building if a considerations document
543 does not restrict their use. For example, an airport could decide to
544 place the gate number in the UNIT element, and a location recipient
545 could identify that PIDF-LO by the value of the PLC Element. The
546 name of the airport could be placed in NAM.
548 5. Security Considerations
550 RFC 4119 contains general security considerations for handling PIDF-
551 LOs.
553 6. IANA Considerations
555 This document requests creation of the registry "PIDF-LO Civic
556 Address Consideration Registry", according to the following
557 definitions. Furthermore, this document requests registration of a
558 civic address considerations document for Austrian addresses as
559 provided in the Appendix of this document and also registers the
560 considerations of RFC 4776 as obsolete.
562 6.1. PIDF-LO Civic Address Consideration Registry
564 6.1.1. Structure
566 The IANA Registry contains the following fields:
568 o Country-Code: Either the ISO 3166 alpha-two code of the country to
569 which the consideration applies or "other" in case the
570 consideration document is not specific to a particular country.
571 This field is to be defined by the requestor.
573 o Serial Number: A number that uniquely identifies a considerations
574 document within a certain "Country-Code" field value. Serial
575 Numbers are sequentially assigned by IANA per "Country-Code"
576 value, start at zero, and are never reused.
578 o Reference to specification: This field contains a reference to the
579 considerations document.
581 o Requestor: The author of the document.
583 o Status: One of "active" or "obsolete". When the document is
584 registered by IANA, the status is first set to "active" by IANA.
585 Experts may later request changing the status to "obsolete",
586 especially if there is an updated version of the considerations
587 document available. Authors of consideration documents must
588 contact the experts if they wish to change the status of the
589 document.
591 Note: The combination of "Country-Code" and "Serial Number" fields
592 uniquely identify a considerations document in the registry (for
593 example, "AT-0", "US-0", "US-1" or "other-0").
595 6.1.2. Registration Template
597 For registration of address considerations documents in the registry,
598 requestors SHOULD use the following template. The template SHOULD be
599 contained in the considerations document itself.
601
602
603
605
606
607
609
610
611
612
613
615
616
618
619
620
621
622
623
624
625
626
628 6.1.3. Registry Location
630 Approved registrations are published in the IANA registry named
631 "PIDF-LO Civic Address Consideration Registry", which is available at
632 the following URI: XXX ((TO BE DEFINED BY IANA)).
634 Registrations are sorted by ascending order by the country code, and
635 by serial number within country code values. Registrations with
636 country code of "other" are put at the end of the list.
638 6.1.4. Registration Procedure
640 Following the policies outlined in [RFC5226], new address
641 considerations are added to the registry after Expert Review (see
642 Section 4.1 in RFC 5226). The Expert will generally check if the
643 submitted address considerations conforms the civic address
644 guidelines in this document (see Section 4). If in doubt, the
645 Experts SHOULD consult the GEOPRIV mailing list or it's dedicated
646 successor. If possible, the Experts SHOULD check the available
647 documentation on which the address consideration is based.
649 6.2. Registration Request for Austria
651 This document requests registration of the Civic Address
652 Considerations for addresses from the official Austrian Building and
653 Habitation registry, according to the registration procedure
654 described above. The required information is contained in Appendix
655 A.
657 6.3. Registration of the considerations in RFC 4776 as obsolete
659 Since this document updates RFC 4776, the considerations on the sub-
660 division elements in Section 3.4 of RFC 4776 for Canada, Germany,
661 Japan, Korea and the United States are obsolete. The following IANA
662 registration records register them in the IANA Registry as obsolete.
664 Canada:
666
667 CA
668
669 urn:ietf:rfc:4776
670
671
672
673 obsolete
674
676
677
678 Henning Schulzrinne
679 Columbia University
680 mailto:hgs+geopriv@cs.columbia.edu
681 2009-01-09
682
683
685 Germany:
687
688 DE
689
690 urn:ietf:rfc:4776
691
692
693
694 obsolete
695
697
698
699 Henning Schulzrinne
700 Columbia University
701 mailto:hgs+geopriv@cs.columbia.edu
702 2009-01-09
703
704
706 Japan:
708
709 JP
710
711 urn:ietf:rfc:4776
712
713
714
715 obsolete
716
718
719
720 Henning Schulzrinne
721 Columbia University
722 mailto:hgs+geopriv@cs.columbia.edu
723 2009-01-09
724
725
727 Korea:
729
730 KR
731
732 urn:ietf:rfc:4776
733
734
735
736 obsolete
737
739
740
741 Henning Schulzrinne
742 Columbia University
743 mailto:hgs+geopriv@cs.columbia.edu
744 2009-01-09
745
746
748 United States:
750
751 US
752
753 urn:ietf:rfc:4776
754
755
756
757 obsolete
758
760
761
762 Henning Schulzrinne
763 Columbia University
764 mailto:hgs+geopriv@cs.columbia.edu
765 2009-01-09
766
767
769 7. Acknowledgements
771 The authors would like to thank Martin Thomson and Richard Barnes for
772 reviewing the document, and Gregor Jaenin for contributing insights
773 into the Austrian civic address data format.
775 Appendix A. Civic Address Considerations Registration for the Austrian
776 building and habitation registry
778 The Austrian "Gebaeude- und Wohnungsregistergesetz" (building and
779 habitation registry law) is the legal basis for the obligation to
780 provide a registry of civic addresses, buildings and their usable
781 units (subdivisions of buildings). The registry is operated by
782 "Statistik Austria GmbH", a fully governmental owned company.
783 Responsibility for keeping records in the registry up to date is an
784 obligation to the local administration of the individual townships.
786 The data format definition for the individual records is publicly
787 available (data access itself is however restricted). Hence, a
788 uniform address data base for the whole Austria is available. A
789 detailed description of the Statistik Austria civic address data
790 format is contained in section Appendix A.1.
792 A.1. Civic Address Format in Austria
794 Statistik Austria data describes estates, buildings and usable units
795 [refs.merkmalskatalog]. On a single estate there may be any number
796 of buildings. Apartment houses that have more than one staircase,
797 are split up in separate buildings at every staircase. In every
798 building, there may be several usable units. For example, an
799 apartment house may have several apartments, counting as separate
800 usable units. Moreover, one building may have more than one address,
801 but at least one address. Below, the address Fields for estates
802 (Table 1), buildings (Table 2) and usable units (Table 3) are shown.
804 The ADDCODE, A5 and PCN Elements are optional, and the other Elements
805 MUST be used if the data source contains their corresponding Fields.
806 The Elements A1 and A2 (not listed in the tables) SHOULD also be used
807 if data is available. Exception: when using the address codes only
808 (access to the codes is necessary for creator and receiver of the
809 location information), just the ADDCODE and country Elements are
810 mandatory, the other Elements can be used optionally of course.
812 +-------------------------+-------------------------------+---------+
813 | Statistik Austria name | Explanation | PIDF-LO |
814 | | | Element |
815 +-------------------------+-------------------------------+---------+
816 | Adresscode | address identifier | ADDCODE |
817 | | | |
818 | Gemeindename, | commune name and identifier | A3 |
819 | Gemeindekennziffer | | |
820 | | | |
821 | Ortschaftsname, | village name and identifier | A4 |
822 | Ortschaftskennziffer | | |
823 | | | |
824 | Strassenname, | street name and identifier | RD |
825 | Strassenkennziffer | | |
826 | | | |
827 | Katastralgemeindename, | cadastral municipality and | A5 |
828 | Katastralgemeindenummer | identifier | |
829 | | | |
830 | Hausnummerntext | text in front of the house | HNO |
831 | | number | |
832 | | | |
833 | Hausnummer - 1. Teil - | first part of the house | HNO |
834 | Nummer | number, numeric | |
835 | | | |
836 | Hausnummer - 1. Teil - | first part of the house | HNO |
837 | Buchstabe | number, character | |
838 | | | |
839 | Hausnummer - | links first and Bis part of | HNO |
840 | Verbindungszeichen Teil | house number | |
841 | 1 -> Bis | | |
842 | | | |
843 | Hausnummer - Bis-Nummer | number of bis part of house | HNO |
844 | | number | |
845 | | | |
846 | Hausnummer - | character of bis part of | HNO |
847 | Bis-Buchstabe | house number | |
848 | | | |
849 | Hausnummernbereich | indicates if all house | HNO |
850 | | numbers specified or just odd | |
851 | | or even numbers are stated | |
852 | | | |
853 | Postleitzahl | postal code | PC |
854 | | | |
855 | Postleitzahlengebiet | postal community code | PCN |
856 | | | |
857 | Vulgoname | local name | NAM |
858 | | | |
859 | Hofname | farm name | LMK |
860 +-------------------------+-------------------------------+---------+
862 Table 1: Civic Address Fields for Estates
864 +------------------------+--------------------------------+---------+
865 | Statistik Austria name | Explanation | PIDF-LO |
866 | | | Element |
867 +------------------------+--------------------------------+---------+
868 | Adresssubcode | address subcode | ADDCODE |
869 | | | |
870 | Objektnummer | object code | ADDCODE |
871 | | | |
872 | Hausnummer - | links Bis and second part of | HNO |
873 | Verbindungszeichen | house number | |
874 | Teil Bis -> Teil 2 | | |
875 | | | |
876 | Hausnummer - 2. Teil | second part of the house | HNO |
877 | - Nummer | number, numeric | |
878 | | | |
879 | Hausnummer - 2. Teil | second part of the house | HNO |
880 | - Buchstabe | number, character | |
881 | | | |
882 | Hausnummer - | links second and third part of | HNO |
883 | Verbindungszeichen | house number | |
884 | Teil 2-> Teil 3 | | |
885 | | | |
886 | Hausnummer - 3. Teil | third part of the house | HNO |
887 | - Nummer | number, numeric | |
888 | | | |
889 | Hausnummer - 3. Teil | third part of the house | HNO |
890 | - Buchstabe | number, character | |
891 | | | |
892 | Gebaeudeunterscheidung | for differentiation of | HNO |
893 | | buildings, e.g. Maierweg 27 | |
894 | | Hotel vs. Maierweg 27 | |
895 | | Appartmenthaus | |
896 | | | |
897 +------------------------+--------------------------------+---------+
899 Table 2: Additional Civic Address Fields for Buildings
901 +-----------------------------+---------------------------+---------+
902 | Statistik Austria name | Explanation | PIDF-LO |
903 | | | Element |
904 +-----------------------------+---------------------------+---------+
905 | Nutzungseinheitenlaufnummer | usable unit code | ADDCODE |
906 | | | |
907 | Tuernummer | door number | HNO |
908 | | | |
909 | Topnummer | unit number | HNO |
910 | | | |
911 | Lagebeschreibung | for verbal description | HNO |
912 | | | |
913 | Lage | describes if the usable | FLR |
914 | | unit is in the basement, | |
915 | | mezzanine, attic floor, | |
916 | | ... (but not the floor | |
917 | | number) | |
918 | | | |
919 | Stockwerk | floor | FLR |
920 | | | |
921 +-----------------------------+---------------------------+---------+
923 Table 3: Additional Civic Address Fields for usable units
925 Note: "Floors" in Austria (as in most parts of Europe) are counted
926 differently compared to the US. The "1st floor" in Austria is
927 actually the floor above the floor at street level (2nd floor in US),
928 not considering the fact that in old buildings there might be even
929 more floors between street level and 1st floor, like "mezzanine",
930 "2nd mezzanine". So, an Austrian "1st floor" could well be the "4th
931 floor" according to US nomenclature.
933 According to Statistik Austria [refs.adrwarten], 81.5% of Austrian
934 addresses are of the simple type Musterstrasse 1 (Musterstrasse is an
935 example street name). 5% of all addresses have an additional
936 character, like Musterstrasse 1b. 1% of Austrian addresses look like
937 Musterstrasse 21A - 23A. For 8% of addresses, an additional separator
938 is necessary, like Musterstrasse 10 Haus 1 Stiege 2 or Musterstrasse
939 20 Gruppe A Reihe 1 Parzelle 13 or Musterstrasse 30 Weg 1 Parzelle
940 10. Very seldom, there are so called special addresses (0.03%), for
941 example Musterstrasse gegenueber 3A, meaning this address is actually
942 opposite of house number 3A. Rather surprisingly, 4.47% of Austrian
943 addresses contain the identifier of the estate since no house number
944 is assigned at all, for example: Musterstrasse GNR 1234, or
945 Musterstrasse GNR .12/4 Kirche (this type of addresses is common for
946 churches) or a real example in Stockerau: Kolomaniwoerth GNR 1583.
947 This identifier is stored by Statistik Austria as Hausnummerntext.
948 Otherwise one could misinterpret this number as a house number, what
949 would be definitely wrong.
951 A.2. Sample Addresses
953 In order to clarify the Austrian civic address format, this section
954 provides some exemplary addresses:
956 1234 Musterstadt, Hauptstrasse 1a - 5a Block 1b Haus 2c Stiege 1
957 Postleitzahl: 1234
958 Stadt: Musterstadt
959 Strasse: Hauptstrasse
960 Hausnummer - 1. Teil - Nummer: 1
961 Hausnummer - 1. Teil - Buchstabe: a
962 Hausnummer - Verbindungszeichen Teil 1 -> Bis: -
963 Hausnummer - 2. Teil - Nummer: 5
964 Hausnummer - 2. Teil - Buchstabe: a
965 Hausnummer - Verbindungszeichen Teil Bis -> Teil 2: Block
966 Hausnummer - 2. Teil - Nummer: 1
967 Hausnummer - 2. Teil - Buchstabe: b
968 Hausnummer - Verbindungszeichen Teil 2-> Teil 3: Haus
969 Hausnummer - 3. Teil - Nummer: 2
970 Hausnummer - 3. Teil - Buchstabe: c
971 Gebaeudeunterscheidung: Stiege 1
973 1234 Musterstadt, Musterstrasse 13 Hotel
974 Postleitzahl: 1234
975 Stadt: Musterstadt
976 Strasse: Musterstrasse
977 Hausnummer - 1. Teil - Nummer: 13
978 Gebaeudeunterscheidung: Hotel
980 6020 Innsbruck, Anichstrasse vor 35
981 Postleitzahl: 6020
982 Stadt: Innsbruck
983 Strasse: Anichstrasse
984 Hausnummerntext: vor ("in front of")
985 Hausnummer: 35
987 6173 Oberperfuss, Riedl 3097 (Pfarrkirche)
988 Postleitzahl: 6173
989 Stadt: Oberperfuss
990 Strasse: Riedl
991 Hausnummerntext: 3097
992 (since the estate identifier is 81305 3097 where 81305 is the
993 Katastralgemeindenummer (cadastral municipality) and no house
994 number is assigned)
995 Vulgoname: Pfarrkirche
997 A.3. Address Codes in Austria
999 Statistik Austria registers 4 codes: Adresscode, Adresssubcode,
1000 Objektnummer and the Nutzungseinheitenlaufnummer. The Adresscode (7
1001 digits) is a unique code for an address in Austria. The
1002 Adressregister maps the Adresscode to the civic address. If there is
1003 a building located at an address, there is also an Adresssubcode (3
1004 digits) assigned. Every building at an address has its own
1005 Adresssubcode (assigned sequentially starting with 001, 002, 003 and
1006 so on) in order to distinguish between buildings at the same address.
1007 Furthermore, every building located in Austria has its own unique
1008 code, the Objektnummer (7 digits). This code identifies the building
1009 independent of the Adresscode. That's because addresses are subject
1010 to change while the building may persist. To differ multiple usable
1011 units inside a building, the Nutzungseinheitenlaufnummer (4 digits)
1012 is used. This code is also assigned in sequential order for each
1013 building.
1015 Besides, every address and building is geocoded by Statistik Austria.
1016 Hence, if every PIDF-LO location object would carry data in the
1017 format of Statistik Austria and every PSAP would use the database of
1018 Statistik Austria for mapping, a time saving, definite mapping
1019 without irregularities could be achieved.
1021 Besides these codes, Statistik Austria maintains reference numbers
1022 for communes, localities or streets, to mention just a few.
1024 A.4. Austrian Addresses in PIDF-LO
1026 The following subsections define the mapping procedure.
1028 A.4.1. Country
1030 The country element for Austria must be set to AT, since this is the
1031 ISO 3166-1 [refs.ISO3166-1] alpha-2 code for Austria.
1033 AT
1035 The usage of the ISO 3166 code is demanded by RFC 4119 [RFC4119] and
1036 RFC 5139 [RFC5139] proposes to use upper case characters only.
1038 A.4.2. Country Subdivisions A1-A6
1039 A1 province (Bundesland), Section A.4.2.1
1040 A2 political district name or identifier (politischer Bezirk),
1041 Section A.4.2.2
1042 A3 commune name or identifier (Gemeinde), Section A.4.2.3
1043 A4 village name or identifier (Ortschaft), Section A.4.2.4
1044 A5 cadastral municipality name or identifier (Katastralgemeindename
1045 or Katastralgemeindenummer), Section A.4.2.5
1047 Element A6 must not be used.
1049 Last, there is an exception to mention concerning the Austrian
1050 capital Vienna (Wien). The city of Vienna is equal to its political
1051 district and even the province is called Vienna. Nevertheless,
1052 Vienna is separated in 23 districts within the same political
1053 district. Consequently, an address in Vienna would look like:
1055 AT
1056 Wien
1057 Wien
1058 Wien
1059 Favoriten or 10
1060 Inzersdorf Stadt
1062 The element A4, holding the city division, can hold the name or the
1063 number of the district.
1065 A.4.2.1. A1 Element
1067 As proposed in RFC 5139 [RFC5139], for the PIDF-LO element A1, the
1068 second part of ISO 3166-2 [refs.ISO3166-2] can be used. However, in
1069 Austria it is also common to write out the names of the states.
1070 Table 4 shows the possible values of the A1 element for Austrian
1071 states.
1073 +------------------------+--------------------------------+
1074 | Bundesland | second part of ISO 3166-2 code |
1075 +------------------------+--------------------------------+
1076 | Burgenland | 1 |
1077 | | |
1078 | K=U+00E4rnten | 2 |
1079 | | |
1080 | Nieder=U+00F6sterreich | 3 |
1081 | | |
1082 | Ober=U+00F6sterreich | 4 |
1083 | | |
1084 | Salzburg | 5 |
1085 | | |
1086 | Steiermark | 6 |
1087 | | |
1088 | Tirol | 7 |
1089 | | |
1090 | Vorarlberg | 8 |
1091 | | |
1092 | Wien | 9 |
1093 +------------------------+--------------------------------+
1095 Table 4: A1 element format for Austria (Note: values are shown in
1096 UTF-8, which is recommended to be used for PIDF-LO)
1098 A.4.2.2. A2 Element
1100 Names of the Austrian political districts are available at Statistik
1101 Austria [refs.bezirke]. These names, the unique code for the
1102 political district or both can be used for the A2 element. If the
1103 content of the A2 element is numeric, obviously the code is provieded
1104 (there is no political district in Austria with a number in its
1105 name). In case both, the name and the code are provided, they are
1106 separated by a semicolon, and the name must be listed first.
1108 The district of "Bruck an der Leitha" could be represented by:
1110 Bruck an der Leitha or 307 or
1111 Bruck an der Leitha;307
1113 A.4.2.3. A3 Element
1115 The element A3 holds the Gemeindename (commune name) or the
1116 identifier of the Gemeinde, or both separated by a semicolon (the
1117 name must be listed first). If the content of the A3 element
1118 consists of a number only, it is obvious that just the identifier is
1119 provided. Statistik Austria maintains a table with the Gemeindenamen
1120 and identifiers [refs.gemeinden], which must be used as the content
1121 for the A3 element, no other spelling is allowed.
1123 Sample:
1125 Neusiedl am See
1126 or
1127 10713
1128 or
1129 Neusiedl am See;10713
1131 A.4.2.4. A4 Element
1133 The element A4 holds the Ortschaftsname (village name), the
1134 Ortschaftskennziffer (the identifier), or both separated by a
1135 semicolon (the name must be listed first). If the content of the A4
1136 element consists of a number only, it is obvious that just the
1137 identifier is provided since there are no Ortschaftsnamen in Austria
1138 which contain a number. Statistik Austria maintains a table with the
1139 Ortschaftsnamen and identifiers [refs.ortschaften], which must be
1140 used as the content for the A4 element, no other spelling is allowed.
1142 Sample:
1144 Wilfleinsdorf or 03448 or
1145 Wilfleinsdorf;03448
1147 A.4.2.5. A5 Element
1149 The element A5 holds the Katastralgemeindename (cadastral
1150 municipality), the Katastralgemeindenummer (the identifier), or both
1151 separated by a semicolon (the name must be listed first). If the
1152 content of the A5 element consists of a number only, it is obvious
1153 that just the identifier is provided since there are no
1154 Katastralgemeindenamen in Austria which contain a number.
1156 Sample (Vienna, Fuenfhaus):
1158 Oberbaumgarten or 1208 or
1159 Oberbaumgarten;1208
1161 A.4.3. Road and Street Names
1163 The PIDF-LO element RD holds the complete street name, including the
1164 street suffix. No abbreviations are allowed. No other elements are
1165 needed for streets and must not be used.
1167 A.4.4. House Numbers
1169 Statistik Austria lists 14 data fields related to the house number of
1170 a building plus another 5 fields for distinction of different usable
1171 units inside a building (including the floor, which has a separate
1172 element in PIDF-LO). Unfortunately, PIDF-LO only defines a single
1173 house number element (HNO, numeric part only) and a house number
1174 suffix element (HNS). Therefore, this section defines a mapping in
1175 order to accommodate all data: All house number data is concatenate
1176 into a single HNO element, even though it is expected to hold numeric
1177 part only.
1179 In order to allow automatic procession of the HNO Element, it is
1180 necessary to use a semicolon as delimiter symbol (Austrian house
1181 numbers do not contain semicolons). The house number parts MUST be
1182 provided in the order as they are listed by the Statistik Austria
1183 document [refs.merkmalskatalog]. For user interface representation,
1184 the semicolon separated format can be transformed by replacing
1185 semicolons by spaces (multiple spaces should be combined) and no
1186 space should be present between a numeric part of a house number part
1187 and its related character.
1189 It is not allowed to use the HNS element for Austrian addresses,
1190 since there are addresses that do not have just a single suffix.
1192 The house number "vor 1 - 1A" (consisting of a house number text
1193 "vor", first part of the house number numeric "1", "-" as the link of
1194 the first and Bis part, "1" as house number bis part numeric, "A" as
1195 character of the bis part) would be mapped to:
1197 vor;1;;-;1;A;;;;;;;;;;;
1199 A.4.5. Local Names
1201 NAM: contains the Vulgoname (local name), multiple local names are
1202 separated by a semicolon (if applicable)
1204 LMK: contains the farm name (just one name possible) (if applicable)
1206 LOC: can be used without restriction for additional location
1207 information (as per RFC 4119)
1209 A.4.6. Floors
1211 The floor element may contain numbers or text describing the floor.
1212 The first floor (1) is the floor above the floor at street
1213 level. The floor at street level is EG or 0.
1214 Other floors may have names like mezzanine, for example. The
1215 Statistik Austria data elements Lage and Stockwerk are concatenated
1216 if necessary.
1218 A.4.7. Additional Code Element
1220 The element additional code may be used to hold the codes provided by
1221 Statistik Austria. There is an Adresscode, Adresssubcode,
1222 Objektnummer and a Nutzungseinheitenlaufnummer. These unique codes
1223 identify the location. Actually, these codes alone would be enough,
1224 but requires that the location recipient has access to the database
1225 of Statistik Austria.
1227 If the additional code in a PIDF-LO document is going to hold the
1228 codes from Statistik Austria, the following format should be used:
1230 AdrCD=1234567;AdrsubCD=123;
1231 ObjNr=2333211;NtzLnr=0001
1233 It is not necessary to provide all codes, but there are some
1234 restrictions: The Adresssubcode cannot be used without an Adresscode.
1235 More restrictions are defined by Statistik Austria. By setting the
1236 country element to AT (see Section 4.2.1), indicating an Austrian
1237 address, the Additional Code element is expected to hold codes from
1238 Statistik Austria only. When creating PIDF-LO documents using
1239 address codes by Statistik Austria, the country and ADDCODE elements
1240 are mandatory.
1242 A.4.8. Other Elements
1244 The elements PC and PCN can hold the data form Statistik Austria, the
1245 POBOX can be used if the post assigned a post office box. At least
1246 the PC element should be present.
1248 PC: Postleitzahl (postal code)
1250 PCN: Postleitzahlengebiet (postal community name)
1252 POBOX: Postfach
1254 The elements UNIT, ROOM, SEAT, PLC and BLD may be used without
1255 further restriction.
1257 A.4.9. Elements not to be used
1258 A6
1259 STS
1260 HNS
1261 PRD
1262 POD
1263 RDBR
1264 RDSUBBR
1265 PRM
1266 POM
1268 A.5. Example
1270 This section shows an example mapping of an Austrian address to
1271 PIDF-LO.
1273 Address:
1275 Bundesland: Wien
1276 Politischer Bezirk: Wien
1277 Gemeindename: Wien
1278 9. Bezirk
1279 Strasse: Lazarettgasse
1280 Hausnummer - 1. Teil - Nummer: 13
1281 Hausnummer - 1. Teil - Buchstabe: A
1282 Hausnummer - Verbindungszeichen Teil 1-Bis: -
1283 Hausnummer - Bis-Nummer: 13
1284 Hausnummer - Bis-Buchstabe: C
1285 Postleitzahl: 1090
1287 PIDF-LO:
1289
1290
1294
1295
1296
1297
1298
1299 AT
1300 Wien
1301 Wien
1302 Wien
1303 9
1304 Lazarettgasse
1305 ;13;A;-;13;C;;;;;;;;;;;;
1306 1090
1307
1308
1309
1310 yes
1311 2009-11-10T12:00:00Z
1312
1313
1314
1315 2009-02-09T12:00:00Z
1316
1317
1319 A.6. IANA Registration Record
1320
1321 AT
1322
1324
1325
1326
1328
1329
1330
1331
1333
1334
1336
1337
1338 Alexander Mayrhofer
1339 nic.at GmbH
1340 mailto:alexander.mayrhofer@nic.at
1341 2009-01-09
1342
1343
1344 Karl Heinz Wolf
1345 nic.at GmbH
1346 mailto:karlheinz.wolf@nic.at
1347 2009-01-09
1348
1349
1351 8. References
1353 8.1. Normative References
1355 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
1356 Requirement Levels", BCP 14, RFC 2119, March 1997.
1358 [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
1359 Format", RFC 4119, December 2005.
1361 [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
1362 (DHCPv4 and DHCPv6) Option for Civic Addresses
1363 Configuration Information", RFC 4776, November 2006.
1365 [RFC5139] Thomson, M. and J. Winterbottom, "Revised Civic Location
1366 Format for Presence Information Data Format Location
1367 Object (PIDF-LO)", RFC 5139, February 2008.
1369 [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
1370 IANA Considerations Section in RFCs", BCP 26, RFC 5226,
1371 May 2008.
1373 [RFC4589] Schulzrinne, H. and H. Tschofenig, "Location Types
1374 Registry", RFC 4589, July 2006.
1376 8.2. Informative References
1378 [refs.adrwarten]
1379 Statistik Austria, "Handbuch Adress-GWR-Online Teil A
1380 Theoretisches Handbuch Kapitel 2 Warten von Adressen im
1381 Adress-GWR-Online", Jan 2005.
1383 [refs.merkmalskatalog]
1384 Statistik Austria, "Handbuch Adress-GWR-Online Teil C
1385 Anhang 2 Merkmalskatalog", Sept 2004.
1387 [refs.ISO3166-1]
1388 International Organization for Standardization, "Codes for
1389 the representation of names of countries and their
1390 subdivisions - Part 1: Country codes", ISO Standard 3166-
1391 1:1997, 1997.
1393 [refs.ISO3166-2]
1394 International Organization for Standardization, "Codes for
1395 the representation of names of countries and their
1396 subdivisions - Part 2: Country subdivision code", ISO
1397 Standard 3166-2:1998, 1998.
1399 [refs.bezirke]
1400 Statistik Austria, "Politische Bezirke, Gebietsstand
1401 2008", Feb 2008.
1403 [refs.gemeinden]
1404 Statistik Austria, "Gemeindeliste sortiert nach
1405 Gemeindekennziffer, Gebietsstand 2008", Feb 2008.
1407 [refs.ortschaften]
1408 Statistik Austria, "Gemeinden mit Ortschaften und
1409 Postleitzahlen, Gebietsstand 2008", Feb 2008.
1411 Authors' Addresses
1413 Karl Heinz Wolf
1414 nic.at GmbH
1415 Karlsplatz 1/2/9
1416 Wien A-1010
1417 Austria
1419 Phone: +43 1 5056416 37
1420 Email: karlheinz.wolf@nic.at
1421 URI: http://www.nic.at/
1423 Alexander Mayrhofer
1424 nic.at GmbH
1425 Karlsplatz 1/2/9
1426 Wien A-1010
1427 Austria
1429 Phone: +43 1 5056416 34
1430 Email: alexander.mayrhofer@nic.at
1431 URI: http://www.nic.at/