Modeling the Digital Map based on RFC 8345: Sharing Experience and Perspectives
draft-havel-opsawg-digital-map-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Olga Havel , Benoît Claise , Oscar Gonzalez de Dios , Ahmed Elhassany , Thomas Graf , Mohamed Boucadair | ||
| Last updated | 2023-10-23 | ||
| Replaced by | draft-havel-nmop-digital-map | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-havel-nmop-digital-map | |
| 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 shares experience in modelling digital map based on the IETF RFC 8345 topology YANG modules and some of its augmentations. First, the concept of Digital Map is defined and its connection to the Digital Twin is explained. Next to Digital Map requirements and use cases, the document identifies a set of open issues encountered during the modelling phases, the missing features in RFC 8345, and some perspectives on how to address them.
Authors
Olga Havel
Benoît Claise
Oscar Gonzalez de Dios
Ahmed Elhassany
Thomas Graf
Mohamed Boucadair
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)