[6lo] New Version Notification for draft-thubert-6lo-forwarding-fragments-06.txt

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 19 July 2017 21:55 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 40FA6131BB2; Wed, 19 Jul 2017 14:55:48 -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 5Q3a2p4fiMot; Wed, 19 Jul 2017 14:55:46 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34DF7131BBD; Wed, 19 Jul 2017 14:55:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2424; q=dns/txt; s=iport; t=1500501339; x=1501710939; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=p7FwFzrRl0si2GqFcjHzJs7abK4N94RdE0TIhWgXltg=; b=TPJ9XD9IDEQ8rgJNKIVeo5YkEIRzj8+qfVZJZJSFyEUyH0DDQfvIF/H9 ZIzikE+u4tuHN8UGWyKVQVkeHaUBkU0Fr1IdepWo7bUdwQSwYF8dhUVnG TRTMp+aHfWTI2mrpI5u2lx3k9n70wXGLKGlGeMfc/PO8tK6TMnZrIvcn5 4=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DJAAAF1W9Z/4YNJK1cGgEBAQECAQEBAQgBAQEBg1pkgRQHjgSna4IRLoUZAhqDST8YAQIBAQEBAQEBayiFGQMDIxFDEgIBIgImAgICMBUQAgQBGoonELEUgiaLIQEBAQEBAQEBAQEBAQEBAQEBAQEBAR2BC4Idg02FBYMmhFeCYQWQV45iAodJjEWCFVeEeIpVlVsBHziBCnUVH4U6H4FndgGIEoENAQEB
X-IronPort-AV: E=Sophos;i="5.40,381,1496102400"; d="scan'208";a="456079694"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Jul 2017 21:55:30 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v6JLtUu0011911 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Jul 2017 21:55:30 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Wed, 19 Jul 2017 16:55:30 -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; Wed, 19 Jul 2017 16:55:30 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: "6lo@ietf.org" <6lo@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
Thread-Topic: New Version Notification for draft-thubert-6lo-forwarding-fragments-06.txt
Thread-Index: AQHTANj67pp8I7gHWkqcnptbqlUrE6JbsU1g
Date: Wed, 19 Jul 2017 21:55:29 +0000
Deferred-Delivery: Wed, 19 Jul 2017 21:55:10 +0000
Message-ID: <138e4e46f3cf4a34855c1e9a79690cd7@XCH-RCD-001.cisco.com>
References: <150050099386.7479.14777318079789135764.idtracker@ietfa.amsl.com>
In-Reply-To: <150050099386.7479.14777318079789135764.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.61.169.57]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/LXNuQHsN7bnO3iQPRd9bXZcX7Qo>
Subject: [6lo] New Version Notification for draft-thubert-6lo-forwarding-fragments-06.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: Wed, 19 Jul 2017 21:55:48 -0000

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

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

Abstract:
   Considering that an LLN frame can have a MAC payload below 100 bytes,
   an IPv6 packet might be fragmented into more than 10 fragments at the
   6LoWPAN layer.  In a 6LoWPAN mesh-under 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