Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Juliusz Chroboczek
> So even though link-local multicast may be part of the IPv6 base spec, > it may be desirable to avoid use of multicast traffic where > possible. e.g. a routing protocol could perform initial neighbor > discovery using multicast, but then switch to unicast when maintaining > individual neighbor as

Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Ray Hunter
Juliusz Chroboczek 14 June 2014 16:25 Is a specific update address preferred? [my view] The routing protocol should support both use of unicast and multicast updates. Please clarify. Are you saying that the routing protocol must be able to run over lin

Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Juliusz Chroboczek
> Is a specific update address preferred? > [my view] The routing protocol should support both use of unicast and > multicast updates. Please clarify. Are you saying that the routing protocol must be able to run over link layers that don't support link-local multicast? AFAIK, link-local multic

Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Ted Lemon
That's really helpful, Ray. Thanks! (I don't know the answers to those questions, but they're just the sort of questions I wouldn't have thought to ask, which is why I tossed this back to the working group.) ___ homenet mailing list homenet@ietf.org

Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Ray Hunter
Tim Chown wrote: On 13 Jun 2014, at 14:57, Ted Lemon > wrote: On Jun 13, 2014, at 9:48 AM, Lorenzo Colitti > 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 shou

Re: [homenet] Updates to Homenet Architecture Principles doc

2014-06-14 Thread Mark Townsley
On Jun 13, 2014, at 10:44 PM, Ted Lemon wrote: > On Jun 13, 2014, at 4:27 PM, Brian E Carpenter > wrote: >> It's prototype implementations and early deployments that will >> tell us the right answer, not further debate. > > Again, I didn't ask for "the answer." I asked for a description of