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? 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? 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. 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? -- Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting ) Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
