IETF Logo Mail Archive

Re: [Dots] merging requirements and use cases drafts?

"Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com> Tue, 28 February 2017 09:08 UTC

Return-Path: <tireddy@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 8DBD612706D for <dots@ietfa.amsl.com>; Tue, 28 Feb 2017 01:08:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.523
X-Spam-Level:
X-Spam-Status: No, score=-14.523 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, 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 zcsHcOvSf2gO for <dots@ietfa.amsl.com>; Tue, 28 Feb 2017 01:08:18 -0800 (PST)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 02B2A126D74 for <dots@ietf.org>; Tue, 28 Feb 2017 01:08:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2542; q=dns/txt; s=iport; t=1488272898; x=1489482498; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=XGLmx3K4hRGrFmzfhBbpJp4UbRT0iewFGfhBODvQK38=; b=gvjjDuAaVKSSvhh5AS6EDTqe4+OdfqoZ2K7hD/SxhtpwfUM++fNzxcf+ 5yVIue2e47GetXEGPTfkP8tW16nxiBgQk6HbFkyGehFWSdPKxZC+vHHkt 8hH9r8gYh1Btj5hRM9Z2XKbecZTNDdy/NcYaUiJRDjSvWkPf6Bw68NyaE w=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DyAQB/PbVY/4cNJK1dGQEBAQEBAQEBAQEBBwEBAQEBg1BhgQkHg1SKCJFjlTWCDR8LhXgCGoINPxgBAgEBAQEBAQFiKIRwAQEBBAEBIRE6FwQCAQgRBAEBAwIjAwICAiULFAEICAIEARIIiWwOsCmCJos1AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAWBC4VBhG+EMIMqgl8FlW+GMgGSIJEhkzABHziBAVQVPoRPHYFhdYdrgTCBDQEBAQ
X-IronPort-AV: E=Sophos;i="5.35,218,1484006400"; d="scan'208";a="389934312"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 28 Feb 2017 09:08:17 +0000
Received: from XCH-RCD-016.cisco.com (xch-rcd-016.cisco.com [173.37.102.26]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v1S98Hdd023341 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 28 Feb 2017 09:08:17 GMT
Received: from xch-rcd-017.cisco.com (173.37.102.27) by XCH-RCD-016.cisco.com (173.37.102.26) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 28 Feb 2017 03:08:16 -0600
Received: from xch-rcd-017.cisco.com ([173.37.102.27]) by XCH-RCD-017.cisco.com ([173.37.102.27]) with mapi id 15.00.1210.000; Tue, 28 Feb 2017 03:08:16 -0600
From: "Tirumaleswar Reddy (tireddy)" <tireddy@cisco.com>
To: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "Mortensen, Andrew" <amortensen@arbor.net>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: merging requirements and use cases drafts?
Thread-Index: AQHSkSlHPjfCqL/HTUaPO9bSB5JdCKF+D3eQgAARtRA=
Date: Tue, 28 Feb 2017 09:08:16 +0000
Message-ID: <ce1550b82eeb4250a12c1f09622cfd45@XCH-RCD-017.cisco.com>
References: <CE7B264D-CAC1-41DF-8650-702E120BFBF9@arbor.net> <787AE7BB302AE849A7480A190F8B933009E1989A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B933009E1989A@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.89.55]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/rKc3zzxHEzMPuEtw-QZqiMkK0Js>
Subject: Re: [Dots] merging requirements and use cases drafts?
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
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, 28 Feb 2017 09:08:19 -0000

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

v2.23.0 | Report a Bug | By Email