[arin-discuss] use of 128.66.0.0/16 not clear
Scott Leibrand
scottleibrand at gmail.com
Wed Sep 23 09:58:33 EDT 2009
I know a couple folks who do volunteer network setup for Interop
shows, and I know they do still use this space then. Not sure what
it's used for in between shows, and no idea how much less space they
could get away with if needed...
-Scott
On Sep 23, 2009, at 8:52 AM, Jason Schiller <schiller at uu.net> wrote:
> On Tue, 22 Sep 2009, David Farmer wrote:
>
>> The only thing I can find in whois now;
>>
>> OrgName: Interop Show Network
>> OrgID: ISN-4
>> Address: 600 Harrison St
>> City: San Francisco
>> StateProv: CA
>> PostalCode: 94107
>> Country: US
>>
>> NetRange: 128.64.0.0 - 128.64.255.255
>> CIDR: 128.64.0.0/16
>> NetName: SHOWNETB3
>> NetHandle: NET-128-64-0-0-1
>> Parent: NET-128-0-0-0-0
>> NetType: Direct Assignment
>> NameServer: DNS.INTEROP.NET
>> NameServer: SOLARIS.CC.VT.EDU
>> Comment:
>> RegDate: 1991-09-18
>> Updated: 2003-03-06
>>
>> Maybe we can get this returned too?
>
> Looks to me like this space is in use Orignated from:
> 209 - Qwest
> 11192, 10949 - Smart City
> 21882 - Priority Networks
>
> It is possible that Interop Show Network gets transit from Qwest,
> and has
> some sort of customer relationship with Priority Networks and Smart
> City
> who both provide Internet access to hotels and confrence sites. It is
> even possible that Interop Show Network became a corporation and
> spun off
> into both Priority Networks and Smart City.
>
> If you have information that this space is either not being used, or
> has
> been hi-jacked then you should provide that information to ARIN so
> they
> can investigate...
>
> __Jason
>
>
> show route 128.64.0.0/16
> inet.0:
> + = Active Route, - = Last Active, * = Both
>
> 128.64.0.0/24 *[BGP/170] 7w0d 08:06:43, MED 10, localpref 100,
> from
> AS path: 209 I
> 128.64.1.0/24 *[BGP/170] 7w0d 08:06:43, MED 10, localpref 100,
> from
> AS path: 209 I
> 128.64.2.0/24 *[BGP/170] 7w0d 08:06:43, MED 10, localpref 100,
> from
> AS path: 209 I
> 128.64.128.0/22 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> [BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.132.0/23 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> [BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.134.0/24 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> [BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.135.0/24 *[BGP/170] 9w0d 09:23:14, MED 10, localpref 100,
> from
> AS path: 1239 21882 I
> 128.64.136.0/24 *[BGP/170] 9w0d 09:23:14, MED 10, localpref 100,
> from
> AS path: 1239 21882 I
> 128.64.139.0/24 *[BGP/170] 1d 03:51:44, MED 10, localpref 100, from
> AS path: 174 10949 I
> 128.64.142.0/24 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> [BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.146.0/23 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.156.0/24 *[BGP/170] 1w3d 17:03:19, MED 10, localpref 100,
> from
> AS path: 3549 21882 I
> 128.64.162.0/24 *[BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> [BGP/170] 22w6d 08:28:41, MED 0, localpref 100,
> from
> AS path: 23005 11192 I
> 128.64.163.0/24 *[BGP/170] 1d 03:51:44, MED 10, localpref 100, from
> AS path: 174 10949 I
> 128.64.172.0/24 *[BGP/170] 1w5d 06:06:55, MED 10, localpref 100,
> from
> AS path: 3549 21882 I
> 128.64.175.0/24 *[BGP/170] 9w0d 09:23:14, MED 10, localpref 100,
> from
> AS path: 1239 21882 I
> 128.64.176.0/23 *[BGP/170] 1w5d 00:20:33, MED 10, localpref 100,
> from
> AS path: 3549 22822 21882 ?
> 128.64.180.0/24 *[BGP/170] 1w5d 06:06:55, MED 10, localpref 100,
> from
> AS path: 3549 21882 I
> 128.64.192.0/22 *[BGP/170] 1w5d 00:20:33, MED 10, localpref 100,
> from
> AS path: 3549 22822 21882 ?
> 128.64.196.0/24 *[BGP/170] 1w3d 16:14:00, MED 10, localpref 100,
> from
> AS path: 3549 21882 I
> 128.64.211.0/24 *[BGP/170] 9w0d 09:23:14, MED 10, localpref 100,
> from
> AS path: 1239 21882 I
> 128.64.220.0/24 *[BGP/170] 1w5d 06:06:55, MED 10, localpref 100,
> from
> AS path: 3549 21882 I
>
>
>>
>> So we are talking about maybe re-aggregating a whole /12 if
>> 128.64.0.0/16 and 128.66.0.0/16 were returned to IANA and put in the
>> free pool. A /12 is going to become a very globally significant
>> chunk
>> of IP space very soon now.
>>
>> So I take back my initial reaction and believe that Owen is right,
>> document that 128.66.0.0/16 is no longer considered a test network,
>> raise the word far and wide don't filter 128.66.0.0. Then recover
>> it.
>>
>> Further, should Interop be asked to return 128.64.0.0/16?
>>
>> It should be done very politely, with the utmost diplomacy, if it is
>> asked at all. But, should it be asked? If, so Who? and, How?
>>
>
>
> _______________________________________________
> ARIN-Discuss
> You are receiving this message because you are subscribed to
> the ARIN Discussion Mailing List (ARIN-discuss at arin.net).
> Unsubscribe or manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/arin-discuss
> Please contact info at arin.net if you experience any issues.
More information about the ARIN-discuss
mailing list