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 16:02 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 AD62D1202E4 for <lsr@ietfa.amsl.com>; Mon, 1 Apr 2019 09:02:08 -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=d6wlebp1; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=O7eRQU8q
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 zEXE9zsjpY9V for <lsr@ietfa.amsl.com>; Mon, 1 Apr 2019 09:02:06 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2E4212030C for <lsr@ietf.org>; Mon, 1 Apr 2019 09:00:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2272; q=dns/txt; s=iport; t=1554134453; x=1555344053; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=qOpcqGfDJQtU063jWw78bMs4wTpGe9qOLJgk0KWj060=; b=d6wlebp1pxFeLaoxVEdj5AqSwishFL+QORH84JN4j9faGRPeMvIEwzFD IyEQYqrQuBtNOskO+Yo55EdJrQk35mQQhqkE9BhyEToxFUUq8epnyxyEv wr+aEMvLBkbcaU62GdwCvk2KbK1gowIDYtWa/tQSi4TB2vH+721NT1Ale 8=;
IronPort-PHdr: 9a23:8DoLRBU+E4bY6ke8B3ApiBL+xTLV8LGuZFwc94YnhrRSc6+q45XlOgnF6O5wiEPSA9yJ8OpK3uzRta2oGXcN55qMqjgjSNRNTFdE7KdehAk8GIiAAEz/IuTtank1HcJZXlJ/8FmwMFNeH4D1YFiB6nA=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAABINKJc/40NJK1jGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgT1QA4FcBAsnhA6DRwOEUopggleJOI1XgS4UgRADVA4BASyEQAIXhS0iNAkNAQEDAQEJAQMCbRwMhUoBAQEBAgEjEQwBATUCAQsEAgEIEQQBAQMCJgICAh8RFQgIAgQBDQUIhHgDDQgBAqE2AooUcYEvgnkBAQWEeg0LggwIgQskAYsyF4FAP4FXgkw+ghqCEhqDCDGCJop8ggeLX4w1NgkCkB6DWo05hnOLP4dNjAECBAIEBQIOAQEFgU04gVZwFYMnggqDboNGhw1ygSiPMwEB
X-IronPort-AV: E=Sophos;i="5.60,297,1549929600"; d="scan'208";a="456930070"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 01 Apr 2019 16:00:52 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by alln-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x31G0qrM011101 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 1 Apr 2019 16:00:53 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 11:00:52 -0500
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 1 Apr 2019 11:00:51 -0500
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 1 Apr 2019 12:00:50 -0400
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=qOpcqGfDJQtU063jWw78bMs4wTpGe9qOLJgk0KWj060=; b=O7eRQU8qePpBoFU+zYqKvRp1oucJfotshpSpJV4QRXoFQse+onos8tiyYCn8Wx2DnovjBz9v19i075S1xJLZcQCUZRGUbnbieECxeTZcqs+qJx2bun7bjydtCNDxVtRlFb1Y1DGkdPmLrzgciFLPQQ0dtCSX2IzN2Ma+uOYQsoE=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB2549.namprd11.prod.outlook.com (52.135.226.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1750.22; Mon, 1 Apr 2019 16:00: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 16:00:49 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "tony.li@tony.li" <tony.li@tony.li>, "7riw77@gmail.com" <7riw77@gmail.com>
CC: "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: [Lsr] FW: New Version Notification for draft-white-distoptflood-00.txt
Thread-Index: AQLwM/JIkPbzT8Vkdbi80JHv2Wjy+aPvl4FQgAA2U4CAABvKAIAAY84AgAApq4CAAGRqgIAAA3gA
Date: Mon, 01 Apr 2019 16:00:48 +0000
Message-ID: <BYAPR11MB363804568F36E4045C1AC441C1550@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> <BYAPR11MB363894C676CF19DB5DE35291C1550@BYAPR11MB3638.namprd11.prod.outlook.com> <004601d4e86f$7e744530$7b5ccf90$@gmail.com> <AFA28AD5-1A52-4776-A25F-344B0A0AB151@tony.li>
In-Reply-To: <AFA28AD5-1A52-4776-A25F-344B0A0AB151@tony.li>
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: 1394bab3-25f7-4579-8cfc-08d6b6bb356d
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600139)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BYAPR11MB2549;
x-ms-traffictypediagnostic: BYAPR11MB2549:
x-microsoft-antispam-prvs: <BYAPR11MB2549BD812D6710BAF1797332C1550@BYAPR11MB2549.namprd11.prod.outlook.com>
x-forefront-prvs: 0994F5E0C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(396003)(39860400002)(376002)(346002)(366004)(13464003)(189003)(199004)(71190400001)(71200400001)(93886005)(110136005)(81156014)(81166006)(8676002)(316002)(97736004)(478600001)(6116002)(33656002)(305945005)(14444005)(14454004)(7736002)(256004)(74316002)(99286004)(5660300002)(2906002)(25786009)(52536014)(86362001)(476003)(486006)(6246003)(53936002)(4326008)(53546011)(6506007)(76176011)(186003)(102836004)(7696005)(106356001)(105586002)(446003)(11346002)(2501003)(46003)(15650500001)(229853002)(68736007)(6436002)(8936002)(9686003)(55016002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2549; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: sPpU+AqbK+4maEJEHNUb//MsF/ipmP2CkFltlJedcyz9zpvPULeps4LfPtXuvtgbFM6fxBo7/J6+u9Lz4jwEHAZFjfkdbeUPSULi0Nl3FkJ23aU39Ht8vN5g7EUHwUTdgKLvgc3npmf2HP0DLOWf1v79ExRaCLjPHeumpyN47ATTenvt+ZIiE4VSJOCQopIeI2VxQT7xwQqwqWPpfaeoAQbNxQWtSGRG3h5vZUYW5BkX9FIGv32FxT+oBGZBr2PX0Rt1E4Ro8sRldDfJSGHv65HDY1HpKBQI++jTUlTEPTh6t+4YVRIADPqBsdfb3667JLDHJNhdtH4uvh8fNa+ZDHK6tdJ/ZYmy3ws+yDoiKXPPm1EByGBz2J462ZCeF1/gStv4VVnWEj+6sYb3101SFKrntNw7zuwZHiLte0/phaQ=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1394bab3-25f7-4579-8cfc-08d6b6bb356d
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Apr 2019 16:00:49.0054 (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: BYAPR11MB2549
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: alln-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/f6VACYK_Ovq8jjya473ENQZ_O8I>
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 16:02:09 -0000

Tony -

> -----Original Message-----
> From: Tony Li <tony1athome@gmail.com> On Behalf Of tony.li@tony.li
> Sent: Monday, April 01, 2019 8:44 AM
> To: 7riw77@gmail.com
> Cc: Les Ginsberg (ginsberg) <ginsberg@cisco.com>; lsr@ietf.org
> Subject: Re: [Lsr] FW: New Version Notification for draft-white-distoptflood-
> 00.txt
> 
> >
> >> 3)The adjacency formation logic discussed in Section 2 isn’t directly
> relevant
> >> to calculating a flooding topology. There are existing implementations
> which
> >> use the techniques you define as a means of reducing redundant flooding
> >> associated with adjacency bringup when there are parallel links between
> two
> >> nodes. Note this can be (and is) done without  requiring protocol
> >> extensions/specification i.e., a node can do this today without introducing
> >> any interoperability issues. So while this is definitely a good idea, it isn’t
> >> directly related to the work on flooding topologies and I think is better
> >> removed from the draft.
> >
> > Okay -- it seems like this technique is not documented anyplace, and could
> be used for all adjacencies.
> 
> 
> I’m going to risk disagreeing with Les again

[Les:] :-)

 and suggest that this should be
> documented.  It need not be in this draft, but it is useful to have in an RFC
> somewhere.

[Les:] If someone wants to write this up in a draft that's fine with me - but it should be an Informational/BCP draft.

My point in the context of this thread is that it isn’t directly related to flooding optimization work and therefore doesn’t belong in such drafts.

   Les

> 
> Tony
>

v2.23.0 | Report a Bug | By Email