Re: [lp-wan] Review of draft-ietf-lpwan-overview-06.txt
Stephen Farrell <stephen.farrell@cs.tcd.ie> Tue, 03 October 2017 15:23 UTC
Return-Path: <stephen.farrell@cs.tcd.ie>
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 957A6134CEB for <lp-wan@ietfa.amsl.com>; Tue, 3 Oct 2017 08:23:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 oifOxW7MkRkj for <lp-wan@ietfa.amsl.com>; Tue, 3 Oct 2017 08:23:30 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 557151342D2 for <lp-wan@ietf.org>; Tue, 3 Oct 2017 08:19:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 966C1BEC3; Tue, 3 Oct 2017 16:19:24 +0100 (IST)
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u0wKDEDPZHSV; Tue, 3 Oct 2017 16:19:24 +0100 (IST)
Received: from [134.226.36.93] (bilbo.dsg.cs.tcd.ie [134.226.36.93]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 369EBBEE5; Tue, 3 Oct 2017 16:19:23 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1507043963; bh=/7//6KbsyGYsedOKV1NnYGBqRHE/m12ZTqGqPJiua9E=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=WGcNHxBkidelnrVihQFvHA9K4jR5ilbt+I6l8Z6kglrcyhEHUrhrKNmQNgSnG80I+ tppsAMN5xVt4zF6RtZQRyodqya9XO8Ih32jXf3MOS5jYv2FP0YYIiGK2xdxb3wUtbT DxWuW6sTtNuPM/AOiWgeBG+WFteR9XXGbn/6Mrfw=
To: sarikaya@ieee.org
Cc: lp-wan <lp-wan@ietf.org>
References: <CAC8QAcdANWAL4rz7_xVve8U6W80xGj8ibs6JfE6RpvBeOpBBLQ@mail.gmail.com> <23416f7b-c23e-b5a0-4917-061449b4ce18@cs.tcd.ie> <CAC8QAcfco-GMs+ikSDMz1NWpL0WJaUynMkLwa61AuNCG7i6Haw@mail.gmail.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <c2fefb8d-40f3-7a02-784d-8f624b329422@cs.tcd.ie>
Date: Tue, 03 Oct 2017 16:19:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.3.0
MIME-Version: 1.0
In-Reply-To: <CAC8QAcfco-GMs+ikSDMz1NWpL0WJaUynMkLwa61AuNCG7i6Haw@mail.gmail.com>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="EMIHNwvpOUHv4Olpbc0eVtj9s52UJcMQI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/pIvPlGIPMAE-wge-CkmDFgOciBI>
Subject: Re: [lp-wan] Review of draft-ietf-lpwan-overview-06.txt
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: Tue, 03 Oct 2017 15:23:33 -0000
Hiya, (Chopping out the "done" bits...) On 03/10/17 16:07, Behcet Sarikaya wrote: >>> p.14 >>> EPC not defined >> > Evolved Packet Core (EPC) Ack. Ta. > > There are lots of nb-IoT/LTE terms there that could be >> better explained. But if you want to offer text for some >> of those I'd be happy to add that. >> >>> Fig. 1, Fig. 7 refer to non-3GPP architectures which means LoRaWAN, >> SIGFOX >>> and Wi-SUN are basically IEEE 802.15.4 type of technologies? >> >> I'm not sure what change you'd like. >> > Maybe state that Wireless Smart Ubiquitous Network (Wi-SUN) is based on > the IEEE 802.15.4g standard, therefore it is mesh network while Low Power > Wide Area Network (LoRaWAN), SIGFOX support star architecture and are built > on proprietary technologies. I suspect that the proponents of those might not like the term proprietary and the point about mesh and star networks is already made I think. > >> >>> Regarding battery life, referred to on Page 11 for NB-IoT and p.15 for >>> SIGFOX, p.21 for Wi_SUN, >>> if these technologies are used to connect devices like refrigerators >> which >>> are almost always powered up, why long term battery life is an issue? >>> On the other hand the use on the pets is a different issue. >> >> Even when mounted on a mains-powered bit of equipment, >> sometimes these devices run on their own battery. >> > maybe add some text like above including mobility. Again, if you'd like to offer text, we could look at that but I think that point is pretty clear really to anyone who'd read this document. > > On 28/07/17 23:17, Behcet Sarikaya wrote: >>> More comments: >>> p.13 & p.24 >>> P-GW is packet data network gateway >>> it is not application server, the classification in Fig. 8 seems to be >>> correct. >> >> Sorry, not sure what you mean. Figure 3 and that text were >> contributed by folks who know more than me about that, but >> if you'd like to suggest specific text I'd be happy to make >> a change, if there are no objections on the list. >> >> I meant change this: > > Packet Data Node Gateway (P-GW) > > to > packet data network gateway Ah, gotcha. Sure, if that's better. >>> p.30 section 4.8 second paragraph: >>> add the use of a gateway with LTE uplink as a mobility solution. >> >> I'm not sure what specific text you'd like. >> >> > Add to the second paragraph > NEMO [RFC3963 <https://tools.ietf.org/html/rfc3963>] Mobility solutions > or a gateway with LTE uplink > may be used ... Fair enough. Added text along those lines. Version -07 will pop out shortly with these and the changes from Alper. Thanks, S.
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Behcet Sarikaya
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Stephen Farrell
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Stephen Farrell
- [lp-wan] Review of draft-ietf-lpwan-overview-06.t… Behcet Sarikaya
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Behcet Sarikaya
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Behcet Sarikaya
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Edgar Ramos
- Re: [lp-wan] Review of draft-ietf-lpwan-overview-… Stephen Farrell