[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Need for working ENUM [was Re: Welcome! ]
Just a quick response to Paul (sorry for the manufactured info but I was not
subscribed to the list until just now).
----------Attributed to Paul Vixie----------
i happen to agree about SIP, simply because that's what we use internally.
but, i'd hate to find myself in the middle of a war about it. is the choice
of SIP noncontroversial? or do we need two enum-like trees, one for each
protocol? or does the NAPTR/SRV model naturally support both such that if
you find that the other end only speaks a protocol you don't speak, you can
just treat it as "no ENUM found, goto TDM"?
---------End Paul Attribution----------------
E164.org allows a variety of mappings, SIP/IAX to name two. The idea is
pretty neat but may have some problems scaling. You can maintain one ENUM
tree but you would have incompatible client issues in certain situations
(IAX to SIP for example).
To unsubscribe send a message to firstname.lastname@example.org with
the word 'unsubscribe' in a single line as the message text body.
An archive is at <http://psg.com/lists/voip-peering/>.