Re: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09

Tianran Zhou <zhoutianran@huawei.com> Tue, 17 December 2019 13:26 UTC

Return-Path: <zhoutianran@huawei.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D65AD120274; Tue, 17 Dec 2019 05:26:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 t1tLuqtD0Dxr; Tue, 17 Dec 2019 05:25:57 -0800 (PST)
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 DF21D1201E5; Tue, 17 Dec 2019 05:25:56 -0800 (PST)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 5DE34697EE94CB88A46A; Tue, 17 Dec 2019 13:25:54 +0000 (GMT)
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 17 Dec 2019 13:25:53 +0000
Received: from lhreml702-chm.china.huawei.com (10.201.108.51) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Tue, 17 Dec 2019 13:25:53 +0000
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml702-chm.china.huawei.com (10.201.108.51) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Tue, 17 Dec 2019 13:25:53 +0000
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0439.000; Tue, 17 Dec 2019 21:25:48 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Benoit Claise <bclaise@cisco.com>, opsawg <opsawg@ietf.org>, "draft-song-opsawg-ifit-framework.authors" <draft-song-opsawg-ifit-framework.authors@ietf.org>
CC: opsawg-chairs <opsawg-chairs@ietf.org>
Thread-Topic: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09
Thread-Index: AdWuTgs1peGnP0a/SLi3HG/cQ1ovRgGSEt+AABHJ6BA=
Date: Tue, 17 Dec 2019 13:25:47 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BF1472CD@NKGEML515-MBX.china.huawei.com>
References: <BBA82579FD347748BEADC4C445EA0F21BF135AC8@NKGEML515-MBX.china.huawei.com>, <67f5447c-37a0-62e4-9dd0-0ae380178dc3@cisco.com>
In-Reply-To: <67f5447c-37a0-62e4-9dd0-0ae380178dc3@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_BBA82579FD347748BEADC4C445EA0F21BF1472CDNKGEML515MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/J3NNyiLugxlJWz1OxpUFwQsUQXQ>
Subject: Re: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 13:26:01 -0000

Hi Benoit,

My last question was only to check if there is enough interest on this work, not an adoption call. There was q&a after the presentation. And Joe cut the line because of the time.

Now this is an adoption call. You are free to suggest or object. And we believe debate is really helpful.

Cheers,
Tianran


________________________________
Sent from WeLink

发件人: Benoit Claise<bclaise@cisco.com<mailto:bclaise@cisco.com>>
收件人: Tianran Zhou<zhoutianran@huawei.com<mailto:zhoutianran@huawei.com>>;opsawg<opsawg@ietf.org<mailto:opsawg@ietf.org>>;draft-song-opsawg-ifit-framework.authors<draft-song-opsawg-ifit-framework.authors@ietf.org<mailto:draft-song-opsawg-ifit-framework.authors@ietf.org>>
抄送: opsawg-chairs<opsawg-chairs@ietf.org<mailto:opsawg-chairs@ietf.org>>
主题: Re: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09
时间: 2019-12-17 20:56:58

Dear all,

After reviewing the meeting minutes<https://datatracker.ietf.org/doc/minutes-106-opsawg/>, I was a little bit puzzled. From my recollection, Joe and Frank had some good feedback on the draft.
Also, in the minutes, I did not see any mention of Joe's feedback. And Frank's feedback on the draft is summarized as 4 words: "the scope is large"
So I went back and reviewed the youtube video<https://www.youtube.com/watch?v=rY-u8177wpU>.

I support Frank's feedback that this document scope is too large: a mix of an inventory of what exists, a set of requirements, and specifications/framework. I'm wondering: what is the scope of this document? Before we clarify this, I don't think we should adopt this document.

The OPSAWG chair questions at the end of the presentation were:

        Chair: How many of you have read this document? quite a lot.
        Chair: How many of you think this is a useful work and the working group could
        work on it? still many, 20+.

I was waiting for the negative question but to my surprise, it never came...

        Chair: How many of you don't think ...


If that question would have been asked, I would have come to mic. or at least raised my hand.

It's important to make a distinction between the interest to solve those problems (I believe we have full agreement) and whether this document is a good starting point. I object to the latter, with the document in the current form.

Regards, Benoit
Hi WG,

On IETF 106 meeting, we saw predominant interest and support to this draft, especially from operators. The authors then resolved all the open issues.
As requested by the authors, this email starts a 2 weeks working group adoption call for draft-song-opsawg-ifit-framework-09.
https://datatracker.ietf.org/doc/draft-song-opsawg-ifit-framework/

If you support adopting this document please say so, and please give an indication of why you think it is important. Also please say if you will be willing to review and help the draft.
If you do not support adopting this document as a starting point to work on, please say why.
This poll will run until Dec 23..

Thanks,
Tianran as co-chair



_______________________________________________
OPSAWG mailing list
OPSAWG@ietf.org<mailto:OPSAWG@ietf.org>
https://www.ietf.org/mailman/listinfo/opsawg