Re: #6: Support for arbitrary topologies

IEEE P1905 is one tool that helps in that regard...
http://grouper.ieee.org/groups/1905/1/

regards, kiwin

On 3/24/2012 1:04 PM, Brian E Carpenter wrote:
> Barbara,
>
>
> On 2012-03-25 08:44, STARK, BARBARA H wrote:
>>>> #6: Support for arbitrary topologies
>
> ...
>> I don't think it should be a question of trying to stop anybody from doing anything. It's a question of what
do we want to make easy (via auto-configuration or minimal configuration like turning something on/off).
> ...
> (Much good sense deleted)
>
>> And my experience with users is that they're thrilled if there is "a" way to make things work, that's
simple and reasonably intuitive. They aren't stuck on needing all possible ways to work.
>
> I agree entirely, and it's clear that somebody (not necessarily vendors)
> will need to write a simple guide on ways to connect up your homenet.
> What we should perhaps worry about is tools (beyond classical loop
> prevention in bridging and routing protocols) to detect broken topologies
> and tell the user about them in a meaningful way. In other words,
> instead of "support" arbitrary topologies, "diagnose" unsupported
> topologies.
>
>      Brian
> _______________________________________________
> homenet mailing list
> homenet <at> ietf.org
> https://www.ietf.org/mailman/listinfo/homenet
>

--

-- 
Stephen [kiwin] Palm   Ph.D.                          E:  palm <at> kiwin.com
Senior Technical Director                             T: +1-949-926-PALM
Broadcom Broadband Communications Group               F: +1-949-926-7256
Irvine, California                               W: http://www.kiwin.com
Secondary email accounts:  stephenpalm <at> alumni.uci.edu  palm <at> broadcom.com
s.palm <at> ieee.org  palm <at> itu.ch  spalm <at> cs.cmu.edu  palm <at> ics.t.u-tokyo.ac.jp