Re: [6lo] RIOT implementation for Selective Fragment Recovery
"Pascal Thubert (pthubert)" <pthubert@cisco.com> Thu, 07 November 2019 04:42 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 AAD5112009E for <6lo@ietfa.amsl.com>; Wed, 6 Nov 2019 20:42:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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 header.b=ddqNrIZd; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=u5lLu7Fg
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 TQbnM9AOR3dd for <6lo@ietfa.amsl.com>; Wed, 6 Nov 2019 20:42:21 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 297D0120033 for <6lo@ietf.org>; Wed, 6 Nov 2019 20:42:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5305; q=dns/txt; s=iport; t=1573101741; x=1574311341; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=2BeJosPz5OkT0hx7okyhu0WOvbYzscIgrYONoE5TVyo=; b=ddqNrIZdthU8QuMCupqMMxQ4VYpZBHBDiTw/7n7ALmMIEYmR+9rWDiT+ 9LEwuH95QOzGy6itqJKce2Rxs7s0nOzNxtd1ivKlCxmsNrcvmeVZRGtIp TbbK4nYSTPKbAkRNkl4wLa2SrpfgLm56wigLn2Ipan437E5vcZ3cZOegW c=;
IronPort-PHdr: 9a23:VUqOAhNuMffcjGPBt/Ml6mtXPHoupqn0MwgJ65Eul7NJdOG58o//OFDEu6w/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETBoZkYMTlg0kDtSCDBjjMP73ZSEgAOxJVURu+DewNk0GUMs=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D4AADGn8Nd/5pdJa1lHAEBAQEBBwEBEQEEBAEBgWwFAQELAYFKJCwFbFggBAsqCoQfgV6BaAOLAYI5k0GEYoEugSQDVAkBAQEMAQEYAQoKAgEBgwqBNgIXg3ckNgcOAgMLAQEEAQEBAgEFBG2FNwyFUgIEAQEQER0BASwLAQ8CAQgECjQCAgIlCyUCBA4FIoMAAYF5TQMuAQIBC6dTAoE4iGB1gTKCfgEBBYE0AYEUgkAYghcDBoE2AYUZaYYRGIFAP4EQAScME4JMPoJiAQGBOwYBAUuCYzKCLI0pgl6FP4k7jwcKgiSGMmSOKBuCPIdgj1aWdpE4AgQCBAUCDgEBBYFZAjCBWHAVOyoBgkFQERSQEiSDc4UUhT90gSiNLA4XgQsBgQ4BAQ
X-IronPort-AV: E=Sophos;i="5.68,276,1569283200"; d="scan'208,217";a="572544553"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Nov 2019 04:42:19 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id xA74NSSs031378 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 7 Nov 2019 04:24:28 GMT
Received: from xhs-aln-001.cisco.com (173.37.135.118) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Nov 2019 22:23:58 -0600
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 6 Nov 2019 22:23:58 -0600
Received: from NAM04-BN3-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 6 Nov 2019 23:23:58 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=aiL9O3/SBOD0ZCDyVhLjlpZP5pJih6HUXWo2d4XTavwMyN2yMs0TmdLFF235Y+UPzr6dHDvbgBcUKdaxU/pdk9wEBZ6DqZaZKEZZkr62a/i2EEi7vS5JwSJDBwt8LR2Z+bIrZ0opio/5ZZUgu8TCS3VIy55cTVE7nwONXt8Gbnd4fmupSuwE84/XWdvfdsF++r07m/wyUpxnMn4r28SnuBCeCtffbahOoc2Fn/9CeJBSyekzK4mclEZWZGZ6qquuJEKbWCtXtuf8CHHYK9329suuZnjly09UwSKaqT3WdqJ8LgGOZbuI7K9aXeXDrTgKpqLSdIkJtG0FeezxGeU/TQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2BeJosPz5OkT0hx7okyhu0WOvbYzscIgrYONoE5TVyo=; b=MNOMLksRTJgGJw5kcM0m315kSGOx9Cov9oTygu8idmP8QaG+Gyan8xJwHdJR4YC8OdrTNDEQ2aKC51rdEe8CcptL+8BRG7o0lKFSBpVhhidhOBk9RdyhdCUeJ+3XucTFmvHkV0W/tRTP97wUGUarTrnM+xYwE9y+KqieF2o4PD+BCzMCgmGftlc3cqdApFYjHSbzWqPMCmWPtqLHAcsV4TCocKwpP2raF/WM3gXYYiHrxwiB68mpDM9ikrcppe0QF3gMue7I4YKH2NXh/qIvChB653hOCGok3ATCgS6SPwd+5NMPsVDCEnfWTZQAtNbuf+yB0eCsTzZAbOgsmge0bw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=2BeJosPz5OkT0hx7okyhu0WOvbYzscIgrYONoE5TVyo=; b=u5lLu7Fg/k6VRZvEDl/ndpvfpJ3Dmsx9CZAtXVG1i8KVh1Trbkw5H8L4h+8ZD7X16Z4DZHVmprVT2KAjB53aJTY4EoSnQI0ATQiM6PyulE8ClffhTIYHHbavCLEp70dLBCR7Qw1T8yISFPeN8RtWCoUhBWoH63dvbsJJpRfdWQk=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (20.178.250.159) by MN2PR11MB4144.namprd11.prod.outlook.com (20.179.150.210) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.23; Thu, 7 Nov 2019 04:23:57 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::31c9:3a31:3c07:a920%6]) with mapi id 15.20.2430.020; Thu, 7 Nov 2019 04:23:57 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Martine Lenders <mail@martine-lenders.eu>
CC: "6lo@ietf.org" <6lo@ietf.org>
Thread-Topic: [6lo] RIOT implementation for Selective Fragment Recovery
Thread-Index: AQHVlGq6M5gO4qFEGE6MyMe2VTF1Vqd/HYLZ
Date: Thu, 07 Nov 2019 04:23:57 +0000
Message-ID: <DB633F1A-57F8-4361-9F5B-4A6173AEBBC7@cisco.com>
References: <CALHmdRwnxq-P96dcTzZ5mQgHsJR7q4833JTwdc4z_CJh4+Qs-A@mail.gmail.com>
In-Reply-To: <CALHmdRwnxq-P96dcTzZ5mQgHsJR7q4833JTwdc4z_CJh4+Qs-A@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pthubert@cisco.com;
x-originating-ip: [93.158.30.114]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1e005b37-b4ba-4138-957d-08d7633a4eb1
x-ms-traffictypediagnostic: MN2PR11MB4144:
x-ms-exchange-purlcount: 2
x-microsoft-antispam-prvs: <MN2PR11MB41448711C2E1CA533ADFC3A0D8780@MN2PR11MB4144.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0214EB3F68
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(396003)(366004)(39860400002)(376002)(189003)(199004)(76116006)(91956017)(33656002)(7736002)(66066001)(478600001)(81166006)(81156014)(8676002)(446003)(76176011)(11346002)(6436002)(66446008)(6916009)(476003)(64756008)(2906002)(2616005)(6506007)(66946007)(8936002)(316002)(66476007)(66556008)(486006)(99286004)(229853002)(25786009)(3846002)(26005)(6116002)(14444005)(256004)(36756003)(14454004)(66574012)(606006)(186003)(6246003)(54896002)(6306002)(5660300002)(71190400001)(71200400001)(236005)(6512007)(102836004)(966005)(4326008)(6486002)(1250700005)(86362001)(244885003); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB4144; H:MN2PR11MB3565.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: wgNtooaB6NvQpO761pXydbd3KhiXGGylFlYXWmH5DfcxhD/eOVTvuHudyrwOBfGgO3zC6KYTDgxCrJDIOL3UyzQbTYiwBg0W3r3zp/jWBpN5aKkTbhNxVBKG3EIRNXLipNAqquZOC4P8q9U7jpD3C5tOI/LhJoAkyseldP+N9v2wup+WQ6+W084rwLoomLG/e5UT+JZ9bsw+7+Y9jLqQNT6LdyixRpUUMCkTesxMIGYdOXMPhtpeqjt98XLGMO50ha6Wp32ayBQcJi/qpK/MVnUHgefwA6NANg53naUVOYrkVFWMP9mhrlZNMo/lLY74Fa+ndRRSkeO2Ukb6JJsEa0+I+Wt8Uw5lB0MCjgwHA5i64JWdu/xQ6yBv2LFmiy+92r/bNbbfGd8SGFjfQqlG/u4xbQfWFDHSicouvHfxLRhgwCdfIg9mfYiGeotnhNQ8twI+7MeioqsZYZa3XLgR3R3uCrDYuf18OgOY+L0ravo=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DB633F1A57F843619F5B4A6173AEBBC7ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 1e005b37-b4ba-4138-957d-08d7633a4eb1
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Nov 2019 04:23:57.4699 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zKumT58Z7gQX6/1XRnqB/qd5OR8HYNe4zzqqGvilZPGP/ok5Rd0lDyEebBBMmUo/XOYys46oaz8+P2Hf0BKL5A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB4144
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.21, xch-aln-011.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/6lo/ALry8PjaHlHy2xA97lzbb9URd2o>
Subject: Re: [6lo] RIOT implementation for Selective Fragment Recovery
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: Thu, 07 Nov 2019 04:42:24 -0000
Fantastic Martine. Please note that you do not need to send the message in error back in full. Only up to the offset where the error is detected. Since the control is in the first fragment there is no point reassembling in the middle of the network. The hard question that we discuss in the other thread is whether to send back the compressed form and to whom. This was overlooked so far. Forwarding fragments makes it even harder because a problem with the compression may be caused not only by the previous hop but also by the source or even a node in between. Regards, Pascal Le 6 nov. 2019 à 07:23, Martine Lenders <mail@martine-lenders.eu> a écrit : Hello, I finally finished a first presentable draft of my Selective Fragment Recovery implementation for RIOT [1]. It still needs a lot of testing and thus there are most definitely still some major bugs in there, but feel free to have a look. Regarding my previous question [2]: I solved it now by making the node where the hop-limit is reached the reassembling end-point, which is I believe most in line with the protocol as it was designed. Best regards, Martine [1] https://github..com/RIOT-OS/RIOT/pull/12648<https://github.com/RIOT-OS/RIOT/pull/12648> [2] https://mailarchive.ietf.org/arch/msg/6lo/vWZvBbdjR15vOYNkz-mw6VXBJH0 _______________________________________________ 6lo mailing list 6lo@ietf.org https://www.ietf.org/mailman/listinfo/6lo
- [6lo] RIOT implementation for Selective Fragment … Martine Lenders
- Re: [6lo] RIOT implementation for Selective Fragm… Pascal Thubert (pthubert)