On Fri, May 14, 2021 at 11:17 AM Michael Richardson <[email protected]> wrote:
> > Daniel Migault <[email protected]> wrote: > > Please find the new version that is considering the discussions of > the > > mailing list as well as comments received from Med. > > Daniel, I was just proofreading, and you'll see a pull request "typos" > > 1. reading at the beginning, I didn't recall if we had concluded that we > were > going to mandate the AXFR to be XoT (AXFR over TLS) or not. > We later reference [I-D.ietf-dprive-xfr-over-tls], but not section > 4.5.1. > Is it enough to say it in section 5.1? > <mglt> In my mind, we were mandating AXFR over TLS. So we should probably clarify this in section 4.5.1 as well. </mglt> > > 2. What if the zone template provided by the DM has to change. > (Because, for instance, the distribution server NS records change). > Is the template retrieve each time the zone is signed? > Once? (And never again?...) > Based upon some TTL? > > <mglt> That is a good catch. The TTL of the NS may be a good indication. But we may also recommend the HNA to check it regularly, like every day or every week. </mglt> > 3. Section 4.6, we say "SHOULD" on TLS, but in which case, what exception > are we > thinking? I guess we three will have to do another SHOULD/MUST audit. > Noting that RECOMMENDED ==> SHOULD. > > <mglt> I think we said SHOULD in case some deployment wants to use other means. The one that come to my mind is if a deployment is willing to use TSIG for example. I am find moving this to MUST use TLS. </mglt> > > Section 5 has "YYYY" and "XX"... which feels like maybe we forgot to do > some > IANA thing. Maybe we should omit the placeholders? What does the WG > think? > > <mglt> I think the 4 digit port and 2 digit port are clearly represented by these variables, but I am fine we remove these if that bring any confusion. </mglt> > -- > Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) > Sandelman Software Works Inc, Ottawa and Worldwide > > > > > -- Daniel Migault Ericsson
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
