On Thu, 26 Mar 2009, Stark, Barbara wrote:
The capabilities described in RFC 4191 are certainly something the BBF is looking at, and it would be interesting to hear IETF thoughts on the cases that it might handle. Here are some possible scenarios: (1) CPE Router has multiple WAN connections. Let's say one is a
(2) CPE Router has a wired WAN connection and a backup wireless WAN connection. Both support "default" connectivity. RFC 4191 could be used
(3) The home has multiple connections through multiple routers. Perhaps RIPng (or other protocols like it) doesn't really seem to be the right answer here. As mentioned in the CPE Router draft, it has scalability concerns in the access network. And it seems kind of weird in the LAN. But using RFC 4191 to supply route info in the RA would be pretty easy. This route info is fairly static. By the way -- these are all real scenarios. People and service providers do these things. They just don't always do them well, today. (1) is particularly common in IPv4, and is handled through static routing table
Concur. Even for the general case of multiple cascaded CPERs, I think we do want them to know how to talk directly to each other rather than forcing all intra-customer traffic through the next upstream CPER.
Antonio Querubin whois: AQ7-ARIN