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

"zhouyujing (A)" <zhouyujing3@huawei.com> Tue, 16 November 2021 12:10 UTC

Return-Path: <zhouyujing3@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4695C3A0860 for <anima@ietfa.amsl.com>; Tue, 16 Nov 2021 04:10:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VhApzB2-GBKV for <anima@ietfa.amsl.com>; Tue, 16 Nov 2021 04:10:09 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A52C3A085E for <anima@ietf.org>; Tue, 16 Nov 2021 04:10:09 -0800 (PST)
Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4HtlHX18Nmz67mB8; Tue, 16 Nov 2021 20:10:00 +0800 (CST)
Received: from dggpemm500019.china.huawei.com (7.185.36.180) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.20; Tue, 16 Nov 2021 13:10:07 +0100
Received: from dggpemm500018.china.huawei.com (7.185.36.111) by dggpemm500019.china.huawei.com (7.185.36.180) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.20; Tue, 16 Nov 2021 20:10:05 +0800
Received: from dggpemm500018.china.huawei.com ([7.185.36.111]) by dggpemm500018.china.huawei.com ([7.185.36.111]) with mapi id 15.01.2308.020; Tue, 16 Nov 2021 20:10:05 +0800
From: "zhouyujing (A)" <zhouyujing3@huawei.com>
To: Toerless Eckert <tte@cs.fau.de>, "anima@ietf.org" <anima@ietf.org>
Thread-Topic: [Anima] Call for adoption: draft-dang-anima-network-service-auto-deployment
Thread-Index: AQHX2tN2z7n7OVWXakaFIElq4vyTp6wGD79Q
Date: Tue, 16 Nov 2021 12:10:05 +0000
Message-ID: <306f5df3cacb478c87cedbf7a4197117@huawei.com>
References: <YZMUt21i6qVWNJka@faui48e.informatik.uni-erlangen.de> <YZMWHusYVImm/liv@faui48e.informatik.uni-erlangen.de>
In-Reply-To: <YZMWHusYVImm/liv@faui48e.informatik.uni-erlangen.de>
Accept-Language: zh-CN, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.166.240]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/OwEEE-ktf8jo54b_DPzKmp-KprY>
Subject: Re: [Anima] Call for adoption: draft-dang-anima-network-service-auto-deployment
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Nov 2021 12:10:14 -0000

Hi, Toerless

Thanks for your opinion, We are planning to add the clarification text to the next version.

1) We will update more cases to make the draft more clearly. And topology ASCII pictures are a good idea to express the case.

2) The draft will consider more specific cases. We will add more detail about the discovery, negotiation, and synchronization.

3) About "detnet-like": We think that the draft will help to improve QoS service for some cases, but it is one result of ASA ensuring the resource in the network. The draft has a wider range of use cases. It defines how to negotiate and distribute resource in the network. 

Best regards
Yujing

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

And chiming n with my own opinion, repeating what i said on the microphone at IETF112:

I would really like to see a reference example, for example in a new section:
   - as simple as possible, but still exploiting all aspects of the draft
     and showing the value of the draft.

   - i always love a good topology ASCII picture to go along with an example.

   - specific enough so that it could be implemented and verified.

   - seems like this could be some kind of "detnet-like"?! improved
     QoS service for some traffic class (how is the traffic class specified)..
     etc.pp: aka: answering all the question to round up such an
     example is the easiest way to determine if there are just minor
     or any mayor gaps in the proposed approach.

Thanks!
    Toerless

On Tue, Nov 16, 2021 at 03:17:27AM +0100, Toerless Eckert wrote:
> 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