Re: [lp-wan] Window mode as default fragmentation in SCHC + Minutes from Interim on 24/05

Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com> Mon, 29 May 2017 18:01 UTC

Return-Path: <juancarlos.zuniga@sigfox.com>
X-Original-To: lp-wan@ietfa.amsl.com
Delivered-To: lp-wan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A958129AFC for <lp-wan@ietfa.amsl.com>; Mon, 29 May 2017 11:01:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.912
X-Spam-Level:
X-Spam-Status: No, score=-2.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H5=-1, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=sigfoxgroup.onmicrosoft.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 mVw8_BqbF0ed for <lp-wan@ietfa.amsl.com>; Mon, 29 May 2017 11:00:57 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00123.outbound.protection.outlook.com [40.107.0.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E09C129AF4 for <lp-wan@ietf.org>; Mon, 29 May 2017 11:00:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sigfoxgroup.onmicrosoft.com; s=selector1-sigfox-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ASYx6kVsCB+u/mRQkHNhaM/QRBV59tx54+5VHEz6Y2k=; b=PRjkWTtyo7UsAxRXatgJQKa9Z21NvmW4ihZd5sC88/SM4bLaGzuwvzjqQGJsaqlNs57oCoMr/mJg2CAV4m0DaJi6zQ+UdZXjWm/cHW3gcw5LZQcqTEty1ygyrphm3654oUs35YizD9X1HCDgx87tmpsc2dZrQZbwJnvpWBa9biY=
Received: from DB6PR08MB2679.eurprd08.prod.outlook.com (10.175.235.12) by DB6PR08MB2679.eurprd08.prod.outlook.com (10.175.235.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1124.9; Mon, 29 May 2017 18:00:53 +0000
Received: from DB6PR08MB2679.eurprd08.prod.outlook.com ([fe80::3c08:54b8:1c7c:498a]) by DB6PR08MB2679.eurprd08.prod.outlook.com ([fe80::3c08:54b8:1c7c:498a%13]) with mapi id 15.01.1124.009; Mon, 29 May 2017 18:00:53 +0000
From: Juan Carlos Zuniga <juancarlos.zuniga@sigfox.com>
To: Alexander Pelov <a@ackl.io>, lp-wan <lp-wan@ietf.org>
Thread-Topic: [lp-wan] Window mode as default fragmentation in SCHC + Minutes from Interim on 24/05
Thread-Index: AQHS2JlZVZYBIug+0UOzL245ZsvsG6ILmJLg
Date: Mon, 29 May 2017 18:00:53 +0000
Message-ID: <DB6PR08MB26796C058745A9F08408226189F30@DB6PR08MB2679.eurprd08.prod.outlook.com>
References: <F3ADB78A-E88A-4354-B347-A9960EAA71EF@ackl.io>
In-Reply-To: <F3ADB78A-E88A-4354-B347-A9960EAA71EF@ackl.io>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ackl.io; dkim=none (message not signed) header.d=none;ackl.io; dmarc=none action=none header.from=sigfox.com;
x-originating-ip: [104.163.152.104]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR08MB2679; 7:mpf+SJL222T/0Ncl2ISFqL+mueFnCgNDaG+eTvzHq2kgprHC+LVF/hVz9QVOrRiEz+NIsiUFF/2bcz5/4I1LrzLBmNcYvrImwEjCZ9OTgNAUmpTU3+TKIjDJLuJUnDtiE5Wb7KiaO5Lrm/DduF6vbX9WFlVkmoF2sOnnGJPw+2MfgHDA7rkTmtwoPn5CJBtfpftR1UvQyI9Uo6g7U8kI3HJbAkOVykCYFfSrxbdho4uYPa7yqj4FJk7h4h1KbtSSfhbfxj0KJhe1C4xjuWlu4lw1EE+pAazwD7RNf6u/1AYC7PJt0Q4VabOl2qx54HUXTf5PT/n8bLz8UX7TerAf7Q==
x-ms-traffictypediagnostic: DB6PR08MB2679:
x-ms-office365-filtering-correlation-id: dde2f7ca-e739-4dbd-16a2-08d4a6bca61b
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081)(201702281549075); SRVR:DB6PR08MB2679;
x-microsoft-antispam-prvs: <DB6PR08MB2679B846DDC01E82B7F9842489F30@DB6PR08MB2679.eurprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123558100)(20161123564025)(20161123560025)(20161123562025)(20161123555025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(6072148); SRVR:DB6PR08MB2679; BCL:0; PCL:0; RULEID:; SRVR:DB6PR08MB2679;
x-forefront-prvs: 0322B4EDE1
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39450400003)(39400400002)(39410400002)(39830400002)(13464003)(377454003)(25786009)(3846002)(2900100001)(966005)(7696004)(189998001)(6436002)(76176999)(38730400002)(14454004)(50986999)(99286003)(6306002)(9686003)(6506006)(6116002)(53546009)(6246003)(7736002)(102836003)(53936002)(478600001)(66066001)(86362001)(2906002)(8936002)(305945005)(5660300001)(81166006)(5250100002)(55016002)(8676002)(33656002)(3660700001)(3280700002)(74316002)(54356999)(27393003)(781001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR08MB2679; H:DB6PR08MB2679.eurprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: sigfox.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 May 2017 18:00:53.4281 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: fcbc8bb1-061e-4b94-9f70-3ad917b0c8d3
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR08MB2679
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/2WFVqSM50tJy92hPW2F_9xVKL84>
Subject: Re: [lp-wan] Window mode as default fragmentation in SCHC + Minutes from Interim on 24/05
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Low-Power Wide Area Networking \(LP-WAN\), also known as LPWA or Low-Rate WAN \(LR-WAN\)" <lp-wan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lp-wan/>
List-Post: <mailto:lp-wan@ietf.org>
List-Help: <mailto:lp-wan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lp-wan>, <mailto:lp-wan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 May 2017 18:01:00 -0000

Hi Alex,

I agree that the window mode provides enough support and flexibility for the basic use cases. The more advanced fragmentation mechanisms to be defined later on can be easily supported and communicated with Rule IDs, as you mention.

+1       for Window as default fragmentation mode.

Best,

Juan Carlos 

> -----Original Message-----
> From: lp-wan [mailto:lp-wan-bounces@ietf.org] On Behalf Of Alexander Pelov
> Sent: May 29, 2017 12:34 PM
> To: lp-wan <lp-wan@ietf.org>
> Subject: [lp-wan] Window mode as default fragmentation in SCHC + Minutes
> from Interim on 24/05
> 
> Dear all,
> 
> The minutes from the last interim meeting have been uploaded and can be
> found at the following address: https://www.ietf.org/proceedings/interim-
> 2017-lpwan-03/minutes/minutes-interim-2017-lpwan-03-201705241600-00
> 
> One of the main topics that were discussed was the advancement of the
> fragmentation part of the IP/UDP SCHC document (
> https://tools.ietf.org/html/draft-ietf-lpwan-ipv6-static-context-hc-03 ).
> 
> During the call we have reached a rough consensus that the Window mode
> covers all use-cases, is simple (from implementation and protocol point of
> view), is well understood, and can be included as a default mode for
> fragmentation in the RFC.
> 
> We have also indicated that there are other ways of doing the fragmentation
> (most notably the Packet mode), but some corner cases still need to be covered
> (e.g. bitmap sizes bigger than available payload limiting the MTU to less than
> 1280), and some advanced ways of actually solving this (Bloom filters were
> mentioned I think). These are all interesting ideas and they merit a longer
> discussion to find the right balance. These are to be kept in a separate
> document, which can continue its life independently, and if the WG decides can
> be included as a future WG item. If a future devices implement these other
> fragmentation mechanisms, they will be perfectly compatible with the default
> Window mode (the Rule ID can indicate which fragmentation mode is used).
> 
> We would like to confirm that you approve the Window mode as the default
> mode for fragmentation to be included in the SCHC IP/UDP document.
> 
> Best,
> The chairs
> 
> _______________________________________________
> lp-wan mailing list
> lp-wan@ietf.org
> https://www.ietf.org/mailman/listinfo/lp-wan