From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 2491C3B29E for ; Fri, 17 Feb 2023 13:40:06 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 28FEF3898F for ; Fri, 17 Feb 2023 14:11:06 -0500 (EST) Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id gOKldRFdXPOR for ; Fri, 17 Feb 2023 14:11:05 -0500 (EST) Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id 7635D3898E for ; Fri, 17 Feb 2023 14:11:05 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1676661065; bh=WcsFFrYFMXcxF0d65+F9hTVeyHijkHeB3g8W7fJBeeU=; h=From:To:Subject:Date:From; b=Rp6XyAybD+b2BHizBHEGBAjvr8GsVjaQxeMepGVT9B9xXMtDTfTcm+uNcIEUWVVaE 3jNG01t3iXrGM7Hb824RNqAEHQ/jgcOXM+3Mb5NoiQCjlq91zORfWrShldvGfrGXKe F5ZWwN55lJ6DZBE44XaQjQLogvSOCHw11PmwI1AyF2IexTnpPw7bb/XqvCpdhj+ArR WrPlpIg1wA5VSXsh3DTk+6riZYiTDcy68MKCf8rHxzGnRxwiJydbi42pY7FgbmuLp/ 9ZJpmoM2I/eh//gR4Au/e7i+yVl8PZrPQUuHJomlMHKr+TPa4I1fU3V0xIyx/TS2Gw Ez+oFbHB3Ah+g== Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B809115B for ; Fri, 17 Feb 2023 13:40:03 -0500 (EST) From: Michael Richardson To: starlink@lists.bufferbloat.net X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1 X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m Subject: [Starlink] WG Action: Formed Time-Variant Routing (tvr) (fwd) The IESG: WG Action: Formed Time-Variant Routing (tvr) X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 17 Feb 2023 18:40:06 -0000 Return-Path: Received: from tuna.sandelman.ca ([unix socket]) by tuna (Cyrus 3.0.8-Debian-3.0.8-6+deb10u6) with LMTPA; Fri, 17 Feb 2023 13:55:55 -0500 X-Cyrus-Session-Id: cyrus-13703-1676660155-2-15786339154267142084 X-Sieve: CMU Sieve 3.0 Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id C51113898C for ; Fri, 17 Feb 2023 13:55:55 -0500 (EST) X-Quarantine-ID: X-Amavis-Alert: BAD HEADER SECTION, Duplicate header field: "MIME-Version" Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id bJscaa6MVSpz for ; Fri, 17 Feb 2023 13:55:53 -0500 (EST) Received: from mail.ietf.org (mail.ietf.org [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by tuna.sandelman.ca (Postfix) with ESMTPS id AE6EB3898B for ; Fri, 17 Feb 2023 13:55:53 -0500 (EST) Authentication-Results: tuna.sandelman.ca; dkim=pass (1024-bit key; secure) header.d=ietf.org header.i=@ietf.org header.b="odBSzRNk"; dkim=pass (1024-bit key) header.d=ietf.org header.i=@ietf.org header.b="odBSzRNk"; dkim-atps=neutral Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BFA01C136149 for ; Fri, 17 Feb 2023 10:24:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1676658287; bh=9Tq17KZ18sRxq92lSIMHQxhDlX19QWv1yxCzQ6dKFkY=; h=From:To:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=odBSzRNkAi5g+xWeBHP0rknwV3bbYn3ti3xEiokucLXNwCh9bNMa+nPTGouJEfPW8 lx3YoUa8Ppe55wRgXry2WF+FUj0Ay+++fb6uy84PpOMhS0ihB95GoMfDJr6SSqQ1oU VffVYcxeBInDG9rG3qJIZzTL/E97565TRbpAilBc= X-Mailbox-Line: From ietf-announce-bounces@ietf.org Fri Feb 17 10:24:47 2023 Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 72777C1524BC; Fri, 17 Feb 2023 10:24:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1676658287; bh=9Tq17KZ18sRxq92lSIMHQxhDlX19QWv1yxCzQ6dKFkY=; h=From:To:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:Cc; b=odBSzRNkAi5g+xWeBHP0rknwV3bbYn3ti3xEiokucLXNwCh9bNMa+nPTGouJEfPW8 lx3YoUa8Ppe55wRgXry2WF+FUj0Ay+++fb6uy84PpOMhS0ihB95GoMfDJr6SSqQ1oU VffVYcxeBInDG9rG3qJIZzTL/E97565TRbpAilBc= X-Original-To: ietf-announce@ietf.org Delivered-To: ietf-announce@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C93CC14F74B; Fri, 17 Feb 2023 10:24:45 -0800 (PST) MIME-Version: 1.0 From: The IESG To: "IETF-Announce" Subject: WG Action: Formed Time-Variant Routing (tvr) X-Test-IDTracker: no X-IETF-IDTracker: 9.10.0 Auto-Submitted: auto-generated Precedence: bulk MIME-Version: 1.0 Message-ID: <167665828550.20350.8180153576099315786@ietfa.amsl.com> Date: Fri, 17 Feb 2023 10:24:45 -0800 Archived-At: X-BeenThere: ietf-announce@ietf.org X-Mailman-Version: 2.1.39 List-Id: "IETF announcement list. No discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: tvr@ietf.org, The IESG , tvr-chairs@ietf.org Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ietf-announce-bounces@ietf.org Sender: "IETF-Announce" A new IETF WG has been formed in the Routing Area. For additional information, please contact the Area Directors or the WG Chairs. Time-Variant Routing (tvr) ----------------------------------------------------------------------- Current status: Proposed WG Chairs: Edward Birrane Tony Li Assigned Area Director: Alvaro Retana Routing Area Directors: Alvaro Retana John Scudder Andrew Alston 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 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 groups working on non-terrestrial networks, including DTN, CCAMP, DETNET, RAW, and DRIP. In addition, 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, for configuration and monitoring. (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 _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www.ietf.org/mailman/listinfo/ietf-announce