IETF Logo Mail Archive

Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.txt

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Sun, 31 March 2019 23:47 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 5C31F1201A3 for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 16:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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=czZ0x8Fp; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=DbXOzPbD
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 SHHjuYjobDQL for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 16:47:34 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9102A120073 for <lsr@ietf.org>; Sun, 31 Mar 2019 16:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=4364; q=dns/txt; s=iport; t=1554076054; x=1555285654; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=ej5Omyzu+si6mBFEmbZoLXrnOJldlTSGKpY2SrEqT1k=; b=czZ0x8FpnK0OPgF8v0aLys4Pybmzu/scg4GGlFJ5XQTF/4XuQBf0MJX3 S/EFAJ977Sa5Jl6OU1etZahn7O7rZ70iv/Pr/frYuaDmmQAc767aC3YuJ OVsRZRoIm2MUdaSSkJHcoVG2SdwlczCS+DBONux3Pv7aUyN07aHU8Ry1J A=;
IronPort-PHdr: 9a23:9kSexxZIrhsaQ7iAL6B3Bcr/LSx94ef9IxIV55w7irlHbqWk+dH4MVfC4el20gabRp3VvvRDjeee87vtX2AN+96giDgDa9QNMn1NksAKh0olCc+BB1f8KavlbiohFslYW3du/mqwNg5eH8OtL1A=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AEAADGUKFc/4MNJK1jGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBPVADaHQECyeEDoNHA4RSimBKgg2JOI1XgS6BJANUDgEBGAsJhEACF4UgIjQJDQEBAwEBCQEDAm0cDIVKAQEBBAEBIREMAQEsCQMLBAIBBgIRBAEBAwImAgICHwYLFQgIAgQBEgiDG4FdAxUBAgyMSJBeAooUcYEvgnkBAQWBNQIOQYJzDQuCDAiBCyQBizIXgUA/gRBHgkw+ghpHAQECAQGBXySCZDGCJopcgieEQZNTNgkCh2+IL4NaggNdhS+MHYs/hhGBPIwBAgQCBAUCDgEBBYFNOIFWcBUaIYJsCYIBg26FFIU/coEojzMBAQ
X-IronPort-AV: E=Sophos;i="5.60,294,1549929600"; d="scan'208";a="323459095"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 31 Mar 2019 23:47:32 +0000
Received: from XCH-RCD-017.cisco.com (xch-rcd-017.cisco.com [173.37.102.27]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x2VNlWQY023518 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 31 Mar 2019 23:47:32 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-017.cisco.com (173.37.102.27) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 31 Mar 2019 18:47:32 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 31 Mar 2019 19:47:31 -0400
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 31 Mar 2019 18:47:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ej5Omyzu+si6mBFEmbZoLXrnOJldlTSGKpY2SrEqT1k=; b=DbXOzPbDL056yDO2IlQg9JKIQYrw0H7yepBbNY0if8gUMU9FBS2ziTfb8aPJVPneuXDze2DKu7W0vAYIJJj/LCGAU4DuTuHVL0/P9cLaGP5H3HgjIguACwMUlpo9YLz3DMIiw02kyocNZJjVdOG2Z+dYfWe07/Xjd0v69jRJQb4=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3095.namprd11.prod.outlook.com (20.177.227.77) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.17; Sun, 31 Mar 2019 23:47:29 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::28ae:a91c:f4fd:15cb]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::28ae:a91c:f4fd:15cb%4]) with mapi id 15.20.1750.017; Sun, 31 Mar 2019 23:47:29 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "7riw77@gmail.com" <7riw77@gmail.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.txt
Thread-Index: AQLwM/JIkPbzT8Vkdbi80JHv2Wjy+aPvl4FQgAA2U4A=
Date: Sun, 31 Mar 2019 23:47:29 +0000
Message-ID: <BYAPR11MB3638929C928DC680677E182DC1540@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <155406381670.12357.17272312414769230549.idtracker@ietfa.amsl.com> <04bf01d4e7ff$e16d7230$a4485690$@gmail.com>
In-Reply-To: <04bf01d4e7ff$e16d7230$a4485690$@gmail.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: [2001:420:c0c8:1008::92]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0ccb5142-b361-412b-4b88-08d6b6333c6b
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB3095;
x-ms-traffictypediagnostic: BYAPR11MB3095:
x-ms-exchange-purlcount: 6
x-microsoft-antispam-prvs: <BYAPR11MB309562C7AA488F0ED43555C2C1540@BYAPR11MB3095.namprd11.prod.outlook.com>
x-forefront-prvs: 0993689CD1
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(39860400002)(346002)(366004)(376002)(396003)(199004)(189003)(13464003)(81156014)(6436002)(53546011)(478600001)(66574012)(102836004)(110136005)(5660300002)(6506007)(6306002)(256004)(99286004)(966005)(33656002)(106356001)(7696005)(105586002)(55016002)(14454004)(14444005)(53936002)(52536014)(68736007)(9686003)(186003)(15650500001)(8676002)(6116002)(6246003)(2906002)(486006)(76176011)(11346002)(8936002)(476003)(305945005)(71190400001)(71200400001)(316002)(7736002)(2501003)(46003)(446003)(81166006)(25786009)(74316002)(86362001)(97736004)(229853002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3095; 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: RjYrApTD7Af8wnU7j2WE8IwVNAhKP+2DTUZQJuxUxYje12uol//LqoB56p3AIyqFuXVeVocS94m1jW45ZFr+X/l3NtOgnxLx5m0W4kxIiXAqmVlG1bTAUhQFPJSGTRgXTG3BG73Hx+S+W9yAs/Aq7QUnKGVeA445WBH917UmJ1Ol6jzQAuzweLpZGnnq/U0/PaLW8yRDNX/1vEkdsOjUdbUiH0oKLWrDtACdZDTSmGsoqUD93IsVud930Ia+cSS6Kvp2YRFVlhGdK+700+0hc7Gux/GtlmQqOkvH3VdVBImrr4HCTE356gAejQ9zJ2dtdMn+ZTtun3wFsk7jcCnsHrXhyVkoXDeEpvzu9N39IzbnqhepxIAyrcDKXXEvtL7BWDbhY4n/p1T0Nc8Iq/KSg2E93YJSri/BQ5lHxRWn8L4=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0ccb5142-b361-412b-4b88-08d6b6333c6b
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Mar 2019 23:47:29.0794 (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: BYAPR11MB3095
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.27, xch-rcd-017.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/W-eK4wbBDSM4qNZ_yyKRUO4SS1s>
Subject: Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.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: Sun, 31 Mar 2019 23:47:38 -0000

Russ -

The WG just went through a lengthy consideration of multiple flooding optimization drafts and selected https://datatracker.ietf.org/doc/draft-ietf-lsr-dynamic-flooding/ as the vehicle for the WG to use to move forward in this area.

It would be good if, in the context of the above, you articulated why it makes sense for the WG to do yet another round of such discussion. 

(Full disclosure: I am a co-author on draft-ietf-lsr-dynamic-flooding - but my question isn't coming from that perspective. )

   Les


> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of 7riw77@gmail.com
> Sent: Sunday, March 31, 2019 1:25 PM
> To: lsr@ietf.org
> Subject: [Lsr] FW: New Version Notification for draft-white-distoptflood-
> 00.txt
> 
> 
> FYI -- I've put just the flooding optimizations from the openfabric work into a
> separate draft and submitted it. I've also modified the wording a bit, as this is
> applicable far beyond data center fabrics.
> 
> 😊 /r
> 
> > -----Original Message-----
> > From: internet-drafts@ietf.org <internet-drafts@ietf.org>
> > Sent: Sunday, March 31, 2019 4:24 PM
> > To: Shawn Zandi <szandi@linkedin.com>; Russ White <russ@riw.us>
> > Subject: New Version Notification for draft-white-distoptflood-00.txt
> >
> >
> > A new version of I-D, draft-white-distoptflood-00.txt has been successfully
> > submitted by Russ White and posted to the IETF repository.
> >
> > Name:		draft-white-distoptflood
> > Revision:	00
> > Title:		IS-IS Optimal Distributed Flooding for Dense Topologies
> > Document date:	2019-03-31
> > Group:		Individual Submission
> > Pages:		13
> > URL:            https://www.ietf.org/internet-drafts/draft-white-distoptflood-
> > 00.txt
> > Status:         https://datatracker.ietf.org/doc/draft-white-distoptflood/
> > Htmlized:       https://tools.ietf.org/html/draft-white-distoptflood-00
> > Htmlized:       https://datatracker.ietf.org/doc/html/draft-white-
> distoptflood
> >
> >
> > Abstract:
> >    Dense topologies, such as data center fabrics based on the Clos and
> >    butterfly fabric topologies.  Flooding mechanisms designed for sparse
> >    topologies, when used in these dense topologies, can result in slower
> >    convergence times and higher resource utilization.  The modifications
> >    to the flooding mechanism in the Intermediate System to Intermediate
> >    System (IS-IS) link state protocol described in this document reduce
> >    resource utilization to a minimum, while increaseing convergence
> >    performance in dense topologies.
> >
> >    Note that a Clos fabric is used as the primary example of a desne
> >    flooding topology throughout this document.  However, the flooding
> >    optimizations described in this document apply to any dense topology.
> >
> >
> >
> >
> > 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.
> >
> > The IETF Secretariat
> 
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email