% How is the number of the routing entries going to be decreased % with transport level solution? % % I can clearly see that multihoming is be solved but not the % primary goal of scalability. Any thoughts?
At present, most of the scalability issue with the routing system is CREATED by the extra more-specific prefixes that are carried in the DFZ to enable site multii-homing.[1] So any multi-homing approach that does NOT require those more-specific prefixes to continue within the DFZ *greatly* improves the scalability of the DFZ routing system. So a transport-based approach, which you agree can solve the multi-homing issue, obviously therefore CAN greatly improve the scalability of the deploying routing system. Separately, the Routing RG charter does not list "scalability" as THE primary goal. Instead, the charter is clear that there are several equally weighted goals, including but not limited to scalability and multi-homing. For example, the charter lists "mobility" as a goal equal with those first two. Yours, Ran Atkinson [EMAIL PROTECTED] [1] There are some other reasons that a few of the more specific prefixes might exist. However, published analyses of the actual routing tables indicate those other reasons are NOT a major source of DFZ RIB/FIB entropy at present. -- to unsubscribe send a message to [EMAIL PROTECTED] with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/rrg/> & ftp://psg.com/pub/lists/rrg
