Re: [Anima] Call for adoption: draft-dang-anima-network-service-auto-deployment

Hi, Med

Thanks for your opinions, we think these will help us a lot. Here are some comments that I briefly explain. And I will prepare another email with more in-depth explanation. We may discuss those later then.

[BMI1]：As for resource requirements, we think that we should use "queue and priority" replace "latency, and jitter". Like you say it is not resource requirement. But in here we want to express that the draft can negotiate and distribute many kinds of resource.
[BMI4]: I agree with you that the service head-ends may not be in the network. It is an end-to-end case and we discuss this in the ANIMA meeting, IETF 112. I will expand this in the next version and I think we can talk more detail about this question.
[BMI19]: We think that the negotiation step is the interaction of two nodes, so the a ResourceManager ASA choose one node. But why the first one is needed for discussion, choosing the first node is just our suggestion.
[BMI20]: Yes, it is the same meaning.
[BMI21]: We think different types of resource can be requested together. The ResourceManager GRASP Objective support this. 

As you say there are something the draft defined not clearly and need to be expanded. We hope we can have a deep discussion about this points. We are glad that you can help us expand them together.

We will improve some writing and highlight display problems in the next version, and thank you again for your careful reading.

Best regards
Yujing

-----Original Message-----
From: mohamed.boucadair@orange.com <mohamed.boucadair@orange.com> 
Sent: 2021年11月16日 15:57
To: Toerless Eckert <tte@cs.fau.de>; anima@ietf.org
Subject: Re: [Anima] Call for adoption: draft-dang-anima-network-service-auto-deployment

Hi all, 

I do see a value in documents that exercise how GRASP can be used in specific contexts. The authors can follow the structure in RFC8992 to better describe the target case, the theory of operation, etc. 

FWIW, some quick comments to the authors can be seen at:

* pdf: https://raw.githubusercontent.com/boucadair/IETF-Drafts-Reviews/master/draft-dang-anima-network-service-auto-deployment-01-rev%20Med.pdf
* doc: https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-dang-anima-network-service-auto-deployment-01-rev%20Med.doc

Cheers,
Med

> -----Message d'origine-----
> De : Anima <anima-bounces@ietf.org> De la part de Toerless Eckert 
> Envoyé : mardi 16 novembre 2021 03:17 À : anima@ietf.org Objet : 
> [Anima] Call for adoption: draft-dang-anima-network-service-auto-
> deployment
> 
> The authors of draft-dang-anima-network-service-auto-deployment have 
> asked ANIMA WG for adoption of the work.
> 
> Given how we are probably all still exhausted from IETF112, let me 
> give this one a bit more time:
> 
> This emails starts a three week call for adoption for 
> draft-dang-anima- network-service-auto-deployment The adoption call 
> does end when December 6 has passed for everyone on planet earth.
> 
> draft-dang-anima-network-service-auto-deployment-01
> 
> Abstract
> 
>    This document specifies an autonomic mechanism for resource-based
>    network services deployment through the Autonomic Control Plane (ACP)
>    in an Autonomic Network.  This mechanism uses the GRASP in [RFC8990]
>    to exchange the information among the autonomic nodes so that the
>    resource among the service path can be coordinated.
> 
> So, please check out the document and chime in!
> 
> Toerless, for the ANIMA chairs.
> 
> _______________________________________________
> Anima mailing list
> Anima@ietf.org
> https://www.ietf.org/mailman/listinfo/anima

_________________________________________________________________________________________________________________________

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.