[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Welcome!
At 03:11 PM 5/17/2004, Paul Vixie wrote:
...snip...
i'd like to be able to reach the rest of the SIP-reachable world without
using TDM as my fabric. ITU won't allow that to happen until they're
sure they've re-monetized it in ways beneficial to their members.
reinventing TPC.INT wasn't precisely on my list of things to accomplish,
i just want a richer set of TDM bypass information without waiting for ITU.
FWIW, it isn't necessarily the ITU-T that is holding up deployment of
e164.arpa.
The IAB selected RIPE NCC to operate e164.arpa. The instructions it gave
RIPE NCC for delegation under e164.arpa. can be found at:
http://www.ripe.net/enum/instructions.html
As can be seen there, the IAB instructions allow the ITU-T to screen
requests for delegation of Country Codes. The procedures ITU-T currently
follows can be found at: http://www.itu.int/ITU-T/inr/enum/. In short, the
ITU-T TSB notifies the Member State representative of the request and lets
the State decide.
So in effect, each country (or group of countries) decides what to do in
terms of delegating its Country Code. Country Codes and phone numbers are
viewed as National Resources by most countries.
So while IAB could have provided different instructions, not including
ITU-T, it would have then had to be the one that vetted requests for
Country Code delegations and I don't think it wanted to be involved in a
political process like that.
And the ITU-T (as an inter-governmental organization) doesn't really have a
choice as to how it vets potential delegations other than to defer to the
Member States.
BTW, 1.e164.arpa (NANP) has its own problems since it encompasses multiple
(18) countries.
Chip
---------------------------------------------------
Chip Sharp Consulting Engineering
Cisco Systems
tel:+1.919.392.3121
---------------------------------------------------
--
To unsubscribe send a message to voip-peering-request@psg.com with
the word 'unsubscribe' in a single line as the message text body.
An archive is at <http://psg.com/lists/voip-peering/>.