[Bier] The offline talk about BIERin6 and BIER-ipv6-requirements drafts

Xiejingrong <xiejingrong@huawei.com> Sat, 27 July 2019 11:24 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 323611201E3; Sat, 27 Jul 2019 04:24:38 -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 uQpUZ3vw17Ki; Sat, 27 Jul 2019 04:24:36 -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 6E65012015D; Sat, 27 Jul 2019 04:24:36 -0700 (PDT)
Received: from lhreml706-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id E22DD695EF391079D4A3; Sat, 27 Jul 2019 12:24:33 +0100 (IST)
Received: from NKGEML413-HUB.china.huawei.com (10.98.56.74) by lhreml706-cah.china.huawei.com (10.201.108.47) with Microsoft SMTP Server (TLS) id 14.3.408.0; Sat, 27 Jul 2019 12:24:33 +0100
Received: from NKGEML514-MBS.china.huawei.com ([169.254.3.121]) by NKGEML413-HUB.china.huawei.com ([10.98.56.74]) with mapi id 14.03.0439.000; Sat, 27 Jul 2019 19:24:19 +0800
From: Xiejingrong <xiejingrong@huawei.com>
To: BIER WG <bier@ietf.org>
CC: "draft-zhang-bier-bierin6@ietf.org" <draft-zhang-bier-bierin6@ietf.org>, "draft-ietf-bier-ipv6-requirements@ietf.org" <draft-ietf-bier-ipv6-requirements@ietf.org>
Thread-Topic: The offline talk about BIERin6 and BIER-ipv6-requirements drafts
Thread-Index: AdVEbDdfSasS0zeXTT+PUAHUwHtauQ==
Date: Sat, 27 Jul 2019 11:24:19 +0000
Message-ID: <16253F7987E4F346823E305D08F9115AAB90D974@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.93.219]
Content-Type: multipart/alternative; boundary="_000_16253F7987E4F346823E305D08F9115AAB90D974nkgeml514mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/qUFe16q9gV09mDcRjnNAVCcqLPE>
Subject: [Bier] The offline talk about BIERin6 and BIER-ipv6-requirements drafts
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, 27 Jul 2019 11:24:38 -0000

Thanks Jeffrey and Sandy for the patient talk offline about the BIERin6 and BIER-ipv6-requirements yesterday.
I summarized the talk afterwards, and have the following points.

(1) BIERin6 is a Layer-4 solution, which has its special advantages and disadvantages in different scenarios, comparing to Layer-3 solution (the solution using IPv6 Extension Header).

(2) The <bier-ipv6-requirements> can be more inclusive to include Layer-3, Layer-4, and Layer-5 solution, so that many of the interests, Layer-3/4/5, in the WG can be all considered.

What's your opinion ?

Thanks
Jingrong