%% You should probably cite draft-acee-ospf-geo-location-05 instead of this revision. @techreport{acee-ospf-geo-location-00, number = {draft-acee-ospf-geo-location-00}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-acee-ospf-geo-location/00/}, author = {Acee Lindem and Naiming Shen and Enke Chen}, title = {{OSPF Extensions for Advertising/Signaling Geo Location Information}}, pagetotal = 6, year = 2016, month = feb, day = 12, abstract = {This document specifies an OSPF Link-Local-Signaling (LLS) TLV to signal the current Geo Coordinates of the OSPF router. For Point-to- Point (P2)) and Point-to-Multi-Point (P2MP) networks, the Geo Coordinates can be used to dynamically computing the cost to neighbors. This is useful both from the standpoint of auto- configuration and situations where the OSPF routers are moving. The Geo Coordinates are also useful for other applications such as Traffic Engineering (TE) and network management and can be advertised in the OSPF Router Information (RI) LSA.}, }