[Tvr] Re: [External] FW: New Version Notification for draft-zdm-tvr-applicability-05.txt
"zhangli (CE)" <zhangli344@huawei.com> Wed, 11 February 2026 09:58 UTC
Return-Path: <zhangli344@huawei.com>
X-Original-To: tvr@mail2.ietf.org
Delivered-To: tvr@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id E3F5BB54C8FB for <tvr@mail2.ietf.org>; Wed, 11 Feb 2026 01:58:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -4.196
X-Spam-Level:
X-Spam-Status: No, score=-4.196 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pySHFUNHxKVD for <tvr@mail2.ietf.org>; Wed, 11 Feb 2026 01:58:53 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id D2294B54C5D7 for <tvr@ietf.org>; Wed, 11 Feb 2026 01:58:28 -0800 (PST)
Received: from mail.maildlp.com (unknown [172.18.224.83]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4f9v46619jzJ46j7 for <tvr@ietf.org>; Wed, 11 Feb 2026 17:57:26 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id EE56640573 for <tvr@ietf.org>; Wed, 11 Feb 2026 17:58:26 +0800 (CST)
Received: from dggpemf100007.china.huawei.com (7.185.36.214) by kwepemh500011.china.huawei.com (7.202.181.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 11 Feb 2026 17:58:09 +0800
Received: from kwepemj200018.china.huawei.com (7.202.194.30) by dggpemf100007.china.huawei.com (7.185.36.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Wed, 11 Feb 2026 17:58:09 +0800
Received: from kwepemj200018.china.huawei.com ([7.202.194.30]) by kwepemj200018.china.huawei.com ([7.202.194.30]) with mapi id 15.02.1544.011; Wed, 11 Feb 2026 17:58:09 +0800
From: "zhangli (CE)" <zhangli344@huawei.com>
To: "King, Daniel" <d.king@lancaster.ac.uk>
Thread-Topic: [External] FW: New Version Notification for draft-zdm-tvr-applicability-05.txt
Thread-Index: AdybPMRKavy+m7IhTBar5ilPL/TJwg==
Date: Wed, 11 Feb 2026 09:58:08 +0000
Message-ID: <ce7ae5194b014c39a012d5a1dcd7fe4d@huawei.com>
Accept-Language: en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.112.40.51]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Message-ID-Hash: L6OHQDDPDTH7Z4LH26GPR5KDEZDGRPPE
X-Message-ID-Hash: L6OHQDDPDTH7Z4LH26GPR5KDEZDGRPPE
X-MailFrom: zhangli344@huawei.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: tvr <tvr@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tvr] Re: [External] FW: New Version Notification for draft-zdm-tvr-applicability-05.txt
List-Id: Time-Variant Routing <tvr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tvr/ybMFaaTp9lRBtxIm8-TxY7SHdqI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tvr>
List-Help: <mailto:tvr-request@ietf.org?subject=help>
List-Owner: <mailto:tvr-owner@ietf.org>
List-Post: <mailto:tvr@ietf.org>
List-Subscribe: <mailto:tvr-join@ietf.org>
List-Unsubscribe: <mailto:tvr-leave@ietf.org>
Hi Dan, Thanks a lot for your contributions and support to this I-D. I think the question is for the WG, whether we need to focus on a single example and go into more detail. And whether we need a hackathon to prototype some TVR capabilities? Best regards Li > -----邮件原件----- > 发件人: King, Daniel <d.king@lancaster.ac.uk> > 发送时间: 2026年2月10日 6:02 > 收件人: zhangli (CE) <zhangli344@huawei.com> > 抄送: tvr <tvr@ietf.org> > 主题: RE: [External] FW: New Version Notification for > draft-zdm-tvr-applicability-05.txt > > Thanks, Li, and other I-D authors. > > I appreciate the time you took to publish a new version of the I-D, and thanks for > addressing my comments and assorted updates. Good job. > > Re: JSON examples > > Although I appreciate the multiple examples in the document, I wonder > whether we should focus on a single example and go into more detail. This > might depend on what the WG considers a suitable example of the TVR > schedule being applied. The document has five examples; would two or three be > enough, and then focus effort on providing a more detailed analysis and > over-the-wire example code via a repository in an appendix. > > Thinking aloud, why not combine with a network controller such as > TeraFlowSDN (https://tfs.etsi.org/) and work with partners to prototype some > TVR capabilities and consider operational aspects? This could also be supported > via an IETF Hackathon. I'd be willing to volunteer and contribute code to > achieve this if other people are also interested. > > Re: Next Steps > > Obviously up to the Chairs and WG, but I'd support adopting the I-D. I think it > provides a necessary step towards achieving the WG's final chartered > goals/milestones: > > https://datatracker.ietf.org/group/tvr/about/ > > Nov 2025 Applicability Statement > Mar 2026 Implementation and Operational Considerations > > BR, Dan. > > -----Original Message----- > From: zhangli (CE) <zhangli344@huawei.com> > Sent: 09 February 2026 12:17 > To: tvr <tvr@ietf.org> > Cc: tvr-chairs@ietf.org; King, Daniel <d.king@lancaster.ac.uk> > Subject: [External] FW: New Version Notification for > draft-zdm-tvr-applicability-05.txt > > This email originated outside the University. Check before clicking links or > attachments. > > Dear TVR WG, > > As you see, a new version of draft-zdm-tvr-applicability. This version addresses > multiple comments from Dan King and also includes additional improvements to > the document for clarity and explanation, including: > > - Editorial/Readability Improvements > - Explaining TVR definitions > - Clarification for protocol usage and data stores related to TVR usage > - Further narrowing the scope of use cases and examples > - More details on handling schedule conflicts > - Recommendations for Security Considerations > - Practical Operator Considerations > - Cleaning up code and NITS related to JSON > - Additional References > > Thanks a lot for Dan King's valuable comments and suggestions. > > So, dear chairs and all, does the working group want to adopt the document? > > If so, I think there is a need to make sure we have the right examples. A > suggestion from Dan King is that maybe we can extend the detail of the use case > JSON examples. Maybe Dan King can expand on what he means by this? > > Best regards > Li > > -----邮件原件----- > 发件人: internet-drafts@ietf.org <internet-drafts@ietf.org> > 发送时间: 2026年2月9日 19:39 > 收件人: Dongjie (Jimmy) <jie.dong@huawei.com>; zhangli (CE) > <zhangli344@huawei.com>; Mohamed Boucadair > <mohamed.boucadair@orange.com> > 主题: New Version Notification for draft-zdm-tvr-applicability-05.txt > > A new version of Internet-Draft draft-zdm-tvr-applicability-05.txt has been > successfully submitted by Li Zhang and posted to the IETF repository. > > Name: draft-zdm-tvr-applicability > Revision: 05 > Title: Applicability of TVR YANG Data Models > Date: 2026-02-09 > Group: Individual Submission > Pages: 39 > URL: https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.txt > Status: https://datatracker.ietf.org/doc/draft-zdm-tvr-applicability/ > HTML: https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.html > HTMLized: https://datatracker.ietf.org/doc/html/draft-zdm-tvr-applicability > Diff: https://author-tools.ietf.org/iddiff?url2=draft-zdm-tvr-applicability-05 > > Abstract: > > Time-Variant Routing (TVR) is a routing system that can accommodate > predicted topology changes caused by internal or external factors. > Typical use cases include resource preservation networks, operating > efficiency networks and dynamic reachability networks. This document > provides examples of how to implement the TVR scheduling capabilities > for key use cases. It describes which part of the TVR data model is > used and why, and it outlines operational and security considerations > when deploying TVR-based technologies. > > > > The IETF Secretariat >
- [Tvr] FW: New Version Notification for draft-zdm-… zhangli (CE)
- [Tvr] Re: [External] FW: New Version Notification… King, Daniel
- [Tvr] Re: [External] FW: New Version Notification… zhangli (CE)