Re: [GROW] Alvaro Retana's No Objection on draft-ietf-grow-filtering-threats-07: (with COMMENT)

"Alvaro Retana (aretana)" <aretana@cisco.com> Tue, 15 September 2015 12:24 UTC

Return-Path: <aretana@cisco.com>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A82DF1ACD18; Tue, 15 Sep 2015 05:24:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 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, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 rLexqxuMFiMP; Tue, 15 Sep 2015 05:24:26 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11D731B2D70; Tue, 15 Sep 2015 05:24:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2461; q=dns/txt; s=iport; t=1442319866; x=1443529466; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=OjCMU/Ga+bkFxYJlJLxdSRHvT1UUZrwH9F8RN608yIY=; b=Cn+V11KNP8bJ6ju/IdAdB5Lz3IszG4t5TTHN0vzDzbGv9fPu9c4vruVy 5L4p0oHq0oiXEK6+64p3BNpEfVZvYr7A2gvBc6soIpFXmyJZyLfzOLSio AZsMW1dNIIjHUPoURT/K2SOsz0+4cV3NTwkPf4nxArN853xbAgKI9XYLY 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AHBQA4DfhV/5BdJa1egyOBPQa9VIdyAoFCORMBAQEBAQEBgQqEJAEBBHkQAgEIDjgyJQIEDgWILsl2AQEBAQEBAQMBAQEBAQEBARqGcwGEfIRaMweELAEEhzKLAoMoAYV2hwyBTJk3IwI+gkOBPnGJJYEFAQEB
X-IronPort-AV: E=Sophos;i="5.17,535,1437436800"; d="scan'208";a="29034576"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by rcdn-iport-6.cisco.com with ESMTP; 15 Sep 2015 12:24:25 +0000
Received: from XCH-ALN-006.cisco.com (xch-aln-006.cisco.com [173.36.7.16]) by rcdn-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id t8FCOPux002851 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 15 Sep 2015 12:24:25 GMT
Received: from xch-aln-006.cisco.com (173.36.7.16) by XCH-ALN-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 15 Sep 2015 07:24:17 -0500
Received: from xhc-aln-x14.cisco.com (173.36.12.88) by xch-aln-006.cisco.com (173.36.7.16) with Microsoft SMTP Server (TLS) id 15.0.1104.5 via Frontend Transport; Tue, 15 Sep 2015 07:24:17 -0500
Received: from xmb-aln-x15.cisco.com ([169.254.9.140]) by xhc-aln-x14.cisco.com ([173.36.12.88]) with mapi id 14.03.0248.002; Tue, 15 Sep 2015 07:24:17 -0500
From: "Alvaro Retana (aretana)" <aretana@cisco.com>
To: Camilo Cardona <juancamilo.cardona@imdea.org>
Thread-Topic: [GROW] Alvaro Retana's No Objection on draft-ietf-grow-filtering-threats-07: (with COMMENT)
Thread-Index: AQHQ76xseQn4gg7D4EyeibEkxCldRJ49lFsA
Date: Tue, 15 Sep 2015 12:24:16 +0000
Message-ID: <D21D8361.D02AE%aretana@cisco.com>
References: <20150818200348.20146.83912.idtracker@ietfa.amsl.com> <FF194D71-98B3-4F7F-A271-C177617CA4DC@imdea.org>
In-Reply-To: <FF194D71-98B3-4F7F-A271-C177617CA4DC@imdea.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [173.36.7.13]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <0DDF0446FA102743982B3C065617FE20@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/25jXQs-f9UiiStUAicqZd9A1pEk>
Cc: "grow-chairs@ietf.org" <grow-chairs@ietf.org>, "grow@ietf.org grow@ietf.org" <grow@ietf.org>, "draft-ietf-grow-filtering-threats.ad@ietf.org" <draft-ietf-grow-filtering-threats.ad@ietf.org>, "draft-ietf-grow-filtering-threats@ietf.org" <draft-ietf-grow-filtering-threats@ietf.org>, The IESG <iesg@ietf.org>, "draft-ietf-grow-filtering-threats.shepherd@ietf.org" <draft-ietf-grow-filtering-threats.shepherd@ietf.org>
Subject: Re: [GROW] Alvaro Retana's No Objection on draft-ietf-grow-filtering-threats-07: (with COMMENT)
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/grow/>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Sep 2015 12:24:27 -0000

On 9/15/15, 7:48 AM, "Camilo Cardona" <juancamilo.cardona@imdea.org> wrote:

Camilo:

Hi!

>>----------------------------------------------------------------------
>>COMMENT:
>>----------------------------------------------------------------------
>>I have a non-blocking comment related to the characterization of the
>>unexpected traffic flows (and a nit).
>>Section 6. (Security Considerations)  Throughout the document the
>>unexpected traffic flows were characterized as potential policy
>>violations, not as routing security issues as is done here.  I know that
>>the text has gone around the point of malicious intent (or not) before,
>>but I think that if you¹re going to mention that it could be a "potential
>>routing security issue², then you should say something more about it
>>(even if it is the result of non-malicious intent) ‹ or just leave it at
>>policy violations.
>
><JCC> The security section indeed mentions that the objective of the
>document is security, however, we stopped focusing on that aspect at an
>earlier version. We¹ll correct that part to something along the next
>lines:
>
>OLD: The objective of this document is to inform on this potential
>routing security issue, and analyze ways for operators to defend against
>them.
>NEW: The document informed on the potential routing security issue, and
>analyzed ways for operators to defend against them.

That does not solve the point I was trying to make.

The point is this: this (the sentence above) is the only place in the
draft where an unexpected traffic flow is characterized as a ³potential
routing security issue².  If you¹re going to characterize it that way,
then I think you should explain more: why is is a security issue, what is
the effect, what can be done to avoid it, etc.

You mention that the security focus is no more; that¹s in line with what
Joel wrote (in the thread related to Kathleen¹s comments:

On 9/1/15, 12:11 PM, "iesg on behalf of joel jaeggli"
<iesg-bounces@ietf.org on behalf of joelja@bogus.com> wrote:

>We worked pretty hard to keep both the attack terminology out of the
>document and to keep the focus on the non-malicious action of ordinary
>actors. I think it's better that we don't lump that in with malicious
>action of varying varieties.

I fully agree!  You can make the decision, but if it was me, I would just
take the sentence out.

Thanks!

Alvaro.