Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

Chenshuanglong <chenshuanglong@huawei.com> Sun, 06 August 2023 09:39 UTC

Return-Path: <chenshuanglong@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C5EC14CE4D; Sun, 6 Aug 2023 02:39:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.193
X-Spam-Level:
X-Spam-Status: No, score=-4.193 tagged_above=-999 required=5 tests=[AC_DIV_BONANZA=0.001, BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4eB1vi1O_Qn2; Sun, 6 Aug 2023 02:39:49 -0700 (PDT)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E6F6C14CE33; Sun, 6 Aug 2023 02:39:49 -0700 (PDT)
Received: from lhrpeml100002.china.huawei.com (unknown [172.18.147.206]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RJZ6j3Wzzz67h72; Sun, 6 Aug 2023 17:34:53 +0800 (CST)
Received: from kwepemi100018.china.huawei.com (7.221.188.35) by lhrpeml100002.china.huawei.com (7.191.160.241) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Sun, 6 Aug 2023 10:39:45 +0100
Received: from kwepemi500002.china.huawei.com (7.221.188.171) by kwepemi100018.china.huawei.com (7.221.188.35) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Sun, 6 Aug 2023 17:39:43 +0800
Received: from kwepemi500002.china.huawei.com ([7.221.188.171]) by kwepemi500002.china.huawei.com ([7.221.188.171]) with mapi id 15.01.2507.027; Sun, 6 Aug 2023 17:39:43 +0800
From: Chenshuanglong <chenshuanglong@huawei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>, BESS <bess@ietf.org>, "bess-chairs@ietf.org" <bess-chairs@ietf.org>, "Dongjie (Jimmy)" <jie.dong@huawei.com>
Thread-Topic: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported
Thread-Index: AQHZwOs8RXWG+VDF5UmmIOamYxU6C6/dDhrQ
Date: Sun, 06 Aug 2023 09:39:43 +0000
Message-ID: <3fb306591af34a35b5eedcebccf9f531@huawei.com>
References: <CABNhwV2fKc90vn2QJRZdZ4h81i+BFGXj6_UarQ10WKphfFFFRg@mail.gmail.com>
In-Reply-To: <CABNhwV2fKc90vn2QJRZdZ4h81i+BFGXj6_UarQ10WKphfFFFRg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.84.91.44]
Content-Type: multipart/alternative; boundary="_000_3fb306591af34a35b5eedcebccf9f531huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/dXrC2l_4-X7_N-G6eoS5lRQbV3g>
Subject: Re: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Aug 2023 09:39:54 -0000

Hi WG

As a co-author,  I support merging these files. This is a useful work, which will help focus on the discussion and simplify the design.

Best Regards
Shuanglong

From: BESS <bess-bounces@ietf.org> On Behalf Of Gyan Mishra
Sent: Friday, July 28, 2023 8:32 AM
To: BESS <bess@ietf.org>; bess-chairs@ietf.org; Dongjie (Jimmy) <jie.dong@huawei.com>
Subject: [bess] IETF 117 BESS - IPv6 Only PE Design & IPv4 Only PE Design ALL SAFI Supported

Dear BESS WG,

From my presentation today discussion on "merging" of drafts I  would like to poll the BESS WG on merging of the two drafts labeled #1 & #2 below into the WG document labeled #3 below:
Please respond  to this email.

Some history:
IPv6 Only PE design / ALL SAFI:
draft-ietf-bess-ipv6-only-pe-design-04 (BCP) (Original BCP testing draft with Cisco, Juniper, Nokia, Arista, Huawei) (WG document)
IPv6 Only PE design single IPv6 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv6-only-pe-design-all-safi-04 (Standards Track) (New Draft) - Extended Standards Track to support ALL IPv4 SAFI

IPv4 Only PE design / ALL SAFI:
The below drafts were two separate drafts but I have combined into single draft since they both were not WG documents
draft-mishra-bess-ipv4-only-pe-design-02 -(BCP) (POC testing draft with Cisco, Juniper, Nokia, Arista, Huawei)
IPv4 Only PE design single IPv4 peer - testing SAFI 1,128,129
draft-mishra-bess-ipv4-only-pe-design-all-safi-05 (Standards track) (New Draft) - Extended Standards Track to support ALL IPv4 SAFI (Both v4 drafts have been combined into this Draft early this year)
(Introduces new IPv4 next hop encoding IANA capability codepoint standardization following RFC 8950 IPv4 next hop and not legacy IPv4 mapped IPv6 address next hop ::FFFF::1.1.1.1)
(Today there is a mix of IPv4 next hop and IPv4 mapped IPv6 next hop across all vendors and within same vendor platform -afi/safi matrix to be added to merged draft)

Combine these two drafts --> So now we are left with  these 2 new drafts that extend to support ALL SAFI

#1 draft-mishra-bess-ipv6-only-pe-design-all-safi-03 (Standards Track)
#2 draft-mishra-bess-ipv4-only-pe-design-all-safi-04 (Standard Track)

Into WG document below:

#3 draft-ietf-bess-ipv6-only-pe-design-04 (BCP)

And make the new combined draft "Standards Track" as it will have the operational process and procedure update for the alternative dual stacking method for all SAFI
as well as New IANA capability code point for IPv4 next hop encoding similar to RFC 8950.

NEW DRAFT NAME:

 draft-ietf-bess-v4-v6-pe-all-safi (Standards Track)

Why combine?

  *   Both IPv4 Only PE Design & IPv6 Only PE design are identical concepts of single IPv4 peer or single IPv6 peer carrying SAFI 1,128.129 for both v4 & v6 prefixes being POC tested - can now be done in parallel
  *   Extensibility of both the IPv4 Only PE Design & IPv6 Only PE design extends to the same set of ALL IPv4 / IPv6 SAFI's
  *   Saves both WG time on progressing 3 separate drafts
  *   Single draft that has the entire v4 / v6 design & architecture in one spot versus being broken out into separate drafts added complexity

Thank you


[http://ss7.vzw.com/is/image/VerizonWireless/vz-logo-email]<http://www.verizon.com/>

Gyan Mishra

Network Solutions Architect

Email gyan.s.mishra@verizon.com<mailto:gyan.s.mishra@verizon.com>

M 301 502-1347