IETF Logo Mail Archive

Re: [Gen-art] Genart Telechat review: draft-ietf-grow-filtering-threats-07

Robert Sparks <rjsparks@nostrum.com> Thu, 20 August 2015 14:38 UTC

Return-Path: <rjsparks@nostrum.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4CB071ACED2; Thu, 20 Aug 2015 07:38:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 jTzkYna9hM9O; Thu, 20 Aug 2015 07:38:03 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (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 37F411ACEB4; Thu, 20 Aug 2015 07:38:03 -0700 (PDT)
Received: from unnumerable.local (pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t7KEc2pq089384 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=OK); Thu, 20 Aug 2015 09:38:02 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
X-Authentication-Warning: raven.nostrum.com: Host pool-71-170-237-80.dllstx.fios.verizon.net [71.170.237.80] claimed to be unnumerable.local
Message-ID: <55D5E645.20501@nostrum.com>
Date: Thu, 20 Aug 2015 09:37:57 -0500
From: Robert Sparks <rjsparks@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <558B3AEE.2010009@nostrum.com> <55D21E56.7040608@nostrum.com> <3209D838-C031-4689-8CCB-6EAFE25CC2D1@piuha.net> <55D5DF94.2030003@nostrum.com> <DC452CCA-33CB-4B51-9FBD-C27FBD02D78F@piuha.net>
In-Reply-To: <DC452CCA-33CB-4B51-9FBD-C27FBD02D78F@piuha.net>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/Xv51QkJuRyyAY-6ZmeIQ1l1fhYQ>
Cc: General Area Review Team <gen-art@ietf.org>, grow@ietf.org, "ietf@ietf.org" <ietf@ietf.org>, draft-ietf-grow-filtering-threats.all@ietf.org
Subject: Re: [Gen-art] Genart Telechat review: draft-ietf-grow-filtering-threats-07
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Aug 2015 14:38:04 -0000


On 8/20/15 9:34 AM, Jari Arkko wrote:
> After some more staring of the data tracker settings, you are of course completely correct,
> Robert :-) The document is marked as having IETF consensus setting, so the text that you
> quoted will get inserted into the RFC.
>
> Pardon my mistake in assuming it wasn’t.
>
> On the IESG call we had a discussion about this issue. We saw two separate questions:
>
> 1) Substance: Is there a consensus behind the document’s recommendations? The sponsoring AD
> and the IESG believes so.
>
> 2) Editorial: Is it appropriate to use the “the authors recommend…” form for IETF-level
> consensus statements? The sponsoring AD took your comment about the formulation
> (also recommended by other ADs) and will work with the author to revise the document.
> However, this matter is indeed editorial, i.e., a Comment rather than a Discuss level
> requirement from the IESG.
>
> So the document will be approved, after some editorial modifications, and will become
> an RFC.
That plan works for me. Thanks!
>
> Jari
>

v2.23.0 | Report a Bug | By Email