Re: [homenet] final planning for not formally meeting

RayH <v6ops@globis.net> Sat, 20 July 2019 13:50 UTC

Return-Path: <v6ops@globis.net>
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 D59AB120052 for <homenet@ietfa.amsl.com>; Sat, 20 Jul 2019 06:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.222
X-Spam-Level:
X-Spam-Status: No, score=-0.222 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTML_MIME_NO_HTML_TAG=0.377, MIME_HTML_ONLY=0.1, MISSING_MIMEOLE=1.899, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 YsO48TeYOaFp for <homenet@ietfa.amsl.com>; Sat, 20 Jul 2019 06:50:07 -0700 (PDT)
Received: from globis01.globis.net (mail.globis.net [IPv6:2001:470:1f15:62e::2]) by ietfa.amsl.com (Postfix) with ESMTP id 4927C1200E3 for <homenet@ietf.org>; Sat, 20 Jul 2019 06:50:06 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by globis01.globis.net (Postfix) with ESMTP id 9522A40192; Sat, 20 Jul 2019 15:50:05 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at globis01.globis.net
Received: from globis01.globis.net ([127.0.0.1]) by localhost (mail.globis.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7LrjQAwsvoJ0; Sat, 20 Jul 2019 15:50:02 +0200 (CEST)
Received: from [192.168.2.81] (ppp-94-64-221-62.home.otenet.gr [94.64.221.62]) (Authenticated sender: v6ops@globis.net) by globis01.globis.net (Postfix) with ESMTPSA id 4314F40156; Sat, 20 Jul 2019 15:50:01 +0200 (CEST)
Date: Sat, 20 Jul 2019 16:49:57 +0300
Message-ID: <7702c3d5-b5b2-4c65-a2ff-37d6d05f72cc@email.android.com>
X-Android-Message-ID: <7702c3d5-b5b2-4c65-a2ff-37d6d05f72cc@email.android.com>
In-Reply-To: <95CFEF29-18B7-4724-B956-4275DD7C8C80@fugue.com>
From: RayH <v6ops@globis.net>
To: Ted Lemon <mellon@fugue.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, homenet <homenet@ietf.org>, "STARK, BARBARA H" <bs7652@att.com>
Importance: Normal
X-Priority: 3
X-MSMail-Priority: Normal
MIME-Version: 1.0
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/homenet/pRgHdYAfKxzlcNPAaZkXXlgNd8U>
Subject: Re: [homenet] final planning for not formally meeting
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.29
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: Sat, 20 Jul 2019 13:50:09 -0000




On 20 Jul 2019 13:04, Ted Lemon <mellon@fugue.com> wrote:
We have a design for local resolution in the homenet naming architecture doc.

This (expired) draft?


Or have I missed something?


I haven’t reviewed the latest front-end naming doc yet but presumably we can implement that and see what happens. :)

Sure.


Sent from my iPhone

On Jul 20, 2019, at 4:46 AM, RayH <v6ops@globis.net> wrote:

> If anybody is interested in building what I’m building, I can supply some pointers. 

Please. A working build chain would save a lot of effort. I'm on vacation now, but I should have some time when I get back.

Stuart and I have four AR750S routers between us. The challenge will be figuring out how to get HNCPd to negotiate naming.

I think that depends on how the name space, serving, and resolving is going to be structured.

Do you already have ideas?

A fully distributed system would need to inform other name servers of the local zones in use, and break ties. A centralised system would need to crown a queen in a similar way to selecting the root bridge in 802.1d.

Regards,


On 20 Jul 2019 02:49, Ted Lemon <mellon@fugue.com> wrote:

Stuart and I have four AR750S routers between us. The challenge will be figuring out how to get HNCPd to negotiate naming.

Sent from my iPhone

> On Jul 19, 2019, at 7:15 PM, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>
>
> STARK, BARBARA H <bs7652@att.com> wrote:
>> If there are people interested in HNCP integration, I’m happy to
>> reserve space for that (at a time different from the -naming effort),
>> and I’m happy to participate in that as well.
>
> I want to do HNCP integration at the hackathon, if we can.
> If it overflows into the Code Lounge, fine.  But, my idea for Tuesday morning
> is that it's about bashing documents, not code.
>
>> I’ll see about reflashing my router to the most current OpenWRT. It
>> really needs updating, anyway.
>
> I'm also happy if we get (at the Hackathon) devices that people bring up to "current"
>
> --
> ]               Never tell me the odds!                 | ipv6 mesh networks [
> ]   Michael Richardson, Sandelman Software Works        | network architect  [
> ]     mcr@sandelman.ca  http://www.sandelman.ca/" rel="nofollow">http://www.sandelman.ca/        |   ruby on rails    [
>   

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet" rel="nofollow">https://www.ietf.org/mailman/listinfo/homenet