IETF Logo Mail Archive

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

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 01 April 2019 01: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 65CD91200EC for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 18:55:55 -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_HIGH=-0.001, 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, URIBL_BLOCKED=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=TMLHRzMH; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=T8heZAF/
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 x4L5q64DtxQh for <lsr@ietfa.amsl.com>; Sun, 31 Mar 2019 18:55:53 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 208C812006F for <lsr@ietf.org>; Sun, 31 Mar 2019 18:55:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2710; q=dns/txt; s=iport; t=1554083753; x=1555293353; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=XtH8IJfwIKl3DNjvZ9rwwKEWTWKwPSCXM3vIgu/IGTU=; b=TMLHRzMH9Hd20elAuiAEmuhDIELqox70dVKBtoy6KefQvbOlk5kvWJ/i 8IIeZ7/9MI4kqzYBI7euE1sxSiJXD6piF8aozi06uvfLZS6O2hpGEhDWN xCoUYx+XShzedEpp9+GiAA3UjF9SQ5bhW8SjvfEmyxKRzCOjRR8QrrJ2+ w=;
IronPort-PHdr: 9a23:koWaPRIwangoctirENmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeBvKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXEL6KuXgYjY1NM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAAB5bqFc/5FdJa1jGwEBAQEDAQEBBwMBAQGBUQYBAQELAYE9UANodAQLJ4QOg0cDhFKKYIJXiTiNV4EugSQDVA4BARgLCYRAAheFICI0CQ0BAQMBAQkBAwJtHAyFSgEBAQEDAQEhEQwBASwJAwsEAgEGAhEEAQEDAiYCAgIfBgsVCAgCBAESCIMbgV0DFQECDIw1kF4CihRxgS+CeQEBBYFFQYJzDQuCDAMFgQskAYsyF4FAP4FXgkw+ghpHAQECAQGBX4MIMYImjQOLdoweNgkCh2+IL4NaggOGDIwdiz+GEYE8jAECBAIEBQIOAQEFgU04gVZwFTuCbIIKg26FFIU/coEojzMBAQ
X-IronPort-AV: E=Sophos;i="5.60,294,1549929600"; d="scan'208";a="252963581"
Received: from rcdn-core-9.cisco.com ([173.37.93.145]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Apr 2019 01:55:51 +0000
Received: from XCH-ALN-008.cisco.com (xch-aln-008.cisco.com [173.36.7.18]) by rcdn-core-9.cisco.com (8.15.2/8.15.2) with ESMTPS id x311tpqY017777 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Apr 2019 01:55:51 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-ALN-008.cisco.com (173.36.7.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 31 Mar 2019 20:55:50 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Sun, 31 Mar 2019 20:55:50 -0500
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Sun, 31 Mar 2019 20:55:50 -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=XtH8IJfwIKl3DNjvZ9rwwKEWTWKwPSCXM3vIgu/IGTU=; b=T8heZAF/ue/9zmXp2agUTnL8rBboxR+T3NmSV41Jc5xyVbEBu+PEcTnR9lJlQHU6VwVAG2zidDF03Ah8vdyhILrBLqyB8L0UcZyEks1UO2GcjhvUYAdbt9Oz2SowsPQl/vAitVHIB7es0TH1nDq+mtx76+Q54vSzoNgE8W+D2zA=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3526.namprd11.prod.outlook.com (20.177.227.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.20; Mon, 1 Apr 2019 01:55:49 +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; Mon, 1 Apr 2019 01:55:49 +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+aPvl4FQgAA2U4CAABvKAIAACRpw
Date: Mon, 01 Apr 2019 01:55:49 +0000
Message-ID: <BYAPR11MB36389F54D29EC92B1E5E9BB3C1550@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <155406381670.12357.17272312414769230549.idtracker@ietfa.amsl.com> <04bf01d4e7ff$e16d7230$a4485690$@gmail.com> <BYAPR11MB3638929C928DC680677E182DC1540@BYAPR11MB3638.namprd11.prod.outlook.com> <073101d4e828$c2209c80$4661d580$@gmail.com>
In-Reply-To: <073101d4e828$c2209c80$4661d580$@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: 539b4fe0-e868-4d6b-cc57-08d6b6452a59
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(5600139)(711020)(4605104)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB3526;
x-ms-traffictypediagnostic: BYAPR11MB3526:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <BYAPR11MB35267109A47B3A0C439FB513C1550@BYAPR11MB3526.namprd11.prod.outlook.com>
x-forefront-prvs: 0994F5E0C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(396003)(39860400002)(136003)(376002)(346002)(199004)(189003)(13464003)(14454004)(99286004)(316002)(478600001)(2501003)(2906002)(97736004)(7736002)(6246003)(33656002)(25786009)(52536014)(106356001)(53936002)(966005)(55016002)(6306002)(9686003)(8936002)(7696005)(81166006)(81156014)(8676002)(5660300002)(6116002)(46003)(93886005)(476003)(11346002)(71200400001)(71190400001)(6506007)(53546011)(446003)(102836004)(186003)(256004)(105586002)(486006)(68736007)(14444005)(15650500001)(76176011)(86362001)(74316002)(229853002)(110136005)(305945005)(6436002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3526; 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: rREzQxJ9UlC1Tz0CeDVzXd39vO2swQ2H1y83rVMcQ6gTeDP2Ajy9dj7HA3q/0+QrLhdSNWX2odVMkOr3P/igAVproriZ8KuqEi9ci6B2wSkNvZ7KhF1bS8x2Dglv5xj+ds6o+osInoBpR6VdSYAQy0HFIzkW2OuMWMNGUW1+MWMs0K+5ERVVL1oFRzLYpw/UX283gmDivmlnX+nBrGFltaZleJxPhOg4jYA2TDB6IsxoCDI0YnWWL0vpb62tlUqmlQOvmbOhVrQ4WqY94o5PphOrWynSfc0ORgn/4pZ77ybwrJWqa0Kr7fip2UMvKvsI7BjudHaFz9tHJE23bjGbq8KYWAGeOayL7RUxeKX2wRh7rfEy27pbF5lI52I93JInTjsJfjS+/7MI5cqnPBJZ/ZM0MCi/5lSoK478aB+MGl8=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 539b4fe0-e868-4d6b-cc57-08d6b6452a59
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2019 01:55:49.7769 (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: BYAPR11MB3526
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.18, xch-aln-008.cisco.com
X-Outbound-Node: rcdn-core-9.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/eYoPlKtE4WJLvbfx7WnomftYQV8>
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: Mon, 01 Apr 2019 01:55:56 -0000

Russ -

Please state explicitly whether you want:

a)This draft to be considered by the WG in addition to draft-ietf-lsr-dynamic-flooding (i.e., we should work on both drafts in parallel)

b)This draft to be considered as a replacement for draft-ietf-lsr-dynamic-flooding (i.e., we should abandon work on draft-ietf-lsr-dynamic-flooding and instead work on this draft)

c)You want the ideas articulated in this draft to be incorporated into draft-ietf-lsr-dynamic-flooding

(and please don't say "it doesn't matter" - because it certainly does matter :-) )

Thanx.

   Les


> -----Original Message-----
> From: Lsr <lsr-bounces@ietf.org> On Behalf Of 7riw77@gmail.com
> Sent: Sunday, March 31, 2019 6:18 PM
> To: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; lsr@ietf.org
> Subject: Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-
> 00.txt
> 
> 
> > 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.
> 
> Yep.
> 
> > 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.
> 
> ==
> In this idea, the flooding topology is computed within an IGP area
>    with the dense topology either centrally on an elected node, termed
>    the Area Leader, or in a distributed manner on all nodes that are
>    supporting Dynamic Flooding.
> ==
> 
> Because this is only one way to solve the problem... The process outlined in
> the draft I just published is a different and simpler way that applies to a wider
> range of topologies than the dynamic flooding draft does, afaict.
> 
> 😊 /r
> 
> 
> _______________________________________________
> Lsr mailing list
> Lsr@ietf.org
> https://www.ietf.org/mailman/listinfo/lsr

v2.23.0 | Report a Bug | By Email