On Fri, Jun 21, 2013 at 8:28 AM, Juliusz Chroboczek <
[email protected]> wrote:
> > if it turns out to be multicast specific it could go in 3.5.1.
> > if there are more general issues to consider then perhaps a new
> sub-section?
>
> No, I think it's more general. What about something like the following:
>
>
>
> Homenets tend to grow organically over many years, and a homenet
> will typically be built over link-layer technologies from different
> generations. Current homenets typically use links ranging from
> 1Mbit/s up to 1Gbit/s, which is a three orders of magnitude speed
> discrepancy. We expect this discrepancy to get worse as both
> high-speed and low-power technogies are deployed.
>
> Homenet protocols should be designed to deal well with
> interconnecting links of very different speeds. In particular,
> flows local to a link should not be flooded throughout the homenet,
> even when sent over multicast, and, whenever possible, the homenet
> protocols should be able to choose the faster links and avoid the
> slower ones.
>
Here's a version derived from Juliusz's try. I also substitute
"bandwidth" for "speed", as
being sloppy about the language has tended to get us into the bufferbloat
mess.
- Jim
Homenets tend to grow organically over many years, and a homenet
will typically be built over link-layer technologies from different
generations. Current homenets typically use links ranging from
1Mbit/s up to 1Gbit/s, which is a three orders of magnitude bandwidth
discrepancy. We expect this discrepancy to widen further as both
high-speed and low-power technologies are deployed.
Homenet protocols should be designed to deal well with interconnecting
links of very different bandwidths. In particular, flows local to a link
should
not be flooded throughout the homenet, even when sent over multicast,
and, whenever possible, the homenet protocols should be able to choose the
faster links and avoid the slower ones.
Links (particularly wireless links) may also have limited numbers of
transmit opportunities
(txops), and there is a clear trend driven by both power and downward
compatibility constraints
toward aggregation of packets into these limited txops while increasing
bandwidth.
Transmit opportunities may be your scarcest resource and therefore also
strongly limit
actual bandwidth available.
Therefore protocols that avoid being "chatty", do not require flooding, and
enable isolation
of traffic between subnets are preferable to those which burn scarce
resources.
>
> If you wish, I can add a sentence saying "This implies that a link-state
> protocol must be used in the homenet" ;-)
>
> -- Juliusz
> _______________________________________________
> homenet mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/homenet
>
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
