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

Haoyu Song <haoyu.song@futurewei.com> Tue, 17 December 2019 18:24 UTC

Return-Path: <haoyu.song@futurewei.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 3C8FF1208C2; Tue, 17 Dec 2019 10:24:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 Ag90daLS_1eS; Tue, 17 Dec 2019 10:24:38 -0800 (PST)
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (mail-eopbgr700129.outbound.protection.outlook.com [40.107.70.129]) (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 52F3A12087E; Tue, 17 Dec 2019 10:24:37 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QpRIwOv46A7hD/jwPoIQPND1QK+2rwbvH3hD08kh59APi3o9mUSOBXbDVKwzfOWleBp2Y6/DWMUFX7bI4Pac6T6bM7Xcf5el55j3mFwJXA0KH7D9VkvKze4gco7WNStkPcAiiZzmslK9f/wYFgQirJ06RGDootUwcexBQ2ZSUQ+wM2/l8aCzlvl1nh0FgO2378pWM88UD/PbEblqvxYr7YZF3ueAUcosn+TdDfeqpslVkyS+xCL7Y9z14efRPDmtDvN92lDgrwxhBfp2OQ3vHBzKul5ImAo6RJlLtQPVW48VGgddieKHMQDAYM8i2h9QupSyF8Ps4+Lre7hmYmijCQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bJq6I/1Ko/wuJWXhQMZu4XatI07HvoLfS+g2WT2kI5Y=; b=WJEIWQuZMxsnMfkN0zYVU78xwJzneMqdS3qr6wGuPxQZ3i5dY5coeGGCqKIDyDZGqO+CSu0TE16ffcInQ0jcpYL3VCsTp5kn7rgJku4ovHKVT3dBuLt6BzgzFf3nC7XgNbSsKUno3gQexoPg+Yk3YQ4OlAYEMlMXFlNs3wEsPec8xaXnHBnUX4pzGQbeIdxV2Qb/c2xx4GIahYbZvBZK+eQ3FZJi5Rvc10xPU1nHIQgFy4Udv1uGYiaqQtYKu9AvwlNqhatG5H/dI+lat06qovMgYucyb52FyeE1kNk8T6NEZBkLNK5c70C1lVcC2xCG7RVa8tMF3X/CPZID8Qq4/w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bJq6I/1Ko/wuJWXhQMZu4XatI07HvoLfS+g2WT2kI5Y=; b=YNMvlpW+B/OuoaXckUeFD7fS0UfiejIvTd1emp1hqCx1XeaV/nDlfCa8JjkLanSMzc137EMF6VINqgGxZin7iG4fk/JxL0bWNrKsT1/RGNcfymcS8dktpxXIaRH/6lJw1ZQf9ESyUVi4XfBa40+zVMsD3J6aPcjSlwHcu0GLvWU=
Received: from BYAPR13MB2485.namprd13.prod.outlook.com (52.135.228.19) by BYAPR13MB2343.namprd13.prod.outlook.com (52.135.226.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2559.12; Tue, 17 Dec 2019 18:24:35 +0000
Received: from BYAPR13MB2485.namprd13.prod.outlook.com ([fe80::61a4:f17f:156:4876]) by BYAPR13MB2485.namprd13.prod.outlook.com ([fe80::61a4:f17f:156:4876%7]) with mapi id 15.20.2559.012; Tue, 17 Dec 2019 18:24:34 +0000
From: Haoyu Song <haoyu.song@futurewei.com>
To: Benoit Claise <bclaise@cisco.com>, Tianran Zhou <zhoutianran@huawei.com>, "opsawg@ietf.org" <opsawg@ietf.org>, "draft-song-opsawg-ifit-framework.authors@ietf.org" <draft-song-opsawg-ifit-framework.authors@ietf.org>
CC: "opsawg-chairs@ietf.org" <opsawg-chairs@ietf.org>
Thread-Topic: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09
Thread-Index: AdWuTgs1peGnP0a/SLi3HG/cQ1ovRgGi1miAAAsyDNU=
Date: Tue, 17 Dec 2019 18:24:34 +0000
Message-ID: <BYAPR13MB2485083EC0A6842AEDB3467A9A500@BYAPR13MB2485.namprd13.prod.outlook.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: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=haoyu.song@futurewei.com;
x-originating-ip: [12.111.81.71]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 22a9f654-d517-4fc8-44fb-08d7831e5e2e
x-ms-traffictypediagnostic: BYAPR13MB2343:
x-microsoft-antispam-prvs: <BYAPR13MB2343B1D78F3EA66F6CE7EE2B9A500@BYAPR13MB2343.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02543CD7CD
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(136003)(366004)(396003)(39850400004)(376002)(346002)(189003)(199004)(66556008)(64756008)(66476007)(66946007)(76116006)(66446008)(4326008)(26005)(7696005)(8676002)(33656002)(45080400002)(81156014)(5660300002)(8936002)(186003)(81166006)(52536014)(44832011)(478600001)(71200400001)(2906002)(86362001)(966005)(110136005)(316002)(6506007)(55016002)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR13MB2343; H:BYAPR13MB2485.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: G9Pbjds1q2Z9TZ4sA0owIBLTC9zpzivMfKVvE4lJM1QLN0PecSK3P5zpbBsOBvIBoU+a+8fcEGuBpcwhl3r8jupV0T/NvpkysYNpprJj+8xSXWjGp/d5BddXoABemjEHOgggAP9BQ6xwBGx6CttkLOgcT4pMF37NEgbYp5HrHTzxmt3KE4DBzTXOsbKZfwYY3/TIhUzC9wH7o8+/OWTiVJrtYSLBAqOz+YZLpXNKk/JB3FjAicUKgYhZTrDNh37ElNbz0YD1GSlqIy1+7e+0DsV+cuqleY/f326sDM3wutoLIO3Ll7wkBVHTPXdje/DQ5ABuqP00pum0SVtGG+jqKfupFeVeRxD8jx/XoBMTnjZeWkMVc6sMSLlE4qIuknrjf320Zo42vCVWSvXzwNO+AuJEdZcB5GhVu9O+KpiEbuLIVaMHkCyUo6Gn45byRIuYgFbOJ9mejpiDkN1V/GSw2qQpz8XVDG5PET31I440nxs=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR13MB2485083EC0A6842AEDB3467A9A500BYAPR13MB2485namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 22a9f654-d517-4fc8-44fb-08d7831e5e2e
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Dec 2019 18:24:34.6503 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SIrhFhuihTQtu7v65woSplVYCEKpF3wfhVlceoqtMMPr61//v7maLMftMV3z+XBv9ZFvplh+q0CUcmnA1DUYdg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR13MB2343
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/M-VMfb4WEW3ycN3T_y4IpTYRKWc>
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 18:24:42 -0000

Hi Benoit,

Did you read my summary email? In it I summarized all the questions raised during the meeting and I asked if there was anything missed and promised to address or clarify them in draft revisions.

I have updated the draft two times since then and I believe I have addressed all the issues.  Please take a look at it and specifically point out why you think some issues are still not addressed. If you have other concerns, please also be specific. Thank you very much!

Haoyu

获取 Outlook for Android<https://aka.ms/ghei36>

________________________________
发件人: Benoit Claise <bclaise@cisco.com>
发送时间: 2019年12月17日星期二 上午4:56
收件人: Tianran Zhou; opsawg@ietf.org; draft-song-opsawg-ifit-framework.authors@ietf.org
抄送: opsawg-chairs@ietf.org
主题: Re: [OPSAWG] WG adoption call for draft-song-opsawg-ifit-framework-09

Dear all,

After reviewing the meeting minutes<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fminutes-106-opsawg%2F&data=02%7C01%7Chaoyu.song%40futurewei.com%7Ca3128704007e42e662f608d782f08eae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637121842029952673&sdata=euXQxEzZrhghAme0Iv1LrFRYsqnmSN5xbhp4CNC5Q1E%3D&reserved=0>, 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://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DrY-u8177wpU&data=02%7C01%7Chaoyu.song%40futurewei.com%7Ca3128704007e42e662f608d782f08eae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637121842029962668&sdata=PGD1nUvH2a0QWwjmRQ54%2FcVi2k3LNDR39o4PP0NfY7U%3D&reserved=0>.

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/<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-song-opsawg-ifit-framework%2F&data=02%7C01%7Chaoyu.song%40futurewei.com%7Ca3128704007e42e662f608d782f08eae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637121842029962668&sdata=m%2FIqZwn7ARorYqGwXx%2FCqRaF6U%2BMFM7vxfegiEND8Ig%3D&reserved=0>

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<https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fopsawg&data=02%7C01%7Chaoyu.song%40futurewei.com%7Ca3128704007e42e662f608d782f08eae%7C0fee8ff2a3b240189c753a1d5591fedc%7C1%7C0%7C637121842029972664&sdata=lMy2W1NoojeqhUVp2AvtBa8QZCzeLHliGzUAyz5EWUA%3D&reserved=0>