Re: [lp-wan] overview draft with some text...

Stephen Farrell <stephen.farrell@cs.tcd.ie> Sat, 29 October 2016 22:46 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 412B31294D5 for <lp-wan@ietfa.amsl.com>; Sat, 29 Oct 2016 15:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.732
X-Spam-Level:
X-Spam-Status: No, score=-4.732 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, RP_MATCHES_RCVD=-0.431, SPF_PASS=-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 LGb9PadnB2LL for <lp-wan@ietfa.amsl.com>; Sat, 29 Oct 2016 15:46:19 -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 93E3712940F for <lp-wan@ietf.org>; Sat, 29 Oct 2016 15:46:19 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 00C34BE50; Sat, 29 Oct 2016 23:46:16 +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 DkKGQvYNAVJM; Sat, 29 Oct 2016 23:46:15 +0100 (IST)
Received: from [10.87.48.210] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id D4318BE32; Sat, 29 Oct 2016 23:46:14 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1477781175; bh=4c5MhZU9R2IThn0cXST1StUMA6unw1/nyWpLRor8vTQ=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=tlfcIaBP8VvWieYlxhBfse4pptcNf5lgxCtQmaQ/o2Uu7Hdl6/PnC6fwTU+rve+7a IEeDjVJfkFsS1OWZ0gd9bz1ae2gowRudx2N03Th4fYeYjlanPhGzcCBzZ+MFvlNrhB f0PhqpjhfQZGldKqg4SLMkees2RNWHVX+kQbcoxc=
To: Jiazi Yi <ietf@jiaziyi.com>
References: <ae4d58bd-9ceb-85da-6517-b4b71967454f@cs.tcd.ie> <D2311B5C-AA00-48BA-B049-3AEFEFE874E2@jiaziyi.com>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <4891a4f9-f268-78cb-ab07-ded419e39b33@cs.tcd.ie>
Date: Sat, 29 Oct 2016 23:46:15 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <D2311B5C-AA00-48BA-B049-3AEFEFE874E2@jiaziyi.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms090203040607010900060900"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lp-wan/wTUa--4roAHcn0uSch6nqEPW_3E>
Cc: lp-wan@ietf.org
Subject: Re: [lp-wan] overview draft with some text...
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: Sat, 29 Oct 2016 22:46:22 -0000

Hiya,

On 29/10/16 23:19, Jiazi Yi wrote:
> Dear Stephen,
> 
> Thanks a lot for the work!
> 
> A general comment before going into details:
> 
> When introducing characteristics and performance of different
> technologies, I think we need to pay attention that:
> 
> 1) focus on the objective characteristics, such as frequency band,
> bandwidth, data rate, etc. I would avoid using text like “foo has
> battery life of XXX years” or “bar can support YYY devices in a
> single cell”. Those kind of characteristics depend on highly on the
> configuration of the network, application traffic pattern, network
> environment, etc. It’s very hard to extract useful information from
> such kind of assertions.

Fully agree with editing out any such statements. Feel free to
point out any that are in there now, but I'll also do a pass for
that myself later on.

> 
> 2) For each technology, we talk only the current characteristics, not
> the targeting characteristics (especially those long target).

I'm not sure I agree there. If there are changes planned that'd
happen in the next say 5 years, then it seems like those would
be fine input for the WG to consider. Of course, I do agree that
the WG will need to be exercise judgement about how they consider
any such plans, as we're all prone to being a bit optimistic
about the future:-)

FWIW, I think anything written down as an IETF contribution or
that can be referenced from one should be good input to the WG.

What the WG choose to conclude from such input is of course
another question. But that's just me. Whether or not the WG have
consensus to regard some input or claim as outlandish or worth
documenting and analysis is not my call.

> 
> 3) It’s welcome to report implementation status of different
> technologies, but if the contributors choose to do so, please provide
> a bit more details (such as the scale of the deployment, applications
> running over it, etc.), with appropriate references.

I'm curious myself about some of the current implementations and
deployments and whether those might constrain the work here. But
I'm not clear about the level of detail the WG need about that.

> 
> The purpose is to have an objective standard as possible for all the
> technologies listed in the draft. We have to admit that, although we
> (all?) agree, and called out explicitly that this document is NOT
> intended to compare which technology is better, we couldn’t stop the
> readers from making such kind of comparison.

Not sure I'm following the point there.

One thing I do think though - regardless of whether or not the
WG decide this draft ought end up as an RFC, we still only need
the text here to be sufficiently clear for the WG to do it's
job. And if we aim for perfect wording then we'll probably take
a lot of time to just not achieve that. So while we do need to
ensure that the overall text doesn't give a wrong impression, I
figure being careful to not waste time aiming for a non-useful
level of perfection will be better.

Cheers,
S.


> 
> regards
> 
> Jiazi
> 
>> On 29 Oct 2016, at 01:57, Stephen Farrell
>> <stephen.farrell@cs.tcd.ie> wrote:
>> 
>> 
>> Hiya,
>> 
>> I've incorporated descriptive text about some of the "input"
>> technologies for lpwan in -01 of the overview draft. [1] That
>> includes text from a lora draft that Alper and I also posted
>> recently [2] and from the existing sigfox and nb-iot drafts. Next
>> up will be adding text from the gap analysis work in the places 
>> indicated. I hope to post that before the cutoff. We may also get
>> text on WI-SUN by then too.
>> 
>> Comments on any inaccuracies or omissions in [1] are of course very
>> welcome. There's a github repo [3] if anyone prefers that. (Though
>> my github foo is modest so bear with me if taking that approach:-)
>> I'll make sure that any substantive discussion initiated on github
>> is reflected to the list.
>> 
>> Cheers, S.
>> 
>> [1] https://tools.ietf.org/html/draft-farrell-lpwan-overview-01 [2]
>> https://tools.ietf.org/html/draft-farrell-lpwan-lora-overview-01 
>> [3] https://github.com/sftcd/lpwan-ov
>> 
>> 
>> _______________________________________________ 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
>