<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.havel-nmop-digital-map" target="https://datatracker.ietf.org/doc/html/draft-havel-nmop-digital-map-01">
   <front>
      <title>Modeling the Digital Map based on RFC 8345: Sharing Experience and Perspectives</title>
      <author initials="O." surname="Havel" fullname="Olga Havel">
         <organization>Huawei</organization>
      </author>
      <author initials="B." surname="Claise" fullname="Benoît Claise">
         <organization>Huawei</organization>
      </author>
      <author initials="O. G." surname="de Dios" fullname="Oscar Gonzalez de Dios">
         <organization>Telefonica</organization>
      </author>
      <author initials="A." surname="Elhassany" fullname="Ahmed Elhassany">
         <organization>Swisscom</organization>
      </author>
      <author initials="T." surname="Graf" fullname="Thomas Graf">
         <organization>Swisscom</organization>
      </author>
      <date month="July" day="5" year="2024" />
      <abstract>
	 <t>   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 &quot;Digital
   Map: Concept, Requirements, and Use Cases&quot; 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.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-havel-nmop-digital-map-01" />
   
</reference>
