Dynamic Host Configuration Protocol DHCPv4 and DHCPv6 Option for Civic Addresses Configuration Infor

1
Dynamic Host Configuration Protocol (DHCPv4 and
DHCPv6) Option for Civic Addresses Configuration
Information draft-ietf-geopriv-dhcp-civil-09

• Henning Schulzrinne
• Columbia University

2
Overview

• Complementary to RFC 3825 (geo)
• Meant for network operator to convey civil
  location to device
• country, administrative units, street, floor
• use cases emergency services, device management
• Likely applications
• enterprise LAN
• hotel, airport hot spots
• home networks
• Does not provide location to third parties, just
  own location to target
• Attempts to be country-neutral
• just assumes a hierarchical division of country
• extensible if more descriptors are needed later
• Support both civic (street) and postal addresses

3
DHCPv4 Format
GEOCONF_CIVIC
length
what (server, NE, client)
country code
civic address elements

• what DHCP, closest network element or client
• country code e.g., US, DE

4
Element format
CAtype
CAlength
CAvalue
CAtype type of data CAlength length (bytes) of
CAvalue
5
Elements Administrative Subdivisions
6
Languages and scripts

• DHCP option uses UTF8
• Some elements may have multiple variations
• scripts (e.g., Japan) UTF8 does not necessarily
  distinguish (Han unification)
• languages (Köln, Cologne)
• Others may only have one rendering
• street names
• uses CAtypes 0 (language) and 128 (script) to
  mark sets of CAtypes
• language e.g., de-CH German as used in
  Switzerland
• script e.g., Latn

7
Street Names
8
More location elements
RED draft-ietf-geopriv-revised-civic-lo
9
Branching streets
Carol Ln
West Alice Pde.
Section 1
Section 2
Section 3
Carol Ln
Alley 2
10
Conclusion

• Attempt at global civic address format
• including multi-script and multi-language
  addresses
• extensible (within DHCP size constraints)
• Supports both postal and civic addresses
• Being mapped to XML (PIDF) format