Re: [bmwg] Feedback on the IPv6 and MPLS SR drafts - to consolidate or not?

Vasilenko Eduard <vasilenko.eduard@huawei.com> Tue, 08 August 2023 06:33 UTC

Return-Path: <vasilenko.eduard@huawei.com>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C88F9C15107C for <bmwg@ietfa.amsl.com>; Mon, 7 Aug 2023 23:33:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.205
X-Spam-Level:
X-Spam-Status: No, score=-4.205 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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_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 ONonI7260mAQ for <bmwg@ietfa.amsl.com>; Mon, 7 Aug 2023 23:33:40 -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 BBF0AC131810 for <bmwg@ietf.org>; Mon, 7 Aug 2023 23:33:23 -0700 (PDT)
Received: from mscpeml500001.china.huawei.com (unknown [172.18.147.201]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4RKjvx0FsCz6J7rB; Tue, 8 Aug 2023 14:29:32 +0800 (CST)
Received: from mscpeml500001.china.huawei.com (7.188.26.142) by mscpeml500001.china.huawei.com (7.188.26.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.27; Tue, 8 Aug 2023 09:33:20 +0300
Received: from mscpeml500001.china.huawei.com ([7.188.26.142]) by mscpeml500001.china.huawei.com ([7.188.26.142]) with mapi id 15.01.2507.027; Tue, 8 Aug 2023 09:33:20 +0300
From: Vasilenko Eduard <vasilenko.eduard@huawei.com>
To: "sbanks@encrypted.net" <sbanks@encrypted.net>, "bmwg@ietf.org" <bmwg@ietf.org>
Thread-Topic: [bmwg] Feedback on the IPv6 and MPLS SR drafts - to consolidate or not?
Thread-Index: AQHZyWBDyMVVGn6s106VlxcLUk1oHq/f70Eg
Date: Tue, 08 Aug 2023 06:33:20 +0000
Message-ID: <1327e195e377458997f06bf82464db6f@huawei.com>
References: <e96d1651-f6e3-37de-bf1d-9232983dbb8e@hit.bme.hu> <46FA6F0C-D40B-4867-8840-8C46461A7661@encrypted.net>
In-Reply-To: <46FA6F0C-D40B-4867-8840-8C46461A7661@encrypted.net>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.199.56.242]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/iCAUFQP7_TJKrVgcmQlRcXaDJSs>
Subject: Re: [bmwg] Feedback on the IPv6 and MPLS SR drafts - to consolidate or not?
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 Aug 2023 06:33:42 -0000

Hi all,
The technology difference (that I have pointed out on the IETF 117) is possible to cover properly in the common document.
Would be a small inconvenience that not all tests would be needed for both (4 against 3 in every sub-section), and would be many places "if SRv6 then ... else ...".

The bigger problem is that SR-MPLS against SRv6 is a pretty religious decision.
People that choose one (for the deployment and test) would never need to test the other one.
Hence, they have 50% of the information in the draft that they need to scroll.
The audience for SRv6 and SR-MPLA is different. These are different Carriers.

Hence, it is better to keep documents separate.
But merge is possible.

Eduard
-----Original Message-----
From: bmwg [mailto:bmwg-bounces@ietf.org] On Behalf Of sbanks@encrypted.net
Sent: Monday, August 7, 2023 9:51 PM
To: bmwg@ietf.org
Subject: [bmwg] Feedback on the IPv6 and MPLS SR drafts - to consolidate or not?

Good afternoon BMWG,
	At IETF 117 in San Francisco, we had a discussion around whether or not to consolidate the IPv6 and MPLS SR drafts - they’re currently separate. We, as a group, took an action to continue that conversation on the list, prior to calling for the adoption of either 1 (consolidated) or both drafts. To that end, I’d like to ask BMWG for their opinions here. Gabor has already weighed in (thank you Gabor!). What say the rest of us?

Thank you,

Sarah
BMWG Co-Chair
_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www.ietf.org/mailman/listinfo/bmwg