Geolocation information

ietf-ccamp-wg / ietf-network-inventory

3 stars 5 forks source link

Geolocation information #62

Open italobusi opened 1 year ago

italobusi commented 1 year ago

Consider using the geolocation instead of location for the equipment-room

italobusi commented 1 year ago

2023-01-11 Network Inventory weekly call

Bo suggested also to consider using the geolocation instead of location for the equipment-room

italobusi commented 1 year ago

Should it be alternative or complementary option? IMHO, we should allow reporting only the postal address or only the geolocation or both.

italobusi commented 1 year ago

2023-02-15 Network Inventory weekly call

Jeff: we have a requirement for the SDN controller to provide a GUI to report the GIS (geolocation information system) of the NEs

Agreed to:

rename the "location" attribute as "room-location" and keep it optional to report the equipment-room postal address;
add a geolocation container for the GIS and defined it as optional

Therefore there is complete freedom to report only the postal address or the GIS or both

Two options to analyze: a) use the groupings defined in RFC9179 b) use the geolocation-container grouping defined in RFC8795

To be further discussed

italobusi commented 1 year ago

2023-02-22 Network Inventory weekly call

The information in the RFC9179 grouping is a super-set of the information in RFC8795 grouping

Advantages of RFC8795:

simpler
sufficient to address the current use cases

Advantages of RFC9179:

canonical grouping (no need to justify why using this grouping)
module intended only for import (RFC8795 may not be always required to be implemented but would be need to be imported in order to use the grouping)

Using the grouping defined in RFC9179 seems the safer approach for this draft

[ ] @YuChaode update the YANG model to (1) rename the "location" attribute as "room-location" (optional to report the equipment-room postal address) and (2) add a new container with the geolocation position using the grouping defined in RFC9179

oscargdd commented 1 year ago

Some network elements have connection to GPS information. I would include together with the container a leaf indicating the source, to distinguish between coordinates information provided by the node itself or information that has been externally provided to the controller. Geolocation container could be augmented. For fixed nodes the g is not going to change much, but if we include in the inventory nodes that can move, I would also add a timestamp to indicate when was the last geolocation was provided (if we consider only the fixed... forget the last one)