IETF Logo Mail Archive

Re: Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.

Ted Lemon <Ted.Lemon@nominum.com> Fri, 06 February 2015 23:06 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF8CB1A889B; Fri, 6 Feb 2015 15:06:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 kxLzY2gqEuKY; Fri, 6 Feb 2015 15:06:05 -0800 (PST)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 129411A6F02; Fri, 6 Feb 2015 15:05:13 -0800 (PST)
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 8C0A8DA013D; Fri, 6 Feb 2015 23:05:13 +0000 (UTC)
Received: from webmail.nominum.com (cas-03.win.nominum.com [64.89.235.66]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 48E7653E08A; Fri, 6 Feb 2015 15:05:13 -0800 (PST)
Received: from [172.21.196.201] (64.110.2.19) by CAS-03.WIN.NOMINUM.COM (64.89.235.66) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 6 Feb 2015 15:05:12 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: Naive question on multiple TCP/IP channels and please dont start a uS NN debate here unless you really want to.
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <CAMm+LwhZXJb-cENRwySUWQGzDxG7E4Ca1ikjqYrxz7_HM_aADA@mail.gmail.com>
Date: Fri, 06 Feb 2015 16:05:05 -0700
Content-Transfer-Encoding: quoted-printable
Message-ID: <07E75BE1-FB76-4FB6-90A5-9E1F07D3699D@nominum.com>
References: <D0F962E2.1E9B2%richard@shockey.us> <CAGhGL2AAda10+YY54GJRN4Af_pGC4ZaMv=97=6aNRzqKfJBqkg@mail.gmail.com> <CAMm+Lwj4QVKQwwMvmypf6Gv8KEThbWzTFL+OR7ytjPT+RtGwRA@mail.gmail.com> <D0FA6196.1EB9C%richard@shockey.us> <CAMm+LwhZXJb-cENRwySUWQGzDxG7E4Ca1ikjqYrxz7_HM_aADA@mail.gmail.com>
To: Phillip Hallam-Baker <phill@hallambaker.com>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [64.110.2.19]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/eWKDUkRB_VczvWBJJxEreEjoYuU>
Cc: IETF Discussion Mailing List <ietf@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, Richard Shockey <richard@shockey.us>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Feb 2015 23:06:07 -0000

On Feb 6, 2015, at 12:13 PM, Phillip Hallam-Baker <phill@hallambaker.com> wrote:
> What would be useful to us is knowing electricity use by circuit which means instrumenting the circuit breaker board or by socket which means even more measurement.

We have that.   It was a PITA to install, requiring an extra box because of the space it consumed.   The data is sort of cool, but I'm not convinced anybody but an energy geek would be willing to pay the cost.

On the other hand, being able to look at my flows in real time and in history would actually be useful to me.

v2.23.0 | Report a Bug | By Email