[6lo] FW: New Version Notification for draft-thubert-6lo-forwarding-fragments-05.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 06 April 2017 17:17 UTC

Return-Path: <pthubert@cisco.com>
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 55A6C129571 for <6lo@ietfa.amsl.com>; Thu, 6 Apr 2017 10:17:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 s_5yqO-4pc1y for <6lo@ietfa.amsl.com>; Thu, 6 Apr 2017 10:17:36 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71C90129488 for <6lo@ietf.org>; Thu, 6 Apr 2017 10:17:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2440; q=dns/txt; s=iport; t=1491499056; x=1492708656; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=s/OTLkLGvaQJr03krnv/FUTlwrGbJIvPkE3M0GmRoTI=; b=Z52KHadCCFGV3NoCT5XbseokX7Rz8K183bSuwOQRXNKguX0/o6DjUTlP nH3q2Wio7jQrTYcTNFEpbjjZO2+Kx7I0t9PqnNKfKX9KPkWOebAFjLYoY PPEBoEMV2BaBaWHdaBdBF117b/eeaDRA/gIMFYwdEVcHqaKJ3vGdbCalq o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CfAgBId+ZY/5hdJa1cGwEBAQMBAQEJAQEBg1RhgQsHg1yKEqcSgg8shXYCGoMrPxgBAgEBAQEBAQFrHQuFFgMDIxFDEgIBCBoCJgICAjAVBgEGAwIEG4oGDqo7giaKZwEBAQEBAQEBAQEBAQEBAQEBAQEfgQuFQ4RwgxeERYJfBY9pjQoBhn2LTIIHVYRZihGTdwEfOIEFWxUYhQEggWN1AYhRgQ0BAQE
X-IronPort-AV: E=Sophos;i="5.37,160,1488844800"; d="scan'208";a="407892733"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 06 Apr 2017 17:17:35 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v36HHZKh012007 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <6lo@ietf.org>; Thu, 6 Apr 2017 17:17:35 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 6 Apr 2017 12:17:34 -0500
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1210.000; Thu, 6 Apr 2017 12:17:34 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-forwarding-fragments-05.txt
Thread-Index: AQHSrvlR+u/QwNjB40m8dUdyD98E7KG4lPDg
Date: Thu, 06 Apr 2017 17:17:19 +0000
Deferred-Delivery: Thu, 6 Apr 2017 17:17:06 +0000
Message-ID: <48682a24f56745adab5d10cab08c6dad@XCH-RCD-001.cisco.com>
References: <149149889451.22012.6754114764872651376.idtracker@ietfa.amsl.com>
In-Reply-To: <149149889451.22012.6754114764872651376.idtracker@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.55.22.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/eOzn3sUf024snT-rICb4Arsr8qw>
Subject: [6lo] FW: New Version Notification for draft-thubert-6lo-forwarding-fragments-05.txt
X-BeenThere: 6lo@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 06 Apr 2017 17:17:38 -0000


A new version of I-D, draft-thubert-6lo-forwarding-fragments-05.txt
has been successfully submitted by Pascal Thubert and posted to the IETF repository.

Name:		draft-thubert-6lo-forwarding-fragments
Revision:	05
Title:		LLN Fragment Forwarding and Recovery
Document date:	2017-04-06
Group:		Individual Submission
Pages:		18
URL:            https://www.ietf.org/internet-drafts/draft-thubert-6lo-forwarding-fragments-05.txt
Status:         https://datatracker.ietf.org/doc/draft-thubert-6lo-forwarding-fragments/
Htmlized:       https://tools.ietf.org/html/draft-thubert-6lo-forwarding-fragments-05
Htmlized:       https://datatracker.ietf.org/doc/html/draft-thubert-6lo-forwarding-fragments-05
Diff:           https://www.ietf.org/rfcdiff?url2=draft-thubert-6lo-forwarding-fragments-05

Abstract:
   Considering that an LLN link-layer frame can have a payload below 100
   bytes, an IPv6 packet might be fragmented more than 10 fragments at
   the 6LoWPAN layer.  In a 6LoWPAN mesh-under mesh network, the
   fragments can be forwarded individually across the mesh, whereas a
   route-over mesh network, a fragmented 6LoWPAN packet must be
   reassembled at every hop, which causes latency and congestion.  This
   draft introduces a simple protocol to forward individual fragments
   across a route-over mesh network, and, regardless of the type of
   mesh, recover the loss of individual fragments across the mesh and
   protect the network against bloat with a minimal flow control.

                                                                                  


Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat