Re: [lp-wan] Review of draft-ietf-lpwan-overview-06.txt
Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 04 October 2017 08:43 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 2249A134222 for <lp-wan@ietfa.amsl.com>; Wed, 4 Oct 2017 01:43:57 -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 MUgJZMCHmZ_G for <lp-wan@ietfa.amsl.com>; Wed, 4 Oct 2017 01:43:54 -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 59EAF13214D for <lp-wan@ietf.org>; Wed, 4 Oct 2017 01:43:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 025F1BE5D; Wed, 4 Oct 2017 09:43:53 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
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 YWUgALCUP9IW; Wed, 4 Oct 2017 09:43:50 +0100 (IST)
Received: from [10.244.2.100] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 8B5F8BE2F; Wed, 4 Oct 2017 09:43:50 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1507106630; bh=rMPTb/bk/zIRK/4T6ZZKbEO/LGgYkgX4talcxsj93UM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=uFg2WLXxc4W7YFkNjK3AICOb+Wi1SzKXvdb47IpLXhO0Ct2q81/ALm2d1FUkhXy9E 77UKnu083ieqxdlYVRpYiAODPYPs6B77Lc2EZpPVfZnf8pjTM1gWc+l85DqJppVh6L +IRVxUNNd2LNQejR5dV5veMyFy+9BWWCwdzC3ykM=
To: Edgar Ramos <edgar.ramos@ericsson.com>
Cc: lp-wan <lp-wan@ietf.org>
References: <CAC8QAcdANWAL4rz7_xVve8U6W80xGj8ibs6JfE6RpvBeOpBBLQ@mail.gmail.com> <23416f7b-c23e-b5a0-4917-061449b4ce18@cs.tcd.ie> <94554BCAC338AB47A9A96BAFDDA4C7853C0F66B6@ESESSMB107.ericsson.se>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <2ed2e449-977d-a53f-1360-9d17832942ab@cs.tcd.ie>
Date: Wed, 04 Oct 2017 09:43:49 +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: <94554BCAC338AB47A9A96BAFDDA4C7853C0F66B6@ESESSMB107.ericsson.se>
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="J3iXoRFwXQx7XMRCuHQKjhus15ecn6tRI"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/mbZEQLAnzLxEMXf5RKYo-F3GjNQ>
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: Wed, 04 Oct 2017 08:43:57 -0000
Hi Edgar, On 04/10/17 09:12, Edgar Ramos wrote: > Hi Stephen, > > I can provide you with better explanation for nb-iot/LTE terminology > that you consider not well explained. Are there any in particular > that you have in mind ? Thanks! I'll go over it to see what's left (that's still puzzling to me:-) and send a substative reply later. (Won't be today though.) Cheers, S. > > Br > > EDGAR RAMOS Senior Researcher > > Oy LM Ericsson AB Hardware, Devices and EMF IoT technologies > Ericsson Research 02420 Jorvas, Finland www.ericsson.com > > > > > This Communication is Confidential. We only send and receive email > on the basis of the terms set out at > www.ericsson.com/email_disclaimer > > > > > > > > -----Original Message----- From: Stephen Farrell > [mailto:stephen.farrell@cs.tcd.ie] Sent: Tuesday, October 03, 2017 > 4:09 PM To: sarikaya@ieee.org Cc: lp-wan <lp-wan@ietf.org> Subject: > Re: [lp-wan] Review of draft-ietf-lpwan-overview-06.txt > > > Hiya, > > Thanks for the review. > > Belatedly responding to your various mails as I get the -07 ready. > > On 28/07/17 22:47, Behcet Sarikaya wrote: >> Hi all, >> >> Here are my comments after reading the overview document: page 4. >> LoRaWAN acronym? > > It's not quite an acronym afaik. > >> page 8. NwkID in Table 3, is it supposed to be NetID? > > Yep, I think you're right. > >> p.9 DevEUI and AppEUI I think they refer to the device and the >> application MAC addresses in 64-bits > > Yes, those are explained in the text I think. > >> p. 13 The 3GPP radio protocol architecture is illustration in >> Figure 4 s/illustration/illustrated > > Yep, ta. > >> >> control plane protocol stack and data plane protocol stack section >> numbering is missing > > I think that's ok, a 2-level TOC is enough. > >> p.14 EPC not defined > > 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. > >> >> 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. > > 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. > > > On 31/07/17 22:40, Behcet Sarikaya wrote: >> Comments on Section 4: p.28 Valid Lifetime in the 6CO it should be >> >> 6LoWPAN Context Option > > Ack. Ta. > >> >> p.30 s/LPWANs nodes/LPWAN nodes > > Ack. Ta. > >> p.31 staple OCSP responses >> >> Online Certificate Status Protocol (OCSP) > > Ack. Ta. > >> >> 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. > > Cheers, S. > >> >> > > > Cheers, S. > >> >> Regards, >> >> Behcet On Fri, Jul 21, 2017 at 2:46 AM, <internet-drafts@ietf.org> >> wrote: >> >>> >>> A New Internet-Draft is available from the on-line >>> Internet-Drafts directories. This draft is a work item of the >>> IPv6 over Low Power Wide-Area Networks WG of the IETF. >>> >>> Title : LPWAN Overview Author : Stephen >>> Farrell Filename : draft-ietf-lpwan-overview-06.txt Pages >>> : 41 Date : 2017-07-21 >>> >>> Abstract: Low Power Wide Area Networks (LPWAN) are wireless >>> technologies with characteristics such as large coverage areas, >>> low bandwidth, possibly very small packet and application layer >>> data sizes and long battery life operation. This memo is an >>> informational overview of the set of LPWAN technologies being >>> considered in the IETF and of the gaps that exist between the >>> needs of those technologies and the goal of running IP in >>> LPWANs. >>> >>> >>> The IETF datatracker status page for this draft is: >>> https://datatracker.ietf.org/doc/draft-ietf-lpwan-overview/ >>> >>> There are also htmlized versions available at: >>> https://tools.ietf.org/html/draft-ietf-lpwan-overview-06 >>> https://datatracker.ietf.org/doc/html/draft-ietf-lpwan-overview-06 >>> >>> >>> >>> A diff from the previous version is available at: >>> https://www.ietf.org/rfcdiff?url2=draft-ietf-lpwan-overview-06 >>> >>> >>> Please note that it may take a couple of minutes from the time >>> of submission until the htmlized version and diff are available >>> at tools.ietf.org. >>> >>> Internet-Drafts are also available by anonymous FTP at: >>> ftp://ftp.ietf.org/internet-drafts/ >>> >>> _______________________________________________ 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 >
- 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