IETF Logo Mail Archive

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

Thomas King <thomas.king@de-cix.net> Tue, 16 January 2018 14:28 UTC

Return-Path: <thomas.king@de-cix.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 2103413155D; Tue, 16 Jan 2018 06:28:59 -0800 (PST)
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 autolearn_force=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 3e-IPWyiG0uP; Tue, 16 Jan 2018 06:28:57 -0800 (PST)
Received: from de-cix.net (relay3.de-cix.net [46.31.123.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9B16F131560; Tue, 16 Jan 2018 06:28:16 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.46,368,1511823600"; d="scan'208";a="1359766"
Received: from smtp.de-cix.net ([192.168.65.10]) by mailgw013.de-cix.net with ESMTP; 16 Jan 2018 15:28:14 +0100
Received: from MS-EXCHANGE.for-the-inter.net (MS-EXCHANGE.for-the-inter.net [192.168.49.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by smtp.de-cix.net (Postfix) with ESMTPS id 4E67AB00B8; Tue, 16 Jan 2018 15:28:14 +0100 (CET)
Received: from MS-EXCHANGE.for-the-inter.net (192.168.49.2) by MS-EXCHANGE.for-the-inter.net (192.168.49.2) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Tue, 16 Jan 2018 15:28:14 +0100
Received: from MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c]) by MS-EXCHANGE.for-the-inter.net ([fe80::9449:4d85:69bf:3d4c%12]) with mapi id 15.00.1347.000; Tue, 16 Jan 2018 15:28:14 +0100
From: Thomas King <thomas.king@de-cix.net>
To: Job Snijders <job@instituut.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>
Thread-Topic: [GROW] Handling of LAGs in Mitigating Negative Impact of Maintenance through BGP Session Culling
Thread-Index: AQHTiT1EVmpr6uxEKUG4l9q8mMNj9KNrWI6AgABC9QCAAARwgIADlWIAgAYQtAD///WVgIABXmEA
Date: Tue, 16 Jan 2018 14:28:13 +0000
Message-ID: <F5BCB532-0D06-480B-B95B-30AA92062A77@de-cix.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> <20180115183409.GL33439@vurt.meerval.net>
In-Reply-To: <20180115183409.GL33439@vurt.meerval.net>
Accept-Language: en-US, de-DE
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.60.10]
Content-Type: text/plain; charset="utf-8"
Content-ID: <5C5C1D74B756A44F840F8B6717B28FC1@for-the-inter.net>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/grow/QXvkdYpVzumw7OeyCTwQwHcbYrM>
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: Tue, 16 Jan 2018 14:28:59 -0000

Hi Job,

to be clear, my suggestion covers MC-LAGs and more importantly LAGs. Both is missing in the current document. I think the working group should decide if the current document is good to go or whether it is missing important parts and should be revised.

If we as a working group decide to move ahead and add the proposed changes on an update of the BCP I will definitely contribute.

Best regards,
Thomas


On 15.01.18, 19:34, "Job Snijders" <job@instituut.net> wrote:

    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