[Lsr] LEEF bit behavior) RE: I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
Huaimo Chen <hchen@futurewei.com> Wed, 22 May 2019 20:52 UTC
Return-Path: <hchen@futurewei.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 319931200E5 for <lsr@ietfa.amsl.com>; Wed, 22 May 2019 13:52:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 T4T2mvMWLdYU for <lsr@ietfa.amsl.com>; Wed, 22 May 2019 13:52:24 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-eopbgr740104.outbound.protection.outlook.com [40.107.74.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C4891200A3 for <lsr@ietf.org>; Wed, 22 May 2019 13:52:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=e14Ki/IiyhD+ZYjSeTdKkmehfgtr9MONy8xCMjvPatQ=; b=J3onf2O6I2z3wvEncL0EnDsN55h173ErAyO7P11eq2NpA9bfsLj9bEOSfBecYm+Qi27mHy30B8VofHUoCck8cFX1bnuS16BJx5vvIAE6e8hSbRpQAel+rpf4oBAnEeOClEflsicgAkO35Wd5u2/GWeGwLueieQ18Sg2/rGymED4=
Received: from MN2PR13MB3470.namprd13.prod.outlook.com (10.255.237.83) by MN2PR13MB2768.namprd13.prod.outlook.com (20.178.253.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1922.10; Wed, 22 May 2019 20:52:21 +0000
Received: from MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::2528:ed2a:12eb:38df]) by MN2PR13MB3470.namprd13.prod.outlook.com ([fe80::2528:ed2a:12eb:38df%4]) with mapi id 15.20.1922.016; Wed, 22 May 2019 20:52:21 +0000
From: Huaimo Chen <hchen@futurewei.com>
To: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>, "lsr@ietf.org" <lsr@ietf.org>
Thread-Topic: LEEF bit behavior) RE: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
Thread-Index: AQHVEOACty7NddjteUSYP7U4rpAHmw==
Date: Wed, 22 May 2019 20:52:21 +0000
Message-ID: <MN2PR13MB3470099009F14B8436828F32A3000@MN2PR13MB3470.namprd13.prod.outlook.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=hchen@futurewei.com;
x-originating-ip: [206.16.17.232]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2084b52a-5809-4901-49f8-08d6def762ce
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(7021145)(8989299)(4534185)(7022145)(4603075)(4627221)(201702281549075)(8990200)(7048125)(7024125)(7027125)(7023125)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:MN2PR13MB2768;
x-ms-traffictypediagnostic: MN2PR13MB2768:
x-microsoft-antispam-prvs: <MN2PR13MB27689FA120CCD8B063F8D915A3000@MN2PR13MB2768.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0045236D47
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39850400004)(396003)(346002)(376002)(366004)(136003)(189003)(199004)(13464003)(25786009)(561944003)(19627405001)(68736007)(2501003)(33656002)(508600001)(52536014)(186003)(26005)(53546011)(64756008)(66556008)(66476007)(76116006)(54896002)(66946007)(9686003)(73956011)(14444005)(6606003)(53336002)(66446008)(55016002)(102836004)(6506007)(6436002)(5660300002)(2906002)(6116002)(3846002)(256004)(476003)(71200400001)(53936002)(74316002)(486006)(71190400001)(316002)(99286004)(110136005)(14454004)(86362001)(8936002)(8676002)(81156014)(81166006)(7696005)(66066001)(7736002); DIR:OUT; SFP:1102; SCL:1; SRVR:MN2PR13MB2768; H:MN2PR13MB3470.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: LVO8uCHIIXzvKrCwufdvHEQeIAGzMgghTOtCw5YOPP6tj5rk6Ans7lr+FGo2UJhBIOgCNhJVrmkzj6/pDUwHGQtWELQOSY+xJ4Pgmtj+7FXCZXUPDRQqMZ3ABLNuJjzAiWuzibkyeQEn5vFE3vYQrUuP2cMSpa9UJvkBlwEKLKrCGicHdRohzoscn9S0NJfdkz0IlV0pvPIVvEsqyv7BrXcJfdZ1w8tec3BdPBfSh92qX7e0aSR9mv1F4DKHIah212Zn4Cj/xWnJGvMpT2e/3Yq2kKrFjV7rYLe/h598BLQgJ75xdf3LUdsX65Y8ZCG0N89Ah79GY0L2FRjUSwJFoL3naNnz5nzp0Hnvc0QCfagSND1ip4JiMSi+4x+7ChIakbmy2V7d3tEkUnXh1hSD61yczcBGWbi0gSEjfNwuZIs=
Content-Type: multipart/alternative; boundary="_000_MN2PR13MB3470099009F14B8436828F32A3000MN2PR13MB3470namp_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2084b52a-5809-4901-49f8-08d6def762ce
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 May 2019 20:52:21.3467 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hchen@futurewei.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR13MB2768
Archived-At: <https://mailarchive.ietf.org/arch/msg/lsr/m2k6Pl-A7r-zBfZ7LgeDpfDNN3E>
Subject: [Lsr] LEEF bit behavior) RE: 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: Wed, 22 May 2019 20:52:27 -0000
Hi Les,
Thank you very much for adding the LEEF bit into the draft based on the FT bit for a link. The bit advertised by one end node of the link indicates whether the link is on the flooding topology.
Would you mind adding the behavior below for checking and handling the inconsistency of the flooding topology through using this bit?
For a link L between node A and node B, if the LEEF bit for link L advertised by node A is different from the one advertised by node B, then the flooding topology is inconsistent, the node receiving the LEEF bit set to one for link L from the other node adds link L on the flooding topology temporarily.
If one of the two nodes receives the LEEF bit set to one for link L from the other, but advertises the LEEF bit set to zero for link L for a given time such as 5 seconds, then a warning is issued or logged.
Best Regards,
Huaimo
-----Original Message-----
From: Lsr [mailto:lsr-bounces@ietf.org] On Behalf Of Les Ginsberg (ginsberg)
Sent: Tuesday, May 21, 2019 1:56 PM
To: lsr@ietf.org
Subject: Re: [Lsr] I-D Action: draft-ietf-lsr-dynamic-flooding-01.txt
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
- [Lsr] LEEF bit behavior) RE: I-D Action: draft-ie… Huaimo Chen
- Re: [Lsr] LEEF bit behavior) RE: I-D Action: draf… Les Ginsberg (ginsberg)