IETF Logo Mail Archive

[Bier] Comments on draft-zhang-bier-flooding

"Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net> Fri, 10 November 2017 00:44 UTC

Return-Path: <zzhang@juniper.net>
X-Original-To: bier@ietfa.amsl.com
Delivered-To: bier@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7DE129400; Thu, 9 Nov 2017 16:44:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.8
X-Spam-Level:
X-Spam-Status: No, score=-4.8 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, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=juniper.net
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 k-EO-YGWZWTe; Thu, 9 Nov 2017 16:44:36 -0800 (PST)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0103.outbound.protection.outlook.com [104.47.38.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 744F81242F5; Thu, 9 Nov 2017 16:44:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=juniper.net; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=U72oVqXLq4D4aHlFY1allan3qLghZTNJVA+CS/X+rWk=; b=FDUD3gvAN52ttp+C9LT8lsPsITi9HNI6ho7M0D8y5NuK7pvcBPkbwhOC35vFwVYopoS2r9hmBAMSEuDdy7NlBmH8RRsgz3ZkzMLXqyI2fRWNdzKJETOxHxNHqBr2sFb2Luca+hRF/uhbt/xaDaC7lizapVbNZlChu4VEXJwQnQM=
Received: from DM5PR05MB3145.namprd05.prod.outlook.com (10.173.219.15) by DM5PR05MB3148.namprd05.prod.outlook.com (10.173.219.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P384) id 15.20.239.4; Fri, 10 Nov 2017 00:44:34 +0000
Received: from DM5PR05MB3145.namprd05.prod.outlook.com ([10.173.219.15]) by DM5PR05MB3145.namprd05.prod.outlook.com ([10.173.219.15]) with mapi id 15.20.0239.004; Fri, 10 Nov 2017 00:44:34 +0000
From: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>
To: "bier@ietf.org" <bier@ietf.org>, "pim@ietf.org" <pim@ietf.org>
Thread-Topic: Comments on draft-zhang-bier-flooding
Thread-Index: AdNZu1qQrnBGKjw6ReC0e9uBiQtrNQ==
Date: Fri, 10 Nov 2017 00:44:34 +0000
Message-ID: <DM5PR05MB3145F3F771BF0977057C45FDD4540@DM5PR05MB3145.namprd05.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=zzhang@juniper.net;
x-originating-ip: [66.129.241.11]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR05MB3148; 6:Dsf7EA7XJIfGul+Bc2OjO4as6AUcGhKYYTvQhHSWDtV0cwP2eIboyOp1rz6WnVZxDJZWoZINUtJa4JFvywr1B32yik9d0OgbVoRgTXpkgeE0lhUOI89/rCo2zosVRf51knDRTnojQXX6k728wCuAuiMzSzwo/OBUltRDdJgHvTFducTsZS9ZVlt5Z9Lmkm5nj1fnQBmP00MOV0E/5KYUs0/ZxPVkMZvmvw9iIoyZdb6ajcxmhBH7MyQe2OKg4R04NV2yz8z3yVYuzweo0DSwG9ybYOpWz0r99XAIwjA9zRkHQaW96IDbdIXlPGzErcWOFl+3B80gobu5rEr4XTJSWsX6iwMGP0gtr4NeFZ0+gRY=; 5:LHc19AqBjV18FugwGX+oDfTZmKElVIJDhu20z9bGBJusa0X/KKZD6AZgkzUssfeWDKJekfn/lKgabLBxbe4GJhaH2Ebs9C2ZQLOsRqbfitIVRi+Ckc56rQNx57ifUTGgo5xo8fJB9q0WQG2amSAk/mTQWOUP6lEhvkDFnAk8atM=; 24:x4l1gpAWyT17fbw9rFXH66XySw1xB5dzvBuHSiomNJFpQPtI6TYOnJwulGTiz7jGiHXXlbJzd8VI/ZDuwwoE2CWih/wzpXCmXIumOEPYiI4=; 7:Z+zT083Y+VFUXsi3cAriyNLfcBHCQu3AhrKsmdh0K0q29rVSmWNNpGufdBcVFBeA0XCdYKlVlS7mmiPfK+X4Rcw1D64g3D9m6OfXba8fJZcOUcRhDN1DyOY9Grydk86Ipidpr0GBm+hLQSqS2xYR6k8qwTHHTDpfoiX3OKWzAfTRqkfz0OmWDOerq4nckuhOnCZpRAoPU7+AXxeHc7JTA05V+Nk/kX+TenYog3fdZMSjMo9VlpWnTy7CaKu+frpL
x-ms-exchange-antispam-srfa-diagnostics: SSOS;
x-ms-office365-filtering-correlation-id: f76df395-5984-4709-c423-08d527d436af
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(4534020)(4602075)(4627115)(201703031133081)(201702281549075)(48565401081)(2017052603199); SRVR:DM5PR05MB3148;
x-ms-traffictypediagnostic: DM5PR05MB3148:
x-exchange-antispam-report-test: UriScan:(21748063052155);
x-microsoft-antispam-prvs: <DM5PR05MB3148914695BCDF8B793E9506D4540@DM5PR05MB3148.namprd05.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(3231021)(3002001)(93006095)(93001095)(10201501046)(6055026)(6041248)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123555025)(20161123564025)(20161123558100)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DM5PR05MB3148; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DM5PR05MB3148;
x-forefront-prvs: 0487C0DB7E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(346002)(376002)(39860400002)(189002)(199003)(53936002)(9686003)(478600001)(6306002)(8676002)(55016002)(6436002)(3660700001)(99286004)(2906002)(97736004)(316002)(6506006)(2501003)(77096006)(189998001)(230783001)(74316002)(305945005)(7736002)(66066001)(3280700002)(81156014)(86362001)(110136005)(81166006)(14454004)(105586002)(8936002)(450100002)(50986999)(54356999)(68736007)(7696004)(966005)(2900100001)(101416001)(25786009)(106356001)(6116002)(5660300001)(102836003)(33656002)(3846002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR05MB3148; H:DM5PR05MB3145.namprd05.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: juniper.net does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR05MB3145F3F771BF0977057C45FDD4540DM5PR05MB3145namp_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-Network-Message-Id: f76df395-5984-4709-c423-08d527d436af
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Nov 2017 00:44:34.5581 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR05MB3148
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/IN6BNKZOUGLCatTJzgGOCyJWST0>
Subject: [Bier] Comments on draft-zhang-bier-flooding
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "\"Bit Indexed Explicit Replication discussion list\"" <bier.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bier>, <mailto:bier-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bier/>
List-Post: <mailto:bier@ietf.org>
List-Help: <mailto:bier-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bier>, <mailto:bier-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 10 Nov 2017 00:44:39 -0000

Hi Sandy,

During a recent offline discussion on OSPF/ISIS inter-area BIER signaling, I brought up that when an area border router re-advertise into another area, it does not need to advertise the encapsulation sub-TLV, because routers in other areas won't use that information at all. All that is needed is the BFR-IDs.

The same could be applied to the use case you're describing:



                              |                |
                     .........|................|.........
                     .  ISIS  |                |        .
                     .        |                |        .
                     .       MR1--------------MR2       .
                     .        |  .          .  |        .
                     .        |    .      .    |        .
                     .        |      .  .      |        .
                     .        |       ..       |        .
                     .        |     .    .     |        .
                     .        |   .        .   |        .
                     .        | .            . |        .
                     .        MR3              MR4      .
                     .       /  \             /  \      .
                     ....................................
                            /    \           /    \
                           /      \         /      \
                          /        \       /        \
                     ...................  ................
                     .    B1--------B2 .  .B3--------B4  .
                     .                 .  .              .
                     .   Rm            .  . Rx           .
                     .       ...       .  .     ...      .
                     .            Rn   .  .         Ry   .
                     .                 .  .              .
                     .         OSPF    .  .       OSPF   .
                     ...................  ................
                       Figure 1: An typical hybrid network

So, I don't see a need to use BSR to flood the BIER info across those different routing domains. As long as the border routers advertise the BFR-IDs of its downstream nodes to neighboring border routers, and its neighboring border routers continue to advertise the BFR-IDs of those downstream nodes, it will work.

For example, MR3 has to learn routes to Rm...Rn somehow - as long as that learning includes the BFR-IDs of Rm...Rn, and MR3 advertises those to its neighbors in the ISIS domain and so on, things will work.

Jeffrey

v2.23.0 | Report a Bug | By Email