IETF Logo Mail Archive

Re: [homenet] tuscles and conflicting goals / trust with draft-tldm-simple-homenet-naming CFA

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 18 August 2017 15:28 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66C6E13296D for <homenet@ietfa.amsl.com>; Fri, 18 Aug 2017 08:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9dn-DhHS8fhd for <homenet@ietfa.amsl.com>; Fri, 18 Aug 2017 08:28:11 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 353EF132977 for <homenet@ietf.org>; Fri, 18 Aug 2017 08:28:11 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A8220E20C; Fri, 18 Aug 2017 11:24:12 -0400 (EDT)
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EC11880E71; Fri, 18 Aug 2017 11:21:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "STARK, BARBARA H" <bs7652@att.com>
cc: Andrew Sullivan <ajs@anvilwalrusden.com>, "homenet@ietf.org" <homenet@ietf.org>
In-Reply-To: <2D09D61DDFA73D4C884805CC7865E6114DC00E2A@GAALPA1MSGUSRBF.ITServices.sbc.com>
References: <FCAD81FA-BBA0-45B0-8F1F-D1D5FD010484@fugue.com> <87shgvxybl.fsf@toke.dk> <4AF8CF8A-F781-449F-9C53-A9603889746E@fugue.com> <87lgmnxr3u.fsf@toke.dk> <E3E75086-BF36-4F59-86BD-7FFDAFE772AB@fugue.com> <87fuctxdrc.fsf@toke.dk> <FB44A942-9DE3-4CE6-88C5-402B20756462@fugue.com> <877ey4y62g.fsf@toke.dk> <6DF8489E-D780-4E4C-A132-31EEF8285BB7@fugue.com> <12755.1502913036@obiwan.sandelman.ca> <20170816203557.ieqnyepjqpoeq6um@mx4.yitter.info> <3387.1502980011@obiwan.sandelman.ca> <2D09D61DDFA73D4C884805CC7865E6114DC00E2A@GAALPA1MSGUSRBF.ITServices.sbc.com>
X-Mailer: MH-E 8.6; nmh 1.6+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 18 Aug 2017 11:21:26 -0400
Message-ID: <18536.1503069686@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/RJjMG426ZioRQ8Wenk8R8XJrw7o>
Subject: Re: [homenet] tuscles and conflicting goals / trust with draft-tldm-simple-homenet-naming CFA
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Aug 2017 15:28:13 -0000

STARK, BARBARA H <bs7652@att.com> wrote:
    >> This suggests to me that the next step in HOMENET, which I think the naming
    >> architecture could lead, is to provide for (automatic) collection of statistics for
    >> diagnostics purposes.
    >> i.e. Homenet OAM.

    > Not as chair...

    > I disagree this has anything to do with the naming architecture.

The reason I suggest that the naming architecture could lead this, is because
due to the multi-provider nature, we get specifically interesting statistics
From end-systems about how well they are communicating with their intended
targets.  Further, in order to deal with this kind of thing, there are host
changes desired, so doing OAM on those changes seems like not too much a stretch.

For instance, how many times did they pick a src/dst combination for a DNS
query, or a data transmission, for which there was a communication failure?

    > I have long felt the best way to accomplish this would be to have a
    > discoverable (DNS-SD) NetJSON (http://netjson.org/) "service" on all
    > consumer routers, which would supply NetJSON types via http.

    > I agree supplying statistics info to the home network would be a good
    > thing for homenet to tackle.
    > I've been wanting to propose this for a while, but keep getting side-tracked.

You have described a mechanism to collect the statistics, and it seems like a
very good suggestion.


--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email