Return-Path: 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 AE9C212867A; Thu, 21 Feb 2019 06:18:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cooperw.in header.b=trHXTgtT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=5OdoMWK3 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 dq1sEk57Pt1Y; Thu, 21 Feb 2019 06:18:40 -0800 (PST) Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E6BE1279E6; Thu, 21 Feb 2019 06:18:40 -0800 (PST) Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id A661830B5; Thu, 21 Feb 2019 09:18:38 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Thu, 21 Feb 2019 09:18:39 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= from:message-id:content-type:mime-version:subject:date :in-reply-to:cc:to:references; s=fm2; bh=YZ07ZMnatOHyoufL9ZS1mSM 3yo2UFEHE8wjJvbEHsWo=; b=trHXTgtTukeOWtlh8MsP661MC2nCHMnr5fX07uW YDK8NR1JGXtby0HQD4173bDvl0A9OwIMaeyjhVB2LNGnwMHZnWbQAD2ig2XuRUU9 vJu6CNzHndWSQPNIhHN+0/XehZSSBNNU/NHIUZGJzuzXt45xil7mvUKtG7mKl/M3 erZ6Lv5Z47BypFX2UM0aIdNn1FMHA94mm3cYEf1cI7kpZHZqBnJXzxb/JovHqUCy cTNQz5M5ZdOWexDLp+hTq7oyKx/3JjUH2BILUzUAdi/mmmI1FL4Xia8DGiq9YS7A PFKL8U3CpcVXlLku5cczXG+kzAY/klFlO5S5DsHpHBzu50A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=YZ07ZM natOHyoufL9ZS1mSM3yo2UFEHE8wjJvbEHsWo=; b=5OdoMWK3dc2E2r6EqyCquo 8RFez8hcT2FB9lxOZE1cLA2DnqYhrMM5tU4Wo7OoYLvNUqqlQJu0rE/TeBkcBZfL nwGob9jHbJNoQD/+RB4Tx0dJiYIeSq0QPaP3WWk4bapa6eaP0EnLVxVz079dIqZ4 VTKDO68eOu1ZJJV2EFqTN2qjJdc0QuqgBRme13P5PBaYzkIwOGINby3GPwa5o+wo 327bOXJIZZswGbiKXoFtowpnPB0FVsdOfQWyFeWCfPMZfxczdAyyccXKmrBHbPcT Cs4w9po+0MYXD/OLg1CcxoD0liPfWJO/twVJdLnKjv+FGwh0QcJE4UFHZlgc2nIA == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrtdekgdeigeculddtuddrgedtledrtddtmd cutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfhuthen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffktgggufffjgfvfhfosegrtdhmrehhtddvnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecukfhppeduje efrdefkedruddujedrieeknecurfgrrhgrmhepmhgrihhlfhhrohhmpegrlhhishhsrges tghoohhpvghrfidrihhnnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: Received: from rtp-vpn2-1805.cisco.com (unknown [173.38.117.68]) by mail.messagingengine.com (Postfix) with ESMTPA id D16F9E425A; Thu, 21 Feb 2019 09:18:36 -0500 (EST) From: Alissa Cooper Message-Id: <1C51C4F3-5B18-4F5A-A25D-4A9129E2EE38@cooperw.in> Content-Type: multipart/alternative; boundary="Apple-Mail=_A1C67C0C-24F2-402B-91BA-4F88BE28C00A" Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Thu, 21 Feb 2019 09:18:35 -0500 In-Reply-To: Cc: "gen-art@ietf.org" , "draft-ietf-dots-requirements.all@ietf.org" , "ietf@ietf.org" , "dots@ietf.org" To: "Konda, Tirumaleswar Reddy" , Robert Sparks References: <155007101476.9655.11486107409890423462@ietfa.amsl.com> X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: Re: [Dots] [Gen-art] Genart telechat review of draft-ietf-dots-requirements-18 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." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Feb 2019 14:18:43 -0000 --Apple-Mail=_A1C67C0C-24F2-402B-91BA-4F88BE28C00A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Robert, thanks for your review. I agree about the heartbeat requirements = and said so in my No Objection ballot. Tiru, thanks for your response on = the other point. Alissa > On Feb 14, 2019, at 1:08 AM, Konda, Tirumaleswar Reddy = wrote: >=20 > Hi Robert, >=20 > Please see inline >=20 >> -----Original Message----- >> From: Robert Sparks > >> Sent: Wednesday, February 13, 2019 8:47 PM >> To: gen-art@ietf.org >> Cc: draft-ietf-dots-requirements.all@ietf.org = ; ietf@ietf.org = ; dots@ietf.org >> Subject: Genart telechat review of draft-ietf-dots-requirements-18 >>=20 >> This email originated from outside of the organization. Do not click = links or >> open attachments unless you recognize the sender and know the content = is safe. >>=20 >> Reviewer: Robert Sparks >> Review result: Ready with Issues >>=20 >> I am the assigned Gen-ART reviewer for this draft. The General Area = Review >> Team (Gen-ART) reviews all IETF documents being processed by the IESG = for >> the IETF Chair. Please wait for direction from your document shepherd = or AD >> before posting a new version of the draft. >>=20 >> For more information, please see the FAQ at >>=20 >> . >>=20 >> Document: draft-ietf-dots-requirements-18 >> Reviewer: Robert Sparks >> Review Date: 2019-02-13 >> IETF LC End Date: 2018-11-23 >> IESG Telechat date: 2019-02-21 >>=20 >> Summary: Ready, but with a process issue for the shepherd and AD to = consider. >>=20 >> This version addressed all of my comments on version -16. Thank you. >>=20 >> However, the diff shows that a large number of SHOULDs were changed = to >> MUSTs. >> I'm guessing that was in response to a comment in the TSVART review = of -16. >=20 > Yup. >=20 >> This large scale substitution makes me worry - are they really the = right >> adjustments? Has the group reviewed and agreed to these normative = changes? >=20 > The WG has not identified any qualifying exceptional conditions for = these requirements when the discussing the DOTS protocol and = requirements drafts, hence I updated=20 > these requirements to use MUST. >=20 >>=20 >> As a nit, I'll note that the additional description of heartbeating = creeps into >> specifying protocol rather than requirements. >=20 > The additional text in SIG-004 is added to justify the reason for = using "SHOULD". >=20 > Cheers, > -Tiru=20 >=20 >>=20 >=20 > _______________________________________________ > Gen-art mailing list > Gen-art@ietf.org > https://www.ietf.org/mailman/listinfo/gen-art = --Apple-Mail=_A1C67C0C-24F2-402B-91BA-4F88BE28C00A Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii Robert, thanks for your review. I agree about the heartbeat = requirements and said so in my No Objection ballot. Tiru, thanks for = your response on the other point.

