Mikael,
Um, what does a router do? Look at the example in the text and ask yourself if you want an average user (my canonical "average user" being my daughter, who wanted me to come to her house to install a camera on her computer so she could use it on Skype - "did you try plugging it in?") manually installing routes in each of the four routers when they could in fact learn them from each other directly?So, looking at this from another angle, namely deployment. I'm a router engineer, I support the use of routing protocols as much as the next router engineer, but I think a good question to ask is whether most home CPE vendors think RIP for IPv6 is hard to implement, or if this is something they consider easy?If it's easy to implement RIP for IPv6 then I'm a proponent for that model.
RIP is by far the easiest routing protocol to implement. and yes it is very easy. as a side note if anyone remembers the "zerorouter?" BOF work going on a few years back one solution to solving subnet id election and arbitrary topology was to use new LSAs for OSPF.
in any case aren't there enough open source implementations around for any routing protocol? wouldn't think a CPE vendor would need to implement it themselves from scratch.
Fred, (just checking) the model you're advocating then is that DHCPv6-PD from the main home CPE (with WAN connection) hands out subnets which are then announced to all home gateways via RIP(v6) ?
each requesting router i.e the router which has received the sub delegation will advertise that prefix.
cheers, Ole
smime.p7s
Description: S/MIME cryptographic signature
-------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
