[6lo] RFC 8930 on On Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6 Network
rfc-editor@rfc-editor.org Mon, 23 November 2020 20:05 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: 6lo@ietfa.amsl.com
Delivered-To: 6lo@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 96A083A0C04; Mon, 23 Nov 2020 12:05:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.01
X-Spam-Level:
X-Spam-Status: No, score=0.01 tagged_above=-999 required=5 tests=[SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 L8hmwN-BWivx; Mon, 23 Nov 2020 12:05:30 -0800 (PST)
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 BA89C3A0C40; Mon, 23 Nov 2020 12:05:18 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 3E191F4078C; Mon, 23 Nov 2020 12:05:17 -0800 (PST)
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, 6lo@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20201123200517.3E191F4078C@rfc-editor.org>
Date: Mon, 23 Nov 2020 12:05:17 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/Ige8o2Q6pADTC4V9UlPbliJNfcI>
Subject: [6lo] RFC 8930 on On Forwarding 6LoWPAN Fragments over a Multi-Hop IPv6 Network
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Mailing list for the 6lo WG for Internet Area issues in IPv6 over constrained node networks." <6lo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lo>, <mailto:6lo-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/6lo/>
List-Post: <mailto:6lo@ietf.org>
List-Help: <mailto:6lo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lo>, <mailto:6lo-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 20:05:39 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8930
Title: On Forwarding 6LoWPAN Fragments over
a Multi-Hop IPv6 Network
Author: T. Watteyne, Ed.,
P. Thubert, Ed.,
C. Bormann
Status: Standards Track
Stream: IETF
Date: November 2020
Mailbox: thomas.watteyne@analog.com,
pthubert@cisco.com,
cabo@tzi.org
Pages: 12
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-6lo-minimal-fragment-15.txt
URL: https://www.rfc-editor.org/info/rfc8930
DOI: 10.17487/RFC8930
This document provides generic rules to enable the forwarding of an
IPv6 over Low-Power Wireless Personal Area Network (6LoWPAN) fragment
over a route-over network. Forwarding fragments can improve both
end-to-end latency and reliability as well as reduce the buffer
requirements in intermediate nodes; it may be implemented using RFC
4944 and Virtual Reassembly Buffers (VRBs).
This document is a product of the IPv6 over Networks of Resource-constrained Nodes 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