Re: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Tue, 21 May 2019 17:55 UTC

Return-Path: <ginsberg@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 31763120183 for <lsr@ietfa.amsl.com>; Tue, 21 May 2019 10:55:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 header.b=WkadovU/; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=OrqMNGYs
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 M-YqNM5cBohO for <lsr@ietfa.amsl.com>; Tue, 21 May 2019 10:55:49 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7ABA12002E for <lsr@ietf.org>; Tue, 21 May 2019 10:55:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2929; q=dns/txt; s=iport; t=1558461349; x=1559670949; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=Ob+BQL70rLABYgJ+TabubBXtVTPlsKTm0EMW6YV6Qcw=; b=WkadovU/sz+kGxxzVEXV27VUUvIK/NqLpjeToLeyummVcz/jwZfcSr9s iLuB+qUEl9ftyCnFEY7/vW6/C0sgNktI1JxhhZ+rLWzyh60ltfCr59nBJ C07Mu2fkahC42emZtU8IfDvwvDo0SNjruQvwpnBIVZ2nOUubXtdaacLVZ c=;
IronPort-PHdr: =?us-ascii?q?9a23=3Am+YKVhUyp45MQbOURsHUmijwwlPV8LGuZFwc94?= =?us-ascii?q?YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTF?= =?us-ascii?q?dE7KdehAk8GIiAAEz/IuTtank1HcJZXlJ/8FmwMFNeH4D1YFiB6nA=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BsAAAvOuRc/5ldJa1lHQEBBQEHBQG?= =?us-ascii?q?BUQgBCwGBPVADaVUgBAsoCodQA4RSiiVKgg2XJ4EugSQDVAkBAQEMAQEYDQg?= =?us-ascii?q?CAQGEQAKCJiM0CQ4BAwEBBAEBAgEEbRwBC4VKAQEBBAEBECgGAQEsDAsEAgE?= =?us-ascii?q?IEQQBAR8QJwsdCAIEEwgTB4MBgWoDHQECDJwkAoE1iF+CIIJ5AQEFgTcCDkG?= =?us-ascii?q?CfhiCDwmBNAGLUBeBQD+BEEeCTD6CYQEBAgEBFoFJJIMWgiaoJwkCgg2GLox?= =?us-ascii?q?tgh5nhXSNM4xWhnKOVgIEAgQFAg4BAQWBTziBV3AVGiGCbAmCBoNvhRSFP3K?= =?us-ascii?q?BKYs2KoEHAYEgAQE?=
X-IronPort-AV: E=Sophos;i="5.60,496,1549929600"; d="scan'208";a="274725575"
Received: from rcdn-core-2.cisco.com ([173.37.93.153]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 21 May 2019 17:55:48 +0000
Received: from XCH-ALN-016.cisco.com (xch-aln-016.cisco.com [173.36.7.26]) by rcdn-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id x4LHtmrZ016568 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <lsr@ietf.org>; Tue, 21 May 2019 17:55:48 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-016.cisco.com (173.36.7.26) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 12:55:47 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 21 May 2019 13:55:46 -0400
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 21 May 2019 12:55:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=N/m8ehFeIkaLUuxSkou/M9sPCE+t9TaQB4YS4t2XZis=; b=OrqMNGYsxavIcomCHcixSZfA3i3y6wxoO4FjKLbXE9HBZyIHuoY3NJhW3uC55aZFHCwV0eLwLc83V9dO589cge15VP/0R51s+yGxE2VjBLPVIffVeed2K++KyJIcmEN5dhfruUTb9OCa3F10kYoeyrHhgtu0ntr6kF+MPM0d6ko=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB2709.namprd11.prod.outlook.com (52.135.227.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1900.18; Tue, 21 May 2019 17:55:45 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::ace2:8693:202d:5a30%7]) with mapi id 15.20.1900.020; Tue, 21 May 2019 17:55:45 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
Thread-Index: AQHVD/4rQJfUSYotSEWgNftQU/1D0aZ13IEA
Date: Tue, 21 May 2019 17:55:45 +0000
Message-ID: <BYAPR11MB363825D457A8022006668E24C1070@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <155846121653.2708.1407404790410858156@ietfa.amsl.com>
In-Reply-To: <155846121653.2708.1407404790410858156@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ginsberg@cisco.com;
x-originating-ip: [128.107.241.170]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 5d47186d-d12b-4499-1d7b-08d6de158cd4
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR11MB2709;
x-ms-traffictypediagnostic: BYAPR11MB2709:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <BYAPR11MB2709745E63470E28AEC1808FC1070@BYAPR11MB2709.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0044C17179
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39860400002)(346002)(366004)(376002)(136003)(396003)(199004)(189003)(13464003)(66946007)(73956011)(81166006)(1730700003)(186003)(66476007)(26005)(74316002)(33656002)(64756008)(53936002)(5640700003)(8676002)(81156014)(476003)(8936002)(76116006)(66066001)(446003)(11346002)(66446008)(66556008)(966005)(71200400001)(25786009)(561944003)(316002)(55016002)(256004)(5660300002)(2906002)(52536014)(68736007)(14444005)(71190400001)(6306002)(9686003)(14454004)(7736002)(305945005)(99286004)(6436002)(6116002)(102836004)(86362001)(478600001)(76176011)(6246003)(53546011)(6916009)(66574012)(229853002)(7696005)(3846002)(2351001)(486006)(6506007)(2501003); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2709; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5iLa2Nfpe2y90cCPkgtvuKDUXt3J2ZgBmPAGWGmuzCO96sNnq1xuIznh6ff3oLq0iaFWFROO37vOtD1rdGUde74YVYRuu81ABM4kaglQypGAmeneGvNdrnGwv6nowsEZzl64zBrZ0UBD3VdZKF1YAxMwxhe1WEJityoXRXym912/dEqrqUBqt/8vL7G9+0yXybtKrC4wnlUkp+doGEFTtYfScV3/9Tf6s1Z0nq5JrZ1HKlpV4x40HMDrZgRyyQ8vjzS0yf6ehI0esl5RYTCPHhRtv9irMp/xZ7QcoyogiSNLxu/ct5GigYc8fS02Dd6mhnXz82AaBrX8iYVA0tRXU5RVPJDeHcCOrsNJU7Ld1MbOg6IKjfXRdXxwR74UB70QGJiX1cAwmqVvNG2Va1JT92hg3nkGiU3GPDEe1Fnilco=
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 5d47186d-d12b-4499-1d7b-08d6de158cd4
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 May 2019 17:55:45.5905 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR11MB2709
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.26, xch-aln-016.cisco.com
X-Outbound-Node: rcdn-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/B547ZDu57985lTw5f818AWB4GE4>
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
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, 21 May 2019 17:55:52 -0000

