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

Benoit Claise <bclaise@cisco.com> Tue, 17 December 2019 13:43 UTC

Return-Path: <bclaise@cisco.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 E8A6F12082D; Tue, 17 Dec 2019 05:43:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 W78z2m9ntxJ1; Tue, 17 Dec 2019 05:43:22 -0800 (PST)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E6CF112082B; Tue, 17 Dec 2019 05:43:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10816; q=dns/txt; s=iport; t=1576590202; x=1577799802; h=subject:to:cc:references:from:message-id:date: mime-version:in-reply-to; bh=9IKa2Ym4JEPvHNn2J5RVij6SgTzR6mDl7q0J5vZSYrI=; b=XOWg7bqAiWu0DehO4SBhCW30OpySQhodyG0B3Me9H14j+fjqMdTDmEkm /gAP/RRop0gdSTYNTDZ5RUNJ56wH4VJjDJUXre75PPPl5M1Dr70aVzL0U Tw2VDrElt/LjzdOd3cLgdhqt+IA8xp88vvl22NnxMFRQ55IODWqDlMmqN 0=;
X-IPAS-Result: A0BfAAB42vhd/xbLJq1lGgEBAQEBAQEBAQMBAQEBEQEBAQICAQEBAYF+gwxVIBIqhASJA4gzkyWGI4FnCQEBAQwBARgBCgwBAYN7RQKCPDgTAgMBAQEDAgMBAQEBBAEBAQIBBQRthTcMhV8CAQMBARsGSwsQCQI/AwICJx8RBgEMBgIBAYMeAYJ3D5Ismn91gTIfhB8EDEFAgz+BQgaBNowygUE/gTiCbD6CZAEBAgEBGIEPBQESAScuglqCXgSHOoYHoUSCPocvhHCCa4cABhuCQ4d2hBonh3eDWI5NiFCIO4lCAhEVgWkiZ3EzGggbFTuCbFARFI0eF4NQhRSFQEADMI9OgjIBAQ
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.69,211,1571702400"; d="scan'208,217"; a="20411419"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 17 Dec 2019 13:43:15 +0000
Received: from [10.55.221.36] (ams-bclaise-nitro3.cisco.com [10.55.221.36]) (authenticated bits=0) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPSA id xBHDhCPC021665 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=NO); Tue, 17 Dec 2019 13:43:15 GMT
To: Tianran Zhou <zhoutianran@huawei.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>
References: <BBA82579FD347748BEADC4C445EA0F21BF135AC8@NKGEML515-MBX.china.huawei.com> <67f5447c-37a0-62e4-9dd0-0ae380178dc3@cisco.com> <BBA82579FD347748BEADC4C445EA0F21BF1472CD@NKGEML515-MBX.china.huawei.com>
From: Benoit Claise <bclaise@cisco.com>
Message-ID: <421292da-8b8a-86eb-a02a-47049b62ed31@cisco.com>
Date: Tue, 17 Dec 2019 14:43:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <BBA82579FD347748BEADC4C445EA0F21BF1472CD@NKGEML515-MBX.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------F25F894355938F090F59580E"
Content-Language: en-US
X-Authenticated-User: bclaise
X-Outbound-SMTP-Client: 10.55.221.36, ams-bclaise-nitro3.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/_L2bZ3duhbZB26qwgMRlCBZ4Dxc>
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:43:26 -0000

Hi Tianran,
> 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.
I just did :-)

Regards, B.
> 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 themeeting 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, wesaw 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
>> https://www.ietf.org/mailman/listinfo/opsawg
>