IETF Logo Mail Archive

[Dyncast] CAN BoF issues and the next steps

"liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com> Mon, 11 April 2022 06:32 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 0525A3A1BF1 for <dyncast@ietfa.amsl.com>; Sun, 10 Apr 2022 23:32:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikcMS29VNrWl for <dyncast@ietfa.amsl.com>; Sun, 10 Apr 2022 23:31:57 -0700 (PDT)
Received: from cmccmta2.chinamobile.com (cmccmta2.chinamobile.com [221.176.66.80]) by ietfa.amsl.com (Postfix) with ESMTP id 741E43A1BED for <dyncast@ietf.org>; Sun, 10 Apr 2022 23:31:56 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app06-12006 (RichMail) with SMTP id 2ee66253cb58003-681fc; Mon, 11 Apr 2022 14:31:54 +0800 (CST)
X-RM-TRANSID: 2ee66253cb58003-681fc
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[10.2.53.104]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee46253cb58c67-0a31d; Mon, 11 Apr 2022 14:31:54 +0800 (CST)
X-RM-TRANSID: 2ee46253cb58c67-0a31d
Date: Mon, 11 Apr 2022 14:36:04 +0800
From: "liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com>
To: dyncast <dyncast@ietf.org>
X-Priority: 3
X-GUID: 782D2FB4-DD7D-418A-836F-31AD2145A4A1
X-Has-Attach: no
X-Mailer: Foxmail 7.2.21.453[cn]
Mime-Version: 1.0
Message-ID: <2022041114360459722023@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart125034030354_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/UfQ0HpotkIZyCLO7zLB_D0Q1O2g>
Subject: [Dyncast] CAN BoF issues and the next steps
X-BeenThere: dyncast@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 11 Apr 2022 06:32:02 -0000

Dear all,

Thanks for supporting and joining the CAN work.  We can see that the BoF was successful and had a good discussion, and almost everyone agree on the use case that considering more metrics for steering traffic is valuable and a right direction. https://notes.ietf.org/notes-ietf-113-can. 

Here we list the issues according to BoF talking and give the preliminary answers to them, which could be found at https://github.com/CAN-IETF/CAN-BoF-ietf113/issues. If missing any issue, please let us know and we could add it. The issues will continue to be iterated and then closed.

Moreover, we will update the key drafts according to the BoF talking and further thinking. If you have the interests, please feel free to contact us. 

Regards,
Peng



liupengyjy@chinamobile.com

v2.23.0 | Report a Bug | By Email