Re: [lp-wan] Focused Scope for LPWAN WG at Berlin

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Fri, 22 April 2016 12:11 UTC

Return-Path: <pthubert@cisco.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 30A2312EB30 for <lp-wan@ietfa.amsl.com>; Fri, 22 Apr 2016 05:11:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.516
X-Spam-Level:
X-Spam-Status: No, score=-15.516 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, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_PASS=-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 hV19Z-dYk7Na for <lp-wan@ietfa.amsl.com>; Fri, 22 Apr 2016 05:11:44 -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 A565E12EB2B for <lp-wan@ietf.org>; Fri, 22 Apr 2016 05:11:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=37800; q=dns/txt; s=iport; t=1461327104; x=1462536704; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=+Ri7Mwudyd4pPkgnWv/FPdmj2sicZ/tjYTRRYGVDI2U=; b=F0Q1T39r2iX9tHWZborwMvGnXhLMUaWvUQgSiyf0gAO8UOBAMrz0j8K7 +lQIoDKgcPpYIsJ+rZsKbtytJ+oLMG46wiOVPIfi5acKm+IUXY7ZtJ21F nBS1Rk0w+xVMgGAcFskLgCu9OmJXah/F+enpo5rLgCzVXe12CCxD4v6r5 M=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ACAgD7ExpX/5hdJa1UCoJsTFN9BroAAQ2BbwQXAQqFbAIcgQg4FAEBAQEBAQFlJ4RBAQEBBAEBASAKQQIBCBACAQgRBAEBIQEGAwICAiULFAkIAgQBDQUIE4gPDq19kSsBAQEBAQEBAQEBAQEBAQEBAQEBAQEVhiGES4QPBgsBAhcLByAJAgaCQoJWBZMehHEBiG+CbIIxgW0XhDaIXYYjiQsBHgEBQoIFG4FLbIdCNn8BAQE
X-IronPort-AV: E=Sophos;i="5.24,517,1454976000"; d="scan'208,217";a="263936900"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 22 Apr 2016 12:11:43 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id u3MCBhJE005576 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 22 Apr 2016 12:11:43 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Fri, 22 Apr 2016 07:11:42 -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.1104.009; Fri, 22 Apr 2016 07:11:42 -0500
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Thomas Watteyne <thomas.watteyne@inria.fr>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Thread-Topic: [lp-wan] Focused Scope for LPWAN WG at Berlin
Thread-Index: AQHRmbXNIDkVs0kYFEKulRmaEDoOIp+Q4xTwgABZ3wCABHLfMA==
Date: Fri, 22 Apr 2016 12:11:31 +0000
Deferred-Delivery: Fri, 22 Apr 2016 12:10:35 +0000
Message-ID: <c65d8ef9c99e41c9b9408c9d06da2f2c@XCH-RCD-001.cisco.com>
References: <CAOPRf-dM_XQTfaNq-e78FBcYQ9TFoSmgJOOXD+8fEjGFoxfD9g@mail.gmail.com> <AM4PR08MB109061D14F845F3A43C8B58FFA6C0@AM4PR08MB1090.eurprd08.prod.outlook.com> <CADJ9OA_nC0dbnd=7mdDxZqwPXJ2z_dfXn0=7B6T24oecGbxGwg@mail.gmail.com>
In-Reply-To: <CADJ9OA_nC0dbnd=7mdDxZqwPXJ2z_dfXn0=7B6T24oecGbxGwg@mail.gmail.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: multipart/alternative; boundary="_000_c65d8ef9c99e41c9b9408c9d06da2f2cXCHRCD001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lp-wan/8khz9oDVlMvVMPShqO3-hC45ByU>
Cc: Ana Minaburo <ana@minaburo.com>, "lp-wan@ietf.org" <lp-wan@ietf.org>
Subject: Re: [lp-wan] Focused Scope for LPWAN WG at Berlin
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.17
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: Fri, 22 Apr 2016 12:11:48 -0000

Hello Thomas:

