Re: Sad IPv4 story?

2011-12-17 Thread Roland Perry
In article <4ee6e7d2.8060...@bogus.com>, Joel jaeggli writes So now we will reap the consequences and it will be at the cost of new market entrants (which I am sure will please some people) and perhaps cold hard cash for those who cannot expand their business or have to 'buy' address space. Ne

Re: local_preference for transit traffic?

2011-12-17 Thread Adam Rothschild
I've had similar experiences to Mr. Petach. Depending on order of operations, you can look at this from a different prospective as well -- why go with a soulless entity for your transit (or transport, collocation, ...) requirements, when you can "keep it in the family" and engage a peer who alread

Re: Wireless/Free Space Enterprise ISP in Palo Alto

2011-12-17 Thread Joel jaeggli
I haven't done wireless in downtown palo alto, only metro-e however. Given your proximity to 345 hamilton (under 1000 feet most likely) I would think at&t would be in a position to offer fairly high-rate dsl, On 12/16/11 10:24 , Darren Bolding wrote: > Apologies if this is not the most appropriat

Re: local_preference for transit traffic?

2011-12-17 Thread Joel jaeggli
On 12/17/11 00:14 , Mark Tinka wrote: > On Friday, December 16, 2011 05:02:33 AM Joe Malcolm wrote: > >> Once upon a time, UUNET did the opposite by setting >> origin to unknown for peer routes, in an attempt to >> prefer customer routes over peer routes. We moved to >> local preference shortly th

Re: local_preference for transit traffic?

2011-12-17 Thread Matthew Petach
On Sat, Dec 17, 2011 at 12:14 AM, Mark Tinka wrote: > On Friday, December 16, 2011 05:02:33 AM Joe Malcolm wrote: > >> Once upon a time, UUNET did the opposite by setting >> origin to unknown for peer routes, in an attempt to >> prefer customer routes over peer routes. We moved to >> local prefere

Re: local_preference for transit traffic?

2011-12-17 Thread Mark Tinka
On Friday, December 16, 2011 05:02:33 AM Joe Malcolm wrote: > Once upon a time, UUNET did the opposite by setting > origin to unknown for peer routes, in an attempt to > prefer customer routes over peer routes. We moved to > local preference shortly thereafter as it became clear > this was "changi