In line > I agree that something along the lines of enum could solve this > problem, > and I believe there was a draft that proposed such a thing. This has > been discussed since the start of rfc4474. > > However, I fear that saying, 'use enum' is kind of like saying, we'll > just use an All-Knowing Oracle, so lets figure out the interface > protocol to the Oracle.
Yea and lets end world hunger while we're at it ... The easy part is the interface (the enum > mechanism). The actual hard problem is how to get those entries > populated. The deployment of public enum has been - shall we say - > less than spectacular. "less than spectacular .." now there is an understatement, if there ever was one. Though private non DNS visible enum systems are going like gangbusters as TCAP/SS7 replacements all over the place. I find this entire discussion somewhat hilarious, almost side splitting, considering what some us had to go through to get A. get public ENUM defined B. then see what happened with delegations in the e164.arpa domain in the intervening 6 years or so. The very idea that there is going to be some consensus on who "owns" a phone number, much less a deployable system considering the various competing interests here is a complete fantasy. I'd hate for that to be our only solution. Not that > its obvious what else to do; though I do suggest in my draft how > domain > based authentication, when combined with whitelists and blacklists, > can > help. > > -Jonathan R. > _______________________________________________ Sip mailing list http://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
