Re: [lp-wan] WG Rechartering - new charter approval vote (vote ends Dec 3rd)
Arunprabhu Kandasamy <arun@ackl.io> Thu, 21 November 2019 01:55 UTC
Return-Path: <arun@ackl.io>
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 1C8A412090C for <lp-wan@ietfa.amsl.com>; Wed, 20 Nov 2019 17:55:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.638
X-Spam-Level:
X-Spam-Status: No, score=-1.638 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ackl-io.20150623.gappssmtp.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 aQHZDALaK_EH for <lp-wan@ietfa.amsl.com>; Wed, 20 Nov 2019 17:55:08 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 2DE6812012E for <lp-wan@ietf.org>; Wed, 20 Nov 2019 17:55:08 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id n5so1303248ljc.9 for <lp-wan@ietf.org>; Wed, 20 Nov 2019 17:55:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ackl-io.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=HqMMrWFO5NtipAIMFC2crjMbsImhUQ8tbhTGwIOlY6A=; b=xZQXF0ticqxshjXyjkDW6olEJXqCEeH7Vu99XMhbDxQIyOvlQwzf7vc2l3lIE2mypx 0JuxWaGmPXCD+9zG6O9JdYb2GCrZSvwq8xmylZjjtg1oZJAMrUq3Oq/tt5cNEuq0jjTT Ivrnc66XbBY3c64pnwQOJRv17eXVU31foiOylGW0XA9RoPYYiF9ITcdzReTjvXwT4I+T c1YwhLq0CtXCxrqK83wjL9a9iGX0UdCaCMbtG7xGJGAxfkqgbF6InV9msIdGinMTXZDp ILiv41bDhNgOwN7OVk/DM+7k80MA0Xd5y6DlC7DpuA7lVEoBtCgHaxXOwNOtwni/KhG8 2Pqw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=HqMMrWFO5NtipAIMFC2crjMbsImhUQ8tbhTGwIOlY6A=; b=aYEY8wMqvcMRvGWsgqlQ8WOb1NU4SJDgWpaKt9kxCITm/ig4/Lk0RVe7fuNrgqvgFf bRKBrWtWBMYqPLPWRF0Z5ZB7CtBP7x64bieVG7BkvRAPaoLM/yu1LbelakJO4pbbvBnd DJciBebLY0eYY0CAMbeU0bTw5j5H/sM8fUAhtfO4oiJNef2xnMqtwe3aKJKlzwPQK6Fm O9mUqFXbWR78by59tk89966IyF9UIUkypX4kYP4UvqSFXhJXgU1PlH9Bd8c5BEHy3U2Q NqO1Fjplv04O/RqjOpFYqfVB4WT2TA2Wt8aOsPpIt5euyld9qO2XlN5q0CrQrIoxiMbm s4/g==
X-Gm-Message-State: APjAAAWzSLR97hNhAz+PwKAFL0tqzdjFaEfOE517PUv+IfQq/TePx0kE iZDr+GbnYqToeLxon3S0LV+PW1aRb9wMExnxy4GBdg==
X-Google-Smtp-Source: APXvYqxEu6yJTckxkiD6/e+r5ltxjVdZVZjU+qn4OA0WRG3XVs6yPEWGi42YQbnWZlmKEW7kr17Nyf9lkNeYbbUQC6w=
X-Received: by 2002:a2e:8ed6:: with SMTP id e22mr5179194ljl.3.1574301306185; Wed, 20 Nov 2019 17:55:06 -0800 (PST)
MIME-Version: 1.0
References: <CACQW0ErHmSX7ze5SGUkM=PiEA4-6hsdxC6Z=q0e3PWNKDUeUrg@mail.gmail.com> <31401_1574256631_5DD53FF7_31401_53_1_D9FB60C5.6C220%dominique.barthel@orange.com> <2a030b0dcce24aa3b8c2aec3e92ee8a5@PCYINTPEXMU006.NEOPROD.EDF.FR>
In-Reply-To: <2a030b0dcce24aa3b8c2aec3e92ee8a5@PCYINTPEXMU006.NEOPROD.EDF.FR>
From: Arunprabhu Kandasamy <arun@ackl.io>
Date: Thu, 21 Nov 2019 02:54:53 +0100
Message-ID: <CALF5R+cNAPOm+dSwpqXUsbvL=S5iLJJh=d7r5SFnDT0_5_-G9A@mail.gmail.com>
To: AUDEBERT Vincent <vincent.audebert@edf.fr>
Cc: "dominique.barthel@orange.com" <dominique.barthel@orange.com>, Alexander Pelov <a@ackl.io>, lp-wan <lp-wan@ietf.org>
Content-Type: multipart/related; boundary="00000000000020502e0597d19618"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/yGn6UPxLHRQR_YZe6MJuwvDzr7A>
Subject: Re: [lp-wan] WG Rechartering - new charter approval vote (vote ends Dec 3rd)
X-BeenThere: lp-wan@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 01:55:16 -0000
Hi, I agree with the chartered items in the wg. thanks, On Wed, Nov 20, 2019 at 4:10 PM AUDEBERT Vincent <vincent.audebert@edf.fr> wrote: > +1 > > > > Vincent > > > > > > > > *Vincent AUDEBERT* > * IoT & Telecom Expert* > EDF – R&D Lab Saclay > MIRE > 7 Bd Gaspard Monge > 91120 PALAISEAU > > > *vincent.audebert@edf.fr <vincent.audebert@edf.fr>* > > Phone : + 33 1 78 19 45 64 > Mobile : + 33 6 14 13 23 22 > > > > Un geste simple pour l'environnement, n'imprimez ce message que si vous en > avez l'utilité. > > > > > > *De :* lp-wan [mailto:lp-wan-bounces@ietf.org] *De la part de* > dominique.barthel@orange.com > *Envoyé :* mercredi 20 novembre 2019 14:31 > *À :* Alexander Pelov <a@ackl.io>; lp-wan <lp-wan@ietf.org> > *Objet :* Re: [lp-wan] WG Rechartering - new charter approval vote (vote > ends Dec 3rd) > > > > Hello all, > > > > I agree with the proposed new charter. > > Best regards > > > > Dominique > > > > *De : *lp-wan <lp-wan-bounces@ietf.org> on behalf of Alexander Pelov < > a@ackl.io> > *Date : *Tuesday 19 November 2019 18:04 > *À : *lp-wan <lp-wan@ietf.org> > *Objet : *[lp-wan] WG Rechartering - new charter approval vote (vote ends > Dec 3rd) > > > > Dear all, > > > > As we have achieved all our milestones the LPWAN WG is now rechartering. > We have been discussing the recharter for several IETFs now, so most of the > new charter should be familiar.. > > > > The new charter is as follows: > > - The introduction and the context remain unchanged. > > - Charter item 1 is a generalization of the Charter item 1 we discussed in > past IETFs. > > - Charter items 2 and 4 come directly from our previous charter. > > - Charter item 3 was proposed, discussed and voted during the session. > > - Charter item 5 has been discussed during the past several IETFs. > > > > We would like to confirm the agreement in the room on the mailing list. > > Please vote by December 3rd, 23h55 CET. > > > > Cheers, > > Pascal and Alexander > > > > - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - > > > > *Charter Proposal for LPWAN Working Group* > > *(Changes are given below in bold)* > > A new generation of wireless technologies has emerged under the generic name > of Low-Power Wide-Area (LPWA), with a number of common characteristics, > which make these technologies unique and disruptive for Internet of > Things applications. > Those common traits include an optimized radio modulation, a star topology, > frame sizes in the order of tens of bytes transmitted a few times per day > at ultra-low speeds and sometimes variable MTUs, and, though downstream > may be supported, a mostly upstream transmission pattern that allows the > devices to spend most of their time in low- energy deep-sleep mode. > This enables a range of several kilometers and a long battery lifetime, possibly > ten years operating on a single coin-cell. This also enables simple and > scalable deployments with low-cost devices and thin infrastructures. > Those benefits come at a price: the layer 2 frame formats are optimized and > specific to each individual technology. There is no network layer and the > application is often hard wired to the layer 2 frame format, leading to > siloed deployments that must be managed, secured and operated individually. > Migrating from one LPWA technology to another implies rebuilding the > whole chain. > To unleash the full power of LPWA technologies and their ecosystems, there > is a need to couple them with other ecosystems that will guarantee the > inter-working by introducing a network layer, and enable common components > for management and security, as well as shared application profiles. The > IETF can contribute by providing IPv6 connectivity, and propose > technologies to secure the operations and manage the devices and their > gateways. > The Working Group will focus on enabling IPv6 connectivity over the following > selection of Low-Power Wide-Area technologies: SIGFOX, LoRa, WI-SUN and > NB-IOT. > These technologies present similar characteristics of rare and widely unbalanced > over-the-air transmissions, with little capability to alter the frame > formats to accommodate this work, which makes it so that existing IETF > work (6lo) cannot be trivially applied. > The Working Group will leverage cross-participation with the associated set > of stakeholders to ensure that the work taking place corresponds to real > demands and that the proposed solutions are indeed applicable. > The group will produce informational work describing LPWA technologies > and their needs as well as new standard work to optimize IPv6-based > communications to the end device > > > The group will: > *1. Perform SCHC Maintenance, including enabling SCHC mechanisms for Upper > layer Protocols. * > > > > *2.. Produce Standard Track documents to apply SCHC IPv6/UDP over the > baseline technologies. 3. Produce a Standards Track document to provide a > mechanism to improve the reliability of delivering fragmented multicast > packets. 4. Produce a Standards Track document to define the generic data > models to formalize the compression and fragmentation contexts. 5. Produce > a Standards Track document to enable operations, administration and > maintenance (OAM) to the LPWAN device, including support for delayed or > proxyed liveness verification (Ping).* > > > > > > _________________________________________________________________________________________________________________________ > > > > Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc > > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler > > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, > > Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. > > > > This message and its attachments may contain confidential or privileged information that may be protected by law; > > they should not be distributed, used or copied without authorisation. > > If you have received this email in error, please notify the sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. > > Thank you. > > > Ce message et toutes les pièces jointes (ci-après le 'Message') sont > établis à l'intention exclusive des destinataires et les informations qui y > figurent sont strictement confidentielles. Toute utilisation de ce Message > non conforme à sa destination, toute diffusion ou toute publication totale > ou partielle, est interdite sauf autorisation expresse. > > Si vous n'êtes pas le destinataire de ce Message, il vous est interdit de > le copier, de le faire suivre, de le divulguer ou d'en utiliser tout ou > partie. Si vous avez reçu ce Message par erreur, merci de le supprimer de > votre système, ainsi que toutes ses copies, et de n'en garder aucune trace > sur quelque support que ce soit. Nous vous remercions également d'en > avertir immédiatement l'expéditeur par retour du message. > > Il est impossible de garantir que les communications par messagerie > électronique arrivent en temps utile, sont sécurisées ou dénuées de toute > erreur ou virus. > ____________________________________________________ > > This message and any attachments (the 'Message') are intended solely for > the addressees. The information contained in this Message is confidential. > Any use of information contained in this Message not in accord with its > purpose, any dissemination or disclosure, either whole or partial, is > prohibited except formal approval. > > If you are not the addressee, you may not copy, forward, disclose or use > any part of it. If you have received this message in error, please delete > it and all copies from your system and notify the sender immediately by > return message. > > E-mail communication cannot be guaranteed to be timely secure, error or > virus-free. > _______________________________________________ > lp-wan mailing list > lp-wan@ietf.org > https://www.ietf.org/mailman/listinfo/lp-wan > -- <https://t.sidekickopen05.com/s1t/c/5/f18dQhb0S7lM8dDMPbW2n0x6l2B9nMJN7t5X-FfhMynW4Wr-Yl7d-0fCW56dGqW1GQ8t2102?t=https%3A%2F%2Fackl.io%2F&si=7000000001059340&pi=5991da3d-efb6-4959-f4d5-a627f1b5eb8b> *Arunprabhu KANDASAMY *R&D Engineer-IPCore +33 2 22 06 05 77 www.ackl.io
- [lp-wan] WG Rechartering - new charter approval v… Alexander Pelov
- [lp-wan] Fwd: WG Rechartering - new charter appro… Prof. Diego Dujovne
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Laurent Toutain
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Ivaylo Petrov
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Carles Gomez Montenegro
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Olivier Gimenez
- Re: [lp-wan] WG Rechartering - new charter approv… Georgios Z. Papadopoulos
- Re: [lp-wan] WG Rechartering - new charter approv… dominique.barthel
- Re: [lp-wan] WG Rechartering - new charter approv… AUDEBERT Vincent
- Re: [lp-wan] WG Rechartering - new charter approv… Arunprabhu Kandasamy
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Juan Carlos Zuniga
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Xavi Vilajosana Guillen
- Re: [lp-wan] Fwd: WG Rechartering - new charter a… Ana Minaburo
- Re: [lp-wan] WG Rechartering - new charter approv… Cedric Adjih
- Re: [lp-wan] WG Rechartering - new charter approv… Alexander Pelov