Re: [Lln-futures] What is LLN?
"JP Vasseur (jvasseur)" <jvasseur@cisco.com> Wed, 26 September 2012 14:58 UTC
Return-Path: <jvasseur@cisco.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 7690C21F843F for <lln-futures@ietfa.amsl.com>; Wed, 26 Sep 2012 07:58:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.649
X-Spam-Level:
X-Spam-Status: No, score=-8.649 tagged_above=-999 required=5 tests=[AWL=-1.950, BAYES_00=-2.599, FB_CIALIS_LEO3=3.899, RCVD_IN_DNSWL_HI=-8]
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 Y+WdU6Eg07Ne for <lln-futures@ietfa.amsl.com>; Wed, 26 Sep 2012 07:58:31 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) by ietfa.amsl.com (Postfix) with ESMTP id B441321F8435 for <lln-futures@ietf.org>; Wed, 26 Sep 2012 07:58:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1836; q=dns/txt; s=iport; t=1348671511; x=1349881111; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=aAsilwQOrbOWpxkd1ycQn+3Ww+6Pf4jHHTRSYfIOHOk=; b=W9uux+qbHaQfKUpQAhntbfyCp+/3PcdwiwdHGpzxLrR/y+i03Qvt2LxO oRc0JoVmys/ogkEk7O9h2PkQOzzrrsOeBhXA1XyM4gGNv/2Ei8iu7KPG8 T+o5bH5IuYo/gRV75+HIXHE5NN7PN2WtVl3qCDZGaYDz+KRE51hTibJJV k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av8EAOgWY1CtJV2d/2dsb2JhbABFvlqBCIIgAQEBAwEBAQEPAVsGBQULAgEIDgouJwslAQEEDgUih10GC5k3oC0EixgbhQ5gA5VpjkKBaYJnghc
X-IronPort-AV: E=Sophos;i="4.80,490,1344211200"; d="scan'208";a="125575562"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP; 26 Sep 2012 14:58:31 +0000
Received: from xhc-rcd-x04.cisco.com (xhc-rcd-x04.cisco.com [173.37.183.78]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id q8QEwVSZ021884 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Sep 2012 14:58:31 GMT
Received: from xmb-rcd-x02.cisco.com ([169.254.4.167]) by xhc-rcd-x04.cisco.com ([173.37.183.78]) with mapi id 14.02.0318.001; Wed, 26 Sep 2012 09:58:31 -0500
From: "JP Vasseur (jvasseur)" <jvasseur@cisco.com>
To: Ralph Droms <rdroms.ietf@gmail.com>
Thread-Topic: [Lln-futures] What is LLN?
Thread-Index: Ac2bWAhOfchHWe2SSnG8rZWfLIYBRQAO+xOAABzxdIAAAEOBAA==
Date: Wed, 26 Sep 2012 14:58:30 +0000
Message-ID: <5C81EF23-7528-4E50-85D7-ACAEA11116D5@cisco.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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.60.114.229]
x-tm-as-product-ver: SMEX-10.2.0.1135-7.000.1014-19210.004
x-tm-as-result: No--38.508300-8.000000-31
x-tm-as-user-approved-sender: No
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <03FAFA09FC1326499A1776E8BFCD325D@cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: Geoff Mulligan <geoff@proto6.com>, Farrel Adrian <adrian@olddog.co.uk>, Ulrich Herberg <ulrich@herberg.name>, "<lln-futures@ietf.org>" <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 14:58:32 -0000
Right, hopefully we'll be using the same acronym … for the same low power and lossy networks concept. On Sep 26, 2012, at 1:55 PM, 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 > > _______________________________________________ > Lln-futures mailing list > Lln-futures@ietf.org > https://www.ietf.org/mailman/listinfo/lln-futures
- [Lln-futures] What is LLN? Adrian Farrel
- Re: [Lln-futures] What is LLN? Ulrich Herberg
- Re: [Lln-futures] What is LLN? Ralph Droms
- Re: [Lln-futures] What is LLN? JP Vasseur (jvasseur)
- Re: [Lln-futures] What is LLN? Geoff Mulligan