Re: SIP Addressing Limitations

[Dennis Ferguson <[e-mail]>]

>> From where would you allocate space for a provider that
>> doesn't fall under one of the clusters?  For instance,
>> a provider that has direct customers in the Northeastern
>> USA and the far east (Singapore and Korea, say)?
>>
[...]
> Finally, I don't think the IANA would spend much time considering such a
> provider.  Since it has a private trans-continental link, and a private
> trans-oceanic link (or a very very long trans-oceanic link around the
> Cape, or a very long multi-satellite path), it will be priced far in
> excess of the costs of its competitors.  It will not receive funding
> from any but the most foolish investors, and have none but the most
> foolish customers.  It will fail in the marketplace.
>
> Why are we wasting our time with theoretical examples of providers that
> aren't connected to the internet?
>
> [e-mail]

Somehow your response leaves me feeling a bit uncomfortable.  I would
point out that the current path from places in Thailand to places in
Singapore appears to pass through Virginia and New Jersey, e.g.

% traceroute -g gateway.chula.ac.th. solomon.technet.sg.
traceroute to solomon.technet.sg (192.169.33.3), 30 hops max, 40 byte packets
 1  en-0.ans-gw.ans.net (147.225.1.1)  6 ms  5 ms  4 ms
 2  en-0.enss160.t3.ans.net (192.77.154.2)  8 ms  3 ms  5 ms
 3  t1-2.New-York-cnss35.t3.ans.net (140.222.35.4)  6 ms  8 ms  8 ms
 4  t3-3.New-York-cnss33.t3.ans.net (140.222.33.4)  6 ms  11 ms  8 ms
 5  t3-3.New-York-cnss32.t3.ans.net (140.222.32.4)  6 ms  9 ms  8 ms
 6  t3-1.Washington-DC-cnss56.t3.ans.net (140.222.56.2)  13 ms  13 ms  13 ms
 7  t3-0.Washington-DC-cnss58.t3.ans.net (140.222.58.1)  14 ms  13 ms  13 ms
 8  t3-0.enss136.t3.ans.net (140.222.136.1)  14 ms  13 ms  14 ms
 9  College-Park.MD.ALTER.NET (192.41.177.249)  15 ms  15 ms  16 ms
10  Falls-Church1.VA.ALTER.NET (137.39.11.1)  18 ms  18 ms  16 ms
11  NetBlazer1.Falls-Church.VA.ALTER.NET (137.39.1.10)  19 ms  21 ms  19 ms
12  gateway.chula.ac.th (192.133.10.2)  900 ms  859 ms  877 ms
13  NetBlazer1.Falls-Church.VA.ALTER.NET (137.39.1.10)  918 ms  913 ms  899 ms
14  Falls-Church1.VA.ALTER.NET (137.39.1.1)  896 ms  908 ms  902 ms
15  College-Park.MD.ALTER.NET (137.39.11.2)  900 ms  925 ms  893 ms
16  en-0.ENSS136.t3.ANS.NET (192.41.177.253)  909 ms  894 ms  887 ms
17  t3-1.Washington-DC-cnss58.t3.ans.net (140.222.58.2)  897 ms  1038 ms  918 ms
18  t3-3.Washington-DC-cnss56.t3.ans.net (140.222.56.4)  908 ms  889 ms  887 ms
19  t3-0.New-York-cnss32.t3.ans.net (140.222.32.1)  897 ms  903 ms  906 ms
20  t3-0.New-York-cnss33.t3.ans.net (140.222.33.1)  912 ms  893 ms  897 ms
21  t3-0.enss137.t3.ans.net (140.222.137.1)  947 ms  955 ms  897 ms
22  trillian-gateway.jvnc.net (192.12.211.75)  903 ms  919 ms  896 ms
23  192.169.41.41 (192.169.41.41)  1590 ms  1579 ms  1569 ms
24  solomon.technet.sg (192.169.33.3)  1596 ms  1570 ms  1569 ms

I can hardly wait to see where the packets go when people in Myanmar,
or Viet Nam, decide they'd be best served by dealing with a European
provider.

Dennis Ferguson