Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward
Tony Przygienda <tonysietf@gmail.com> Fri, 24 August 2018 16:56 UTC
Return-Path: <tonysietf@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 8D840130E16 for <lsr@ietfa.amsl.com>; Fri, 24 Aug 2018 09:56:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 nX5cqeOoOx1Q for <lsr@ietfa.amsl.com>; Fri, 24 Aug 2018 09:56:02 -0700 (PDT)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 276D1130DDF for <lsr@ietf.org>; Fri, 24 Aug 2018 09:56:02 -0700 (PDT)
Received: by mail-ed1-x535.google.com with SMTP id p52-v6so6236501eda.12 for <lsr@ietf.org>; Fri, 24 Aug 2018 09:56:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s5Uia4f+MITnw/Fd2900E04ItdMMp3i2SHM63pPEi4g=; b=kPhM6vFfBLTmSJy02WduprqXDjvW2KrdsUHqYZSD6oGRol3kZXq3r/oeYn9xZQW5NF ZL4htEvX4SxxzXE/Uw8N8cqCkiVJK3JbL+WAhl6bONzEqT0vKfz99k9pqyafBbjXDqm3 ZdcDQsqBVJWtzzAAFCw/rWL7XM3uUxSYnKMWDTD+syoC9HrGXzTsZJbluunuJZSRlvil RD3CHTgBeamHq59Ehfk2TLqI9nksAChYKlBf8LmhtiDB0KqZbXfFIv+UEuCD7I4iAXYU n+67s9NS4UwvEZytE/DQaeTq+Zrd/eWueuwIKcgMKi8YG9x8KP/pFW7Wh08cXNxPT7uF eZlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s5Uia4f+MITnw/Fd2900E04ItdMMp3i2SHM63pPEi4g=; b=Pan/6sV3kBMmiyq9RFyDbqKQQSRxpaTyJiA+djNATewSggdE76DG4Yb+NP1Px3TciE TrRXO43E7arZSSVyJ56vjvTAYiVhkImT8yZMZwD6aoloCX8nZEnIuyeoMNpX6L1AObbq a5bPaqlmz4ScHJu+KRxy8Ed8TLPd1IWHKVCDf75WmumebrN8v1b6vrDVvaxEWXobWbkv pdQqe5FLow4RCnKIjCnIHuaqoc+DwwngEzxSwYzDRubB2PCS6/rpaY+Uy0qB08FwJ9Me HfvaNMgDIM2Gi7R1HG2XmkmO2SIN39h+o9kfQoZirb9mk4L3em2HL8yFc8UgoXD57DfL VzaQ==
X-Gm-Message-State: APzg51AHizFJVyJ03zZ+r4gYK4fnAipmCeKErA8AA6FqejP2Rcc13ybx mwH5I3b5E37vZL87vrw/d4bsiKC1KF79Y4usJw4=
X-Google-Smtp-Source: ANB0VdYqrH6krhTSPi75V0rSZUwATsIO6/DzDiacwe/GTPFoVinXPfrTmRPgscNaAh4/9/2jMvm79LSqI9J43IQ4AtA=
X-Received: by 2002:aa7:d707:: with SMTP id t7-v6mr3642623edq.250.1535129760785; Fri, 24 Aug 2018 09:56:00 -0700 (PDT)
MIME-Version: 1.0
References: <8F5D2891-2DD1-4E51-9617-C30FF716E9FB@cisco.com> <C64E476F-1C00-435E-9C74-BEC3053377E8@gmail.com> <2F5FDB3F-ADCA-4DB4-83DA-D2BC3129D2F2@gmail.com> <5B7E78DD.90302@cisco.com> <172728E8-49E6-4F43-9356-815E1F4C22E7@gmail.com> <5B7FCAB3.6040600@cisco.com> <3D1DEC37-ACE7-4412-BB2E-4C441A4E7455@tony.li> <CCF220A3-8308-47B8-8CC6-1989705FF05C@cisco.com> <CA+wi2hNv8AVyR81LRmJ=Pd5_p5rS2djCOjY9YDgKxG=KEO_MkA@mail.gmail.com> <39509D13-4D2D-49A9-8738-C9D1F7C54223@tony.li>
In-Reply-To: <39509D13-4D2D-49A9-8738-C9D1F7C54223@tony.li>
From: Tony Przygienda <tonysietf@gmail.com>
Date: Fri, 24 Aug 2018 09:55:23 -0700
Message-ID: <CA+wi2hPsPQinwL2KL+xZnTYa1dwuw=thKjq_ddHnJQNnr19ugg@mail.gmail.com>
To: Tony Li <tony.li@tony.li>
Cc: acee=40cisco.com@dmarc.ietf.org, Peter Psenak <ppsenak@cisco.com>, lsr@ietf.org, Jeff Tantsura <jefftant.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000136a5f05743140ea"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/I8FcIaavaFT8mkgzoAKxEVTOiII>
Subject: Re: [Lsr] LSR Flooding Reduction Drafts - Moving Forward
X-BeenThere: lsr@ietf.org
X-Mailman-Version: 2.1.27
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: Fri, 24 Aug 2018 16:56:05 -0000
Hey Tony, as to miscabling: yepp, the protocol has either to prevent adjacencies coming up or one has to deal with generic topologies. If you don't want to design miscabling prevention/topology ZTP into protocol (like ROLL or RIFT did) you have to deal with generic graph as you say. I think that if you have 99.99% of the time a predictable graph it's easier to restrict wrong cabling than deal with arbitrary topology when tackling this problem but that's my read. Then I get you on the centralized story ;-) But again, if you're willing to restrict the graph then stuff like RIFT distributed solution is implemented and works fine (yes, it took 2 scraps of the approach until Pascal had the flash of intuition fueled by my-bad-ideas how to use MANET concepts in a novel way with hashes). BTW implementation experience there changed bunch of things on what's published in -02 due to interesting effects, that will be put out in -03 ;-) Another observation though would be that if you have a single mesh then centralized controller delay on failure becomes your delay bound how long flooding is disrupted possibly (unless your single covering graph has enough redundancy to deal with single llink failure, but then you're really having two as I suggest ;-). That could get ugly since you'll need make-before-break if installing a new mesh from controller me thinks with a round-trip from possibly a lot of nodes ... Overall, I'm agnostic and watch how things will play out and what people decide needs be done ... > iii) change in one of the vertex lifts > > > Sorry, I don’t understand point iii). > A mildly stuffed (or mathematically concise ;-) way to say that if you have one or two covering graphs (and vertex lift is the more precise word here since "covering graph" can be also an edge lift which is irrelevant here) and one of those subgraphs gets recomputed & distributed (due to failures, changes in some metrics, _whatever_) then this should not lead to disruption. Basically make-before-break as one possible design point, harder to achieve of course in distributed fashion ... > > > > > moreover, I observe that IME ISIS is much more robust under such > optimizations since the CSNPs catch (@ a somehow ugly delay cost) any > corner cases whereas OSPF after IDBE will happily stay out of sync forever > if flooding skips something (that may actually become a reason to introduce > periodic stuff on OSPF to do CSNP equivalent albeit it won't be trivial in > backwards compatible way on my first thought, I was thinking a bit about > cut/snapshot consistency check [in practical terms OSPF hellos could carry > a checksum on the DB headers] but we never have that luxury on a link-state > routing protocol [i.e. we always operate under unbounded epsilon > consistency ;-) and in case of BGP stable oscialltions BTW not even that > ;^} ]). > > Emacs > > And that I cannot parse. Emacs? You want LISP code? But then, Dino may get offended ;-) --- tony
- [Lsr] LSR Flooding Reduction Drafts - Moving Forw… Acee Lindem (acee)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Jeff Tantsura
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Les Ginsberg (ginsberg)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Naiming Shen (naiming)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Les Ginsberg (ginsberg)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Jeff Tantsura
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Jeff Tantsura
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Les Ginsberg (ginsberg)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Dean cheng
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Naiming Shen (naiming)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Dean cheng
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Peter Psenak
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Jeff Tantsura
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Peter Psenak
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Acee Lindem (acee)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Peter Psenak
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Les Ginsberg (ginsberg)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Robert Raszuk
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … John E Drake
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Christian Hopps
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Peter Psenak
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Les Ginsberg (ginsberg)
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Robert Raszuk
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Robert Raszuk
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Tony Przygienda
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- [Lsr] 答复: LSR Flooding Reduction Drafts - Moving … Aijun Wang
- Re: [Lsr] 答复: LSR Flooding Reduction Drafts - Mov… Peter Psenak
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Christian Hopps
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … tony.li
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … John E Drake
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … John E Drake
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … John E Drake
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Huaimo Chen
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … John E Drake
- Re: [Lsr] LSR Flooding Reduction Drafts - Moving … Christian Hopps