Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call Wed, 27 May 2020 18:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 461933A0844 for <>; Wed, 27 May 2020 11:40:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.499
X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id YoE0Cuopo7G2 for <>; Wed, 27 May 2020 11:40:46 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:4864:20::1032]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AA0633A083B for <>; Wed, 27 May 2020 11:40:46 -0700 (PDT)
Received: by with SMTP id s69so1986304pjb.4 for <>; Wed, 27 May 2020 11:40:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=sender:from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=yxngyWaQgvUybkiV8xvgcLLcdbKKRGnho8L+D48DHdk=; b=jlzzA+t/XJVlLDnsygKLy/CQVT3EiT6UeEUdZce8xi5p+I1hTO+xzFsQmd4dVmub2o pwDWZlrmBR7C8e1HIY75AYW59Nsa1fJsoXveSyjzPviCcgjqVoQYf6LwZ0+aw8Y1fKJL JuGvfQOmIdGzbttcTB67DKLnqJ6qF8gnCF2oLFGgKeq3YKWXyre8QSIBPQ6uUb39dOOw y2UHhupUSwD3MB2NxpMr+9HSvV8oTWFTfu5rRgn2RSteTHnPtvgA/P8Kl7SnEFYDALN+ dyB0sgJsXEKkIs1eZlNjunV1GmfDYBoUNg91LWgwglIj6uYbUJ8XQQGaBSvZGa75cVm6 v4gw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:sender:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=yxngyWaQgvUybkiV8xvgcLLcdbKKRGnho8L+D48DHdk=; b=f7rnBHfIn751SRhSgqTEwci2sKCnnYELWb78Ywdv96utGHgDdORXJgcHJKu+kBU3UA mQMB227LM72T61WFdZSlchZocd1oDaPbHSmi7xvOa+20hbaSsVhAqHC4dsoHVIPiAI2+ deums3rkSFcEdMfDeU4BC4kmtFHCr/ABOLsM3FE4M42AsoSZMeJsDmgPca4/5IJpwNf8 27WsoouUa/KMKJJ+5NQ+LP8QVTWzozJq7HQwxblbxXyAcpXCF0AVfXX6nRuyNVUYgdkO 9szTLzXuR4HTr1l9KLBxFcoB6m5xaEfpnWNvrf9udwmEDGaDOgNDCZiwaIKtm3zd6Sfl SpbA==
X-Gm-Message-State: AOAM533LMLHShqkJnr/L5WavmKKdRn/dZpNqVGOID4NPWhccSoy1STKD w02TXXSyVZegosaT2TZrZ8Q=
X-Google-Smtp-Source: ABdhPJz2YCVwv75bfpsLrxrZcGtFbIVCgHezdaS/JzgXO+/13DcnXEuTQ+beqQE6bYn4OSDOSd+tsg==
X-Received: by 2002:a17:90a:1a90:: with SMTP id p16mr5973690pjp.185.1590604845152; Wed, 27 May 2020 11:40:45 -0700 (PDT)
Received: from [] ([]) by with ESMTPSA id l23sm2500634pff.80.2020. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 May 2020 11:40:44 -0700 (PDT)
Sender: Tony Li <>
Message-Id: <>
Content-Type: multipart/alternative; boundary="Apple-Mail=_C09BCF24-7921-40D5-A691-1647AF3FD2A0"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
Date: Wed, 27 May 2020 11:40:42 -0700
In-Reply-To: <>
Cc: Gyan Mishra <>, "" <>, Huaimo Chen <>, "Acee Lindem (acee)" <>
To: Les Ginsberg <>
References: <> <> <> <> <> <> <>
X-Mailer: Apple Mail (2.3608.
Archived-At: <>
Subject: Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Link State Routing Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 May 2020 18:40:48 -0000


> We are contemplating submitting a draft for this algorithm to the WG.

We would welcome that.  

Does your algorithm have any relationship to <>

> [Les:] As I understand it, draft-chen only supports centralized mode – which is why it is Informational track and does not have interoperability concerns.
> Sarah/Tony - do you have plans to extend this to support distributed mode and then standardize it?

Not at this time.  As we said during our presentation, we found debugging this already ‘challenging’ and morphing it to be distributed and deterministic in distributed mode doesn’t pass our sense of a beneficial cost/benefit ratio.

We have no objections if others want to take this on.  Centralized mode Just Works.

> And the point of allowing multiple standardized algorithms to be defined was in the expectation that more than one might be proven useful.

Interoperability might also prove useful. :-)