-----Original Message----- From: Juliusz Chroboczek [mailto:j...@pps.univ-paris-diderot.fr] Sent: Tuesday, July 28, 2015 5:08 AM To: Hemant Singh (shemant) Cc: HOMENET Subject: Re: [homenet] Moving forward.
>Yes, I have. On one router this is easy. You obviously need two routers in >order to create a loop. Then why do multiple routers work with ISIS is many network topologies including mesh? ISIS works dandy in a RBridged TRILL network as well. No mature routing protocol will re-inject a route received on an interface back out the same interface for a route included in a routing update. Such rules are actually included in ISIS routing. Any other routing developed for a commercial grade routing does follow the same rule. Would you like me to send you a configuration with ISIS MT (ipv4 and ipv6) with RIPng on a Cisco router with no redistribution nuance configured? As others have said, we could work out a managed IPv6 CE router for its homenet properties in CableLabs. More testing is needed with new routing protocols such as Babel for tests such as routing loops, link up/down detection time, debugging support, etc. Do also deploy a test network Babel in the enterprise for more testing. I always want to abstract new routing or disparate routing links (lossy vs. not) in a separate routed domain to narrow down issues faster. I am not for any one routing protocol. Use what the consensus gets to. Hemant _______________________________________________ homenet mailing list homenet@ietf.org https://www.ietf.org/mailman/listinfo/homenet