IETF Logo Mail Archive

Re: [Cats] [cats] draft-ietf-cats-usecases-requirements-00 -> traffic path enforcement type is missing

Cheng Li <c.l@huawei.com> Wed, 06 September 2023 08:20 UTC

Return-Path: <c.l@huawei.com>
X-Original-To: cats@ietfa.amsl.com
Delivered-To: cats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A4E3C15109D for <cats@ietfa.amsl.com>; Wed, 6 Sep 2023 01:20:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-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 p3Deda2kqtLF for <cats@ietfa.amsl.com>; Wed, 6 Sep 2023 01:20:35 -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 24ED7C151098 for <cats@ietf.org>; Wed, 6 Sep 2023 01:20:35 -0700 (PDT)
Received: from frapeml500003.china.huawei.com (unknown [172.18.147.207]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Rgb0P282qz6FGnW; Wed, 6 Sep 2023 16:20:21 +0800 (CST)
Received: from dggpemm500003.china.huawei.com (7.185.36.56) by frapeml500003.china.huawei.com (7.182.85.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.31; Wed, 6 Sep 2023 10:20:29 +0200
Received: from dggpemm500003.china.huawei.com ([7.185.36.56]) by dggpemm500003.china.huawei.com ([7.185.36.56]) with mapi id 15.01.2507.031; Wed, 6 Sep 2023 16:20:27 +0800
From: Cheng Li <c.l@huawei.com>
To: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>, Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>
CC: cats <cats@ietf.org>
Thread-Topic: [Cats] [cats] draft-ietf-cats-usecases-requirements-00 -> traffic path enforcement type is missing
Thread-Index: AdnfzXglO+H7sG5FQX6yY7jRS1o09wAvQwXMAAP5+1A=
Date: Wed, 06 Sep 2023 08:20:27 +0000
Message-ID: <bd917a0b38a04f39bc4fafc48c1a3334@huawei.com>
References: <a21ae45f4f414e6ca4553b30a7dd454d@huawei.com> <tencent_F7E9F91CB087F0DDB4BDA87D4435977F410A@qq.com>
In-Reply-To: <tencent_F7E9F91CB087F0DDB4BDA87D4435977F410A@qq.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.221.205.154]
Content-Type: multipart/alternative; boundary="_000_bd917a0b38a04f39bc4fafc48c1a3334huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/-bgBnRKxNVci5qGvNjdhZStkb9Y>
Subject: Re: [Cats] [cats] draft-ietf-cats-usecases-requirements-00 -> traffic path enforcement type is missing
X-BeenThere: cats@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Computing-Aware Traffic Steering \(CATS\)" <cats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cats>, <mailto:cats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cats/>
List-Post: <mailto:cats@ietf.org>
List-Help: <mailto:cats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cats>, <mailto:cats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 Sep 2023 08:20:39 -0000

Agree with Zongpeng, and I also see the value of Eduard's proposal.

I am not really sure that is it OK to add it as a requirement now, but I am OK to it If the WG agree to do so.

Respect,
Li Cheng



From: Cats <cats-bounces@ietf.org> On Behalf Of duzongpeng@foxmail.com
Sent: Wednesday, September 6, 2023 8:16 AM
To: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>
Cc: cats <cats@ietf.org>
Subject: Re: [Cats] [cats] draft-ietf-cats-usecases-requirements-00 -> traffic path enforcement type is missing

Hi, Eduard

    It is suggested that the CATS group firstly focuses on the requirement, and the architecture.

    However, IMO, I would prefer the tunnel choice.

    Meanwhile, a service point faraway may not be considered as an candidate, so that perhaps we can have a fewer number of tunnels.

Best Regards
Zongpeng Du

________________________________
duzongpeng@foxmail.com<mailto:duzongpeng@foxmail.com> & duzongpeng@chinamobile.com<mailto:duzongpeng@chinamobile.com>

From: Vasilenko Eduard<mailto:vasilenko.eduard=40huawei.com@dmarc.ietf.org>
Date: 2023-09-05 16:05
To: cats<mailto:cats@ietf.org>
Subject: Re: [Cats] [cats] draft-ietf-cats-usecases-requirements-00 -> traffic path enforcement type is missing
Hi all,
Let's assume that the decision has been made and some traffic/session has been decided to push to service instance X.
How?
It is MANDATORY to avoid states on the transit router hops. It is probably what you mean in requirement R13 (I am not sure because of general "node" terminology, "source node" for sure MUST keep all states).
We have potentially 2 choices:
1. Packet header modifications (like NAT, or to be more precise "like Load Balancer").
2. Establish a tunnel (SRv6, SR-MPLS, VxLAN, whatever). Then only the ingress router would keep states.

Of course, it is possible to be silent about this problem, and let all other WGs decide themselves on their way of implementation.
IMHO: it is better to state clearly that header modification is not an option.

By the way, we are talking here about Quadrillions (or Quintillions?) of additional tunnels on a global scale.
It is evident that only "Source Routing" (SRv6 or SR-MPLS) is capable of handling it because only SR is encoding the path in the packet itself.
Refreshment of huge tables through the control plane is not an option.
Maybe it is better to mention it too.

Best Regards
Eduard Vasilenko
Senior Architect
Network Algorithm Laboratory
Tel: +7(985) 910-1105

--
Cats mailing list
Cats@ietf.org<mailto:Cats@ietf.org>
https://www.ietf.org/mailman/listinfo/cats

v2.23.0 | Report a Bug | By Email