In message <[email protected]> Jim Gettys writes: > On 10/13/2011 02:42 PM, Curtis Villamizar wrote: > > > > Yes and there are/were ATM switches that implement RFC1577, LANE, > > MPOA, and NHRP. None of that worked very well and it all is > > essentially abandoned work now. Pre-existence alone is not a worth > > while evaluation criteria. > > > > If zOSPF works perfectly, including in the presence of legacy routers > > which don't look at a new 48 bit mac address router-id extension, we > > have no reason to continue the discussion. We just indicate "use > > zOSPF" and we're done. > > > > There seems to be consensus that we're not done. > > > On my part, I'm interested in understanding the following: > o scaling properties: I worry about the apartment building case, and > related dense mesh case.
Yep. OSPF as is may not be appropriate for wireless mesh. WG needs to consider this. > o behaviour when routing both wired and wireless networks. > o multicast behaviour and impact on wireless networks. > o running code Running code is too seldom available when the IETF rushes forward these days. A reference implementation would be great. I know which code base you have in mind. > And I'll ask the same about any other routing protocol you wish to > name. I'm an equal opportunity parade rainer... > - Jim I haven't checked cerowrt to see how much configuration is required of OSPF. If it is quagga, then a router-id has to be configured and each interface has to have OSPF explicitly enabled all with a Cisco style line oriented config. Curtis _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
