Re: [lp-wan] Next steps on LPWAN WG

Arun <arun@acklio.com> Wed, 24 May 2017 15:27 UTC

Return-Path: <arun@acklio.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 ABB44127369 for <lp-wan@ietfa.amsl.com>; Wed, 24 May 2017 08:27:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.699
X-Spam-Level:
X-Spam-Status: No, score=-0.699 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 cWp154SYnhOJ for <lp-wan@ietfa.amsl.com>; Wed, 24 May 2017 08:27:18 -0700 (PDT)
Received: from relay2-d.mail.gandi.net (relay2-d.mail.gandi.net [IPv6:2001:4b98:c:538::194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1160B129B53 for <lp-wan@ietf.org>; Wed, 24 May 2017 08:27:18 -0700 (PDT)
Received: from mfilter2-d.gandi.net (mfilter2-d.gandi.net [217.70.178.140]) by relay2-d.mail.gandi.net (Postfix) with ESMTP id 30610C5A4E for <lp-wan@ietf.org>; Wed, 24 May 2017 17:27:16 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at mfilter2-d.gandi.net
Received: from relay2-d.mail.gandi.net ([IPv6:::ffff:217.70.183.194]) by mfilter2-d.gandi.net (mfilter2-d.gandi.net [::ffff:10.0.15.180]) (amavisd-new, port 10024) with ESMTP id Y_gu3iKOtth5 for <lp-wan@ietf.org>; Wed, 24 May 2017 17:27:14 +0200 (CEST)
X-Originating-IP: 192.44.77.207
Received: from [192.168.207.230] (nat-asr-incub-v207-1x.rennes.enst-bretagne.fr [192.44.77.207]) (Authenticated sender: arun@acklio.com) by relay2-d.mail.gandi.net (Postfix) with ESMTPSA id 3735AC5A87 for <lp-wan@ietf.org>; Wed, 24 May 2017 17:27:13 +0200 (CEST)
To: lp-wan@ietf.org
References: <337D2F1B-1751-4A49-8773-082A8C5BBE11@ackl.io>
From: Arun <arun@acklio.com>
Message-ID: <34fcea3f-bcb9-e616-106b-6a388e09b73e@acklio.com>
Date: Wed, 24 May 2017 17:27:07 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <337D2F1B-1751-4A49-8773-082A8C5BBE11@ackl.io>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="BF1JVacmMV1w7LGC2jE3e9VJbSFOExJOb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/-ACgBTnOwzstH0aiI5o0GL8hlP4>
Subject: Re: [lp-wan] Next steps on LPWAN WG
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: Wed, 24 May 2017 15:27:23 -0000

+1, ICMP compression.


On 24/05/2017 17:24, Ana Minaburo wrote:
> Hello LPWANers,
>
> What I would like to talk about you during the meeting is about the
> future of the WG. As soon as the work is going on, and the Milestone
> are done we need to start thinking about what are the next steps we
> need to do and which are the most urgent. 
>
> I start a possible list of some of them, but I would like to know what
> do you think and what will be the priorities to the ML. The list is
> not in any order neither in priority so this is only some ideas, and
> if you want to add something the list is open.
>
> Thanks
>
> Ana
>
>
> Next Steps on LPWAN WG:
>
> - YANG data modelling for SCHC 
> - Profile Technologies. Develop the different document for each
> technology in order to define the different parameters.
> - Security, all the security solution for the LPWAN
> - Rules-ID’s management
> + Use to identify some specific cases:
> * Fragmentation
>                 * Format Values
>                 * Rule-IDs dedicated for some specific cases as CBOR
> structure representation, fragmentation, etc
> * The way to use the Rule-Id and their configuration       
> - ICMP Compression
>
>
>
>
> _______________________________________________
> lp-wan mailing list
> lp-wan@ietf.org
> https://www.ietf.org/mailman/listinfo/lp-wan