Re: [GROW] Genart LC review: draft-ietf-grow-filtering-threats-06

Bill Woodcock <woody@pch.net> Wed, 24 June 2015 23:49 UTC

Return-Path: <woody@pch.net>
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 B4C5F1B2FFD; Wed, 24 Jun 2015 16:49:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, 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 vw9gCjq8eSQv; Wed, 24 Jun 2015 16:49:24 -0700 (PDT)
Received: from ldap-01.pch.net (ldap-01.pch.net [206.220.231.75]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6C6F1ACD22; Wed, 24 Jun 2015 16:49:24 -0700 (PDT)
X-Footer: cGNoLm5ldA==
Received: from dhcp-23.brk-office.pch.net ([204.61.213.23]) (authenticated user woody@pch.net) by ldap-01.pch.net (Kerio Connect 7.4.2) (using TLSv1/SSLv3 with cipher AES256-SHA (256 bits)); Wed, 24 Jun 2015 16:49:22 -0700
Content-Type: multipart/signed; boundary="Apple-Mail=_EDAAE8D6-4253-4F0E-AFFA-89FD0482D699"; protocol="application/pgp-signature"; micalg="pgp-sha256"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
X-Pgp-Agent: GPGMail 2.5
From: Bill Woodcock <woody@pch.net>
In-Reply-To: <20150624234512.GG49729@Vurt.local>
Date: Wed, 24 Jun 2015 16:49:08 -0700
Message-Id: <143256C7-F9B0-4B7B-A9C9-3A80F07EB2B6@pch.net>
References: <558B3AEE.2010009@nostrum.com> <m2pp4k7k8o.wl%randy@psg.com> <20150624234512.GG49729@Vurt.local>
To: GROW List <grow@ietf.org>, IETF Disgust <ietf@ietf.org>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/grow/fw1XZ2WOZLTjMLlLYIsl9kTipZ4>
Subject: Re: [GROW] Genart LC review: draft-ietf-grow-filtering-threats-06
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: Wed, 24 Jun 2015 23:49:25 -0000

> On Jun 24, 2015, at 4:45 PM, Job Snijders <job@instituut.net> wrote:
> 
> On Thu, Jun 25, 2015 at 08:35:35AM +0900, Randy Bush wrote:
>>> Is the last paragraph of 4.1 an IETF consensus position on how operators
>>> might charge one another? It would be good to find a way to word this
>>> that look more like statements of fact and less like charging advice.
>> 
>> darn hard as there are no facts there and it is first class lawyer
>> bait.
> 
> Indeed.
> 
> It might be better to remove this part:
> 
> "It is possible that the behavior of the neighboring AS causing the
> unexpected traffic flows opposes the peering agreement.  In this case,
> an operator could account the amount of traffic that has been subject to
> the unexpected flows, using traffic measurement protocols such as IPFIX,
> and charge the peer for that traffic.  That is, the operator can claim
> that it has been a provider of that peer for the traffic that transited
> between the two ASes."
> 
> Instead something like:
> 
> "It is possible that the behavior of the neighboring AS causing the
> unexpected traffic flows violates a contractual agreement between the
> two networks."
> 
> And just leave it at that.


I support Job’s proposed improvement wholeheartedly.

                                -Bill