[Bier] BIER IPv6 Requirement

"Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com> Thu, 20 August 2020 07:14 UTC

Return-Path: <gengxuesong@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 445E43A0962; Thu, 20 Aug 2020 00:14:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 Cy7zN_21O1Os; Thu, 20 Aug 2020 00:14:18 -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 8471C3A095F; Thu, 20 Aug 2020 00:14:17 -0700 (PDT)
Received: from lhreml703-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 91DF6B19921B0EAB1DA2; Thu, 20 Aug 2020 08:14:11 +0100 (IST)
Received: from nkgeml707-chm.china.huawei.com (10.98.57.157) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Thu, 20 Aug 2020 08:14:10 +0100
Received: from dggeme752-chm.china.huawei.com (10.3.19.98) by nkgeml707-chm.china.huawei.com (10.98.57.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.1913.5; Thu, 20 Aug 2020 15:14:07 +0800
Received: from dggeme752-chm.china.huawei.com ([10.6.80.76]) by dggeme752-chm.china.huawei.com ([10.6.80.76]) with mapi id 15.01.1913.007; Thu, 20 Aug 2020 15:14:07 +0800
From: "Gengxuesong (Geng Xuesong)" <gengxuesong@huawei.com>
To: Mike McBride <mmcbride7@gmail.com>, "draft-ietf-bier-ipv6-requirements@ietf.org" <draft-ietf-bier-ipv6-requirements@ietf.org>, "bier@ietf.org" <bier@ietf.org>
Thread-Topic: BIER IPv6 Requirement
Thread-Index: AdZ2v8bLfTLG4bZiScmsiW4U3pxzaA==
Date: Thu, 20 Aug 2020 07:14:07 +0000
Message-ID: <ee1dc8621a8447d8a910f47712d5669c@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.108.242.209]
Content-Type: multipart/mixed; boundary="_004_ee1dc8621a8447d8a910f47712d5669chuaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bier/YejFaCSIuhd1eEv2hQFAOxRJk7k>
Subject: [Bier] BIER IPv6 Requirement
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, 20 Aug 2020 07:14:20 -0000

Hi Mike, authors and WG,

I have read through the existing version of draft-ietf-bier-ipv6-requirements and the comments in the mailing list.  The concerns for this document mainly comes from three aspects:

1.       The problem statement: why we need BIER IPv6 solution (which I think is straight forward: we need solution(s) to deploy BIER in an IPv6 domain)

2.       The conceptual model for BIER IPv6 encapsulation (the existing model classification seems to be roughly agreed in the WG but the descriptions should be modified based on the comments)

3.       The requirement items and classification

I think the previous two points mainly request editing work and a document with some my personal recommended text could be found in the attachment just for your reference.
For the third point, I list the requirement items based on the existing discussions in the WG as follows:
Mandatory:

?   L2 Agnostic (may be removed)

?   Align to BIER architecture defined in RFC8279 (may be removed)

?   Support deployment with Non-BFR routers

?   Support OAM

?   Support overlay service, e.g., MVPN, EVPN
Optional:

?   Support native IPv6 functions, e.g., IPSEC, Fragmentation

?   Support inter-AS multicast deployment

?   Provide necessary security methods (may be removed)

I suggest to discuss and confirm these items in WG first, including what should be included/excluded, which one should be mandatory etc., then we could work on the detailed explanations for each item.

Best Regards
Xuesong