IETF Logo Mail Archive

Re: [GROW] Handling of LAGs in Mitigating Negative Impact of Maintenance through BGP Session Culling

Job Snijders <job@instituut.net> Mon, 15 January 2018 18:34 UTC

Return-Path: <job@instituut.net>
X-Original-To: grow@ietfa.amsl.com
Delivered-To: grow@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85A0912EB42 for <grow@ietfa.amsl.com>; Mon, 15 Jan 2018 10:34:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, 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=instituut-net.20150623.gappssmtp.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 f5_s6bm53jT7 for <grow@ietfa.amsl.com>; Mon, 15 Jan 2018 10:34:13 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (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 6DB7A12EB3E for <grow@ietf.org>; Mon, 15 Jan 2018 10:34:12 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id i186so3632527wmi.4 for <grow@ietf.org>; Mon, 15 Jan 2018 10:34:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=instituut-net.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=aTCfFonVz41TRVj0PLHXcnKjmorM0XJYhkxtwLwQd6c=; b=Bs6fsAHm+dYCz5lC1tWOMfabwLGU8zPD16Zo/jZD6u2qC+4MCiW/ms8/lv2l/uG38E 2FvUbnFaBBob7cr3U1Is4U5pO9qHGef6vLC2c6eT/1/IN3P/2DoWC7kpY2ai+TkUzCzm WCdvmAsRGyEexVK3IRmkV/olZgoVXROAi3j/8qifY0GDHvY536qjlLaoaI31197GSqR9 4ugoRKzlAACnTuJMWdMbr35JfM1ee9DmQ3jxTuphl4OGApYV/Awv4TrGMkMc9goZoPpy FbeDV4SJN84X6QTMkD21fTdI07QEqf8Qp4Qq4xyQpKkoUAR4mAXbwqFDiK69/pQb2/M/ cvtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=aTCfFonVz41TRVj0PLHXcnKjmorM0XJYhkxtwLwQd6c=; b=alWrsMuvhJZl+alz3Pygt8ArQHu7ux/ckYFIT/NP7wWsTNNDEki/6vm59UU2CoG0N1 ITSNHjmKsvdfHlkEOtEAy7Ntn8+3HkR05UWxIXinUUaBrRuyYyHccYETUOqVruReFBWX KWbRIsf80eIjSRyrKqCpuSK+WXMMR00ZiFbvqMZtLWX3gnR4FHwqu9yO1qi/ZMA7JehV 8qKumZG+PDS9/5MNlbS7UXl3fouAiXGjQbB6TMZRxTMxwjSPRBDQm8Pg+bx01JPoWw14 qLdPA28lBfEBdMjy/3cQk0qplJnWPIQxCbqANOiIJFPJfdnmOMOfkk8ih2Xj5Tqav6+6 XlHQ==
X-Gm-Message-State: AKwxytfxJXJ6vzeEU9imSbV6jNk8eOPruvaVpLs+A4KRBxJFSmrkfvj+ 1Hh1Zp/QeZ8Dl2s6rUnaPOEHMw==
X-Google-Smtp-Source: ACJfBosVOmXWFjCWmHBKvcbizqfceVUIxuG7EpQI66NCf/2nedqu9E+h7IaWDiNC4yMP+tVqlz3s2w==
X-Received: by 10.80.196.3 with SMTP id v3mr10009091edf.232.1516041250862; Mon, 15 Jan 2018 10:34:10 -0800 (PST)
Received: from vurt.meerval.net (vurt.meerval.net. [192.147.168.22]) by smtp.gmail.com with ESMTPSA id w17sm260361eda.96.2018.01.15.10.34.09 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 15 Jan 2018 10:34:10 -0800 (PST)
Received: from localhost (vurt.meerval.net [local]) by vurt.meerval.net (OpenSMTPD) with ESMTPA id 339f6616; Mon, 15 Jan 2018 18:34:09 +0000 (UTC)
Date: Mon, 15 Jan 2018 18:34:09 +0000
From: Job Snijders <job@instituut.net>
To: Thomas King <thomas.king@de-cix.net>
Cc: Will Hargrave <will@harg.net>, "grow@ietf.org" <grow@ietf.org>, "draft-ietf-grow-bgp-session-culling@ietf.org" <draft-ietf-grow-bgp-session-culling@ietf.org>
Message-ID: <20180115183409.GL33439@vurt.meerval.net>
References: <8BB20DB3-61E9-4CAC-B33B-B18CA12C2591@de-cix.net> <20180109113506.GA99435@vurt.meerval.net> <53E19D26-D4C0-4722-8CFE-FDC5BF5C3FBC@harg.net> <20180109155039.GD59807@vurt.meerval.net> <DF40EDF7-DFF4-44EA-AF7E-A41552E5400A@de-cix.net> <2EE7BDAB-095C-4D09-B51C-44CFBA48B6FF@de-cix.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <2EE7BDAB-095C-4D09-B51C-44CFBA48B6FF@de-cix.net>
X-Clacks-Overhead: GNU Terry Pratchett
User-Agent: Mutt/1.9.2 (2017-12-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/d0hGUenRP6MkmM-awFqR1ap87Ys>
Subject: Re: [GROW] Handling of LAGs in Mitigating Negative Impact of Maintenance through BGP Session Culling
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 15 Jan 2018 18:34:14 -0000

On Mon, Jan 15, 2018 at 06:11:26PM +0000, Thomas King wrote:
> any update on this?

Hi Thomas,

I hope you realize that pulling the culling document out of the RFC
editor queue, and going again through GROW, IETF and IESG review, is a
very significant amount of work you'd be dumping in our laps. I'm not
sure I'd agree to that. :-)

In my January 9th message https://mailarchive.ietf.org/arch/msg/grow/1H30kxE7e1QN_5bRi3EfOoX9d-U
I mentioned that perhaps a next revision of the BCP can include text
specific to Multi-Chassis LAGs. You are free to propose text for the
next revision, you have not done so yet. I recommend that any proposed
text is based on actual operational experience with the combination of
'culling' and 'MC LAG'.

I indicated that your organisation appears to be in the early stages of
applying the 'culling' mechanism. I recommend you to carefully take
notes on the interaction between LAG and culling, and whatever arises as
the best practise, can maybe be documented in the next revision of the BCP.

Kind regards,

Job

v2.23.0 | Report a Bug | By Email