RE: Power issue at Telx NYC?
Drew, There is definitely a power outage at telx/60 Hudson. According to telx, this was a scheduled maintenance gone bad. I have someone onsite and he is reporting that power should be restored shortly. Note, those with redundant feeds within the facility should only see a partial outage. Regards, Randy > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Drew Linsalata > Sent: Saturday, December 02, 2006 1:09 AM > To: nanog@merit.edu > Subject: Power issue at Telx NYC? > > > > One of our transits is reporting a power outage at Telx in NYC tonight. > Does anyone else have any reports of a power problem in that facility? > We're trying to get some word from Telx now too, but they're slow to > respond. > > > > >
Re: EveryDNS.net down?
Thanks to netops at: nLayer, Cogent, HE for working tirelessly to help mitigate this. No thanks to Level(3) despite the best intentions of one sec-ops person (Richard). -david Nate Carlson wrote: On Fri, 1 Dec 2006, david raistrick wrote: got off the phone with davidu just a second ago. DoS. they're working on it,. Yeah, that's the only thing I'd really expect to take them down. Thanks much for the confirmation! | nate carlson | [EMAIL PROTECTED] | http://www.natecarlson.com | | depriving some poor village of its idiot since 1981|
Power issue at Telx NYC?
One of our transits is reporting a power outage at Telx in NYC tonight. Does anyone else have any reports of a power problem in that facility? We're trying to get some word from Telx now too, but they're slow to respond.
Re: EveryDNS.net down?
On Fri, 1 Dec 2006, david raistrick wrote: got off the phone with davidu just a second ago. DoS. they're working on it,. Yeah, that's the only thing I'd really expect to take them down. Thanks much for the confirmation! | nate carlson | [EMAIL PROTECTED] | http://www.natecarlson.com | | depriving some poor village of its idiot since 1981|
Re: EveryDNS.net down?
On Fri, 1 Dec 2006, Nate Carlson wrote: Anyone here know someone who works on EveryDNS.net? None of their four DNS servers are responding for me from multiple locations; I'm guessing a wide-spread DoS? got off the phone with davidu just a second ago. DoS. they're working on it,. --- david raistrickhttp://www.netmeister.org/news/learn2quote.html [EMAIL PROTECTED] http://www.expita.com/nomime.html
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 01 Dec 2006 17:04:38 GMT, "Chris L. Morrow" said: > On Fri, 1 Dec 2006, Florian Weimer wrote: > > Routers on stub ASs don't need upgrading at all, for instance. > > but filter lists and such I imagine might :( But the industry *did* learn its lesson with 69/8, didn't it? pgpLarx6YnAUy.pgp Description: PGP signature
EveryDNS.net down?
Anyone here know someone who works on EveryDNS.net? None of their four DNS servers are responding for me from multiple locations; I'm guessing a wide-spread DoS? The phone number in their whois record does not work. :( | nate carlson | [EMAIL PROTECTED] | http://www.natecarlson.com | | depriving some poor village of its idiot since 1981|
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, Dec 01, 2006 at 09:49:25PM +0200, Petri Helenius wrote: > > Etaoin Shrdlu wrote: > > > > > >This is an excellent idea, but please do not select the first block > >after 16 bit numbers are up (can you say buffer overflow?). Something > >random, in the middle, would be better. > > > 2752512-2818047 ? 0x2A - 0x2A, IOW ? [Just for those who were curious why those numbers but not curious enough to actually check.] -- Joe Yao --- This message is not an official statement of OSIS Center policies.
Re: The IESG Approved the Expansion of the AS Number Registry
Etaoin Shrdlu wrote: This is an excellent idea, but please do not select the first block after 16 bit numbers are up (can you say buffer overflow?). Something random, in the middle, would be better. 2752512-2818047 ? Pete
Re: The IESG Approved the Expansion of the AS Number Registry
Roland Dobbins wrote: On Dec 1, 2006, at 4:50 AM, Andy Davidson wrote: RIPE will be accepting requests for 32-bit ASNs from 1/1/07, according to an email to ncc-services two weeks ago. Is there any possibility we can now get a block of ASNs set aside for documentation purposes, akin to example.com and/or the TEST network? A block of ASNs for this purpose would be very helpful for folks writing docs, would reduce the possibility of 'cut-and-paste hijacking', and would also allow more accurate documentation (many products and tools have special handling for the designated private ASNs which make documentation difficult). This is an excellent idea, but please do not select the first block after 16 bit numbers are up (can you say buffer overflow?). Something random, in the middle, would be better. -- The weaker the data available upon which to base one's conclusion, the greater the precision which should be quoted in order to give the data authenticity. Norman Augustine
Re: The IESG Approved the Expansion of the AS Number Registry
On Dec 1, 2006, at 4:50 AM, Andy Davidson wrote: RIPE will be accepting requests for 32-bit ASNs from 1/1/07, according to an email to ncc-services two weeks ago. It does not feel too early to start to understand what we must do to as a community to guarantee ubiquity of reachable networks. Is there any possibility we can now get a block of ASNs set aside for documentation purposes, akin to example.com and/or the TEST network? A block of ASNs for this purpose would be very helpful for folks writing docs, would reduce the possibility of 'cut-and-paste hijacking', and would also allow more accurate documentation (many products and tools have special handling for the designated private ASNs which make documentation difficult). --- Roland Dobbins <[EMAIL PROTECTED]> // 408.527.6376 voice All battles are perpetual. -- Milton Friedman
Re: The IESG Approved the Expansion of the AS Number Registry
agreed, let's NOT do the v6 thing... do the 32-bit asn's give us more than just 'more bits' ? :) (Sorry, I couldn't resist). So, yes, let's get someone to start testing, I'd just caution on assigning the 32-bit asn's for real-users, since much of the net might not be able to use them, partial reachability will/could-be a problem. The good news is that 32 bit ASN's won't be assigned by default until 2009. Starting on January 1, 32 bit ASN's will be assigned- but only to those people explicitly requesting them. All in all it seems like a sensible migration strategy. -Don
Weekly Routing Table Report
This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. Daily listings are sent to [EMAIL PROTECTED] For historical data, please see http://thyme.apnic.net. If you have any comments please contact Philip Smith <[EMAIL PROTECTED]>. Routing Table Report 04:00 +10GMT Sat 02 Dec, 2006 Analysis Summary BGP routing table entries examined: 205332 Prefixes after maximum aggregation: 111319 Unique aggregates announced to Internet: 100277 Total ASes present in the Internet Routing Table: 23820 Origin-only ASes present in the Internet Routing Table: 20760 Origin ASes announcing only one prefix: 10013 Transit ASes present in the Internet Routing Table:3060 Transit-only ASes present in the Internet Routing Table: 77 Average AS path length visible in the Internet Routing Table: 3.6 Max AS path length visible: 29 Max AS path prepend of ASN (36728) 27 Prefixes from unregistered ASNs in the Routing Table: 1 Unregistered ASNs in the Routing Table: 2 Special use prefixes present in the Routing Table:0 Prefixes being announced from unallocated address space: 9 Number of addresses announced to Internet: 1642195372 Equivalent to 97 /8s, 225 /16s and 233 /24s Percentage of available address space announced: 44.3 Percentage of allocated address space announced: 62.9 Percentage of available address space allocated: 70.5 Total number of prefixes smaller than registry allocations: 104338 APNIC Region Analysis Summary - Prefixes being announced by APNIC Region ASes:45512 Total APNIC prefixes after maximum aggregation: 18619 Prefixes being announced from the APNIC address blocks: 43077 Unique aggregates announced from the APNIC address blocks:19414 APNIC Region origin ASes present in the Internet Routing Table:2778 APNIC Region origin ASes announcing only one prefix:782 APNIC Region transit ASes present in the Internet Routing Table:411 Average APNIC Region AS path length visible:3.5 Max APNIC Region AS path length visible: 16 Number of APNIC addresses announced to Internet: 270775520 Equivalent to 16 /8s, 35 /16s and 180 /24s Percentage of available APNIC address space announced: 84.7 APNIC AS Blocks4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911 APNIC Address Blocks 58/7, 60/7, 121/8, 122/7, 124/7, 126/8, 202/7 210/7, 218/7, 220/7 and 222/8 ARIN Region Analysis Summary Prefixes being announced by ARIN Region ASes:101808 Total ARIN prefixes after maximum aggregation:60182 Prefixes being announced from the ARIN address blocks:74992 Unique aggregates announced from the ARIN address blocks: 28501 ARIN Region origin ASes present in the Internet Routing Table:11192 ARIN Region origin ASes announcing only one prefix:4257 ARIN Region transit ASes present in the Internet Routing Table:1029 Average ARIN Region AS path length visible: 3.3 Max ARIN Region AS path length visible: 29 Number of ARIN addresses announced to Internet: 311376640 Equivalent to 18 /8s, 143 /16s and 59 /24s Percentage of available ARIN address space announced: 68.7 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959 ARIN Address Blocks24/8, 63/8, 64/5, 72/6, 76/8, 96/6, 199/8, 204/6, 208/7 and 216/8 RIPE Region Analysis Summary Prefixes being announced by RIPE Region ASes: 42128 Total RIPE prefixes after maximum aggregation:27602 Prefixes being announced from the RIPE address blocks:38996 Unique aggregates announced from the RIPE address blocks: 26031 RIPE Region origin ASes present in the Internet Routing Table: 8851 RIPE Region origin ASes announcing only one prefix:4682 RIPE Region transit ASes present in
Re: The IESG Approved the Expansion of the AS Number Registry
On Dec 1, 2006, at 10:54 AM, Chris L. Morrow wrote: On Fri, 1 Dec 2006, Henk Uijterwaal wrote: Last time I spoke to them, the Juniper and Cisco versions only ran on a subset of their routers. Their claim was that almost nobody had asked for this so it doesn't have any priority. 'the power of the market place!' ... perhaps now is the time to call your local (Juniper|Cisco|Other) router vendor sales rep and ask? :) I've hit up my big 3 vendors... no response yet, but it is holiday season
Re: The IESG Approved the Expansion of the AS Number Registry
aren't there still plenty (+20k or so) 16-bit ASN's out there for assignment? (perhaps I'm missing something on the need to allocate the new asn's?) By all means let's wait until the last possible second to upgrade ASN support. The waiting approach has worked so well for IPV6 :) Seriously though- why not let people start registering now. The only way we'll know if 32 bit ASN's will work is if we start using them. agreed, let's NOT do the v6 thing... do the 32-bit asn's give us more than just 'more bits' ? :) (Sorry, I couldn't resist). So, yes, let's get someone to start testing, I'd just caution on assigning the 32-bit asn's for real-users, since much of the net might not be able to use them, partial reachability will/could-be a problem. Wouldn't this just mean (Since Jan 1 2007 hasn't come to pass yet) setting up a Quagga router and plugging it into your existing network? Seems to me that without real support for the existing operating systems... um, the old neighbor xxx.xxx.xxx.xxx remote-as [32bit ASN notation] would pretty much end the experiment. I can easily imagine setting up some test beds with multi-hop so people can test their implementation with real "talkers" -- lol, which is a lot like the way IPV6 is/was set up. If anyone wants to play with this, we'll do our part and set up an AS in the development space of 32bit-AS land and peer with anyone who wants to bang on it... DJ
Re: The IESG Approved the Expansion of the AS Number Registry
* Chris L. Morrow: >> | 6. Transition >> | >> |The scheme described in this document allows a gradual transition >> |from 2-octet AS numbers to 4-octet AS numbers. One can upgrade one >> |Autonomous System or one BGP speaker at a time. >> >> Routers on stub ASs don't need upgrading at all, for instance. > > but filter lists and such I imagine might :( Only if you want to keep your fine-grained filters, which shouldn't be a problem over the next few years. From a purely BGP 4 perspective, the transition looks like a new tier 1 ISP entering the stage. (But if more than one of your peers switch, you better upgrade as well.)
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 1 Dec 2006, Florian Weimer wrote: > * Chris L. Morrow: > > > So, all of the current devices need to get upgraded before 'day one' of > > 32-bit ASN use... that'll be fun :) > > | 6. Transition > | > |The scheme described in this document allows a gradual transition > |from 2-octet AS numbers to 4-octet AS numbers. One can upgrade one > |Autonomous System or one BGP speaker at a time. > > Routers on stub ASs don't need upgrading at all, for instance. but filter lists and such I imagine might :(
Re: The IESG Approved the Expansion of the AS Number Registry
* Chris L. Morrow: > So, all of the current devices need to get upgraded before 'day one' of > 32-bit ASN use... that'll be fun :) | 6. Transition | |The scheme described in this document allows a gradual transition |from 2-octet AS numbers to 4-octet AS numbers. One can upgrade one |Autonomous System or one BGP speaker at a time. Routers on stub ASs don't need upgrading at all, for instance.
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 1 Dec 2006, Donald Stahl wrote: > > So, all of the current devices need to get upgraded before 'day one' of > > 32-bit ASN use... that'll be fun :) Why is RIPE passing out the 32-bit > > ASN's now? > ARIN will begin passing out 32 bit ASN's to anyone who asks as of January > 1, 2007. This is the same policy as RIPE so I don't see what the big deal > is. Uhm, I think I mis-read the date on the original :( I thought they HAD been passing them out, not WILL BE :( need more coffee :( > > > aren't there still plenty (+20k or so) 16-bit ASN's out there > > for assignment? (perhaps I'm missing something on the need to allocate the > > new asn's?) > By all means let's wait until the last possible second to upgrade ASN > support. The waiting approach has worked so well for IPV6 :) Seriously > though- why not let people start registering now. The only way we'll know > if 32 bit ASN's will work is if we start using them. > agreed, let's NOT do the v6 thing... do the 32-bit asn's give us more than just 'more bits' ? :) (Sorry, I couldn't resist). So, yes, let's get someone to start testing, I'd just caution on assigning the 32-bit asn's for real-users, since much of the net might not be able to use them, partial reachability will/could-be a problem.
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 1 Dec 2006, Steven M. Bellovin wrote: > On Fri, 01 Dec 2006 16:02:55 + (GMT) > "Chris L. Morrow" <[EMAIL PROTECTED]> wrote: > > So, all of the current devices need to get upgraded before 'day one' > > of 32-bit ASN use... that'll be fun :) Why is RIPE passing out the > > 32-bit ASN's now? aren't there still plenty (+20k or so) 16-bit ASN's > > out there for assignment? (perhaps I'm missing something on the need > > to allocate the new asn's?) > > > Testing -- better to find out now what breaks, before we really need it. understood, but I took the 'RIPE has been assigning 32-bit ASN's since' to mean that people actually expected them to work.
Re: The IESG Approved the Expansion of the AS Number Registry
So, all of the current devices need to get upgraded before 'day one' of 32-bit ASN use... that'll be fun :) Why is RIPE passing out the 32-bit ASN's now? ARIN will begin passing out 32 bit ASN's to anyone who asks as of January 1, 2007. This is the same policy as RIPE so I don't see what the big deal is. aren't there still plenty (+20k or so) 16-bit ASN's out there for assignment? (perhaps I'm missing something on the need to allocate the new asn's?) By all means let's wait until the last possible second to upgrade ASN support. The waiting approach has worked so well for IPV6 :) Seriously though- why not let people start registering now. The only way we'll know if 32 bit ASN's will work is if we start using them. -Don
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 01 Dec 2006 16:02:55 + (GMT) "Chris L. Morrow" <[EMAIL PROTECTED]> wrote: > > > On Fri, 1 Dec 2006, Andy Davidson wrote: > > > > RIPE will be accepting requests for 32-bit ASNs from 1/1/07, > > according to an email to ncc-services two weeks ago. It does not > > feel too early to start to understand what we must do to as a > > community to guarantee ubiquity of reachable networks. > > So, all of the current devices need to get upgraded before 'day one' > of 32-bit ASN use... that'll be fun :) Why is RIPE passing out the > 32-bit ASN's now? aren't there still plenty (+20k or so) 16-bit ASN's > out there for assignment? (perhaps I'm missing something on the need > to allocate the new asn's?) > Testing -- better to find out now what breaks, before we really need it. --Steve Bellovin, http://www.cs.columbia.edu/~smb
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 1 Dec 2006, Andy Davidson wrote: > > RIPE will be accepting requests for 32-bit ASNs from 1/1/07, > according to an email to ncc-services two weeks ago. It does not > feel too early to start to understand what we must do to as a > community to guarantee ubiquity of reachable networks. So, all of the current devices need to get upgraded before 'day one' of 32-bit ASN use... that'll be fun :) Why is RIPE passing out the 32-bit ASN's now? aren't there still plenty (+20k or so) 16-bit ASN's out there for assignment? (perhaps I'm missing something on the need to allocate the new asn's?) > > There were no definitive answers when John Payne asked on the list > about images supporting 32 bit as numbers - are any independent > bodies going to setup a route behind a 32-bit ASN so that we can > start public reachability testing ? > Given a 32-bit ASN I'd be happy to upgrade code on a connected device and announce a route... of course I'm not sure my upstream will do the right thing with the announcement since it doesn't know (probably) about 32-bit asn's...
Re: The IESG Approved the Expansion of the AS Number Registry
On Fri, 1 Dec 2006, Henk Uijterwaal wrote: > > Last time I spoke to them, the Juniper and Cisco versions only ran on > a subset of their routers. Their claim was that almost nobody had > asked for this so it doesn't have any priority. 'the power of the market place!' ... perhaps now is the time to call your local (Juniper|Cisco|Other) router vendor sales rep and ask? :)
Re: Sprint BGP Outage for 11/28 and 11/29/06
On 12/1/06, Eric Gauthier <[EMAIL PROTECTED]> wrote: Audie, > Sprint technician informed us that there was a power outage in the Baltimore > site on 11/28/06 between 2-3:00 PM EST. During this outage, several our > clients could access our network. This incident re-occured again the next > day between 1:45-4:15 PM. We peer with Sprint in Boston and saw our BGP tables from them drop by about 20k routes on Tuesday and 60k routes on Wednesday at those times. We haven't asked Sprint about it, but something definitely happened on their as we didn't see equivalent drops from our other providers. Eric :) My other ISP is Qwest, which have been experiencing problem also. Here is blog about Federal Reserve recent outages: http://blog.washingtonpost.com/securityfix/ Audie
Re: Sprint BGP Outage for 11/28 and 11/29/06
Audie, > Sprint technician informed us that there was a power outage in the Baltimore > site on 11/28/06 between 2-3:00 PM EST. During this outage, several our > clients could access our network. This incident re-occured again the next > day between 1:45-4:15 PM. We peer with Sprint in Boston and saw our BGP tables from them drop by about 20k routes on Tuesday and 60k routes on Wednesday at those times. We haven't asked Sprint about it, but something definitely happened on their as we didn't see equivalent drops from our other providers. Eric :)
Sprint BGP Outage for 11/28 and 11/29/06
Sprint technician informed us that there was a power outage in the Baltimore site on 11/28/06 between 2-3:00 PM EST. During this outage, several our clients could access our network. This incident re-occured again the next day between 1:45-4:15 PM. Does anyone have further info? thanks, Audie Onibala 703-292-5316
Re: The IESG Approved the Expansion of the AS Number Registry
On 30 Nov 2006, at 07:02, Chris L. Morrow wrote: On Wed, 29 Nov 2006, Deepak Jain wrote: Afraid so. I'm hoping to be out of the industry before calls for 128 bit AS#s come down the pipe and people (at that time) are laughing about how silly 32 bit AS#s seem. anyone have a swag at the number of things that this (32bit asn) touches? Yes, and it means plenty of work for us all - hurray. But we need to take action to preserve the availability of new AS numbers for new network builders. RIPE will be accepting requests for 32-bit ASNs from 1/1/07, according to an email to ncc-services two weeks ago. It does not feel too early to start to understand what we must do to as a community to guarantee ubiquity of reachable networks. There were no definitive answers when John Payne asked on the list about images supporting 32 bit as numbers - are any independent bodies going to setup a route behind a 32-bit ASN so that we can start public reachability testing ? Andy
