IETF Logo Mail Archive

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

"duzongpeng@foxmail.com" <duzongpeng@foxmail.com> Wed, 06 September 2023 06:21 UTC

Return-Path: <duzongpeng@foxmail.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 BEADDC151080 for <cats@ietfa.amsl.com>; Tue, 5 Sep 2023 23:21:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.84
X-Spam-Level:
X-Spam-Status: No, score=0.84 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HELO_DYNAMIC_IPADDR=1.951, HTML_FONT_LOW_CONTRAST=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=foxmail.com
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 M7KRHlWMMw2B for <cats@ietfa.amsl.com>; Tue, 5 Sep 2023 23:21:29 -0700 (PDT)
Received: from out203-205-251-85.mail.qq.com (out203-205-251-85.mail.qq.com [203.205.251.85]) (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 5100CC15107B for <cats@ietf.org>; Tue, 5 Sep 2023 23:21:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=foxmail.com; s=s201512; t=1693980980; bh=8q0XhNBtOzn8pAQq0S+VsgHc2D8uWm9zgxuBC3PEisg=; h=Date:From:To:Cc:Subject:References; b=uL9YYH4OVFIWLLn1NtWdjJ5DAMf4W4flOh2/NFpkbnkDfWPpkhmVPMM2qHBTKRDYQ FcNzhOiy2sAknB3bMi+XBQ4JEw7N0fW57s39dpyvlCOlxb2V4uhgrO293NyjZBgTYm ZAKe70aeiRej3ts8lpPkJ/ZpW7jMwmnp0GKpabN8=
Received: from cmcc-PC ([59.46.77.130]) by newxmesmtplogicsvrszb1-0.qq.com (NewEsmtp) with SMTP id 4131B2DB; Wed, 06 Sep 2023 14:16:19 +0800
X-QQ-mid: xmsmtpt1693980979t6ojzl8av
Message-ID: <tencent_F7E9F91CB087F0DDB4BDA87D4435977F410A@qq.com>
X-QQ-XMAILINFO: Mford2LpU4AoX+MhD3XB1EV71lR8h2fSFjraUTXbABa7z/eBUsJZZKgcNmnKyo /C4JePU83ZCmuB7YGmMdoq/EuRVRbAuq2hhE1wHOUYvGTHFOqvrcp4sjAh3+ts1P/HbA6KJ0/sf9 4grIdHd94yeHsPlj1Zb0zcPfiZGSjluVkBtaeUlEy9hhK0ba3HBVHiPrHcEfjUZMzameAcPAg/ze df9uZM49PiTTfoTNgYlda/vabXwfMuB4H2xZAwfIj1Astq3Tshyw5/gWJOmp8oRSk6iI9p3AfPTn igLrABfcxoT6Pk3g4oW++52dTMQyj2AzpdiJn6cAW7nHmLy/n3aQL1nppuKqDevebvS6d+SH/5Dp gQPThKrvHTz+jRPLANqtqzNsMbhmhhXOgKHNz0TgxW2bnLbyVvOsn7SLXMM6g2ctY3ncVGceicE9 5morCneh5D10DvA6dPJlrfqUQHaZO4lbxuu3wep60dnsaTJsL2Zn3zMcFUmfR9W7bFaWZihSNbta FxNm/DwkHjo0dFXoig3QQEaZ5ydValbjyHoJWtBISsEF/scvqs0jqGeb+K8m0TV7EMfwM7CRCIPh YnN5FunPauEv6FWzjwPCGW8c0DV/jDRUM+k3D9hGC+QhgojsNfqInogkcbpe788IW5pQtKSXuqaW Dawq/kiJcZFnxgByDGnEJfu4817JlTWiMotxO5/BnpRoLmXC66jf9G64JENtrFo2HYriJ+Jxatnw SgAt+sW+t2um75kcTpwYl9wcgrdrHjGxKwWV897wP+HIRiZWAsfQ8kSU0Eo6tCPbQ4zjHuIVWgBM Bt7Sx04FunvfMBxf2ujIsMocZuUTNC4C1jZ0xyraWQbOyXeho7Eb/zzsWOR275FqnOe82WdG0mkO kRJ1+YLHobeY8XYSr6R06fyVmm0D6A3A1XdwramEev7JZoT2hM2GbqRRog3zW7M3Lmiqy0QV09B3 iZ5ijwr2zkpveVT5ZXCyZqtujbIlK5gTkaBSgWLLBVa+VgVoy/I1ogsVyKBtqxDGTI2HGwNu8=
X-QQ-XMRINFO: Nq+8W0+stu50PRdwbJxPCL0=
Date: Wed, 06 Sep 2023 14:16:21 +0800
From: "duzongpeng@foxmail.com" <duzongpeng@foxmail.com>
To: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>
Cc: cats <cats@ietf.org>
References: <a21ae45f4f414e6ca4553b30a7dd454d@huawei.com>
X-Priority: 3
X-GUID: F025ECB9-2824-4DD7-8AA7-552013042242
X-Has-Attach: no
X-Mailer: Foxmail 7.2.25.178[cn]
Mime-Version: 1.0
X-OQ-MSGID: <2023090614162046046712@foxmail.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart837845081153_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cats/190dpIOGD0roTqIPabU5kZnBJXo>
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 06:21:33 -0000

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 & duzongpeng@chinamobile.com 
 
From: Vasilenko Eduard
Date: 2023-09-05 16:05
To: cats
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
https://www.ietf.org/mailman/listinfo/cats

v2.23.0 | Report a Bug | By Email