Alissa

On Feb 14, 2019, at 1:08 AM, = Konda, Tirumaleswar Reddy <TirumaleswarReddy_Konda@McAfee.com> wrote:

Hi Robert,

Please see inline

-----Original Message-----
From: Robert Sparks = <rjsparks@nostrum.com>
Sent: Wednesday, = February 13, 2019 8:47 PM
To: gen-art@ietf.org
Cc: draft-ietf-dots-requirements.all@ietf.org; ietf@ietf.org; dots@ietf.org
Subject: Genart telechat review of = draft-ietf-dots-requirements-18

This email = originated from outside of the organization. Do not click links or
open attachments unless you recognize the sender and know the = content is safe.

Reviewer: Robert Sparks
Review result: Ready with Issues

I= am the assigned Gen-ART reviewer for this draft. The General Area = Review
Team (Gen-ART) reviews all IETF documents being = processed by the IESG for
the IETF Chair. Please wait for = direction from your document shepherd or AD
before posting = a new version of the draft.

For more = information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-dots-requirements-18
Reviewer: Robert Sparks
Review Date: = 2019-02-13
IETF LC End Date: 2018-11-23
IESG = Telechat date: 2019-02-21

Summary: Ready, = but with a process issue for the shepherd and AD to consider.

This version addressed all of my comments on = version -16. Thank you.

However, the diff = shows that a large number of SHOULDs were changed to
MUSTs.
I'm guessing that was in response to a = comment in the TSVART review of -16.

Yup.

This = large scale substitution makes me worry - are they really the right
adjustments? Has the group reviewed and agreed to these = normative changes?

The WG has not identified any qualifying exceptional = conditions for these requirements when the discussing the DOTS protocol = and requirements drafts, hence I updated 
these requirements to use = MUST.


As a nit, I'll note that the additional description of = heartbeating creeps into
specifying protocol rather than = requirements.

The additional text in SIG-004 is added to justify the reason = for using "SHOULD".

Cheers,
-Tiru 



_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www.ietf.org/mailman/listinfo/gen-art

= --Apple-Mail=_A1C67C0C-24F2-402B-91BA-4F88BE28C00A--