[Teas] Re: Call for adoption: draft-havel-nmop-digital-map-concept (Ends 23/09/2024)

[[e-mail]]

Hi Olga, 

Looks good to me. 

Please make sure to reference #9 in #1 before closing it. Thanks.

Cheers,
Med

> -----Message d'origine-----
> De : Olga Havel <olga.havel=[e-mail]>
> Envoyé : vendredi 18 octobre 2024 19:19
> À : Italo Busi <Italo.Busi=[e-mail]>; BOUCADAIR
> Mohamed INNOV/NET <[e-mail]>; [e-mail]
> Cc : TEAS WG ([e-mail]) <[e-mail]>; nmop-
> [e-mail]; [e-mail]
> Objet : RE: Call for adoption: draft-havel-nmop-digital-map-
> concept (Ends 23/09/2024)
> 
> 
> Hi Italo,
> 
> Med opened an issue 1 on github for this feedback
> (Scope/Goal/Intended Use (from Italo) * Issue #1 * ietf-wg-
> nmop/draft-ietf-nmop-digital-map-concept
> (github.com)<https://eur03.safelinks.protection.outlook.com/?url=h
> ttps%3A%2F%2Fgithub.com%2Fietf-wg-nmop%2Fdraft-ietf-nmop-digital-
> map-
> concept%2Fissues%2F1&data=05%7C02%7Cmohamed.boucadair%40orange.com
> %7Cc97c71da9f944e61be8f08dcef98fff2%7C90c7a20af34b40bfbc48b9253b6f
> 5d20%7C0%7C0%7C638648687623453077%7CUnknown%7CTWFpbGZsb3d8eyJWIjoi
> MC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%
> 7C%7C&sdata=qOEb%2FGUKzVJZT6VRuEmWLoNBz2Yv8hhqAabt3nyOhaA%3D&reser
> ved=0>
> I plan to create a new issue for lifecycle/use case clarification
> (Issue 9)  and close Issue 1 as I think that last 2 points have
> been addressed.
> 
> Med, Italo, is that OK with you?
> 
> Best Regards,
> Olga
> 
> From: Italo Busi <Italo.Busi=[e-mail]>
> Sent: Sunday, September 22, 2024 5:04 PM
> To: [e-mail]; [e-mail]
> Cc: TEAS WG ([e-mail]) <[e-mail]>; [e-mail];
> [e-mail]
> Subject: RE: Call for adoption: draft-havel-nmop-digital-map-
> concept (Ends 23/09/2024)
> 
> Hi Med, WG(s),
> 
> I think the document needs some important updates, however I do
> support the adoption of the draft as a WG document
> 
> The work is in the scope of NMOP WG (as explicitly stated in the
> charter) and I agree that NMOP WG needs to develop a common view
> of the definitions, use cases and requirements for digital map,
> which is what this I-D is aiming for
> 
> I wished to provide more constructive and detailed comments to the
> draft, but I am running out of time for the adoption call so I am
> starting to share an high-level overview my major comments. At
> this moment in time, it is not fully clear to me whether the
> digital map is intended to be:
> 
> 
>   *   aimed at supporting the full lifecycle of network
> management/control (as it seems to me being stated in the draft)
> or just the network visualization application (as I have
> understood from previous discussions and PoCs)
> [OH] I created Issue 9 for this. The Digital Map API is used in
> multiple use cases and can support all the functions in the
> lifecycle. The analysis and examples of when write interface is
> needed will be done in the future versions when we add more
> content into how use cases are using Digital Map API
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.