[secdir] [new-work] WG Review: Time-Variant Routing (tvr)
The IESG <iesg@ietf.org> Fri, 03 February 2023 18:43 UTC
Return-Path: <new-work-bounces@ietf.org>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 56BC0C4C0FAD; Fri, 3 Feb 2023 10:43:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1675449821; bh=6Vz9dzrBKiwSStGk1/XFifB8zDMFGVNXlGmfGCaVdmA=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To; b=WdEY2UPZUoIGsZX4c63+I7oNZvhYDoF79R64Tjm1iXjbKWPKmjYFXnqtYiCdgISsS 5S543vW5AFNKjrC1W+aV+xHMWBVdX3Qn6mjKWj1tope0UaqsMhilc06fNzvoNuTKL+ DS9YFhvO1RnHpRHwp0o1MEiLPA+utiAB8u31mBnw=
X-Mailbox-Line: From new-work-bounces@ietf.org Fri Feb 3 10:43:41 2023
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EFBC5C49C221; Fri, 3 Feb 2023 10:43:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1675449821; bh=6Vz9dzrBKiwSStGk1/XFifB8zDMFGVNXlGmfGCaVdmA=; h=From:To:Date:Subject:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Reply-To; b=WdEY2UPZUoIGsZX4c63+I7oNZvhYDoF79R64Tjm1iXjbKWPKmjYFXnqtYiCdgISsS 5S543vW5AFNKjrC1W+aV+xHMWBVdX3Qn6mjKWj1tope0UaqsMhilc06fNzvoNuTKL+ DS9YFhvO1RnHpRHwp0o1MEiLPA+utiAB8u31mBnw=
X-Original-To: new-work@ietf.org
Delivered-To: new-work@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 46D5FC14CF12 for <new-work@ietf.org>; Fri, 3 Feb 2023 10:43:34 -0800 (PST)
MIME-Version: 1.0
From: The IESG <iesg@ietf.org>
To: new-work@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 9.8.0
Auto-Submitted: auto-generated
Precedence: bulk
MIME-Version: 1.0
Reply_to: <iesg@ietf.org>
Message-ID: <167544981428.40004.5910333766159812198@ietfa.amsl.com>
Date: Fri, 03 Feb 2023 10:43:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/new-work/-Ori5Nfb0RsK4ZzkIQ1Xnmr9mAw>
X-BeenThere: new-work@ietf.org
X-Mailman-Version: 2.1.39
Reply-To: iesg@ietf.org
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: new-work-bounces@ietf.org
Sender: new-work <new-work-bounces@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/Scf0oUcNkh1Nbssg5GJgddkE4jU>
X-Mailman-Approved-At: Fri, 03 Feb 2023 13:07:55 -0800
Subject: [secdir] [new-work] WG Review: Time-Variant Routing (tvr)
X-BeenThere: secdir@ietf.org
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Feb 2023 18:43:42 -0000
A new IETF WG has been proposed in the Routing Area. The IESG has not made any determination yet. The following draft charter was submitted, and is provided for informational purposes only. Please send your comments to the IESG mailing list (iesg@ietf.org) by 2023-02-13. Time-Variant Routing (tvr) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Edward Birrane <edward.birrane@jhuapl.edu> Tony Li <tony.li@tony.li> Assigned Area Director: Alvaro Retana <aretana.ietf@gmail.com> Routing Area Directors: Alvaro Retana <aretana.ietf@gmail.com> John Scudder <jgs@juniper.net> Andrew Alston <andrew-ietf@liquid.tech> Mailing list: Address: tvr@ietf.org To subscribe: https://www.ietf.org/mailman/listinfo/tvr Archive: https://mailarchive.ietf.org/arch/browse/tvr/ Group page: https://datatracker.ietf.org/group/tvr/ Charter: https://datatracker.ietf.org/doc/charter-ietf-tvr/ Existing IETF routing protocols expect to maintain contemporaneous, end-to-end connected paths across a network. Changes to that connectivity, such as the loss of an adjacent peer, need the routing protocols to react to reduce the impact on the network traffic. However, a growing number of use cases exist where predicted variations (restoration, activation, or loss) to the topology are an expected part of normal network operations. For example, in networks with mobile nodes, such as aerial vehicles and some orbiting spacecraft constellations, links can be lost and re-established, or neighbors may change as a function of their mobility. Similarly, network traffic might be routed based on energy costs or expected user data volumes, which may vary predictably over time in networks prioritizing green computing and energy efficiency. In these cases, the predicted loss and restoration of an adjacency, or formation of an alternate adjacency, should be seen as non-disruptive events. Support for such use cases and expected changes in a routing system is called Time-Variant Routing (TVR). The Time-Variant Routing Working Group (TVR WG) is chartered to define information and data models that address time-based, scheduled changes to a network. Time-based changes may include changes to links, adjacencies, cost, and - in some cases - traffic volumes. The models are expected to satisfy the non-terrestrial networks' requirements as their main driver. Still, they should be general enough to encompass other types of networks and use cases. They should also be agnostic with respect to other control plane elements. The models are expected to leverage existing IETF-defined protocols and mechanisms where possible. The WG may also define terminology and concepts where needed, as well as address the impacts of a continually changing topology on the hierarchical structure of the network. The TVR WG will collaborate with other groups working on non-terrestrial networks, including DTN, CCAMP, DETNET, and RAW. The outputs from the WG will be provided to other working groups for consideration, which may use the material to incorporate time-variant attributes and behaviors into individual protocols. Specifically, the TVR WG will work on these items: (1) Problem Statement and Use cases This document (or set of documents) should include a description of the problem statement and related use cases to guide the remaining work. It exists to support the efforts of the Working Group and help newcomers, and it might not be published as an IETF Stream RFC. (2) Requirements This document should include definitions, requirements, notes, rationales, and examples. (3) Information Model This document (or set of documents) should describe the attributes needed, and the relationship between them, to enable routing and forwarding decisions in the presence of time-variant network parameters. (4) Data Model This document (or set of documents) should specify a YANG Data Model (or multiple modules) based on the Information Model. (5) Applicability Statement This document should provide an applicability statement on how the information and data models may be used, along with required ancillary IETF technology, to solve the use cases and requirements. (6) Implementation and Operational Considerations This document should provide advice and guidance to implementors and operators. Milestones: Nov 2023 - Problem Statement and Use cases Mar 2024 - Requirements Jul 2024 - Information Model Nov 2024 - Data Model Nov 2024 - Applicability Statement Nov 2024 - Implementation and Operational Considerations _______________________________________________ new-work mailing list new-work@ietf.org https://www.ietf.org/mailman/listinfo/new-work