{a short reply, but I will keep it unread, because I have more to day}
>>>>> "Michael" == Michael Thomas <[email protected]> writes:
>> So, homenet wants a particular configuration, and we need to
>> write it down. We also need to provide for signaling from the
>> ISP as to what they expect. I think that there are four
>> situations, and ideally, I'd like eliminate at least two:
Michael> Can we not use "ISP"? There's no reason why it needs to
Michael> be. Maybe DNS Service Provider (DSP) or something more
Michael> neutral?
Well, there are three possible zones involved:
1) the reverse zone.
2) an ISP specific forward one.
3) a zone the home user provides.
(1) and (2) are *ISP* specific, so I think that actually one does need
to say ISP, and not DSP.
(3) is, I agree, not specific to an ISP.
Michael> I'd venture to say that the requirement ought to be that my
Michael> homenet devices MUST be able to automatically (= no human
Michael> intervention) be able to add/change RR's in my domain
Michael> within some policies. I find it a little more plausible
I agree.
I found the whole "people like to turn off their CER" weird.
But, that's because sandleman.ca lives at my home, and when I'm
travelling is exactly when I don't want my CER off.... but I accept
that I'm an IETF-type geek, and this protocol isn't about me.
Michael> In Mark's parlance if I've got it right, CER would be an
Michael> unlisted authoritative server which is a master to DSP's
Michael> listed authoritative servers who are slaves to CER for my
Michael> domain. I think #2 folds into this too, because even your
Yes.
--
] Never tell me the odds! | ipv6 mesh networks [
] Michael Richardson, Sandelman Software Works | network architect [
] [email protected] http://www.sandelman.ca/ | ruby on rails [
pgpKrWS2jq8Bw.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
