Re: [homenet] primary / secondary configuration

[Michael Richardson <[e-mail]>]

Daniel Migault <[e-mail]> wrote:
    > the zone with the outsourcing infrastructure. To build the zone some
    > elements of the infrastructure are needed such as the NS and IP for
    > example. One way to enable the transmission of information from the the
    > outsourcing infrastructure to the homenet is to use an well known fqdn
    > hna.example.com with an AXFR request. Does it sound reasonable ?

So, during setup phase, the HNA does the equivalent of:

    % dig @configuration-server myDEVICE.r.example.net axfr

and gets back:
    myDEVICE.r.example.net IN SOA mname foo bar ...
                           IN NS ns1.example.com
                           IN NS ns2.example.com
                           IN NS ns3.example.com

which it uses as it's template for building it's zone, which is then signed
and AXFR'ed back to the distribution-master using the normal mechanisms.

There are probably some high-level details that we haven't gotten into the
document yet, which are important for understanding.

We drew this diagram in our call today:
  https://github.com/ietf-homenet-wg/ietf-homenet-hna/blob/master/hna-dm-cfg.svg

although I see some example.com->example.net, and foo.com->example.com edits that I
should make.

--
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-