BIERv6 source-routing multicast -- BIER in IPv6
"Xiejingrong (Jingrong)" <xiejingrong@huawei.com> Wed, 18 March 2020 06:51 UTC
Return-Path: <xiejingrong@huawei.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B6AD3A09C7; Tue, 17 Mar 2020 23:51:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 E6uVw46I_am0; Tue, 17 Mar 2020 23:51:26 -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 E26F53A09C6; Tue, 17 Mar 2020 23:51:25 -0700 (PDT)
Received: from lhreml702-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 2B372545525E2FB7374A; Wed, 18 Mar 2020 06:51:22 +0000 (GMT)
Received: from nkgeml701-chm.china.huawei.com (10.98.57.156) by lhreml702-cah.china.huawei.com (10.201.108.43) with Microsoft SMTP Server (TLS) id 14.3.408.0; Wed, 18 Mar 2020 06:51:21 +0000
Received: from nkgeml705-chm.china.huawei.com (10.98.57.154) by nkgeml701-chm.china.huawei.com (10.98.57.156) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Wed, 18 Mar 2020 14:51:19 +0800
Received: from nkgeml705-chm.china.huawei.com ([10.98.57.154]) by nkgeml705-chm.china.huawei.com ([10.98.57.154]) with mapi id 15.01.1713.004; Wed, 18 Mar 2020 14:51:19 +0800
From: "Xiejingrong (Jingrong)" <xiejingrong@huawei.com>
To: Michael McBride <michael.mcbride@futurewei.com>, "6man@ietf.org" <6man@ietf.org>
CC: "draft-xie-bier-ipv6-encapsulation@ietf.org" <draft-xie-bier-ipv6-encapsulation@ietf.org>
Subject: BIERv6 source-routing multicast -- BIER in IPv6
Thread-Topic: BIERv6 source-routing multicast -- BIER in IPv6
Thread-Index: AdX88DtWd4eeMPLhQ6yuKnKVW/OqqA==
Date: Wed, 18 Mar 2020 06:51:19 +0000
Message-ID: <05501bf5ed82464093b45fa3c7057977@huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.202.118]
Content-Type: multipart/alternative; boundary="_000_05501bf5ed82464093b45fa3c7057977huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/aXRBv912Rx3YSCHCry2A5d9k5g4>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Mar 2020 06:51:29 -0000
Hi 6man WG, Appreciated for your comments for this draft (BIERv6 for short) on this specific topic. https://datatracker.ietf.org/doc/draft-xie-bier-ipv6-encapsulation/ For ease of understanding, I can shortly introduce this behavior we proposed: (1) An encapsulation named BIER IPv6 encapsulation, looks like {IPv6 hdr, DOH<with BIER header as Option Data>, Inner IP-multicast-packet}. The BIER header [RFC8279] contains a BitString, and each bit of the BitString represents an ultimate destination of a router in a limited-domain called BIER domain. (2) Router A send a packet as depicted above to B (with packet's destination address being B's address), and then B send to C and D according to the BitString, with packet's destination address being C's address and D's address respectively, and BitString being changed per the BIER procedures (RFC8279). Best regards, Jingrong From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Michael McBride Sent: Wednesday, March 18, 2020 12:19 PM To: 6man@ietf.org Subject: BIER in IPv6 Hello, The bier wg could use your ipv6 recommendations. We've worked on various solutions to transport a bier header in ipv6. We decided to pause and create a requirements document (draft-ietf-bier-ipv6-requirements) to help steer us towards the right solution(s). In that drafts appendix we have a fairly good summary of the various solutions. We've started to rally behind two solutions which meet the majority of the requirements: draft-xie-bier-ipv6-encapsulation (bier header in ipv6 EH) and draft-zhang-bier-bierin6 (bier header as payload using ipv6 NH). The bier chairs today asked to punt the bierv6 topic to 6man for advice before adopting any of these solutions. So here we are seeking your advice. The most simple approach would probably be to give https://datatracker.ietf.org/doc/draft-ietf-bier-ipv6-requirements/ a look and scroll down to the appendix to see a summary of the various solutions we've been considering. thanks! mike
- BIERv6 source-routing multicast -- BIER in IPv6 Xiejingrong (Jingrong)