Re: [Idr] Alissa Cooper's Discuss on draft-ietf-idr-rfc5575bis-22: (with DISCUSS)

Alvaro Retana <aretana.ietf@gmail.com> Wed, 22 April 2020 16:31 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 77DB73A0FB2; Wed, 22 Apr 2020 09:31:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=gmail.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 8MKA5OHF9ZGW; Wed, 22 Apr 2020 09:31:30 -0700 (PDT)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 F24963A0FAC; Wed, 22 Apr 2020 09:31:29 -0700 (PDT)
Received: by mail-wm1-x32b.google.com with SMTP id h2so3106551wmb.4; Wed, 22 Apr 2020 09:31:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=fvglh/5+A9ZGJ9ZGOBCldXawGuikR0mwlUHSF4+PK4A=; b=bd4G4vPjpeGRgtvfYF++HzAV7cR2qw+o/8MfZrbMT/w4q+9kEsRA5T+rJ/0yGqorfb feQdNCEYPW2fazEk+6g0y+9Wsdvwc7e25I0GKh5BogLQUD1B6hYD3sKmrNXOYu6E1i2u 34AJNoPjZvNQG4sI5OQtKq0gFDMgvdel/GYi8Xl8bMeO7tl5Nl5IhqSIw87m1IvSeQVP d6vZ9I6yHT24NuAiClz4kMlMIrnrneQLptLKB8d7o7Yd6+72M2v0A6IEbx/OK5BViZh0 rSf0M5oNCl9lZnqFL6pFPpQRl5kO9A22sF52zmlRziUGxjezRDao9YrlL04u9SSbrrx2 k2iw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=fvglh/5+A9ZGJ9ZGOBCldXawGuikR0mwlUHSF4+PK4A=; b=Yl2RREpbzoMQCXbzrkNI08jstTTbrcnO5c/ITsBs/WRh9eEuGAd6GPGRUKdioQMCw7 si2ZAanoRCcP9jaR63DWWBTQzGhTsMpIdZzOsEwRgmJs2OmhTjcXVym80HIagnWRKvp1 yqrC9N4JonUUe812IXY8pDHLLj8b20/yCvNupnt0WUd2Zy6Z7/alrBdA5279hrtJnFk3 9jA/RKmVe2uCR2Idc5ytL0DtF3jh7vUYHnxAq9nTeHzmQRmBY7zfQSw8Q9FeEFxzCvnI LWm4sMcf4Va9ZbQxz+F9Xzdj9geQjboTuZp97B5s4XgLP0rHvn+48oCoR5Ypv7l0eqxz YYSA==
X-Gm-Message-State: AGi0Puaow2TvVNI4SVEu2HRpmbuRmphYKUr3CxMVjgB0nFw5Vmv8nVHx 1b6x1Nk8srcBvgr1N3GEj5siS7x8FsMbjSstyNrBVbLK
X-Google-Smtp-Source: APiQypKR0k+54jDY/lGLuyUZ5N3jA16ar6MJSw9jODxgrT5KrDOI/n5+zOazYEPkIRLwEK5W9rGR4qXJHleoAA4xNn4=
X-Received: by 2002:a1c:4b16:: with SMTP id y22mr11472938wma.170.1587573088321; Wed, 22 Apr 2020 09:31:28 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 22 Apr 2020 09:31:27 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <3FC2341A-4760-4129-9DE3-536515C2FC6F@cooperw.in>
References: <158756317450.27447.7394258570701485593@ietfa.amsl.com> <CAMMESswTW_C_wB2g4ADVwDk872PuZqGK=ycnq1QKs4zyu3xTKw@mail.gmail.com> <2316B33C-8C79-4A23-B126-5B4D6EB11FBC@cooperw.in> <006201d618be$03e4afa0$0bae0ee0$@ndzh.com> <3FC2341A-4760-4129-9DE3-536515C2FC6F@cooperw.in>
MIME-Version: 1.0
Date: Wed, 22 Apr 2020 09:31:27 -0700
Message-ID: <CAMMESsymEAPmHmVBb=AjTcOqprdGvWWZAQiBja47rmddG6ephw@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>, Susan Hares <shares@ndzh.com>
Cc: idr-chairs@ietf.org, draft-ietf-idr-rfc5575bis@ietf.org, IESG <iesg@ietf.org>, idr@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fc050305a3e3a9e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/k7GHmrwgI0bHOpltnzFElA2R984>
Subject: Re: [Idr] Alissa Cooper's Discuss on draft-ietf-idr-rfc5575bis-22: (with DISCUSS)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Apr 2020 16:31:33 -0000

Works for me too.

Thanks!

Alvaro.

On April 22, 2020 at 11:56:33 AM, Alissa Cooper (alissa@cooperw.in) wrote:

Works for me. Thanks.
Alissa

> On Apr 22, 2020, at 11:52 AM, Susan Hares <shares@ndzh.com> wrote:
>
> Alissa and Alvaro:
>
> Alissa discuss is correct.
>
> My solution to fix this is to provide the following revisions:
>
> Section 7.1:
> Old/
> Interferes with: No other BGP Flow Specification Traffic Filtering
> Action in this document.
> /
> New/
> Interferes with: May interfere with the traffic-rate-packets (see section
7.2).
> Policy may allow both filtering by traffic-rate-packets and
traffic-rate-bytes.
> If policy does not allow this, these two actions will conflict.
> /
> Section 7.2
> Old/
> Interferes with: No other BGP Flow Specification Traffic Filtering
> Action in this document.
> /
> Interferes with: May interfere with the traffic-rate-bytes (see section
7.1)
> Policy may allow both filtering by traffic-rate-packets and
traffic-rate-bytes.
> If policy does not allow this, these two actions will conflict.
> /
>
> If this fix is acceptable to both of you, please let me know. We will
re-spin the draft.
>
> Sue Hares
>
>
> -----Original Message-----
> From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Alissa Cooper
> Sent: Wednesday, April 22, 2020 10:03 AM
> To: Alvaro Retana
> Cc: draft-ietf-idr-rfc5575bis@ietf.org; idr-chairs@ietf.org; idr@ietf.org;
IESG
> Subject: Re: [Idr] Alissa Cooper's Discuss on
draft-ietf-idr-rfc5575bis-22: (with DISCUSS)
>
> Hi Alvaro,
>
>> On Apr 22, 2020, at 9:53 AM, Alvaro Retana <aretana.ietf@gmail.com>
wrote:
>>
>> On April 22, 2020 at 9:46:15 AM, Alissa Cooper wrote:
>>
>>
>> Alissa:
>>
>> Hi!
>>
>>
>>> ---------------------------------------------------------------------
>>> -
>>> DISCUSS:
>>> ---------------------------------------------------------------------
>>> -
>>>
>>> Apologies as this may be a really silly question, but isn't it
>>> possible for traffic-rate-bytes and traffic-rate-packets to interfere
with each other?
>>> That is, if by mistake a flow specification shows up containing both
>>> actions and they contradict each other (e.g., 0 bytes but 1M
>>> packets), how is that situation supposed to be handled?
>>
>> See §7.7. It is left to the implementation to decide which filtering
>> action to use.
>
> Right, but 7.1 and 7.2 say that traffic-rate-bytes and
traffic-rate-packets don’t interfere with each other (or any other
filtering actions specified), so presumably 7.7 does not apply?
>
> Alissa
>
>>
>>
>> Alvaro.
>
> _______________________________________________
> Idr mailing list
> Idr@ietf.org
> https://www.ietf.org/mailman/listinfo/idr
>