[Roll] RFC 9035 on A Routing Protocol for Low-Power and Lossy Networks (RPL) Destination-Oriented Directed Acyclic Graph (DODAG) Configuration Option for the 6LoWPAN Routing Header

rfc-editor@rfc-editor.org Sat, 01 May 2021 06:15 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 239213A36E2; Fri, 30 Apr 2021 23:15:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4P80cebU9GsM; Fri, 30 Apr 2021 23:15:14 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5F783A36DF; Fri, 30 Apr 2021 23:15:14 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 94B63F407A3; Fri, 30 Apr 2021 23:14:57 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, roll@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210501061457.94B63F407A3@rfc-editor.org>
Date: Fri, 30 Apr 2021 23:14:57 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/oOGBetRLNUDgo0zULPZdm8PQP5I>
Subject: [Roll] =?utf-8?q?RFC_9035_on_A_Routing_Protocol_for_Low-Power_an?= =?utf-8?q?d_Lossy_Networks_=28RPL=29_Destination-Oriented_Directed_Acycli?= =?utf-8?q?c_Graph_=28DODAG=29_Configuration_Option_for_the_6LoWPAN_Routin?= =?utf-8?q?g_Header?=
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/roll/>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 01 May 2021 06:15:20 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 9035

        Title:      A Routing Protocol for Low-Power 
                    and Lossy Networks (RPL) Destination-Oriented Directed 
                    Acyclic Graph (DODAG) Configuration Option for 
                    the 6LoWPAN Routing Header 
        Author:     P. Thubert, Ed.,
                    L. Zhao
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2021 
        Mailbox:    pthubert@cisco.com,
                    liz3@cisco.com
        Pages:      9
        Updates:    RFC 8138

        I-D Tag:    draft-ietf-roll-turnon-rfc8138-18.txt

        URL:        https://www.rfc-editor.org/info/rfc9035

        DOI:        10.17487/RFC9035

This document updates RFC 8138 by defining a bit in the Routing
Protocol for Low-Power and Lossy Networks (RPL) Destination-Oriented
Directed Acyclic Graph (DODAG) Configuration option to indicate
whether compression is used within the RPL Instance and to specify
the behavior of nodes compliant with RFC 8138 when the bit is set and
unset.

This document is a product of the Routing Over Low power and Lossy networks Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC