Re: [Idr] WG LC for draft-ietf-bgp-route-oscillation-stop (4/6 to 4/20)

Daniel Walton <dwalton@cumulusnetworks.com> Tue, 21 April 2015 14:42 UTC

Return-Path: <dwalton@cumulusnetworks.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 80D101ACDA9 for <idr@ietfa.amsl.com>; Tue, 21 Apr 2015 07:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 eLNm0esCcF96 for <idr@ietfa.amsl.com>; Tue, 21 Apr 2015 07:42:24 -0700 (PDT)
Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (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 E17CE1ACDB9 for <idr@ietf.org>; Tue, 21 Apr 2015 07:42:21 -0700 (PDT)
Received: by iecrt8 with SMTP id rt8so15234423iec.0 for <idr@ietf.org>; Tue, 21 Apr 2015 07:42:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cumulusnetworks.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+gzFvrh/Aja9Py1bR6LGtR/H5xwa1Uz1xDUZxQ/8eNs=; b=G2q0oxF2A6SLFpS7fnZrSqEJf47oxp/osTnl99RQxi/Gr8s23swRbe01ZCK+7RsBKP zQa7DzTZRU+gfTqcrSHOJMFhCqgyk0SbLbwAFTWODTwlDmDMY2CqBmzl+Ku0YA2A8wfJ wD+EVRktzHtZ1OVHTVVa0NVAydIKqFvILejQ4=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=+gzFvrh/Aja9Py1bR6LGtR/H5xwa1Uz1xDUZxQ/8eNs=; b=fo6DmnpHPQ0Faa/tp2vaGOtVrA5yxMp74cliyUGWYIwdf6OvjPvbntEvaQCd/rw43G sojP76hozyBXxhtMwx7LZZkSOGGqYbg0m1L1KHDDeWj4VBI6aG+yojsrHpAi8wZ5X3HR x2M2aiv2VSPpsdwplnqwrxoWun6xq+6IOkMw3tLZwS5dRTVOZgeZupnYALPTM6e+Ee8v 9GPzN7d0SkifP0hgtZe2pKGgEjkdP19No79Px1q3pVvocojhkZ1G+26ZpbWzq7J0E86o lZTHVZp1GAtzS18nGGI34CIEseR+uNHwfDd/d9WtyUd5DC+cO2ci3cMo0OXu5xA6mWds QScw==
X-Gm-Message-State: ALoCoQny1kKgePSgEW5jilxw6hj36YpUK+IcTqEEoKM3c6Yv8axSqDMlZVHqFN0s8SbqneRmJ3CF
MIME-Version: 1.0
X-Received: by 10.43.12.136 with SMTP id pi8mr3813688icb.6.1429627341401; Tue, 21 Apr 2015 07:42:21 -0700 (PDT)
Received: by 10.107.129.88 with HTTP; Tue, 21 Apr 2015 07:42:21 -0700 (PDT)
In-Reply-To: <001c01d07b26$c2633680$4729a380$@ndzh.com>
References: <002e01d070ba$275479e0$75fd6da0$@ndzh.com> <76CD132C3ADEF848BD84D028D243C92757D07F7F@nkgeml512-mbx.china.huawei.com> <CANL=f0g2A49G4epq+UorPBJMC1niQtA21P+jQzGJNxnUH3TDWA@mail.gmail.com> <001c01d07b26$c2633680$4729a380$@ndzh.com>
Date: Tue, 21 Apr 2015 10:42:21 -0400
Message-ID: <CANL=f0jFVjiem5q7wLZFGvdRzgojvn90ZF0+CtXYwcgnUykZUw@mail.gmail.com>
From: Daniel Walton <dwalton@cumulusnetworks.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary=bcaec518242cd88abb05143d0d45
Archived-At: <http://mailarchive.ietf.org/arch/msg/idr/vxMvpXG0Hk_Mmqb6DyHvXziBZg8>
Cc: dbrungard@att.com, idr wg <idr@ietf.org>
Subject: Re: [Idr] WG LC for draft-ietf-bgp-route-oscillation-stop (4/6 to 4/20)
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 21 Apr 2015 14:42:25 -0000

On Mon, Apr 20, 2015 at 12:59 AM, Susan Hares <shares@ndzh.com> wrote:

> Daniel:
>
>
>
> Do you see any current changes in the churn level?  Have you examined the
> churn inside of a datacenter?
>

Most customers I worked with that hit MED churn were hitting the Type I
variety (details in rfc3345) and solved it by increasing the IGP metrics
between their clusters or confed sub-ASes.  UUNET was the big exception,
they used confederations and were hitting Type II churn but it wasn't
painful enough for them to make changes to stop it as the changes needed
were fairly dramatic. UUNET's churn was one of the big drivers for doing
add-path.

I haven't run into MED churn in the data center yet.  Many of our data
center customers use BGP without an IGP which eliminates one of the
variables needed to cause the churn.

Daniel