Re: [OPSAWG] Mirja Kühlewind's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)

Stewart Bryant <stewart.bryant@gmail.com> Tue, 04 December 2018 12:07 UTC

Return-Path: <stewart.bryant@gmail.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EACE1277C8; Tue, 4 Dec 2018 04:07:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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=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 R4vRKjsbBZci; Tue, 4 Dec 2018 04:07:18 -0800 (PST)
Received: from mail-wr1-x441.google.com (mail-wr1-x441.google.com [IPv6:2a00:1450:4864:20::441]) (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 28E4712872C; Tue, 4 Dec 2018 04:07:18 -0800 (PST)
Received: by mail-wr1-x441.google.com with SMTP id z5so15676144wrt.11; Tue, 04 Dec 2018 04:07:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language; bh=ULP5cBjNdXjlZTXTV21Pg/NX0JzrLKznQ7ofAfFYpvU=; b=hONCcBCCDymPHCWsEMoN8O0RDiIsSnPsos9RI5jHVSGxViJ8NaRo9tez+8eBPUYKQJ kKOHkvteW1d9rrPOKsM80To4RXyOgejqivG7lt+xye3E6Sne3IHg0Ba0iOXKxpLpL8az EOHMCmAjWmZgn1uo9bDn9hkyRsqmvh0g4CJLRsPJSrL9dI+t0FfqVMgQIfjB7aXeQpgc 8seQKRj2fTSZ1n2SH0wFYsjhe5ggNQZQUWHx5vBRhhte5YOji+xXk4HqRsqpSZmq1UQA NiXEfcVogj53Cbg+rg52rNlB/4+HNmjN+0Us8SIejVXM6CuDdMZFrD3eKf2wiEiIEerx 6CcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=ULP5cBjNdXjlZTXTV21Pg/NX0JzrLKznQ7ofAfFYpvU=; b=D+/jTabUNthCLLIC7b/j8ux+gve7OwFBpmpsn+D+bKEasoXPmQTkbgICBtEasOU+GL Q4acdV2WbZFl7hOhOnpiGfX/ThFp9c27RsxmJd87b3wCnDAKBee/zVRdTLfKsLXVrTli Rru4mPR1fPuwle850QCSelfY/MSbwYk2w3nZ8Fzc57GZLLxyQGPWzKnaw3jpXnwSpRUD Qhg4irorhluqeNUZY7H9m9tKGxyj0yb2kHiBwvE8dKf8aDXFer1wN9kMP2xX+RZZeEAd Fmn/UnEEXy/p3g9nzuMDeQFR++D6BrNT04qcaM+1hjT9g1QRZMpklA064O2EE1hrd8Hp L/cg==
X-Gm-Message-State: AA+aEWZIGlTS0nSVPgOSJSxwGdCYr7GbJkU8uYqZxIUozpIj+M4wc3bt wGqJPwOODqMdv2iLIk0zXzgL26J7
X-Google-Smtp-Source: AFSGD/WKX+bekMX6FePmcpH5cLIZYpSpwJsTgFNrjv93OGNHZ5oVRpY+tM5sCNK/JjaJONhdPhPxWA==
X-Received: by 2002:adf:de91:: with SMTP id w17mr19098658wrl.320.1543925236125; Tue, 04 Dec 2018 04:07:16 -0800 (PST)
Received: from [192.168.2.198] (host213-123-124-182.in-addr.btopenworld.com. [213.123.124.182]) by smtp.gmail.com with ESMTPSA id o4sm8624384wmo.29.2018.12.04.04.07.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 04 Dec 2018 04:07:15 -0800 (PST)
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Mirja Kuehlewind <ietf@kuehlewind.net>
Cc: opsawg@ietf.org, opsawg-chairs@ietf.org, IESG <iesg@ietf.org>, draft-ietf-opsawg-ipfix-bgp-community@ietf.org
References: <154359435795.27526.8666145722848127355.idtracker@ietfa.amsl.com> <CAKKJt-fE9-8BPDaXm4e8f9coZQxHnoSZmw-E41z_Huvg43xPew@mail.gmail.com>
From: Stewart Bryant <stewart.bryant@gmail.com>
Message-ID: <637e246f-9ed8-ab29-71d3-7f3ad31b9db6@gmail.com>
Date: Tue, 04 Dec 2018 12:07:13 +0000
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CAKKJt-fE9-8BPDaXm4e8f9coZQxHnoSZmw-E41z_Huvg43xPew@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------10D7FC7458954FDACA1D5DB0"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/eDNP8HiXIeJE5qsgJwBNqzxy4kk>
Subject: Re: [OPSAWG] Mirja Kühlewind's No Objection on draft-ietf-opsawg-ipfix-bgp-community-11: (with COMMENT)
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 Dec 2018 12:07:21 -0000


On 30/11/2018 19:23, Spencer Dawkins at IETF wrote:
> This is Mirja's comment, but ...
>
> On Fri, Nov 30, 2018 at 10:12 AM Mirja Kühlewind <ietf@kuehlewind.net 
> <mailto:ietf@kuehlewind.net>> wrote:
>
>     Mirja Kühlewind has entered the following ballot position for
>     draft-ietf-opsawg-ipfix-bgp-community-11: No Objection
>
>     When responding, please keep the subject line intact and reply to all
>     email addresses included in the To and CC lines. (Feel free to cut
>     this
>     introductory paragraph, however.)
>
>
>     Please refer to
>     https://www.ietf.org/iesg/statement/discuss-criteria.html
>     for more information about IESG DISCUSS and COMMENT positions.
>
>
>     The document, along with other ballot positions, can be found here:
>     https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-bgp-community/
>
>
>
>     ----------------------------------------------------------------------
>     COMMENT:
>     ----------------------------------------------------------------------
>
>     One comment on section 1:
>     "For example, they can shift some flows
>       from congested links to low utilized links through an SDN controller
>        or PCE [RFC4655]."
>     I'm not aware that ipfix information is commonly used for dynamic
>     traffic
>     adaptation and I'm not sure that is recommendable. C
>
>
> I'm agreeing with Mirja here.
>
> We've spent a LOT of time not recommending dynamic traffic adaptation. 
> Probably half my responsibility as AD for ALTO was repeating "you 
> can't react based on changes to that attribute without taking chances 
> on oscillation" like it was a mystical incantation, and I wasn't the 
> first AD to have that conversation repeatedly.

Yes, I understand the ARPA net had exactly that problem at one stage and 
had to be converted from using a delay based metric to a fixed metric.

>
> I would be happy to hear that all those problems are solved, but I 
> haven't heard that yet. Do the right thing, of course.
>
> Even "can shift some flows from persistently congested links to 
> underutilized links" would cause me less heartburn.

There is no such thing as permanent in network paths!

Like many control problems the first order solution is to damp with a 
suitably long time constant, but  infinity, i.e. permanent, is not a 
satisfactory choice either.

- Stewart

>
> Spencer