[Tvr] Re: Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)

Tianran Zhou <zhoutianran@huawei.com> Fri, 08 May 2026 22:51 UTC

Return-Path: <zhoutianran@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 D6363EB7D662; Fri, 8 May 2026 15:51:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1778280690; bh=4ZQtuLcTjrWARjxCZrKqeSVtRa6gjriKFnrRoskmtz4=; h=From:To:Subject:Date:References:In-Reply-To; b=N622BUKkAXQIu6FQhIT69F99Y34iwLv2hGYKhAG/Hw5O778kdpTJ7ZvabTvy6MuV1 lsf0tFVWIGnqCZxZDsNok79eJe8EU76Ok/xX1W1kC1T7+Ke0IWkGzpCYhv19Jd2UHN 1/UTvQXPxdQZqpnorS0DW2emdAB/iQ3ICOae1lFw=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -3.627
X-Spam-Level:
X-Spam-Status: No, score=-3.627 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, INVALID_MSGID=0.568, 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 I8LqEJBfFhhB; Fri, 8 May 2026 15:51:27 -0700 (PDT)
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 B967FEB7D545; Fri, 8 May 2026 15:50:21 -0700 (PDT)
Received: from mail.maildlp.com (unknown [172.18.224.150]) by frasgout.his.huawei.com (SkyGuard) with ESMTPS id 4gC47p6j5BzJ468N; Sat, 9 May 2026 06:49:58 +0800 (CST)
Received: from kwepemh500011.china.huawei.com (unknown [7.202.181.142]) by mail.maildlp.com (Postfix) with ESMTPS id CF4DF40571; Sat, 9 May 2026 06:50:19 +0800 (CST)
Received: from kwepemf200008.china.huawei.com (7.202.181.234) 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; Sat, 9 May 2026 06:50:17 +0800
Received: from kwepemf100007.china.huawei.com (7.202.181.221) by kwepemf200008.china.huawei.com (7.202.181.234) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1544.11; Sat, 9 May 2026 06:50:17 +0800
Received: from kwepemf100007.china.huawei.com ([7.202.181.221]) by kwepemf100007.china.huawei.com ([7.202.181.221]) with mapi id 15.02.1544.036; Sat, 9 May 2026 06:50:17 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Tony Li <tony.li@tony.li>, "tvr@ietf.org" <tvr@ietf.org>, "tvr-chairs@ietf.org" <tvr-chairs@ietf.org>, "draft-zdm-tvr-applicability@ietf.org" <draft-zdm-tvr-applicability@ietf.org>
Thread-Topic: [Tvr] Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)
Thread-Index: AQHc1NI0mNYd8iFb+UisnHzL3fADOrYE0HCt
Date: Fri, 08 May 2026 22:50:17 +0000
Message-ID: 9D45A1EA-66FA-4A8A-9C46-F4DAF4C7C3B9
References: <177713499783.1637548.13279538944949742448@dt-datatracker-b45949c58-5szpr>
In-Reply-To: <177713499783.1637548.13279538944949742448@dt-datatracker-b45949c58-5szpr>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_9D45A1EA66FA4A8A9C46F4DAF4C7C3B9_"
MIME-Version: 1.0
Message-ID-Hash: GNOJBNZSDNUHLQUFN7AX5YLIAWYCKB2J
X-Message-ID-Hash: GNOJBNZSDNUHLQUFN7AX5YLIAWYCKB2J
X-MailFrom: zhoutianran@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
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Tvr] Re: Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)
List-Id: Time-Variant Routing <tvr.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tvr/5_58q8TaIQznZGRZIaVlgauzY44>
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>

I support the adoption of this draft.
I think it is useful to introduce how to apply TVR in various scenarios.

Cheers,
Tianran




________________________________

Sent from WeLink

发件人:Tony Li via Datatracker <noreply@ietf.org<mailto:noreply@ietf.org>>
收件人:tvr@ietf.org <tvr@ietf.org<mailto:tvr@ietf.org>>;tvr-chairs@ietf.org <tvr-chairs@ietf.org<mailto:tvr-chairs@ietf.org>>;draft-zdm-tvr-applicability@ietf.org <draft-zdm-tvr-applicability@ietf.org<mailto:draft-zdm-tvr-applicability@ietf.org>>
时 间:2026-04-26 00:40:20
主 题:[Tvr] Call for adoption and IPR: draft-zdm-tvr-applicability-05 (Ends 2026-05-09)

This message starts a tvr WG Call for Adoption and IPR of:
draft-zdm-tvr-applicability-05

This Working Group Call for Adoption and IPR ends on 2026-05-09

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.

Please reply to this message and indicate whether or not you support adoption
of this Internet-Draft by the tvr WG. Comments to explain your preference are
greatly appreciated. Please reply to all recipients of this message and
include this message in your response.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Authors and contributors MUST reply to this message with either:

"No, I'm not aware of any IPR that applies to this draft"
or
"Yes, I'm aware of IPR that applies to this draft"

If so, has this IPR been disclosed in compliance with IETF IPR rules
(see RFCs 3669, 5378 and 8179 for more details)?

If yes to the above, please state either:

"Yes, the IPR has been disclosed in compliance with IETF IPR rules"
or
"No, the IPR has not been disclosed"

If you answer no, please provide any additional details you think
appropriate. If you are listed as a document author or contributor
please answer the above by responding to this email regardless of
whether or not you are aware of any relevant IPR. This document will not
advance to the next stage until a response has been received from each
author.

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-zdm-tvr-applicability/

There is also an HTML version available at:
https://www.ietf.org/archive/id/draft-zdm-tvr-applicability-05.html

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-zdm-tvr-applicability-05

--
Tvr mailing list -- tvr@ietf.org
To unsubscribe send an email to tvr-leave@ietf.org