On 01 Oct 2012, at 17:33 , Curtis Villamizar wrote: >>> I prefer if A and B, then C. >> >> I understand you have a personal preference. >> >> A set of people on this list have indicated that >> particular preference is strongly undesirable. > > I agree that it is *very* undesirable. It does work. I've tried it.
It does not *generally* work. If it works for you, that says more about what kind of equipment you are connecting -- and the capabilities of that equipment (e.g. DHCPv6) than anything else. Particularly, DHCPv6 does not work with some widely deployed consumer electronics gear -- gear that only supports SLAAC. >> However, disallowing SLAAC is NOT the ONLY conceivable >> approach. One ought to try to think of other options >> (each of which probably has different tradeoffs). > > AFAIK SLAAC requires a /64 prefix. Yes. > Or are you suggesting changing it? No. > If A and B, then C is a possibility. One of several different possibilities. That one is particularly ugly because it means that some devices won't be able to connect to the network *at all*. Most consumers expect ALL of their devices to be able to connect with and use their home network. Anything less generally is viewed as not satisfactory. > Another option is to use a tunnel rather than > the ISP native IPv6 if the ISP won't allocate > prefixes other than /64. Yes. Other options also exist. > It may be the homenet can say that in order for things to work > in the home certain things are required of the ISP or highly > desirable (DHCPv6 prefix allocation, DNS and rDNS delegation > and secondary, at least /60 on request and preferably without > additional charge, etc). That sounds sensible to me -- and HIGHLY preferable to having HomeNet encourage ISPs to delegate /64s (or even longer prefixes) by standardising kludges that work only for special cases -- or only for equipment with features not universally available now/soon. > btw- if DHCP is not used, then dynamic DNS > has to get populated directly from the host This likely is true EVEN IF one has DHCPv6 in use. Running DHCPv6 does NOT automatically mean that the DNS gets populated correctly. Some DHCPv6 servers might have this capability, but other DHCPv6 servers definitely do not do this. (new topic) You seem to have a very particular brand/make/model of equipment in mind when you write about deployments. IMHO, HomeNet needs to work *in the general case*, without limiting its workability to Brand X, Model Y equipment running software version Z. Yours, Ran _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
