On Aug 3, 2011, at 7:18 AM, Thomas Herbst wrote:

> IMHO, consumers should be able to connect their routers together fairly 
> randomly and have them work, because they will connect them randomly.
> 
> The hard problem we get to fairly quickly with random connections determining 
> which connections do or do not require special security levels. 

the number of time's I've seen two cpe devices cascaded of each other in ipv4 
land is significant, it works for the most part in the sense that double nat 
inside your house works for the most part. normally I take pitty on those folks 
and help them turn the interior one into a bridge, but the  expectation that 
anyone will do more than plug them together is problematic. there are other 
things that are routers that interact with the home network... laptop with 
vmware or virtualbox is a router, today in ipv4 it nats or bridges, smartphones 
are routers potentially with their own downstream devices. some of these 
devices are relatively statically connected and some of them are ephemerally 
connected.

> From: "Torbet, Dan" <[email protected]>
> Date: Wed, 3 Aug 2011 06:42:53 -0700
> To: "[email protected]" <[email protected]>, "[email protected]" <[email protected]>
> Subject: [homenet] default LAN routing protocol for IPv6 CE router
> 
> The conversations so far on this topic have been great.  I think however, we 
> need to take a step back for a moment and think through what the HOMENET 
> network looks like when serviced by a CPE Router.  In my mind, we have a few 
> scenarios that are possible.
>  
> The first is a CPE ingress router to the home and no other routers.  There 
> may be in this device multiple SSIDs and they each might need to have their 
> own address space and have separate firewall/filtering rules.  In this case, 
> everything is contained in a single box and so no additional routing 
> protocols are needed.  This has been defined in the CPE router (RFC 6204)  
> and the bis extension that is in draft right now.
>  
> The second case is a CPE ingress router with N routers behind it.  In this 
> case, I humbly submit that anything where N is greater than 2 says medium 
> sized business maybe larger.  I find it real hard to get any deeper than 2 
> routers in series for a HOMENET class device deployment. Anything greater 
> than that and you likely would not use this class of device anyway.  Sure 
> there will be situations where this is not true ,but I’ll wager that in 90% 
> of the installations where a CPE router is providing the link to the world, 
> this will be the case.  Even factoring in SmartGrid I just can’t see a very 
> deep network.  Is there a use case for more than 1 or 2 layers in a HOMENET 
> deployment that uses a CPE router as the connection to the world? To be clear 
> here – this is what I mean:
> (sorry for the poor ASCII art here )
>  
>                Provider Router -------- CPE router ----------Router ------ 
> Router 
>  
> Or
>  
>  
>                                                             Provider
>                                                                  |
>                                                             CPE Router
>                                                                 ^
>                                              Router                  Router
>                                                 |                             
> |
>                                              Router                 Router
>  
> I will acknowledge that in some business cases you might place a router on 
> each floor or each building in a campus, but this is where things get blurry 
> for me – would you really use a CPE router in these cases for ingress into 
> the business? You certainly could, but would you?
>  
> Given that, I think that defining how many routers exist behind this CPE 
> ingress router will provide us with a reasonable place from which to define 
> the needs and requirements for an IGP running in the home.
>  
> Dan
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet

_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to