>>>>> "Acee" == Acee Lindem <[email protected]> writes: >> The problem with zOSPF is that it doesn't meet our requirements. >> It doesn't detect borders (unless the border happens to have >> another zOSPF router with the wrong password),
Acee> While this should be part of the solution, I don't see this as
Acee> something that it necessarily should be built into the routing
Acee> protocol.
>> it requires configuration (for the password),
Acee> How does any protocol do authentication w/o a shared key? If
Acee> you don't do authentication, you don't need a key.
Yes, this is a general problem, which is why I keep asking what are our
real requirements here.
>> it doesn't handle walled gardens (a requirement being debated),
Acee> I don't fully understand this requirement and how it would be
Acee> handled w/o configuration.
I don't understand this criticism. Why are walled gardens different
than multiple ISPs?
>> it's not lightweight.
Acee> A commercial router implementation supporting all the features
Acee> including OSPF TE and VPNs is certainly not
Acee> lightweight. However, I just downloaded the latest quagga
Acee> suite and it is only about 21K there.
rtr3-[/usr/pkg/sbin] mcr 10007 %size ospf6d /usr/pkg/lib/libzebra.so.0
text data bss dec hex filename
221476 11328 3132 235936 399a0 ospf6d
272449 23848 3120 299417 49199 /usr/pkg/lib/libzebra.so.0
No all of libzebra might really be used. So 11K code, plus up to 23K.
I think that half of the code can be ripped out (and I wish I had time
to do).
--
] He who is tired of Weird Al is tired of life! | firewalls [
] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[
] [email protected] http://www.sandelman.ottawa.on.ca/ |device driver[
Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE>
then sign the petition.
pgp4UAORgHSY9.pgp
Description: PGP signature
_______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
