Skip to main content

Modeling the Digital Map based on RFC 8345: Sharing Experience and Perspectives
draft-havel-nmop-digital-map-02

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Olga Havel , Benoît Claise , Oscar Gonzalez de Dios , Ahmed Elhassany , Thomas Graf
Last updated 2025-04-24 (Latest revision 2024-10-21)
Replaces draft-havel-opsawg-digital-map
Replaced by draft-havel-nmop-simap-yang
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-simap-yang
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. 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. For definition of Digital Map concepts, requirements and use cases please refer to the "Digital Map: Concept, Requirements, and Use Cases" document. Discussion Venues This note is to be removed before publishing as an RFC. Source for this draft and an issue tracker can be found at https://github.com/OlgaHuawei.

Authors

Olga Havel
Benoît Claise
Oscar Gonzalez de Dios
Ahmed Elhassany
Thomas Graf

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)