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

Draft History First presented at IETF 95 in Buenos Aires Common encoding agreed upon across IS-IS, OSPF, BGP, and LISP Privacy Discussions

Geo Location Use Cases P2P, P2MP, and Hybrid automatic link cost 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

OSPF Advertisement OSPF Router-Information Opaque LSA used for both link and wider advertisement No longer sent in OSPF Hello Link Local Signaling (LLS) Link-Scoped OSPF RI LSA used for metric computation use case. Area-Scoped/AS-Scoped OSPF RI LSA used for other applications (e.g., OAM applications)

Geo Location TLV Unified Encoding (1/2)

Geo Location TLV Unified Encoding (2/2) 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. RFC 7459 strongly suggested by Alia as definitive source for geo-privacy. Discussion started with Alissa Cooper and Martin Thomson. May modify encoding based on Martin’s review

Next Steps Complete Privacy Discussion Request WG Adoption