IETF Logo Mail Archive

Re: [Anima] Latest draft charter text of ANIMA

Sheng Jiang <jiangsheng@huawei.com> Tue, 19 March 2019 01:05 UTC

Return-Path: <jiangsheng@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 7643D130E69 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:05:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 p6aj9xhKJgJ8 for <anima@ietfa.amsl.com>; Mon, 18 Mar 2019 18:05:43 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7512124B0C for <anima@ietf.org>; Mon, 18 Mar 2019 18:05:42 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id E3FBCE4C0E075E1CB35C for <anima@ietf.org>; Tue, 19 Mar 2019 01:05:40 +0000 (GMT)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 19 Mar 2019 01:05:40 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0415.000; Tue, 19 Mar 2019 09:05:32 +0800
From: Sheng Jiang <jiangsheng@huawei.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "anima@ietf.org" <anima@ietf.org>, Ignas Bagdonas <ibagdona@gmail.com>
Thread-Topic: [Anima] Latest draft charter text of ANIMA
Thread-Index: AdTdczFSD7JWU1MpTVyITKi7F85Ejf//6sYA//8ArYA=
Date: Tue, 19 Mar 2019 01:05:32 +0000
Message-ID: <5D36713D8A4E7348A7E10DF7437A4B929038D8E5@NKGEML515-MBX.china.huawei.com>
References: <5D36713D8A4E7348A7E10DF7437A4B929038D5EC@NKGEML515-MBX.china.huawei.com> <21884.1552928234@localhost>
In-Reply-To: <21884.1552928234@localhost>
Accept-Language: en-GB, zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.185.119]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/uavOJrB9n4_8RXvzTNr2Dq697Lk>
Subject: Re: [Anima] Latest draft charter text of ANIMA
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, 19 Mar 2019 01:05:44 -0000

In lines.

Sheng

> -----Original Message-----
> From: Anima [mailto:anima-bounces@ietf.org] On Behalf Of Michael Richardson
>     > ANIMA will start to define AFs to enable service automation in
>     > networks; it will also work on generic aspects of ASA including design
>     > guidelines and
>     > lifecycle management including coordination and dependency
> management.
> 
> I think that this is a good set of goals, and I'd like to see AFs built, but I'm not
> seeing them.  

This is in the scope. Whether the WG participants come up with good AFs, we will see. Actually, we saw some AFs came together with use cases. What we are not sure is the balance between specific AFs for narrow usage or generic AFs that can be reused in many scenarios.

> What I'd ideally like to see is:
> 
> 1) some place for enrollment work -- including BRSKI.

It is already in the proposed work items: BRSKI relevant works, including proxies, "enrollment", adaptions over various network protocols, variations of voucher formats, and etc.

> 2) a way to finish and revise the ANI work.   This may need rather some
>    kind of lightweight industrial forum to push interoperability testing
>    leading to Updates to documents presently in the queue or already
>    published.

We believe this is covered. Maybe the word "Works extending ANI" needs be revised? Any suggestion?

> 3) a way to get AFs brought out.  Maybe an IRTF RG, maybe something else.

Generic ASAs that can be reused in multiple scenarios are already in the scope. We are not sure about the dedicated ASAs. They may come up with specific use cases. We need to discuss them case by case when we see them. How to arouse people to work on AFs/ASAs is another topic. It is out of the discussion of WG charter, I believe.

Sheng

> While not properly the business of the IETF, I don't think that (3) can get much
> traction until there is a way to bring up a (virtual) ANI on a bunch of VMs or cheap
> equipment in research labs.
> Having ANI is like Web 1.0... the real value doesn't come until 2.0.
> 
> So one thought is, provided that (1) can be satisfied some other way, is to
> suspend (not shutdown) ANIMA rather than recharter it.  I recognize that such
> an action might have negative consequences to how various people are able to
> participate.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works  -=
> IPv6 IoT consulting =-
> 
>

v2.23.0 | Report a Bug | By Email