Re: [lp-wan] Focused Scope for LPWAN WG at Berlin
Alper Yegin <alper.yegin@actility.com> Thu, 21 April 2016 13:39 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 22C7212DA8A for <lp-wan@ietfa.amsl.com>; Thu, 21 Apr 2016 06:39:12 -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=ham 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 cQQwEAtp1GHj for <lp-wan@ietfa.amsl.com>; Thu, 21 Apr 2016 06:39:08 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 9070012D19B for <lp-wan@ietf.org>; Thu, 21 Apr 2016 06:39:08 -0700 (PDT)
Received: by mail-vk0-x235.google.com with SMTP id t129so98351029vkg.2 for <lp-wan@ietf.org>; Thu, 21 Apr 2016 06:39:08 -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=vuINsmiHtu974cHiqcevNx4PCobPFGho6sH2nvqIyV0=; b=HFqW0ikccn6b+ta5/77pvx0Fi2uJ8zSSiTFRPeY3z4EiyI/cTjZqLs1OuTjqBc53A+ NIBJmNWSR6/5+1KC10Uilubg22LXLN9jG3u148auEgcGvqZPc4XY5u45UE09x7KuYzoz Vzc4eRDF4JCBT6O7fYw3Lzys2VvrP5juZjhPM=
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=vuINsmiHtu974cHiqcevNx4PCobPFGho6sH2nvqIyV0=; b=LzZoBeb0kKk2khEgW1T3QKu2izA/y8wKU7SzqfBELK0vH2a3BxOlEEkPcnoHlXM6Hw p+CubTPFUVx4uVMCk+1Y5AvAYFyxl4x3YH+AlNCGEa8w522ZfkYLZJFSAzq84giCP12U o4AfGk01pc7kM3yFD1ZAQ8JvQ70pha/5WbknhjgTbKGuoVDj1+lEV1HzoSJgayv56NWa jH+j/x+1S/oN40jcRDIqTA0s8y82Ia4XekIwjtmnFpL9ZprErf0vYrvPg/iSffl5uSwt 8eWD/qPJLwgLgUPaFevjUfgmE+EbYbgHhxDGMsOTtETwn0loov9Ln9yue6MEtVyNxJGi e4+w==
X-Gm-Message-State: AOPr4FUjKUSV3vVk576fUS6g6J3oXfitSWqtyVb52KPrtNFQNN+gITuyEey08szOrF62sgl/hxuIYvVZfEzxWeew
MIME-Version: 1.0
X-Received: by 10.31.141.2 with SMTP id p2mr7997265vkd.37.1461245947644; Thu, 21 Apr 2016 06:39:07 -0700 (PDT)
Received: by 10.159.40.6 with HTTP; Thu, 21 Apr 2016 06:39:07 -0700 (PDT)
In-Reply-To: <CAOPRf-fKrBb34Hr6OB+Q3-vz_QOZp04+4KoC=QtFu_v++QvuTQ@mail.gmail.com>
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>
Date: Thu, 21 Apr 2016 16:39:07 +0300
Message-ID: <CACCk=ez-Dzp16aWde9zGiYk3QT3rb5Hy7eTss6q=gzk7sRfqdg@mail.gmail.com>
From: Alper Yegin <alper.yegin@actility.com>
To: Ana Minaburo <ana@minaburo.com>
Content-Type: multipart/alternative; boundary="001a11426040a3c1e20530fed525"
Archived-At: <http://mailarchive.ietf.org/arch/msg/lp-wan/pNdIDBVeN126qkknfoBxmQa_btU>
Cc: "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 13:39:12 -0000
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] Focused Scope for LPWAN WG at Berlin Ana Minaburo
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Hannes Tschofenig
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Thomas Watteyne
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Carles Gomez Montenegro
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Xavier Vilajosana
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Carles Gomez Montenegro
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Michael Richardson
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Pascal Thubert (pthubert)
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Michael Richardson
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Prof. Diego Dujovne
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Laurent Toutain
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Ana Minaburo
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Ana Minaburo
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Alper Yegin
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Alexander Pelov
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Alper Yegin
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Pascal Thubert (pthubert)
- Re: [lp-wan] Focused Scope for LPWAN WG at Berlin Thomas Watteyne