[Dyncast] CAN key Q&A
Peng Liu <liupengyjy@chinamobile.com> Tue, 30 August 2022 08:30 UTC
Return-Path: <liupengyjy@chinamobile.com>
X-Original-To: dyncast@ietfa.amsl.com
Delivered-To: dyncast@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BAEC7C14CE3F; Tue, 30 Aug 2022 01:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.797
X-Spam-Level:
X-Spam-Status: No, score=-1.797 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no 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 lpt1f9dJWdEB; Tue, 30 Aug 2022 01:30:06 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id B570BC14CE44; Tue, 30 Aug 2022 01:30:02 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from cmccmta.chinamobile.com (unknown[172.16.121.91]) by rmmx-syy-dmz-app12-12012 (RichMail) with SMTP id 2eec630dca89f67-77bf4; Tue, 30 Aug 2022 16:30:01 +0800 (CST)
X-RM-TRANSID: 2eec630dca89f67-77bf4
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[10.2.53.83]) by rmsmtp-syy-appsvrnew06-12031 (RichMail) with SMTP id 2eff630dca88c9d-3b375; Tue, 30 Aug 2022 16:30:00 +0800 (CST)
X-RM-TRANSID: 2eff630dca88c9d-3b375
Date: Tue, 30 Aug 2022 16:35:12 +0800
From: Peng Liu <liupengyjy@chinamobile.com>
To: dyncast <dyncast@ietf.org>
Cc: rtgwg <rtgwg@ietf.org>, alto <alto@ietf.org>, tsvwg <tsvwg@ietf.org>
X-Priority: 3
X-GUID: E115B1AA-37D3-4437-8002-0BAF093B2B34
X-Has-Attach: no
X-Mailer: Foxmail 7.2.21.453[cn]
Mime-Version: 1.0
Message-ID: <2022083016351219200993@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart617673053081_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/RPAgFltm5Pkpsa4UY51IlKvVB7c>
Subject: [Dyncast] CAN key Q&A
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Anycast <dyncast.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dyncast>, <mailto:dyncast-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dyncast/>
List-Post: <mailto:dyncast@ietf.org>
List-Help: <mailto:dyncast-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dyncast>, <mailto:dyncast-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2022 08:30:08 -0000
Dear All, According to the progress and long discussion of CAN, we believe we have reached some consensus of the following three important issues. More detailed clarification of those issues could be found in https://github.com/CAN-IETF/CAN-BoF-ietf113/blob/main/CAN-Key-Q%26A.doc. 1. What is the relationship between CAN and ALTO? There were some discussions and the responses in https://github.com/CAN-IETF/CAN-BoF-ietf113/issues/5. After discussion in mailing list, IETF meetings with people interested in CAN and ALTO, we get the conclusion: CAN aims to provide a possible on-path solution for efficiently steering traffic to one of possible many service instances. The on-path solution requires to make the decision on the ingress node of the network based on network and other metrics. These kind of metrics may be distributed through extensions to routing protocols. ALTO is by inquiry and response, i.e., off-path, mechanism, which is different from the on-path approach proposed in CAN. 2. What is the relationship between CAN and TSV Area? We had presented CAN work in TSVWG in IETF114 and get the conclusion from TSV WG: CAN is a Routing Area work item, people can keep following TSV to see what is needed in transport protocols. 3. What is the relationship between CAN and Load Balancer? There are several types of Load Balancer, L7/L4/L3 load balancers. CAN aims to provide L3/L3.5 solution for selecting better instance, therefore CAN could act similar to the role of L3/L3.5 load balancer, but not limited to it. Any comments or suggestions are welcome. Regards, Peng liupengyjy@chinamobile.com
- [Dyncast] CAN key Q&A Peng Liu