> So what I want to see is a proposal for a routing protocol that specify link > metrics for a set of commonly used link types in homes. This spec could be > BCP.
Does it need to be a routing protocol? Just to throw another possible protocol into the mix being tossed around (like we don't have enough), I'd like to suggest that a non-routing protocol be considered for topology discovery and sharing of link metrics. Specifically, IEEE 1905.1a could help with this. It can provide L1 and L2 topology info with link metrics, and identify intervening bridges that support LLDP for IEEE 802.1 bridge discovery. I wouldn't want individual devices all doing their own 1905 topology discovery -- that's too chatty. But if the all the homenet routers did, and then advertised a "service" (DNS-SD) that provided a link to a router-provider HTML page with the topology and metric info the router can discover provided in a standardized XML or JSON syntax, then everything who can discover that service (on each router) would have access to this info. Applications could also make use of this info to do intelligent source address selection in a multi-WAN-interface netw ork, because routers could report on the speed of their WAN connections, as well. Just a thought. I've been working on trying to get myself to write a contribution describing the idea of the router-provided info service for a while now. Barbara _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
