IETF Logo Mail Archive

Re: [Lsr] Open issues with Dynamic Flooding

tony.li@tony.li Tue, 05 March 2019 20:59 UTC

Return-Path: <tony1athome@gmail.com>
X-Original-To: lsr@ietfa.amsl.com
Delivered-To: lsr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D57513133B for <lsr@ietfa.amsl.com>; Tue, 5 Mar 2019 12:59:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.881
X-Spam-Level:
X-Spam-Status: No, score=-1.881 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.018, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 6VdJAy0NHrxN for <lsr@ietfa.amsl.com>; Tue, 5 Mar 2019 12:59:14 -0800 (PST)
Received: from mail-pf1-x42c.google.com (mail-pf1-x42c.google.com [IPv6:2607:f8b0:4864:20::42c]) (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 3BBB11312F7 for <lsr@ietf.org>; Tue, 5 Mar 2019 12:59:14 -0800 (PST)
Received: by mail-pf1-x42c.google.com with SMTP id h1so6623766pfo.7 for <lsr@ietf.org>; Tue, 05 Mar 2019 12:59:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=1TDxqV2PJwjQuRxr8DLxZmPyffV2gWElNv5wHzud0so=; b=LOzJpcLfxVT0oa8g5DxyLb6vUtHUbih7DvDbDQcUKGjima436+XdxKCU6wN8UK8eZh 4x8Hxr4s97N9PCEw5F/aYEgf5ZQ4rmSBxL3wtRLv7PjvJzSWW5jAnc+3ewNY7cb0mV/a Trgb7+kGyTFlNDRzfEdwrsBrl3iqaj8SvFl4Cen2bbtigiZ4F7nlQOV+ZdgPLhxvfsYX YqHQ2/G7IGOjribVe5RxlLs1QAP8mftGBIthWgaHiydYk8SgJBZ0f0kXlxXwO53UV+Ol 6b6/0l/qmH1x4CqCFgbngmjo+pK53BHfoJjTj7mqpsopuzw0tD/WSEpx2W9cYJQmGr3J CDLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:mime-version:subject:from:in-reply-to :date:cc:content-transfer-encoding:message-id:references:to; bh=1TDxqV2PJwjQuRxr8DLxZmPyffV2gWElNv5wHzud0so=; b=emknfvQLGNdCrw82I2m69DyLmvWvh4X3JjmBFUnIPn77J5R+k9sheXV4FBC3ccfj0G O/GhkBSShKwdh2T7icYKwJvYuGOHrDtZ0pSANVrJBJyrc+T/gxWFKEIuMMDXVStEImKz X/TNG8NjT5EPkno/GAtCICaOuhsJXfU2JUZW9vRc//4h+h8fjeiLx6hVkAEyqSSW9fOq XcFc3wbMCURG3asYRXAPBuK7zDW0iBNQo3fTid4Z5XjfysliGrMSI3u+D25j6ife1aYH TIZeC8Ey6CSwitMddec/580F0/V3vNeK0ca8DBdTRcRpNUZJ+FXa/VY8Gn0owTkJ3fV8 MTGQ==
X-Gm-Message-State: APjAAAUR12ES8sueILLtA510bJPYvg/PIH9+n/I8ShEyoevmm7ZAc4aa hyeF6TUD3FRQWvQbsXpdvao=
X-Google-Smtp-Source: APXvYqxo0dbEYRA7eimO7+Igi6lgmxCbQxXqgkdhGUlLqBFWxHgemoCFePpCXUlYzyxGoXOUWWta7Q==
X-Received: by 2002:a62:1b92:: with SMTP id b140mr3783486pfb.159.1551819553564; Tue, 05 Mar 2019 12:59:13 -0800 (PST)
Received: from [172.22.228.48] ([162.210.130.3]) by smtp.gmail.com with ESMTPSA id h87sm19293753pfj.20.2019.03.05.12.59.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 05 Mar 2019 12:59:12 -0800 (PST)
Sender: Tony Li <tony1athome@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
From: tony.li@tony.li
In-Reply-To: <BYAPR15MB30787A962F99F58CC955C79ED0720@BYAPR15MB3078.namprd15.prod.outlook.com>
Date: Tue, 05 Mar 2019 12:59:12 -0800
Cc: Peter Psenak <ppsenak@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <B6A321F8-C485-4D29-A2DE-7CEAB149296B@tony.li>
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li> <c1adac3a-cd4b-130e-d225-a5f40bf0ef55@cisco.com> <F3C4B9B2-F101-4E28-8928-9208D5EBAF99@tony.li> <be28dbcf-8382-329a-229f-5b146538fabe@cisco.com> <966E5756-8CEF-47F4-8564-E23D38F0743E@tony.li> <c8f40acb-94fe-f42a-aa0a-3a42e0067be8@cisco.com> <BYAPR15MB30787A962F99F58CC955C79ED0720@BYAPR15MB3078.namprd15.prod.outlook.com>
To: David Allan I <david.i.allan@ericsson.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/tHgBGthRt3e0v4tA_xvflnXtWkU>
Subject: Re: [Lsr] Open issues with Dynamic Flooding
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <lsr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lsr>, <mailto:lsr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lsr/>
List-Post: <mailto:lsr@ietf.org>
List-Help: <mailto:lsr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lsr>, <mailto:lsr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Mar 2019 20:59:16 -0000

Hi Dave,

> My understanding of this whole endeavor is that:
> 
> - excessive flooding slows convergence
> - so we are seeking to define a reduced flooding topology
> - a failure that does not impact an FT adjacency is propagated throughout the topology and the effects of excessive flooding have been eliminated.... great.
> - a failure that does impact the flooding topology results in the topology trying to mend itself and slowing down convergence while at it.....potentially by a significant amount
> - And the current discussion is headed in the direction of what is the right heuristic to deal with this...
> 
> Do I have this right?

Close.

More specifically, if there is a multiple failure that partitions the FT, how do we repair it?  Fast or safe? Choose one. 

Tony

v2.23.0 | Report a Bug | By Email