[Dots] 答复: merging requirements and use cases drafts?

"Xialiang (Frank)" <frank.xialiang@huawei.com> Mon, 20 March 2017 01:33 UTC

Return-Path: <frank.xialiang@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 D45AA129443 for <dots@ietfa.amsl.com>; Sun, 19 Mar 2017 18:33:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.222
X-Spam-Level:
X-Spam-Status: No, score=-4.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=unavailable 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 Dzhn3TJo-YBf for <dots@ietfa.amsl.com>; Sun, 19 Mar 2017 18:33:43 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E533D1243F6 for <dots@ietf.org>; Sun, 19 Mar 2017 18:28:11 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml702-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DDB66555; Mon, 20 Mar 2017 01:28:09 +0000 (GMT)
Received: from DGGEML404-HUB.china.huawei.com (10.3.17.39) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 20 Mar 2017 01:28:09 +0000
Received: from DGGEML502-MBX.china.huawei.com ([169.254.2.80]) by DGGEML404-HUB.china.huawei.com ([::1]) with mapi id 14.03.0301.000; Mon, 20 Mar 2017 09:28:06 +0800
From: "Xialiang (Frank)" <frank.xialiang@huawei.com>
To: Roman Danyliw <rdd@cert.org>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] merging requirements and use cases drafts?
Thread-Index: AQHSkSlHPjfCqL/HTUaPO9bSB5JdCKF+D3eQgAARtRCAAAJBUIAZ5tgQgACbHgCABGotMA==
Date: Mon, 20 Mar 2017 01:28:05 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12BAA559B@DGGEML502-MBX.china.huawei.com>
References: <CE7B264D-CAC1-41DF-8650-702E120BFBF9@arbor.net> <787AE7BB302AE849A7480A190F8B933009E1989A@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <ce1550b82eeb4250a12c1f09622cfd45@XCH-RCD-017.cisco.com> <E58182C4A35A8E498E553AD3D33FA00101171A327B@ILMB2.corp.radware.com> <359EC4B99E040048A7131E0F4E113AFC0104F1D124@marathon> <44a6b86f-f3ec-9635-4935-df8bcd627858@cisco.com>
In-Reply-To: <44a6b86f-f3ec-9635-4935-df8bcd627858@cisco.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.135.43.91]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.58CF302A.00AC, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.80, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 0c229ea5d1d51db97e7e514b8c4b457e
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/X3kCzGU4fSkt-25nwAirlEKFxCQ>
Subject: [Dots] 答复: merging requirements and use cases drafts?
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 20 Mar 2017 01:33:45 -0000

Hi all,
I see these two drafts have their respective values, and prefer to keeping them separate.

Thanks!

B.R.
Frank

-----邮件原件-----
发件人: Dots [mailto:dots-bounces@ietf.org] 代表 Flemming Andreasen
发送时间: 2017年3月17日 22:01
收件人: Roman Danyliw; dots@ietf.org
主题: Re: [Dots] merging requirements and use cases drafts?

I think both are valuable and prefer keeping them separate.

-- Flemming

On 3/16/17 4:47 PM, Roman Danyliw wrote:
> Hello all!
>
> Any additional opinions on how to handle the WG requirements and use case drafts?
>
> Roman
>
>> -----Original Message-----
>> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Ehud Doron
>> Sent: Tuesday, February 28, 2017 4:14 AM
>> To: Tirumaleswar Reddy (tireddy) <tireddy@cisco.com>; 
>> mohamed.boucadair@orange.com; Mortensen, Andrew 
>> <amortensen@arbor.net>; dots@ietf.org
>> Subject: Re: [Dots] merging requirements and use cases drafts?
>>
>> All
>>
>> +1 on that, I prefer to keep them separate.
>>
>> Thanks, Ehud
>>
>> -----Original Message-----
>> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Tirumaleswar 
>> Reddy (tireddy)
>> Sent: Tuesday, February 28, 2017 11:08 AM
>> To: mohamed.boucadair@orange.com; Mortensen, Andrew 
>> <amortensen@arbor.net>; dots@ietf.org
>> Subject: Re: [Dots] merging requirements and use cases drafts?
>>
>> I prefer to keep them separate.
>>
>> -Tiru
>>
>>> -----Original Message-----
>>> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of 
>>> mohamed.boucadair@orange.com
>>> Sent: Tuesday, February 28, 2017 1:37 PM
>>> To: Mortensen, Andrew <amortensen@arbor.net>; dots@ietf.org
>>> Subject: Re: [Dots] merging requirements and use cases drafts?
>>>
>>> Hi Andrew, all,
>>>
>>> I have an alternate proposal:
>>> * Maintain the requirements draft with its initial scope.
>>> * Abandon the use cases draft.
>>>
>>> I don't see much value in publishing the use case I-D as an RFC. The 
>>> requirements I-D is really important as it sketches the scope and 
>>> required DOTS functionalities.
>>>
>>> Cheers,
>>> Med
>>>
>>>> -----Message d'origine-----
>>>> De : Dots [mailto:dots-bounces@ietf.org] De la part de Mortensen, 
>>>> Andrew Envoyé : lundi 27 février 2017 19:43 À : dots@ietf.org Objet :
>>>> [Dots] merging requirements and use cases drafts?
>>>>
>>>> During the interim meeting, Kathleen Moriarty observed that it 
>>>> might be beneficial to merge the requirements and use cases drafts, 
>>>> since the IESG tends to look more favorably on such drafts.
>>>>
>>>> We did not continue that discussion during the interim meeting, due 
>>>> to limited time, but I think it’s something we need to discuss 
>>>> ahead of the meeting in Chicago. To begin with, I’d like to hear a 
>>>> little more from Kathleen about why a merged draft is likely to be 
>>>> more palatable to the IESG. If nothing else, it’d be nice to avoid 
>>>> coming to the topic cold in Chicago.
>>>>
>>>> andrew
>>>> _______________________________________________
>>>> Dots mailing list
>>>> Dots@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/dots
>>> _______________________________________________
>>> Dots mailing list
>>> Dots@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dots
>> _______________________________________________
>> Dots mailing list
>> Dots@ietf.org
>> https://www.ietf.org/mailman/listinfo/dots
>> _______________________________________________
>> Dots mailing list
>> Dots@ietf.org
>> https://www.ietf.org/mailman/listinfo/dots
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

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