Considerations for Civic Addresses in PIDF-LO draft-wolf-civicaddresses-austria-01 IETF 71, Mar 2008, Philadelphia, PA, USA Karl Heinz Wolf Alexander Mayrhofer.

Slides:



Advertisements
Similar presentations
IETF 71 Philadelphia - ENUM IANA Registration of Enumservices: Guide, Template and IANA Considerations draft-ietf-enum-enumservices-guide-08 B. Hoeneisen.
Advertisements

IETF 71 SIPPING WG meeting draft-ietf-sipping-pai-update-00.
ServiceListBoundary (LoST Extension) draft-wolf-ecrit-lost-servicelistboundary-01 IETF 75, Aug 2009, Stockholm, Sweden Author: Karl Heinz Wolf Presentation:
Update about the “SHOULDs Analysing Project” in RIPE Policy Documents “Should” we use the RFC 2119 Defined Language in RIPE Policy Documents? Jan Žorž,
Things we need to standardise: a recap/review since IETF89 dnssd WG, IETF90, Toronto, 24 th July 2014.
NAT64 Operational Experiences draft-chen-v6ops-nat64-experience-03 IETF 84- Vancouver, Aug 2012 Gang Chen China Mobile Zhen Cao China Mobile Cameron Byrne.
Update to: The OSPF Opaque LSA Option draft-berger-ospf-rfc2370bis Lou Berger Igor Bryskin Alex Zinin
Identity, Spheres and Privacy Rules Henning Schulzrinne (with Hannes Tschofenig and Richard Barnes) Workshop on Identity, Information and Context October.
MPLS Performance Measurement UDP Return Path draft-bryant-mpls-oam-udp-return-02 {stbryant, msiva,
IPv4-Embedded IPv6 Multicast Address draft-ietf-mboned-64-multicast-address-format IETF 84 Vancouver 1.
Section 13.1 Add a hit counter to a Web page Identify the limitations of hit counters Describe the information gathered by tracking systems Create a guest.
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Emergency calls related work done in IETF Gabor Bajko May 22, 2006.
IPv6 RADIUS attributes for IPv6 access networks draft-lourdelet-radext-ipv6-access-01 Glen Zorn, Benoit Lourdelet Wojciech Dec, Behcet Sarikaya Radext/dhc.
Direction of PIDF-LO Profile James Winterbottom. Problems PIDF-LO profile has suffered from feature creep Base level GML is designed to define complex.
3 rd Annual European DDI Users Group Meeting, 5-6 December 2011 The Ongoing Work for a Technical Vocabulary of DDI and SDMX Terms Marco Pellegrino Eurostat.
Civic Address Considerations for Austria draft-wolf-civicaddresses-austria-00 IETF 70, Dec 2007, Vancouver, BC, Canada Karl Heinz Wolf Alexander Mayrhofer.
Dean Cheng Jouni Korhonen Mehamed Boucadair
Android - Project Green basket Android Application * Let's you do your grocery shopping location based. * Let's you decide to go to the closest grocery.
Status and Development of VoIP based emergency calls Alexander Mayrhofer, nic.at GmbH The 1st European Security and Safety Summit Brussels, June 2007.
Experimental Research Methods in Language Learning Chapter 16 Experimental Research Proposals.
FGDC Address Standard Update: What's Next? Address Standard Working Group Martha Wells, GISP Carl Anderson, GISP Sara Yurman, GISP Ed Wells, GISP Hilary.
XCON WG IETF-73 Meeting Instant Messaging Sessions with a Centralized Conferencing (XCON) System draft-boulton-xcon-session-chat-02 Authors: Chris Boulton.
IETF63 - enum WG1 ENUM validation architecture & friends Alex Mayrhofer enum.at / 3.4.e164.arpa Bernie Höneisen SWITCH.
Revised Civic Format James Winterbottom. Motivation Investigations and work done on civic representations has expanded somewhat since the initial version.
IETF GEOPRIV Status Richard L. Barnes BBN Technologies GEOPRIV Secretary Emergency Services Workshop October 2008.
Slide title In CAPITALS 50 pt Slide subtitle 32 pt RTSP 2.0 TLS handling Magnus Westerlund draft-ietf-mmusic-rfc2326bis-12.
ECRIT Virtual Interim Meeting 3rd June 2009, 1PM EDT (New York) Marc Linsner Hannes Tschofenig.
BLISS Problem Statement Jonathan Rosenberg Cisco.
RFC 4477 DHCP: Dual-Stack Issues Speaker: Ching-Chen Chang Date:
March 2006IETF 65, Dallas1 Diameter NASreq (RFC 4005) and RADIUS Compatibility David Mitton RSA Security Inc. draft-mitton-diameter-radius-vsas-01.txt.
draft-mayrhofer-enum-xmpp1 XMPP Enumservice registration draft-mayrhofer-enum-xmpp-00 Alexander Mayrhofer, enum.at
An end-to-end usage of the IPv6 flow label
RTCWEB Considerations for NATs, Firewalls and HTTP proxies draft-hutton-rtcweb-nat-firewall- considerations A. Hutton, T. Stach, J. Uberti.
What do we need to standardise? Open discussion Led by Dave Thaler dnssd WG, IETF89, London, 3 rd March 2014.
IEEE Emergency Services DCN: Title: 802 Location Report Date Submitted: May 06, 2011 Presented at IEEE
RADEXT WG RADIUS Attribute Guidelines Greg Weber March 21 st, 2006 IETF-65, Dallas v1 draft-weber-radius-attr-guidelines-02.txt draft-wolff-radext-ext-attribute-00.txt.
Proposed Changes to PLS FY 2016 Data Elements SDC Meeting December 09, 2015.
A Framework for Session Initiation Protocol User Agent Profile Delivery (draft-ietf-sipping-config-framework-11) SIPPING – IETF 68 Mar 19, 2007 Sumanth.
Submission doc.: IEEE 14-22/0098r0 July 2014 Slide 1 P PAR and CSD Comment Resolution Date: Authors:
Requirements for Generic Rights Trading Ko Fujimura 49th IETF Meeting – San Diego draft-ietf-trade-drt-requirements-01.txt.
IETF 77 RADEXT WG RADIUS Accounting extensions for IPv6 draft-maglione-radext-ipv6-acct-extensions-01 R. Maglione – Telecom Italia B. Varga - Magyar Telekom.
Requirements and Selection Process for RADIUS Crypto-Agility December 5, 2007 David B. Nelson IETF 70 Vancouver, BC.
Subscribing to datastore push updates draft-netmod-clemm-datastore-push-00.txt Alexander Clemm, Alberto Gonzalez Prieto, Eric Voit.
1 Extend FEC BB to RTP streaming? Michael Luby Digital Fountain.
Slide #1 Nov 6 -11, 2005SIP WG IETF64 Feature Tags with SIP REFER draft-ietf-sip-refer-feature-param-00 Orit
Central Massachusetts Regional Library System Libraries and Lean Thinking An Overview / Workshop May 11, 2009.
1 © NOKIA Presentation_Name.PPT / DD-MM-YYYY / Initials Company Confidential XCAP Usage for Publishing Presence Information draft-isomaki-simple-xcap-publish-usage-00.
Civic Address Extensibility draft-ietf-geopriv-prefix draft-george-geopriv-lamp-post draft-winterbottom-geopriv-local-civic.
Slide 1 August 2005, Paris, FranceIETF DNSEXT 2929bis etc. Donald E. Eastlake 3 rd
RFC 3775 bis Julien Laganier, Marcelo Bagnulo MEXT WG chairs IETF-71 Philadelphia, PA, USA March 2008.
Trust Anchor Update Requirements for DNSSEC Russ Mundy for the editors Steve Crocker, Howard Eland, Russ Mundy.
Internet Protocol- based In-Vehicle Emergency Call ECRIT WG draft-rosen-ecrit-ecall-08.txt IETF 86 March, 2013.
1 PSAMP WGIETF, November 2003PSAMP WG PSAMP Framework Document draft-ietf-psamp-framework-04.txt Duffield, Greenberg, Grossglauser, Rexford: AT&T Chiou:
SIEVE Mail Filtering WG IETF 70, Vancouver WG Chairs: Cyrus Daboo, Alexey Melnikov Mailing List: Jabber:
Abstract  An abstract is a concise summary of a larger project (a thesis, research report, performance, service project, etc.) that concisely describes.
Lightweight 4over6: An Extension to DS-Lite Architecture draft-cui-softwire-b4-translated-ds-lite-09 Y. Cui, Q. Sun, M. Boucadair, T. Tsou, Y. Lee and.
CJK IMT 28 Xi’an, China 2-3 Jun CJK IMT 28, Xi’an, China 1/4 CJK-IMT Possible Contribution to 11th Meeting of WP5D ~ Related to Updating of.
FGDC Address Data Standard Scope, Status, and Structure  United States Street, Landmark, and Postal Address Data Standard"  Scope: Street, landmark,
PPSP Tracker Protocol – Extended Protocol draft-huang-ppsp-extended-tracker-protocol- 07 PPSP WG IETF 91 Hawaii Rachel Huang, Rui Cruz, Mário Nunes, João.
Observational Study Working Group
RADEXT WG RADIUS Attribute Guidelines
Diameter NASreq (RFC 4005) and RADIUS Compatibility
AAA and AAAS URI Miguel A. Garcia draft-garcia-dime-aaa-uri-00.txt
Markus Isomäki Eva Leppänen
Proposed Data Standards - Main Points
RADEXT WG RADIUS Attribute Guidelines draft-weber-radius-attr-guidelines-01.txt Greg Weber November 8th, 2005 v1 IETF-64, Vancouver.
Robert Moskowitz, Verizon
REPUTE Document Status
IETF-104 (Prague) DHC WG Next steps
M. Boucadair, J. Touch, P. Levis and R. Penno
Presentation transcript:

Considerations for Civic Addresses in PIDF-LO draft-wolf-civicaddresses-austria-01 IETF 71, Mar 2008, Philadelphia, PA, USA Karl Heinz Wolf Alexander Mayrhofer nic.at GmbH

Motivation RFC 4776 asks for such documents: Mappings and considerations from additional countries may be informally gathered from time to time in independent documents published by the IETF. These should be titled "Civic Address Considerations for [Country]" and should contain similar information to the examples given here. Interopability: PSAPs need consistent mappings to be able to handle location information –Never confuse a PSAP agent! Location publishers: local PIDF-LO usage guidelines help avoiding misinterpretations –Consistent (national) mapping scheme required

What‘s new? IETF 70 –One document per country would be too much –However, a general guideline would be good –Keep Austria as an example Adopted as discussed in Vancouver –(file name unchanged yet) Contents: –Requirements for address mappings –A generic guideline for PIDF-LO element usage –An example mapping for Austrian civic addresses

Specifying PIDF-LO Usage Identify data source(s) –Official building register? Postal register? Line information database? … If possible, use elements as specified in RFC 4119 / If this does not seem possible: –Use an unused PIDF-LO element –Concatenate several data fields into one element –Avoid requesting new CAtypes Define the set of required and optional elements for use with this mapping. List elements not to be used.

Austria Example Most data fields fit into an existing PIDF-LO element, except the 20 “house number” fields Proposed solution to the house number problem: –Concatenate all 20 fields in the order provided by “Statistik Austria” –Delimiter: space (if original fields don’t need to be recovered) or semicolon (if original fields are needed) –House number “vor 1 - 1A”: vor;1;;- ;1;A;;;;;;;;;;; or vor 1 – 1A

Next Steps All suggestions from Vancouver addressed? How to proceed with this document? –In WG scope? (or “sneaked in” via 4776) –make it WG item as discussed in Vancouver? Questions?