while I agree that the hierarchical and distributed nature of the DNS is a scintillating, shimmering attractant, it is wise to be aware of the baseline assumption in your arguement, e.g. that a client will -ALWAYS- ask an authoritative source... The DNS is so designed that caching is a huge component of the scalability of the DNS... and its greatest hinderance for such ideas as are laid out in the ENUM dip lookup. You can't be assured that the data is timely. This is a strong reason to consider that the DNS is _NOT_ the droid you are looking for, in spite of its other attractive qualities. just my 0.02 lira. --bill On 20October2010Wednesday, at 12:25, Richard Shockey wrote: > > And finally, regarding: > > "It is unclear why this data is better maintained by the DNS > than in an unrelated application protocol." > > If a device is performing an ENUM dip hoping to find a contactable SIP URI, > it is simply most efficient for the ENUM response to directly include the > Send-N metadata when needed rather than have separate queries using a > different network protocol. Also, the hierarchical and distributed nature > of the DNS protocol makes it an _ideal_ structural fit for this meta data. > > I believe the onus should be on your draft to explicitly identify valid > technical reasons why the DNS protocol should _not_ be used, rather than > make vague hand-waving assertions which appear to have little or no > justification. > > > > RS> Precisely, What is unclear is why the IETF and the IAB is suddenly > trying to block a perfectly legitimate extension of RFC 3761 that is in > various forms of global deployment, proven to work, scale and more > importantly provides a valuable and essential function in the transition > from analog POTS to SIP based communication. > > Just saying no is not a solution to the real issues of number translation in > carrier networks. > > Ok a lot of people hate phone numbers including, it seems, 50% of RAI > directorate but they are not going away anytime soon. > > So just say it .. is this the message? Don't even try to charter E2MD? > > _______________________________________________ > Ietf mailing list > Ietf@xxxxxxxx > https://www.ietf.org/mailman/listinfo/ietf _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf