[Dyncast] New version of CAN/Dyncast drafts
"liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com> Tue, 12 July 2022 09:14 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 7F160C157B41; Tue, 12 Jul 2022 02:14:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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, 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 wwAOeTim74qz; Tue, 12 Jul 2022 02:14:18 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id CD110C14F733; Tue, 12 Jul 2022 02:14:16 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.97]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee162cd3b666f3-c1c6f; Tue, 12 Jul 2022 17:14:14 +0800 (CST)
X-RM-TRANSID: 2ee162cd3b666f3-c1c6f
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from CMCC-LP (unknown[10.1.6.6]) by rmsmtp-syy-appsvrnew09-12034 (RichMail) with SMTP id 2f0262cd3b62770-c8bf1; Tue, 12 Jul 2022 17:14:13 +0800 (CST)
X-RM-TRANSID: 2f0262cd3b62770-c8bf1
Date: Tue, 12 Jul 2022 17:19:02 +0800
From: "liupengyjy@chinamobile.com" <liupengyjy@chinamobile.com>
To: dyncast <dyncast@ietf.org>
Cc: rtgwg <rtgwg@ietf.org>
X-Priority: 3
X-GUID: B9471CB7-4A07-43FD-934F-04F1416B32C0
X-Has-Attach: no
X-Mailer: Foxmail 7.2.21.453[cn]
Mime-Version: 1.0
Message-ID: <20220712171902397244296@chinamobile.com>
Content-Type: multipart/alternative; boundary="----=_001_NextPart376663174342_=----"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dyncast/-KZFc8ArI6M3X0wkP9_t6lPV3D4>
Subject: [Dyncast] New version of CAN/Dyncast drafts
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, 12 Jul 2022 09:14:22 -0000
Dear All, The updated and new CAN/dyncast drafts were posted. New version of problem statement, use cases, gap analysis and requirements, which were updated according to the BoF discussion and addressed some of the issues: draft-liu-dyncast-ps-usecases-04 (https://datatracker.ietf.org/doc/draft-liu-dyncast-ps-usecases/), updated the problem statement and use cases. draft-liu-dyncast-gap-reqs-00 (https://datatracker.ietf.org/doc/draft-liu-dyncast-gap-reqs/), was replaced with draft-liu-dyncast-reqs, which added the gap analysis and updated requirements. draft-li-dyncast-architecture-04 (https://datatracker.ietf.org/doc/draft-li-dyncast-architecture/), addressed some issues in the BoF. New draft of computing resource modeling, which describes the architecture of modeling and the considered usage in CAN： draft-liu-can-computing-resource-modeling-00 (https://datatracker.ietf.org/doc/draft-liu-can-computing-resource-modeling/) Please check and review them if you are interested in, the co authors welcome any comments and suggestions. Thanks. Regards, Peng liupengyjy@chinamobile.com
- [Dyncast] New version of CAN/Dyncast drafts liupengyjy@chinamobile.com