Folks -

Major changes in this version include:

1)Added support for LANs as part of the flooding tropology

2)Added support for advertising what links are enabled for flooding at each node. This is based on a proposal in draft-cc-lsr-flooding-reduction (the FT bit) but we have defined it to be advertised associated with a link rather than in hellos. This is to allow management tools to more easily verify correctness of the flooding topology on each node. It does NOT change operational state in any way.

3)Added some text around rate limiting temporary flooding when attempting to repair a partitioned flooding topology.

    Les


> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org>; On Behalf Of internet-drafts@ietf.org
> Sent: Tuesday, May 21, 2019 10:54 AM
> To: i-d-announce@ietf.org
> Cc: lsr@ietf.org
> Subject: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Link State Routing WG of the IETF.
> 
>         Title           : Dynamic Flooding on Dense Graphs
>         Authors         : Tony Li
>                           Peter Psenak
>                           Les Ginsberg
>                           Tony Przygienda
>                           Dave Cooper
>                           Luay Jalil
>                           Srinath Dontula
> 	Filename        : draft-ietf-lsr-dynamic-flooding-01.txt
> 	Pages           : 47
> 	Date            : 2019-05-21
> 
> Abstract:
>    Routing with link state protocols in dense network topologies can
>    result in sub-optimal convergence times due to the overhead
>    associated with flooding.  This can be addressed by decreasing the
>    flooding topology so that it is less dense.
> 
>    This document discusses the problem in some depth and an
>    architectural solution.  Specific protocol changes for IS-IS, OSPFv2,
>    and OSPFv3 are described in this document.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-lsr-dynamic-flooding/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-lsr-dynamic-flooding-01
> https://datatracker.ietf.org/doc/html/draft-ietf-lsr-dynamic-flooding-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-lsr-dynamic-flooding-01
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr