OSPF Extensions for Advertising/Signaling Geo Location Information
draft-acee-ospf-geo-location-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
Expired & archived
|
|
|---|---|---|---|
| Authors | Acee Lindem , Naiming Shen , Enke Chen | ||
| Last updated | 2016-08-29 (Latest revision 2016-02-26) | ||
| RFC stream | (None) | ||
| Formats | |||
| Additional resources | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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 (P2P)) 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.
Authors
Acee Lindem
Naiming Shen
Enke Chen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)