Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105

Xiejingrong <xiejingrong@huawei.com> Sat, 13 July 2019 01:23 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 E3C28120041; Fri, 12 Jul 2019 18:23:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.632
X-Spam-Level:
X-Spam-Status: No, score=-3.632 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, 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 rvtzrBv4wsVa; Fri, 12 Jul 2019 18:23:49 -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 53C2A12000E; Fri, 12 Jul 2019 18:23:49 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 282312B4CDD69137CAF7; Sat, 13 Jul 2019 02:23:47 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 13 Jul 2019 02:23:45 +0100
Received: from NKGEML514-MBX.china.huawei.com ([fe80::40a8:f0d:c0f3:2ca5]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Sat, 13 Jul 2019 09:23:35 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: "Jeffrey (Zhaohui) Zhang" <zzhang@juniper.net>, "gjshep@gmail.com" <gjshep@gmail.com>, BIER WG <bier@ietf.org>
CC: "'draft-xie-bier-ipv6-mvpn@ietf.org'" <draft-xie-bier-ipv6-mvpn@ietf.org>, "draft-xie-bier-ipv6-isis-extension@ietf.org" <draft-xie-bier-ipv6-isis-extension@ietf.org>, "draft-geng-bier-ipv6-inter-domain@ietf.org" <draft-geng-bier-ipv6-inter-domain@ietf.org>, "draft-xie-bier-ipv6-encapsulation@ietf.org" <draft-xie-bier-ipv6-encapsulation@ietf.org>
Thread-Topic: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
Thread-Index: AQHVNcSpurLRu4KtS0eNbFcj5+1c/6bBeeIQgAV8GACAANGp4w==
Date: Sat, 13 Jul 2019 01:23:34 +0000
Message-ID: FB695EED-E2D2-4703-A6BE-277AB0B6101D
References: <CABFReBo=+68gyhsFwYktcc1Mr7zkax2MiYFCTSC5osod48x3Jw@mail.gmail.com> <16253F7987E4F346823E305D08F9115AAB8DC2D1@nkgeml514-mbx.china.huawei.com>, <DM5PR05MB3548731B6AE229EA12451E21D4F20@DM5PR05MB3548.namprd05.prod.outlook.com>
In-Reply-To: <DM5PR05MB3548731B6AE229EA12451E21D4F20@DM5PR05MB3548.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_FB695EEDE2D24703A6BE277AB0B6101D_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/QRUcUJ3ZVmdkRmuqxRVHUYPva8o>
Subject: Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
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: Sat, 13 Jul 2019 01:23:52 -0000

Thanks for the comments very much.
Meanful and helpful.
Please see my comments in line below.
发件人:Jeffrey (Zhaohui) Zhang <zzhang@juniper.net>
收件人:Xiejingrong <xiejingrong@huawei.com>;gjshep@gmail.com <gjshep@gmail.com>;BIER WG <bier@ietf.org>
抄 送:'draft-xie-bier-ipv6-mvpn@ietf.org' <draft-xie-bier-ipv6-mvpn@ietf.org>;draft-xie-bier-ipv6-isis-extension@ietf.org <draft-xie-bier-ipv6-isis-extension@ietf.org>;draft-geng-bier-ipv6-inter-domain@ietf.org <draft-geng-bier-ipv6-inter-domain@ietf.org>;draft-xie-bier-ipv6-encapsulation@ietf.org <draft-xie-bier-ipv6-encapsulation@ietf.org>
时间:2019-07-13 04:53:22
主 题:RE: [Bier] BIER WG, Call For Agenda, Montreal IETF 105

Hi Jingrong, Liang,
I have some questions and comments on two of the drafts.
draft-xie-bier-ipv6-encapsulation-02

  *   Use of BIER multicast address FF0X::AB37 does not seem right to me. For example, on a LAN you can’t multicast BIER packets to multiple downstream BFRs – individual copies (with different BitString) must be unicast to those downstreamiBIER-MPLSMPLS domain domain segmented
  *   a nnI PP[XJR] Absolutely! The use of multicast DA can't support some very common usecases that may be assumed as Architecture of BIER. I agree with you to assume using a unicast DA. I will update the draft this way in next version.
  *
  *   Assuming that we agree that a unicast DA address must be used. What’s the rational of “Source Address field in the IPv6 header MUST be a routable IPv6 unicast address of the BFIR in any case”? Since the IPv6 header is only the outer encapsulation to get a packet from BFR1 to BFR2, why would you want to put the BFIR’s address in the outer encapsulation? If you could make both SA/DA of the IPv6 header to be the original SA/DA of the payload it may make some sense, but obviously you can’t do that.
  *   [XJR] Yes, use of the address of the BFIR and keep it unchange when a packet fly through the BFRs is a key of the proposal. I think there is already examples of Source rooting that keep the source address unchange while change the DA in the fly. I would understand the BIER technology as a Multicast source routing!
  *
  *   With the above, I don’t see a real difference between this proposal and draft-zhang-bier-bierin6-03 – it’s just whether the BIER header is in the destination option or in the “payload” part of the IPv6 packet. Can you explain the pros and cons of two?
  *   [XJR]  there are more similarities since I (and you may also agree) want to use unicast DA only. but the difference is mainly two: one is use the address of BFIR without change in the fly as above point. one is use of a BIER specific ipv6 address in DA, which preceding any of the possible EHs and assume being the most efficient for fast path and most less impact on exist IPv6 functions.

draft-geng-bier-ipv6-inter-domain-00

  *   Can you elaborate the following?

  Note: Use of the IPv6 address configured on PE1 to identify an MVPN
  instance can eliminate the need for BFR-id configuration on PE1x,
  which otherwise has to be configured from the space of a sub-domain.

  *   For the “peering multicast”, how many BIER sub-domain do you have?
  *   [XJR] haven't evaluate that so far.I initiate this idea when I found a recent rfc8313 and thought of the tenant spanning multiple DCs. Also I assume the multicast as a service draft for this case.
  *
  *   What’s the real difference between “hierarchical multicast” and “peering multicast”, once you take away the color and MVPN aspects that I believe are orthogonal here?
  *   [XJR] the hierarchical one is a P2MP case like IPTV in service provider. The peering one is an MP2MP case where the multicast source may be more unpredictable.
  *
  *   What’s the significance of “inter-domain” here, that requires this new draft?
  *   [XJR] there is still no inter-domain BIER underlay construction, which I would think comparable to the so called non-segmented mvpn solution. It is the idea in my mind since the first presentation in ietf102 to deploy inter-domain BIER underlay. Also impressed by the points of multicast as a service you proposed.
  *
  *   What’s the uniqueness of IPv6 here?
  *   [XJR] I found it difficult to construct the inter-domain BIFTs since the BIER-MPLS label is dynamic. Use of a static SRGB label as BIER-MPLS of a BR(border router) is waste ful, while use the SRGB for the entire domain seems not welcome in ietf102.
  *   Thanks.
  *   Jingrong.

Thanks!
Jeffrey
From: BIER <bier-bounces@ietf.org> On Behalf Of Xiejingrong
Sent: Monday, July 8, 2019 9:30 PM
To: gjshep@gmail.com; BIER WG <bier@ietf.org>
Cc: 'draft-xie-bier-ipv6-mvpn@ietf.org' <draft-xie-bier-ipv6-mvpn@ietf.org>; draft-xie-bier-ipv6-isis-extension@ietf.org; draft-geng-bier-ipv6-inter-domain@ietf.org; draft-xie-bier-ipv6-encapsulation@ietf.org
Subject: Re: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
We’d like to request 35-40 minutes for the presentation of the following BIERv6 drafts.  I will be the speaker (may have some adjustment before the session).
BIERv6 Encapsulation // draft-xie-bier-ipv6-encapsulation-02, 15min
BIERv6 via IS-IS // draft-xie-bier-ipv6-isis-extension-00  10min
MVPN using BIERv6 // draft-xie-bier-ipv6-mvpn-01            5min
Inter-domain Multicast Deployment using BIERv6  // draft-geng-bier-ipv6-inter-domain-00 10min
Thanks
Jingrong on behalf of the authors
From: BIER [mailto:bier-bounces@ietf.org] On Behalf Of Greg Shepherd
Sent: Tuesday, July 09, 2019 3:37 AM
To: BIER WG <bier@ietf.org<mailto:bier@ietf.org>>
Subject: [Bier] BIER WG, Call For Agenda, Montreal IETF 105
Please send agenda items with title, draft, speaker name, and requested time to this thread.
Thanks,
Shep
(chairs)

Juniper Business Use Only