Last Call: <draft-ietf-roll-dao-projection-36.txt> (Root initiated routing state in RPL) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Wed, 05 February 2025 15:34 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (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 ietfa.amsl.com (Postfix) with ESMTPSA id D6355C14F6AB; Wed, 5 Feb 2025 07:34:31 -0800 (PST)
Received: from [10.244.8.188] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 5CAD4C1D3DC3; Wed, 5 Feb 2025 07:34:31 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-roll-dao-projection-36.txt> (Root initiated routing state in RPL) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 12.34.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <173876967102.456215.9483647261937127919@dt-datatracker-6f7f8bdd64-25rl2>
Date: Wed, 05 Feb 2025 07:34:31 -0800
Message-ID-Hash: BLL4TU6UZZLLSJTAQT7JCRTTKBWBXNAO
X-Message-ID-Hash: BLL4TU6UZZLLSJTAQT7JCRTTKBWBXNAO
X-MailFrom: iesg-secretary@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-roll-dao-projection@ietf.org, mariainesrobles@googlemail.com, roll-chairs@ietf.org, roll@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: last-call@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jwntD3MwNOYwlHzHZYz1xmgwGNE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
The IESG has received a request from the Routing Over Low power and Lossy networks WG (roll) to consider the following document: - 'Root initiated routing state in RPL' <draft-ietf-roll-dao-projection-36.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2025-02-19. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract This document extends RFC 6550, RFC 6553, and RFC 8138 to enable a RPL Root to install and maintain Projected Routes within its DODAG. A Projected Route is one that is computed by a central entity, such as a Path Computation Engine (PCE) and installed in the routers that instantiate it, using the procedures defined here. The routes are installed along a selected set of nodes that may or may not include itself, for a chosen duration. This potentially enables routes that are more optimized or resilient than those obtained with the classical distributed operation of RPL, either in terms of the size of a Routing Header or in terms of path length, which impacts both the latency and the packet delivery ratio. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-roll-dao-projection/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/5761/ https://datatracker.ietf.org/ipr/2620/ The document contains these normative downward references. See RFC 3967 for additional information: rfc9030: An Architecture for IPv6 over the Time-Slotted Channel Hopping Mode of IEEE 802.15.4 (6TiSCH) (Informational - Internet Engineering Task Force (IETF) stream) draft-ietf-raw-architecture: Reliable and Available Wireless Architecture (None - Internet Engineering Task Force (IETF) stream)