Re: [Lln-futures] What is LLN?

Geoff Mulligan <geoff@proto6.com> Wed, 26 September 2012 16:14 UTC

Return-Path: <geoff@proto6.com>
X-Original-To: lln-futures@ietfa.amsl.com
Delivered-To: lln-futures@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C4A21F84D3 for <lln-futures@ietfa.amsl.com>; Wed, 26 Sep 2012 09:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.65
X-Spam-Level:
X-Spam-Status: No, score=-100.65 tagged_above=-999 required=5 tests=[AWL=-1.950, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nwcYxM2Unp3P for <lln-futures@ietfa.amsl.com>; Wed, 26 Sep 2012 09:14:14 -0700 (PDT)
Received: from mail.coslabs.com (mail.coslabs.com [199.233.92.34]) by ietfa.amsl.com (Postfix) with ESMTP id 0F92421F84CF for <lln-futures@ietf.org>; Wed, 26 Sep 2012 09:14:13 -0700 (PDT)
Received: from [199.233.92.4] (unknown [199.233.92.4]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.coslabs.com (Postfix) with ESMTPSA id 154E05F753; Wed, 26 Sep 2012 10:14:11 -0600 (MDT)
Message-ID: <506329D4.3050204@proto6.com>
Date: Wed, 26 Sep 2012 10:14:12 -0600
From: Geoff Mulligan <geoff@proto6.com>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:15.0) Gecko/20120827 Thunderbird/15.0
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
References: <042c01cd9b58$8ac27700$a0476500$@olddog.co.uk> <CAK=bVC-mSVj+A+k07Odz-w1_coOTWi_2a7oFsG7hH3Chy7QUDg@mail.gmail.com> <A49B626D-BA24-448F-9FC5-7D7C919092F2@gmail.com>
In-Reply-To: <A49B626D-BA24-448F-9FC5-7D7C919092F2@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: Farrel Adrian <adrian@olddog.co.uk>, Ulrich Herberg <ulrich@herberg.name>, lln-futures@ietf.org
Subject: Re: [Lln-futures] What is LLN?
X-BeenThere: lln-futures@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <lln-futures.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lln-futures>, <mailto:lln-futures-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lln-futures>
List-Post: <mailto:lln-futures@ietf.org>
List-Help: <mailto:lln-futures-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lln-futures>, <mailto:lln-futures-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 26 Sep 2012 16:14:14 -0000

done
On 09/26/2012 05:55 AM, Ralph Droms wrote:
> Ulrich, Geoff - if you intend to change the meaning of "LLN" to match "low power and lossy networks", it would be good to fix the BoF description in the wiki before today's BoF request at 11:30AM EDT.
>
> - Ralph
>
> On Sep 25, 2012, at 6:06 PM 9/25/12, Ulrich Herberg wrote:
>
>> Hi,
>>
>> I agree with Adrian that we should not use the same acronym for different terms (but maybe it was just a glitch in the BOF request?).
>>
>> I don't think that low-power should be excluded.
>>
>> Best
>> Ulrich
>>
>> On Tue, Sep 25, 2012 at 1:01 PM, Adrian Farrel <adrian@olddog.co.uk> wrote:
>> Bit of a fundamental question to be asking at this stage?
>>
>> ROLL defines LLNs as "Low power and lossy networks"
>> The BOF request defines "Lossy Link Networks"
>>
>> Clearly lossy link networks form a subset of low power and lossy networks. But
>> is the intention to exclude low power considerations?
>>
>> It would really help to not define the same acronym with two different but very
>> close meanings (notwithstanding WAD [RFC5513]).
>>
>> Could you clarify and simplify?
>>
>> Thanks,
>> Adrian
>>
>> _______________________________________________
>> Lln-futures mailing list
>> Lln-futures@ietf.org
>> https://www.ietf.org/mailman/listinfo/lln-futures
>>
>> _______________________________________________
>> Lln-futures mailing list
>> Lln-futures@ietf.org
>> https://www.ietf.org/mailman/listinfo/lln-futures