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

Alper Yegin <alper.yegin@actility.com> Thu, 21 April 2016 21:12 UTC

Return-Path: <alper.yegin@actility.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 3912612E50B for <lp-wan@ietfa.amsl.com>; Thu, 21 Apr 2016 14:12:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=actility.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 OdaqzM0Gl2bF for <lp-wan@ietfa.amsl.com>; Thu, 21 Apr 2016 14:12:29 -0700 (PDT)
Received: from mail-vk0-x234.google.com (mail-vk0-x234.google.com [IPv6:2607:f8b0:400c:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0C23D12DC18 for <lp-wan@ietf.org>; Thu, 21 Apr 2016 14:02:37 -0700 (PDT)
Received: by mail-vk0-x234.google.com with SMTP id e185so113183362vkb.1 for <lp-wan@ietf.org>; Thu, 21 Apr 2016 14:02:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=actility.com; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=dXAsX4w0infCexsDHJSpMnI3cgNqJ7QvHIkppkSg58A=; b=ZIZ17/WA3CQelMLxQpbwwQZRtxviDIHjZivj3nQPe2GuL6OwhU6LP7NA7blZjBEg// oxJZDX80PTJL8+qJhb3TFH5ImVv8qSue9Fm90FF8plCdnge1VmFew/yqE30DHc+l9CWE 8NuI0xZEWH/vzGd1a6/qOF5La71IzqtmtI1A0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=dXAsX4w0infCexsDHJSpMnI3cgNqJ7QvHIkppkSg58A=; b=Xyvf1MBiXXLmJpQVAZYi0iKT5FEa6AoURmS1KkaW2RuLC1I60/lz1PHNExlYfp49yw iOsLboM0dJAEOMlvY57mh3xHD4k/FBi7q/G7aQb0uQt//GtrGtEkdVzPrKcgOE4BWTA4 kIg3zWrrAjFeWSMiS7O0GFHvKz3V6oY030fXp1X6/x3rKGasY+/Hnq8PEKXR3/bxstSr dJVZbfv4w2KCYG7VMdara7L7ZbrkZk//+M5Yr7lGET1VFMQintAV7vGC51upx+pAfZEL KU0FWMpJVsSMz1+KWca3ERd+8n/UUnyilxZa6dzoDhJ4RUI4ZM5yEgDnWirQKTEUSVN/ 6PJw==
X-Gm-Message-State: AOPr4FXQR5PkfcbhV9q/D0tyVK0cxfBdMn8a8tSW8NRsxaMHSmiJFZZRX1LeA4f/C1gjU6/XQIwU7TGgWPGtq85B
MIME-Version: 1.0
X-Received: by 10.31.92.137 with SMTP id q131mr7716724vkb.35.1461272556895; Thu, 21 Apr 2016 14:02:36 -0700 (PDT)
Received: by 10.159.40.6 with HTTP; Thu, 21 Apr 2016 14:02:36 -0700 (PDT)
In-Reply-To: <CF76E47D-1F54-4CA9-8D6F-DA10B805C59B@ackl.io>
References: <CAOPRf-dM_XQTfaNq-e78FBcYQ9TFoSmgJOOXD+8fEjGFoxfD9g@mail.gmail.com> <AM4PR08MB109061D14F845F3A43C8B58FFA6C0@AM4PR08MB1090.eurprd08.prod.outlook.com> <CADJ9OA_nC0dbnd=7mdDxZqwPXJ2z_dfXn0=7B6T24oecGbxGwg@mail.gmail.com> <CAOPRf-fKrBb34Hr6OB+Q3-vz_QOZp04+4KoC=QtFu_v++QvuTQ@mail.gmail.com> <CACCk=ez-Dzp16aWde9zGiYk3QT3rb5Hy7eTss6q=gzk7sRfqdg@mail.gmail.com> <CF76E47D-1F54-4CA9-8D6F-DA10B805C59B@ackl.io>
Date: Fri, 22 Apr 2016 00:02:36 +0300
Message-ID: <CACCk=ex=+oiFDPSXtybJsH5A4b9m+jOLFVumH=XzPdbkTf85jQ@mail.gmail.com>
From: Alper Yegin <alper.yegin@actility.com>
To: Alexander Pelov <a@ackl.io>
Content-Type: multipart/alternative; boundary="001a114cf318ac997205310507dd"
Archived-At: <http://mailarchive.ietf.org/arch/msg/lp-wan/Ml2q4xgNXa1DfEHY-_eEmIKl6bc>
Cc: Ana Minaburo <ana@minaburo.com>, "lp-wan@ietf.org" <lp-wan@ietf.org>, Hannes Tschofenig <Hannes.Tschofenig@arm.com>, Thomas Watteyne <thomas.watteyne@inria.fr>
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: Thu, 21 Apr 2016 21:12:31 -0000

Hello Alexander,


> It’s great that you are interested in our work! We’ll be glad to have you
> on-board for the next IETF meeting in Berlin.
>

Thank you :-)


> Would you be able to attend?
>
>
I'm planning to.

Alper




> Best,
> Alexander
>
>
>
>
> Le 21 avr. 2016 à 15:39, Alper Yegin <alper.yegin@actility.com> a écrit :
>
> Hello Ana, folks,
>
> There is indeed interest on our side. Unfortunately, the last IETF meeting
> collided with a LoRa Alliance meeting, hence I couldn't attend the IETF
> LPWAN meeting, not even remotely.
>
> Cheers,
>
> Alper
>
>
> On Thu, Apr 21, 2016 at 3:43 PM, Ana Minaburo <ana@minaburo.com> wrote:
>
>> Hello Thomas,
>>
>> Thank you for your input, I think we can discuss of which are the good
>> technologies to study, but there is not a doubt about SIGFOX, as they have
>> shown its interested. Ofcourse we can discuss about 802.15.4g and the
>> difference between 6tisch/6lo/6LoWPAN and LP-WAN relations and differences
>> but there are a good collaboration between them and IETF and we can take
>> advantage of it. There is missing one technology, we can wait and start
>> with this two approaches and see if LoRAWAN get into the group, or see if
>> anyone of have a contect with them?
>>
>> Thanks
>> Ana
>>
>> On Tue, Apr 19, 2016 at 9:37 AM, Thomas Watteyne <
>> thomas.watteyne@inria.fr> wrote:
>>
>>> 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> 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] *On Behalf Of *Ana
>>>> Minaburo
>>>> *Sent:* 18 April 2016 23:03
>>>> *To:* 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
>>>> 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
>>> _______________________________________
>>>
>>
>>
>> _______________________________________________
>> lp-wan mailing list
>> lp-wan@ietf.org
>> https://www.ietf.org/mailman/listinfo/lp-wan
>>
>>
>
>
>
>
>
> _______________________________________________
> lp-wan mailing list
> lp-wan@ietf.org
> https://www.ietf.org/mailman/listinfo/lp-wan
>
>
>


-- 
*Alper E. Yegin*
Head of Standards, Actility
Chair of Security Task Force, LoRa Alliance
Vice-Chair of Strategy Committee, LoRa Alliance
+90 533 348 24 02