IETF Logo Mail Archive

Re: [Dots] Call for adoption of draft-hayashi-dots-telemetry-use-cases-00

"Panwei (William)" <william.panwei@huawei.com> Tue, 01 September 2020 08:39 UTC

Return-Path: <william.panwei@huawei.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B9EE73A0DF3; Tue, 1 Sep 2020 01:39:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-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 SjMExYSptxA4; Tue, 1 Sep 2020 01:39:41 -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 212EF3A0DD4; Tue, 1 Sep 2020 01:39:41 -0700 (PDT)
Received: from lhreml704-chm.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 268EEE61B824B1B8A6AA; Tue, 1 Sep 2020 09:39:39 +0100 (IST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by lhreml704-chm.china.huawei.com (10.201.108.53) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Tue, 1 Sep 2020 09:39:38 +0100
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 1 Sep 2020 16:39:36 +0800
Received: from nkgeml705-chm.china.huawei.com ([10.98.57.154]) by nkgeml705-chm.china.huawei.com ([10.98.57.154]) with mapi id 15.01.1913.007; Tue, 1 Sep 2020 16:39:36 +0800
From: "Panwei (William)" <william.panwei@huawei.com>
To: Valery Smyslov <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, H Y <yuuhei.hayashi@gmail.com>, "draft-hayashi-dots-telemetry-use-cases@ietf.org" <draft-hayashi-dots-telemetry-use-cases@ietf.org>
Thread-Topic: [Dots] Call for adoption of draft-hayashi-dots-telemetry-use-cases-00
Thread-Index: AdZ8QgawAJWB9ERrSp2Zb590Qj6oAwD+VTkw
Date: Tue, 01 Sep 2020 08:39:36 +0000
Message-ID: <e52250d510314c868abda421a35a4651@huawei.com>
References: <0be401d67c45$d4381080$7ca83180$@smyslov.net>
In-Reply-To: <0be401d67c45$d4381080$7ca83180$@smyslov.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.99.125]
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/dots/2OJqjMwapXEeghV20GAMyA-9hi4>
Subject: Re: [Dots] Call for adoption of draft-hayashi-dots-telemetry-use-cases-00
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Sep 2020 08:39:43 -0000

+1 support for option 1.

Regards & Thanks!
Wei Pan

-----Original Message-----
From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Valery Smyslov
Sent: Thursday, August 27, 2020 3:44 PM
To: dots@ietf.org
Cc: dots-chairs@ietf.org; H Y <yuuhei.hayashi@gmail.com>; draft-hayashi-dots-telemetry-use-cases@ietf.org
Subject: [Dots] Call for adoption of draft-hayashi-dots-telemetry-use-cases-00

Hi,

after discussion with Yuhei we decided to issue a call for adoption of draft-hayashi-dots-telemetry-use-cases-00 as a WG document.

Note, that the chairs have an opinion, that the DOTS WG has already published quite a lot of informational documents, describing DOTS requirements, architecture, use cases.
We think that having one more auxiliary document that describes use cases only for an optional feature of DOTS
(telemetry) is not fully justified and it's probably better to merge telemetry use cases draft with telemetry I-D. 
We think that for implementers it's generally easier to look into a single document, than to find a separate one describing use cases. Another consideration is that if a separate document is adopted, then the processing of the telemetry I-D will probably have to be slow down until the telemetry use cases draft is ready, so that they are sent to publication together (in this case the telemetry draft will  have a steady reference to RFC and not to I-D).

On the other hand, discussion on last DOTS meeting and on the list indicated that quite a lot of people in the WG prefer to have telemetry use cases as a separate document, instead of merging it with the telemetry draft. The concerns were expressed that telemetry draft is already a long document and authors don't want to make it longer.

So, this message start a two weeks call for adoption of
draft-hayashi-dots-telemetry-use-cases-00 that will end 11 September. 
Please, respond to the list with your preference among 2 options:

1. Adopt this draft as a separate document describing DOTS telemetry use cases.
2. Don't adopt this draft and merge its content into the draft-ietf-dots-telemetry instead.

We'll be very much appreciated if you also give reasoning for your choice.

Regards,
Frank & Valery.

_______________________________________________
Dots mailing list
Dots@ietf.org
https://www.ietf.org/mailman/listinfo/dots

v2.23.0 | Report a Bug | By Email