Re: [Enum] RFC1530 (TPC.INT)

At 06:44 PM 2/22/2001 -0500, Stephane Alnet wrote:
>Hi,
>
>The recent discussion on Designated vs Competitive models reminded me that 
>there's already a E.164-like hierarchy around there, tpc.int [RFC1530]: 
>"The primary purpose of the tpc.int subdomain is to provide transparent 
>mapping between the Internet and telephony environments".
>
>It doesn't provide provisions for ENUM itself but that doesn't seem to be 
>a problem. Has there already been any discussions on re-using that 
>hierarchy (which already has its own policies)?

TPC.INT is not used by many folks for numerous reasons and as such is 
useless model for ENUM specifically..though nearly all of its technicial 
principals for reverse concatenation of the numbers into a single 
"protected" domain derive from it.

TPC.INT was a useful experiment ..nothing more.

>S.

 >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Richard Shockey, Senior Technical Industry Liaison
NeuStar Inc.
1120 Vermont Avenue N.W., Suite 550, Washington DC. 20005
Voice: 202.533.2811,  Cell : 314.503.0640,  Fax: 815.333.1237
<mailto: rshockey@ix.netcom.com> or
<mailto: rich.shockey@neustar.com>
<http://www.neustar.com>
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

_______________________________________________
enum mailing list
enum@ietf.org
http://www1.ietf.org/mailman/listinfo/enum