Re: [Dots] merging requirements and use cases drafts?
Flemming Andreasen <fandreas@cisco.com> Fri, 17 March 2017 14:01 UTC
Return-Path: <fandreas@cisco.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 69B5312943C for <dots@ietfa.amsl.com>; Fri, 17 Mar 2017 07:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, 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 dZJgR0qJdNaT for <dots@ietfa.amsl.com>; Fri, 17 Mar 2017 07:01:04 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BE34129443 for <dots@ietf.org>; Fri, 17 Mar 2017 07:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3366; q=dns/txt; s=iport; t=1489759264; x=1490968864; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=SqRohXQ6crUselFwDIn77kKJ7uwaHRVatQ6cEF4TUQM=; b=QudAKLAWXM5sHv9JREJopr8gzfCGPBu9iwpjvzYfPSvlQ6ZdZFNl3ain 05MQcXRkvVjGFfHd33kZBi/oEh2lUOBNVY0yETQxRPbbWyrEKvCWM4uc4 ba8XbTiKmVKQW1HkhXcYbQEEVqWYMSZhIG9ZHbPZs6DVqgCSciUYHEoFG M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AmAgDP6stY/4oNJK1eGQEBAQEBAQEBAQEBBwEBAQEBg1FhKmCDYooPkTkflUKCDh8LhXgCgwA/GAECAQEBAQEBAWsohRUBAQEBAwEBIQ8BBTYXBAsOAwQBAQECAiMDAgInHwkIBgEMBgIBAYlvDQ6yB4ImilIBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYELhUOCBQiCYoQwgyqCXwEEnEmSQopWhlWTUx84gQQ5HxVBhFcdgX8kNYcagj0BAQE
X-IronPort-AV: E=Sophos;i="5.36,176,1486425600"; d="scan'208";a="399498830"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Mar 2017 14:01:03 +0000
Received: from [10.98.149.202] (bxb-fandreas-8819.cisco.com [10.98.149.202]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id v2HE123i009850; Fri, 17 Mar 2017 14:01:03 GMT
To: Roman Danyliw <rdd@cert.org>, "dots@ietf.org" <dots@ietf.org>
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>
From: Flemming Andreasen <fandreas@cisco.com>
Message-ID: <44a6b86f-f3ec-9635-4935-df8bcd627858@cisco.com>
Date: Fri, 17 Mar 2017 10:01:02 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC0104F1D124@marathon>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/v19pOOC4h5PZk0kISiDR7wlDNsc>
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: Fri, 17 Mar 2017 14:01:06 -0000
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] 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