Hi Kirk, On 08/24/2010 07:43 PM, Kirk Wolff wrote: > The first problem is the GPA; it prevents mapping of the system. There
Mapping? How do you mean. I or one would be extremely hesitant to even consider federated mapping, if only because the end user will have severe trouble keeping track of all the different networks. This is precisely why E164 exists. Keep your numberingspace consistent, regardless of the dialling network. > If a node doesn't fix its failed connections in a reasonable number of > failed attempt reports or number of days then that node would be > blacklisted automatically. It would be more fair if the maintainer were > notified of failed connections through email. 'More fair' is unfortunately not the key issue for a publicly used federation. In general, customers rely on the fact that if they dial a number it will consistently connect to the proper destination. If this is negatively impacted in any way, my consideration as a telco is not wether or not the blacklist is fair to the receiving end. I only have my customers to answer to, and I want the misbehaving party disconnected immediately. > Thirdly, it seems to me that DUNDi requires too much structure. Its > apparent that it must be organized in a top-down methodology. One should > be able to attach to a cloud by way of a key or password, but not be > constrained to a single node. At present each connection requires This is a faulty observation. It is absolutely possible to connect to multiple nodes and perform the discovery over multiple nodes in order to improve resilience of the number discovery function. However, because there is a practical limit (increasing post dial delay) in the amount of hops traversed during discovery, it makes sense (optimisation-wise) to connect at a semi-geographic oriented Tier1/Tier2/Tier3 structure. At two to five nodes, probably. Your security ideas are obviously possible, but I don't really see the point in that. Connecting to more than, say, 10 nodes doesn't really make sense, and adding/removing nodes is not a day-to-day task. With that in mind, manual connection with individual keys should not be that big an issue. To reflect: Do you do BGP peering with anyone? Would you want anyone (without scrutiny!) to be able to broadcast AS-numbers into your routing table? My $0.01 -- Met vriendelijke groet, Florian Overkamp SpeakUp BV T: 088-SPEAKUP (088-7732587) T: 053-4305842 -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- Dundi mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/dundi