The sense of the room and the talks in the corridors made very clear (to me) that there were elephants (and maybe one mammoth) in the room. At the top of the rumor, we found LoRa, SigFox and 802.15.4g. To progress, we need contacts (cross participation, intent messaging from responsible entities), we must identify deliverables that make sense for the IETF (feasibility in due time), and critical mass of people (we seem to have it for identified candidate items).

My perception so far:


-        LoRa: we have an organization to talk to, LoRaWAN; we have not determined yet if and on which topic there is a shared desire to get work done at the IETF

-        802.15.4g: we also have a clear partner organization, and we are used to work together. What is less clear is the issues that this technology has in common with other LPWA networks, and which PHYs would be considered

-        SigFox: we found a common interest, but the exact topics need to be refined before Berlin. It is unclear (to me) if we have a peer organization to talk to and how the adoption of IETF work will happen.

There is also the question of whether the work we do would be of interest for NB-IOT: there was little hope that a consistent sense would emerge between now and Berlin that NB-IOT is willing to consider adopting, say, a new compression technique as an update/replacement to ROHC.

Cheers,

Pascal

From: lp-wan [mailto:lp-wan-bounces@ietf.org] On Behalf Of Thomas Watteyne
Sent: mardi 19 avril 2016 09:37
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: Ana Minaburo <ana@minaburo.com>; lp-wan@ietf.org
Subject: Re: [lp-wan] Focused Scope for LPWAN WG at Berlin

I believe the BoF at Buenos Aires indicated work needs to be done in the area of LPWAN at the IETF.

Most of the discussion in Buenos Aires was about the technology that was going to be addressed; that discussion is missing from the initial e-mail in this thread.

There was a clear consensus from the room to narrow the scope of LPWAN to 2-3 long-range technologies. There were some remarks about whether this was the LPWAN group pushing new technology, or whether there was pull from the entities defining that technology. Since then, representatives of companies working on SIGFOX and IEEE802.15.4g technology spoke up, expressing clear interest for the solutions LPWAN could come up with. There may be others speaking up.

So I believe we have our 2-3 technologies, and I strongly suggest the LPWAN group narrows its scope to those as an initial set. Please note that a IEEE802.15.4g network is not per-se single hop, so that "feature" of LPWAN should be lifted.

My 2c.

Thomas

On Tue, Apr 19, 2016 at 9:17 AM, Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:
Hi Ana,

I would focus on the use of IPv6 over these low power wide area networks.

Device management approaches, OMA LWM2M, COMI/COOL or others, would work over these radio technologies.

For security I haven’t seen a document that convinced me that some work is needed.

Ciao
Hannes

From: lp-wan [mailto:lp-wan-bounces@ietf.org<mailto:lp-wan-bounces@ietf.org>] On Behalf Of Ana Minaburo
Sent: 18 April 2016 23:03
To: lp-wan@ietf.org<mailto:lp-wan@ietf.org>
Subject: [lp-wan] Focused Scope for LPWAN WG at Berlin

Hello again,

Well in this message I would like to discuss the scope of the WG. We need to define the focused gaps we want to work in. Let's agree about which are the subjects we want to study,

I think the following points are vey important in order to create the WG, please tell me which other you think we need to add.


1. IPv6
draft-gomez-lpwan-ipv6-analysis-00
IP End to End Communication
IPv6 MTU requires fragmentation
ND will be configured in advanced

2. Header Compression
draft-toutain-lp-wan-compression-context-00
New Mechanism adapted to challenged networks

3.  Security
Personal information need to be secured,

4. Management
draft-pelov-core-cosol-01
draft-veillette-core-cool-01
draft-somaraju-core-sid-00

Regards
Ana

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

_______________________________________________
lp-wan mailing list
lp-wan@ietf.org<mailto:lp-wan@ietf.org>
https://www.ietf.org/mailman/listinfo/lp-wan



--
_______________________________________

Thomas Watteyne, PhD
Research Scientist & Innovator, Inria
Sr Networking Design Eng, Linear Tech
Founder & co-lead, UC Berkeley OpenWSN
Co-chair, IETF 6TiSCH

www.thomaswatteyne.com<http://www.thomaswatteyne.com>
_______________________________________