Re: [homenet] final planning for not formally meeting

On Jul 20, 2019, at 5:17 PM, RayH wrote: > One question on re-reading this version: why not populate the reserve zone > automatically from the data used to update the forward zone? That’s exactly what we’ve figured out in the Service Registration Protocol document. :)

Re: [homenet] final planning for not formally meeting

On 20 Jul 2019 20:07, Ted Lemon wrote:On Jul 20, 2019, at 9:49 AM, RayH wrote:This (expired) draft?https://tools.ietf.org/html/draft-ietf-homenet-simple-naming-03Yes.We decided to get some implementation experience before proceeding, and it hasn’t popped to the top of the stack

Re: [homenet] final planning for not formally meeting

On Jul 20, 2019, at 9:49 AM, RayH wrote: > This (expired) draft? > > https://tools.ietf.org/html/draft-ietf-homenet-simple-naming-03 > Yes. We decided to get some implementation experience before proceeding, and it hasn’t

Re: [homenet] final planning for not formally meeting

On 20 Jul 2019 13:04, Ted Lemon wrote:We have a design for local resolution in the homenet naming architecture doc.This (expired) draft?https://tools.ietf.org/html/draft-ietf-homenet-simple-naming-03Or have I missed something? I haven’t reviewed the latest front-end naming doc yet but presumably

Re: [homenet] final planning for not formally meeting

We have a design for local resolution in the homenet naming architecture doc.. I haven’t reviewed the latest front-end naming doc yet but presumably we can implement that and see what happens. :) Sent from my iPhone > On Jul 20, 2019, at 4:46 AM, RayH wrote: > > > If anybody is interested in

Re: [homenet] final planning for not formally meeting

> 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