IS-IS Geo Location IETF 97, Seoul Naiming Shen, Cisco Enke Chen, Cisco Acee Lindem, Cisco

Draft History First presented at IETF 96 in Berlin Common encoding agreed upon across IS-IS, OSPF, BGP, and LISP Published 02 version in October 2016 Privacy Discussions

Geo Location Use Cases P2P, P2MP, and Hybrid automatic link cost Overlay with tunnel without underlay distance information Find-My-Router Apps Proximity services in content sharing and SFC Network topology maps Dynamic DNS loadsharing Traffic matrix of location pairs Same ‘subnet’ over WAN and ECMP Future routing/service/mgmt apps Static provisioning, utilize additional information or GPS capable device

Geo Advertisement Optionally in IS-IS LSP for router location Optionally advertise in IIH PDU Notify the neighbor of our location Can be used to calculate P2P, P2MP and hybrid (e.g. RFC 6845) cost

Geo Location TLV Unified Encoding Previous Encoding Fields Flags: U, N, E, A, M Location Uncertainty in centimeters Latitude and Longitude in milliseconds Altitude is a signed integer specified in centimeters or meters New Fields Radius and R, K flags

Privacy Discussion Current encoding has uncertainty in centimeters – Up to 650 meters of uncertainty. We can make to unit to be in meters for the range up to 65KM RFC 7459 strongly suggested by Alia as definitive source for geo-privacy. Discussion started with Alissa Cooper and Martin Thomson.

Next Steps Complete Privacy Discussion Request WG Adoption