On Jun 13, 2014, at 9:48 AM, Lorenzo Colitti <lore...@google.com> wrote: > Not to me they didn't. Seriously - if you understand what we're being asked > to do, and it's simple to explain, then it shouldn't take long for you to > type. Please?
The working group would presumably like for there to be routing on the homenet. What problems is the routing supposed to solve? What things are priorities? What things aren't priorities? Clearly we need the routing solution to get packets to the right egress based on source address. Do we also need it to do load sharing across parallel links, if such links exist? Is it important to minimize the number of hops? How long of a delay can there be between changes to the topology (e.g., a router being unplugged) and recovery, assuming that a flow was going through that router? Is it okay to break a flow in that situation, or does it need to survive the transition? Does the routing protocol need to be aware of the type of media a given link crosses, and does it need to prefer one media type over another where both are available? I'm basically making questions up here. The document should say what the working group wants routing to accomplish. Right now it's a bit of a kitchen sink, with a lot of (IMHO) inappropriately prescriptive text. _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet
