Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

Peter Psenak <ppsenak@cisco.com> Wed, 06 February 2019 10:11 UTC

Return-Path: <ppsenak@cisco.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 3BCA3124D68 for <lsr@ietfa.amsl.com>; Wed, 6 Feb 2019 02:11:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -19.054
X-Spam-Level:
X-Spam-Status: No, score=-19.054 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 I5VqZfVoYOwQ for <lsr@ietfa.amsl.com>; Wed, 6 Feb 2019 02:11:35 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB86012426E for <lsr@ietf.org>; Wed, 6 Feb 2019 02:11:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2853; q=dns/txt; s=iport; t=1549447894; x=1550657494; h=subject:to:references:cc:from:message-id:date: mime-version:in-reply-to:content-transfer-encoding; bh=PVrE30fGPX9CPDV+sOO6AVoj1rE044FC/rZXzXdyDZw=; b=jfvFAfftrDLGYLV8hzzdOJ/4LTxQNIeDhnPK326PfBBI+C5NevqwiPfG afH3n1HQphizhkE/lId8PHbRmnwbeH5bkVHpAoaJ1Fl6FP4oj2sqLjX70 H1eJiBLPHsdA87nWnFJvMK2GPyq/yo7KNErmNIhP8m5RsHCsm749dBE/e 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AUAADYsVpc/xbLJq1lGQEBAQEBAQEBAQEBAQcBAQEBAQGBVAEBAQEBAQsBAYJpUAEgEieMfIxzJZoKDRgLhEkCgzg3Bg0BAwEBAgEBAm0cDEIBEAGEdgEBAQMBAQEwAQU2CwULCxgnBycfEQYBDAYCAQGDHgGBeQgPrgyFRIR1BYxagUA/gTgMgl+DHgEBgR2GJAKLfpcJCZI8BhmBbIVFgxeIBIoskWiBXCKBVjMaCBsVO4JsiVCBToVAPgMwiHWGBQEB
X-IronPort-AV: E=Sophos;i="5.58,339,1544486400"; d="scan'208";a="9908987"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Feb 2019 10:11:32 +0000
Received: from [10.147.24.60] ([10.147.24.60]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTP id x16ABVrr005626; Wed, 6 Feb 2019 10:11:32 GMT
To: Robert Raszuk <robert@raszuk.net>, Tony Li <tony.li@tony.li>
References: <sa65zu31zqk.fsf@chopps.org> <sa64l9n1yqy.fsf@chopps.org> <CAOj+MMHVzuhfUNB+U_wLZ6M1KSPzJ_UNNAMwO0q5t9N3BoVoyQ@mail.gmail.com> <SG2PR06MB23139237E9A2CB6918C571C2FC6C0@SG2PR06MB2313.apcprd06.prod.outlook.com> <MN2PR15MB34394D9C30E039673757ABEDD06C0@MN2PR15MB3439.namprd15.prod.outlook.com> <5316A0AB3C851246A7CA5758973207D463B462E0@sjceml521-mbx.china.huawei.com> <CAOj+MMEwLFPy_fCLHC7XXCLbaYX=O8wDSpXe4ALUh9L24ZvAGg@mail.gmail.com> <04B9EB6B-AD78-4FFA-A292-9AFC06CDC487@tony.li> <CAOj+MME8=XB17OHVChnjes3-Z=-RCpEyLoVHrHjQnEKGQS_wPA@mail.gmail.com>
Cc: Huaimo Chen <huaimo.chen@huawei.com>, "chopps@chopps.org" <chopps@chopps.org>, David Allan I <david.i.allan@ericsson.com>, "li_zhenqiang@hotmail.com" <li_zhenqiang@hotmail.com>, "lsr@ietf.org" <lsr@ietf.org>
From: Peter Psenak <ppsenak@cisco.com>
Message-ID: <3d2c42f5-749d-0861-7fa5-8e9cecf5e8c9@cisco.com>
Date: Wed, 06 Feb 2019 11:11:31 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAOj+MME8=XB17OHVChnjes3-Z=-RCpEyLoVHrHjQnEKGQS_wPA@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Outbound-SMTP-Client: 10.147.24.60, [10.147.24.60]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/m4B3FVtO04O7d_UPbIp5tOdLhJ4>
Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]
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: Wed, 06 Feb 2019 10:11:37 -0000

Hi Robert,

On 03/02/2019 21:37 , Robert Raszuk wrote:
>
> I fully agree and support proceeding with  draft-li-dyanmic-flooding and
> to include protocol extensions in it for centralized topology
> propagation as well as basic hooks like "execute dynamic protocol number
> X" for distributed calculations.
>
> However one may observe that separate distributed algorithms may define
> their own protocol extensions and they should not break the above in any
> way.
>
> Then there is already some requirements of building two disjoined
> topologies in any rich ECMP DC fabric one say for primary paths the
> other for backup flows. (Case of active-active dual streaming
> applications). Question arises if this would be addressed also as part
> of basic spec, be combined with one or many of distributed algorithms or
> will require yet one more document which in turn will "extend" all of
> the above ?

primary/backup topologies are used for transmitting user data, not 
necessarily the flooding data. I don't see how they are related to the 
flooding topology, which is used for flooding only.

To the point, if a new distributed algorithm is defined that needs more 
data to be signaled, then we will extend the existing signaling. I don't 
see that being a problem. The way the signaling is defined in 
draft-li-lsr-dynamic-flooding does allow for such thing.

thanks,
Peter

> And before anyone suggests multi instance approach with
> logical or physical link separation it is not the right direction here.
> If anything perhaps MTR or SR come a bit closer.
>
> Kind regards,
> Robert.
>
>
> On Sun, Feb 3, 2019 at 9:14 PM <tony.li@tony.li
> <mailto:tony.li@tony.li>> wrote:
>
>
>     I think that this discussion would be greatly clarified if we
>     clearly separated the discussion between
>
>     a) the algorithm for computing the flooding topology, and
>     b) the signaling to indicate how to proceed.
>
>     I think that we are all in agreement that the algorithms can and
>     should be separated from the signaling.
>
>     I think that we are all in agreement that each algorithm should be
>     independent.
>
>     I’m of the opinion that the centralized signaling is a bit more
>     extensive than the signaling for the distributed mode, but that
>     there is also considerable overlap and that things would
>     be unnecessarily redundant if we were to separate them. I believe
>     that we are not in disagreement about the basics for the distributed
>     signaling.
>
>     If you disagree with this, please clearly articulate why you feel
>     the signaling should be separated.
>
>     Regards,
>     Tony
>
>
>
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr
>