Re: [Lsr] Open issues with Dynamic Flooding

tony.li@tony.li Mon, 01 April 2019 17:37 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 05A1D120139 for <lsr@ietfa.amsl.com>; Mon, 1 Apr 2019 10:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Level:
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 08ytK4PzcBGg for <lsr@ietfa.amsl.com>; Mon, 1 Apr 2019 10:37:34 -0700 (PDT)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 9D17D120075 for <lsr@ietf.org>; Mon, 1 Apr 2019 10:37:34 -0700 (PDT)
Received: by mail-pl1-x635.google.com with SMTP id p19so4844623plo.2 for <lsr@ietf.org>; Mon, 01 Apr 2019 10:37:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:content-transfer-encoding:mime-version:subject:date :references:to:in-reply-to:message-id; bh=Sh8Eked02Wb8Zfkc6swS2U2in2FzOsZRzIjWKF4syKY=; b=teWAAOMRzI6C5PIPPNabH7DhrCY1STTOwr/Hf64M8kKnTtoSFD5+Kj+ibKXcGPfew6 z1ob+MgkJDk1JMGOOZLaizZTuHIbolX5u1kWrIp0rEsZyY5NchcD/xsngzulCpWA49ft /Ot1RMHxI/bWeAf2M39II5//FQyhCa0lMGeohXDfJYsgj9viInnvG5kAKAsDnlwf4Zte mlv4kCkg+k8OnYdf91/xmZo/4cuhXVysgnDS/ECab3/8xx2+CWy++QFxAEU/Fd8TMfi7 ycdNOJklWMMIU0CQZogPwM3DGmMHk+TC4xlWh/US78Ww1IJ0VtAVtyQyhImUzpKexCFX hxTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:content-transfer-encoding :mime-version:subject:date:references:to:in-reply-to:message-id; bh=Sh8Eked02Wb8Zfkc6swS2U2in2FzOsZRzIjWKF4syKY=; b=nJJ37Ss4T9EYZlxrZGxuSoFqXFETEC4i0PXaOpZlwcGYSHA3gY2+YOt1/XvMO+f5ws f8ZO1CVDK5xCYRho0kkP83o09uccabxRc8xQtGhwyA9FV/iPP5OxMDgTuJuW9l9e0CkM d/D4UYBRG13hje9Mb5u+RGq5MEFGXw7tLGSeT6FcjokbCD2tnYrS1tqcayXhQWetHa5p lCIcubvIER5WJ+D1+BJeOfit8ZG3Y+TdOHJNtQPvxW4tgtM3Jz+5dDReiKMbh2JBZuXa vbbI2jT1zGf962CQ9bpkp7llbGAY/J4itd0SY8IHeYA0PXWlddACW7GnHVT3BFm7whSI wtOQ==
X-Gm-Message-State: APjAAAXfIgaA6ED8BZ0rK6t19cZPpoywxjJfwdQlPXVm7C+Id56r0hnt skLFgSb6kRxnTunDRUB04Zu3stlf
X-Google-Smtp-Source: APXvYqzElgzq1KfmvuURUuN9oRM4NDZev5mvSMsuDGml1/7fcAkQcfC4mUZRM8vjk/lGPz3rUcr2KA==
X-Received: by 2002:a17:902:469:: with SMTP id 96mr63649273ple.46.1554140253889; Mon, 01 Apr 2019 10:37:33 -0700 (PDT)
Received: from [192.168.1.5] (c-73-158-115-137.hsd1.ca.comcast.net. [73.158.115.137]) by smtp.gmail.com with ESMTPSA id j20sm13256075pff.22.2019.04.01.10.37.33 for <lsr@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 01 Apr 2019 10:37:33 -0700 (PDT)
Sender: Tony Li <tony1athome@gmail.com>
From: tony.li@tony.li
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Mon, 01 Apr 2019 10:37:32 -0700
References: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li>
To: lsr@ietf.org
In-Reply-To: <AAD29CF0-F0CA-4C3C-B73A-78CD2573C446@tony.li>
Message-Id: <15C35B7A-6402-4EE3-A85B-5FDCFAA20162@tony.li>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/M6nbCNShJY7yQhLSSjNCMDvkJLc>
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: Mon, 01 Apr 2019 17:37:36 -0000

Hi all,

I hope that everyone had a safe and uneventful trip home from Prague and that no one else had the seat right in front of the screaming baby.  ;-)

I would like to re-open the discussion on the mailing list. Based on the off-line discussions that I had with folks, I believe that we’re leaning towards including the LANs in the signaling and rate limiting link addition during repair.

Dissent? Discussion?

Tony


> On Mar 4, 2019, at 9:54 AM, tony.li@tony.li wrote:
> 
> 
> Hello,
> 
> There are still two issues that need to be discussed and I was hoping that we could make progress on the mailing list before Prague.
> 
> 1) Temporary additions to the flooding topology
> 
>    There are several cases where we would like to make temporary additions to the flooding topology: repairing a partition of the flooding topology or adding a node to the base topology for the first time. We can:
> 
>    (a) Temporarily add all of the links that would appear to remedy the partition. This has the advantage that it is very likely to heal the partition and will do so in the minimal amount of convergence time.
> 
>    (b) For each node adjacent to the partition, add no more than a single link across the partition.  If that does not repair the partition in a while (LSP propagation time + SPF time), then add another link.  
>         Iterate as necessary. This has the advantage that it minimizes the risk of creating a cascade failure.
> 
> 2) Inclusion of pseduonodes in the System IDs TLV
> 
>    In the general case, a topology can include LANs. If a LAN is in parallel with a P2P link, the Area Leader cannot currently distinguish between the two links. This can be of importance if there are other 
>    systems also on the LAN that should be using their LAN interface for flooding.
> 
>    We propose to change the System IDs TLV to include a pseudo-node ID as well as the system ID.  It would also make sense to rename the TLV to be the “IS-IS Area Node IDs TLV”.
> 
>    Behaviorally, we should add a requirement that if the Area Leader includes a pseudonode in the flooding topology, then all systems with an adjacency on that LAN should use the LAN as part of the 
>    flooding topology, whether or not they are explicitly listed as adjacent to the LAN in the Flooding Path TLV.
> 
> Thoughts? Comments? Flames?
> 
> Regards,
> Tony
>