Re: [homenet] naming drafts

Hi everyone

I have belatedly reviewed both drafts. I missed the WGLC due to both
$dayjob and the IETF having a plethora of interesting working groups. But
still, I hope this feedback is useful

In general, I appreciate the aim of the drafts which I will paraphrase as
creating a way to automatically and reliably publish a home zone containing
a number (n) of smart devices. This makes a lot of sense when we know n is
going to carry on growing, and of course renumbering can be frequent.

My specific feedback is below, organised by section number.

*draft-ietf-homenet-front-end-naming-delegation-15*
1 It would be useful if the introductory text in the Abstract also appeared
here in the Introduction.

1.1 Typos: "humuan" and "addressees "

3.1 I'd prefer the diagram to be located at the beginning of this section.

4.7 This section should also state, as it does in section 7, that the
Hidden Primary Server be firewalled such that only the known address range
of the DMs are permitted to connect to it.

7 I'd prefer not to use the word "packets" when it's really messages that
we considering. Also in my opinion invalid messages to/from the DM ought to
be rejected rather than simply dropped.

Here's my suggested version, with changes highlighted in red:
   The Hidden Primary SHOULD drop any packets arriving on
   the WAN interface that are not issued from the DM.  The Hidden
   Primary SHOULD NOT send DNS messages other than DNS NOTIFY query,
   SOA response, IXFR response or AXFR responses.  The Hidden Primary
   SHOULD reject any incoming messages other than DNS NOTIFY response, SOA
   query, IXFR query or AXFR query.  The Hidden Primary SHOULD reject any
   non protected IXFR or AXFR exchange, depending on how the
   synchronization is secured.

12 This acknowledges that it's a little risky to publish names of home
devices publicly, and notes that often it's only the home owner or
immediate family that ought to be able to query these names. It says that
limiting ability to query can be done by IP source (IMHO tricky), or VPN.
To which I think, if the home owner is using a VPN to the home to query the
public zone, why do we need external publication at all? Some words to
explain that better might be useful.

*draft-ietf-homenet-naming-architecture-dhc-options-14*

3 In both American and British English I think the word "collocate" should
be "colocate" (or alternatively "co-locate").

3 What exactly is meant by "(eventually by a self signed certificate)"?

4.2 I think the HNA also needs to learn the set of IP addresses that the DM
might legitimately use in order to contact the HNA, so that these IPs can
be whitelisted in the CPE's firewall. Simply looking up the FQDN doesn't
provide that. Should it be added to this DHCP option?

Hope that's useful.

Thanks,
Chris

On Fri, 4 Jun 2021 at 20:45, STARK, BARBARA H <bs7652@att.com> wrote:

> Hi homenet WG,
> Stephen and I have been chatting about the status of the 2 naming drafts
> (draft-ietf-homenet-front-end-naming-delegation and
> draft-ietf-homenet-naming-architecture-dhc-options).
>
> We started a 3-week WGLC about a month ago (04 May). Both drafts received
> comprehensive review from Med. Stephen reviewed
> front-end-naming-delegation. Bernie reviewed the formatting of the DHC
> option.
> The authors provided updates to resolve these comments. Bernie
> acknowledged satisfactory resolution of his comments.
> Requests to change terminology were satisfactorily resolved -- but that
> discussion doesn't count as really being part of anyone's review of the
> drafts.
> Stephen and Juliusz expressed that they're still not convinced that DDNS
> isn't a good enough solution for the use case.
>
> Stephen and I do not believe these drafts have received enough review or
> support to put them forward as representing WG consensus.
>
> But the authors have spent significant effort in creating these drafts and
> the associated implementation. We will work with Éric V (as INT area AD)
> and the authors to determine next steps.
>
> Barbara and Stephen
>
> _______________________________________________
> homenet mailing list
> homenet@ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>