[Bier] Comments on <draft-hj-bier-mldp-signaling-00>
Xiejingrong <xiejingrong@huawei.com> Thu, 18 July 2019 03:10 UTC
Return-Path: <xiejingrong@huawei.com>
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 0CD94120110 for <bier@ietfa.amsl.com>; Wed, 17 Jul 2019 20:10:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 RZyllkJELifQ for <bier@ietfa.amsl.com>; Wed, 17 Jul 2019 20:10:20 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00116120045 for <bier@ietf.org>; Wed, 17 Jul 2019 20:10:19 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 5D565AAFBAD3837F7B8C for <bier@ietf.org>; Thu, 18 Jul 2019 04:10:17 +0100 (IST)
Received: from NKGEML414-HUB.china.huawei.com (10.98.56.75) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 18 Jul 2019 04:10:15 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.142]) by nkgeml414-hub.china.huawei.com ([10.98.56.75]) with mapi id 14.03.0439.000; Thu, 18 Jul 2019 11:08:16 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: BIER WG <bier@ietf.org>
Thread-Topic: Comments on <draft-hj-bier-mldp-signaling-00>
Thread-Index: AdU9FemVNZuXo0B8SySbJVqDjPa6zw==
Date: Thu, 18 Jul 2019 03:08:16 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB8F2C6A@nkgeml514-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.94.84]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB8F2C6Ankgeml514mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/7jhGfkEHim7rMPOSEinz5Uk10qs>
Subject: [Bier] Comments on <draft-hj-bier-mldp-signaling-00>
X-BeenThere: bier@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 18 Jul 2019 03:10:22 -0000
Hi I have read the draft and think it looks far better by using multi-hop tLDP session than the complex mechanism that I had not understand well in previous draft. some comments/questions below: 3.2. EBBR procedure method The Egress BBR (EBBR) is connected to the mLDP domain which the root of the P2MP or MP2MP LSP resides on. The EBBR should accept the tLDP session and assign a upstream assigned label for arriving FEC. The EBBR should follow the [RFC7060] procedures with following modifications: [XJR] the following procedures follow 7060 or 7389 ? - The label assigned by EBBR cannot be Implicit Null. This is to ensure that identity of each p2mp and/or mp2mp tunnel in BIER domain is uniquely distinguished. - The label can be assigned from a domain-wide Common Block (DCB) [I- D.zzhang-bess-mvpn-evpn-aggregation-label], as well as upstream assigned. - The Interface ID TLV [RFC6389]includes a new BIER sub-domain sub- tlv (type TBD) [XJR] this Interface ID TLV is carried in message from EBBR(BFIR) to IBBR(BFERs)? With same token the EBBR should track all the arriving FECs and the IBBRs that are generating these FECs. EBBR will use this information to build the bier header for each set of common FEC arriving from the IBBRs. [XJR] How does EBBR track the IBBRs? [XJR] Let me imagine: (1) IBBR(BFER) receive the mLDP Mapping from downstream LSR, and send a xxx message to EBBR(BFIR). (2) EBBR(BFIR) send a LDP Mapping message (with Upstream-Assigned Label Request TLV) to all its tLDP neighbors ? (3) BFIR should tell the BFERs the upstrea-assigned Label, and the Sub-domain, and the BFIR-id at least I guess. Is that right ? What's the xxx message (in case the tLDP is static configured, in case the tLDP is dynamicly established)? Thinking of the information need to carry in the LDP message, there will be MPLS WG be considered more. 4. Datapath Forwarding 4.1. Datapath traffic flow On BFIR when the MPLS label for P2MP/MP2MP LSP arrives a lookup in ILM table is done and the label is swapped with tLDP upstream assigned label. The BFIR will note all the BFERs that are interested in specific p2mp/mp2mp LSP (as per section 3.2). BFIR will put the corresponding BIER header with bit index set for all IBBRs interested in this P2MP LSP. BFIR will set the BIERHeader.Proto = MPLS and will forward the BIER packet into BIER domain. [XJR] is there a proper BFIR-id value to be mentioned ? Thanks Jingrong
- [Bier] Comments on <draft-hj-bier-mldp-signaling-… Xiejingrong
- Re: [Bier] Comments on <draft-hj-bier-mldp-signal… Xiejingrong
- Re: [Bier] Comments on <draft-hj-bier-mldp-signal… Bidgoli, Hooman (Nokia - CA/Ottawa)
- Re: [Bier] Comments on <draft-hj-bier-mldp-signal… Xiejingrong