Re: [Dots] 答复: merging requirements and use cases drafts?
Daniel Migault <daniel.migault@ericsson.com> Mon, 20 March 2017 02:04 UTC
Return-Path: <mglt.ietf@gmail.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 EEEB712945B for <dots@ietfa.amsl.com>; Sun, 19 Mar 2017 19:04:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.401
X-Spam-Level:
X-Spam-Status: No, score=-2.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 BfpSSIwmYyK3 for <dots@ietfa.amsl.com>; Sun, 19 Mar 2017 19:04:18 -0700 (PDT)
Received: from mail-it0-x233.google.com (mail-it0-x233.google.com [IPv6:2607:f8b0:4001:c0b::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14C90129455 for <dots@ietf.org>; Sun, 19 Mar 2017 19:04:18 -0700 (PDT)
Received: by mail-it0-x233.google.com with SMTP id y18so3847576itc.1 for <dots@ietf.org>; Sun, 19 Mar 2017 19:04:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=+/cqmO7c9PRnt0nV97ZZjhkFNrB52K4QPpuoZCLfZP4=; b=bAVA3YrWjh1ssxhG80oTFOiMwMThabOHxy/jUFogCXehv6Z+K8DQJiTpua61zSI+gO dk513MpvWpTx8i+MXf5NfBZeUlw5MFkJmmhnKj1uN03z8BYcoCOb2k0BEXJQCoBYhlYG ju+89IiEMGmi51GFcD/vNxy2teH+nuQajqNe5aZjNMiSdH5OtUqxWAqVvF+/czSFRt3b I77nk+kp89ZZh/I8tKWxveFijhleeiwxv0egwknxeGN8uDkzjL04hxVWXmyuF+78NrwC 5RFSFLWuGSsmgmgZvC6gFWsSoAWdEzq3AEMpL/WmLosYMOSlFjGBAeVRHF9EO4Sdp901 p+uQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=+/cqmO7c9PRnt0nV97ZZjhkFNrB52K4QPpuoZCLfZP4=; b=Mzv1W2roIxwKpgOEHvLz7ms2OgvpVL9zJsVviTM7pLOmyOfKOhvvoJrQ31tJ2IgF3d q4RJ0wmwOb7D/GQ5xlPAG8j5HpOKvxJu3cAmS2Eadop8IlyA1vgU5VbPN+wV+0Gok/RE LLFrCctz+2nH1GG/E30vY6lkF3pIdyWY/pyTp/aKa57UF/iZt+MZtDCvJ4fLNSmpFGIi Abt5Ao3gSqHkiJ/XrmHlpEm/aIsGBngHCPIK4BnUO57Fiydo1Wx/bEPscBxc3XsvBYub LGnS7tSAVzAxh54P8MTnmdhJ2BDWmktf6n59g0A9+LTKL1rCRuBK2FNVydr7POtgdlXn H/xA==
X-Gm-Message-State: AFeK/H30QgRB9oFLE2j8VCSYp4qv6EwOp/cshqXx/DUMEDN3h9XssVW25fju8CH7KK/oWcqcNr5idXvF95UPhw==
X-Received: by 10.107.174.27 with SMTP id x27mr24252686ioe.35.1489975457498; Sun, 19 Mar 2017 19:04:17 -0700 (PDT)
MIME-Version: 1.0
Sender: mglt.ietf@gmail.com
Received: by 10.107.35.213 with HTTP; Sun, 19 Mar 2017 19:04:16 -0700 (PDT)
Received: by 10.107.35.213 with HTTP; Sun, 19 Mar 2017 19:04:16 -0700 (PDT)
In-Reply-To: <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> <C02846B1344F344EB4FAA6FA7AF481F12BAA559B@DGGEML502-MBX.china.huawei.com>
From: Daniel Migault <daniel.migault@ericsson.com>
Date: Sun, 19 Mar 2017 22:04:16 -0400
X-Google-Sender-Auth: e4gEPmDopt9xSJfaXKqz5nmem0w
Message-ID: <CADZyTkms4CnD5yYRVV7TyQdvOTopRtX8sQBD34TLzpY5o9bCrg@mail.gmail.com>
To: "Xialiang (Frank)" <frank.xialiang@huawei.com>
Cc: "Roman D. Danyliw" <rdd@cert.org>, dots@ietf.org
Content-Type: multipart/alternative; boundary="001a11449ffcde4ae3054b1ff1cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/VDE_3GRughfPkgMYPP4jWpYrK-I>
Subject: Re: [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 02:04:21 -0000
Hi, I also see value in having two different documents. Yours Daniel On Mar 19, 2017 21:33, "Xialiang (Frank)" <frank.xialiang@huawei.com> wrote: > 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 > _______________________________________________ > Dots mailing list > Dots@ietf.org > https://www.ietf.org/mailman/listinfo/dots >
- [Dots] merging requirements and use cases drafts? Mortensen, Andrew
- Re: [Dots] merging requirements and use cases dra… Kathleen Moriarty
- Re: [Dots] merging requirements and use cases dra… mohamed.boucadair
- Re: [Dots] merging requirements and use cases dra… Tirumaleswar Reddy (tireddy)
- Re: [Dots] merging requirements and use cases dra… Ehud Doron
- Re: [Dots] merging requirements and use cases dra… Roman Danyliw
- Re: [Dots] merging requirements and use cases dra… Roland Dobbins
- Re: [Dots] merging requirements and use cases dra… Flemming Andreasen
- [Dots] 答复: merging requirements and use cases dra… Xialiang (Frank)
- Re: [Dots] 答复: merging requirements and use cases… Daniel Migault
- Re: [Dots] 答复: merging requirements and use cases… kaname nishizuka