- NANOG - lists.nanog.org

UUNET DALLAS <-> HOUSTON fubar
by John M . Brown 04 Aug '00

04 Aug '00

from what I can tell it seems that UUNET in Dallas,Houston is not doing well today. Any other data points on the net ?? Via verio link to dallas traceroute to www.uunet.net (199.170.0.30), 30 hops max, 40 byte packets 1 abq-rtr-01 (206.29.128.1) 0.675 ms 0.571 ms 0.413 ms 2 209-75-129-189.verio-wan-abq.verio.net (209.75.129.189) 2.623 ms 2.446 ms 6.282 ms 3 d3-3-0.r00.dllstx01.us.bb.verio.net (129.250.16.97) 51.483 ms 50.206 ms 50.343 ms 4 ATM3-0.BR1.DFW9.ALTER.NET (137.39.23.221) 51.204 ms 51.148 ms 51.079 ms 5 140.at-5-0-0.XR1.DFW9.ALTER.NET (152.63.98.122) 64.602 ms 51.599 ms 51.360 ms 6 * * * 7 * 132.at-5-0-0.TR1.DCA6.ALTER.NET (152.63.2.173) 569.456 ms * 8 * * 287.at-4-0-0.XR1.DCA1.ALTER.NET (152.63.33.213) 565.894 ms 9 195.ATM8-0-0.GW2.DCA1.ALTER.NET (146.188.161.33) 549.414 ms * 486.788 ms 10 * mas2-gw.customer.alter.net (157.130.82.118) 532.248 ms 533.614 ms via CW link to bloomington (I re-pref'd our traffic) traceroute whois.arin.net traceroute to whois.arin.net (192.149.252.22), 30 hops max, 40 byte packets 1 abq-rtr-01 (206.29.128.1) 0.553 ms 0.413 ms 0.412 ms 2 bordercore2-serial5-0-0-6.Bloomington.cw.net (166.48.176.25) 33.267 ms 27.469 ms 27.404 ms 3 corerouter1.Bloomington.cw.net (204.70.9.147) 34.783 ms 28.046 ms 27.738 ms 4 ATM1-0.BR1.LAX9.ALTER.NET (137.39.23.213) 394.744 ms 368.382 ms 411.652 ms 5 154.at-5-0-0.XR2.LAX9.ALTER.NET (152.63.113.22) 63.784 ms 63.977 ms 72.872 ms 6 190.ATM2-0.TR2.LAX2.ALTER.NET (152.63.112.218) 85.574 ms 79.273 ms 57.300 ms 7 111.ATM7-0.TR2.DCA8.ALTER.NET (146.188.138.197) 96.181 ms 95.849 ms 95.805 ms 8 196.at-4-0-0.XR2.TCO1.ALTER.NET (152.63.32.209) 96.515 ms 95.716 ms 95.763 ms 9 192.ATM6-0.GW5.TCO1.ALTER.NET (146.188.162.165) 100.648 ms 96.039 ms 95.927 ms 10 arin-gw.customer.ALTER.NET (157.130.35.6) 100.158 ms 99.815 ms 99.580 ms 11 rs2.arin.net (192.149.252.22) 102.249 ms^C

1 0

California electric power on the ragged edge
by Sean Donelan 04 Aug '00

04 Aug '00

As you may remember in may the NERC, the National Electrical Reliablility Council issued a press release announcing that generation and transmission resources are expected to be adequate in most areas this summer. Today's New York Times has a story about the close call in California yesterday. Available electrical capacity dropped near 3% reserve in the afternoon, leading to concern CAISO would need to declare a "stage three emergency" and begin controlled rolling blackouts across california. http://www.nytimes.com/library/national/080300ca-power.html In June, PG&E used rolling blackouts around the San Francisco Bay area.

8 9

PGPKEY follow-up
by gerald＠merit.edu 04 Aug '00

04 Aug '00

Merit transitioned to PGPKEY authentication last Sunday, 7/30 as previously announced. As part of the conversion process we created new 'key-cert' objects from our version 5 rings on behalf of those PGP users who had already registered their public key with us. For version 2 keys and other non-version 5 keys the key is displayed as a version 5 key equivalent in the 'key-cert' objects. >From a functional standpoint this does not impact the database submission verification process. For example, submissions signed with a valid version 2 key will correctly verify against our version 5 ring. For users who wish to display their non-version 5 key in their 'key-cert' object instead of a version 5 equivalent, simply re-submit your 'key-cert' object with the key you wish to use to auto-dbm(a)radb.net. This is an artifact of the conversion process and will not affect future transactions. 'key-cert' objects will appear in the database as submitted by the user. Follow-up questions or comments should be directed to db-admin(a)radb.net. IRRd team --Gerald Winters

1 0

[brucew@thawte.com: Thawte PGP Support]
by Shawn McMahon 04 Aug '00

04 Aug '00

Guess I was wrong: ----- Forwarded message from brucew(a)thawte.com ----- From: brucew(a)thawte.com To: <smcmahon(a)eiv.com> Subject: Thawte PGP Support Date: Fri, 04 Aug 2000 09:20:53 GMT X-Thawte-Mail-Version: 1.1 X-UIDL: c39a38e9a7f8151b7a932e633ef5b3cd Hi, ************* This is an official Thawte Personal Certificate Announcement for all our customers using PGP ************* We would like to inform all of Thawte's PGP users that we will soon be discontinuing our support of PGP. We are in the process of making changes to our signing engines, and as of 1 September 2000, we will be converting to new systems. These changes will result in us no longer being able to sign PGP keys for our users. The discontinuation of this system will in no way affect the validity of your keys and the Thawte signatures on your keys will remain valid. For those of you who have had your identities verified for the Thawte Web of Trust, your points will remain and you are invited to obtain personal x.509 certificates which carry your name. Between now and 1 september, please feel free to get any keys that you might have, signed by Thawte. In the past we have attempted to keep up to date with our support of newer releases of PGP, but have not always managed to achieve this with the effectiveness that is commonly associated with other Thawte services. We still believe, however, that PGP is an excellent personal encryption tool, and this decision should in no way be interpreted as an indication of our confidence in PGP. If you have any questions or comments on this announcement, please feel free to contact me at your earliest convenience. Regards, -- Bruce Watermeyer Thawte Certification Need the strongest encryption available? Get a Thawte 128-bit SuperCert at http://www.thawte.com/certs/server/128bit/contents.html "It's better to regret something you did, Than something you didn't do!" ----- End forwarded message -----

1 0

RE: 07/21/00 Internet Routing Problems
by Craig Labovitz 04 Aug '00

04 Aug '00

The full list for each day is available on the IPMA website (http://www.merit.edu/ipma) under the daily statistics and routing problem reports heading. - Craig > Hopefully the full list is available somewhere, but the truncation and > your request seem to indicate that it isn't.

2 1

07/21/00 Internet Routing Problems
by Randy Bush 04 Aug '00

04 Aug '00

ok boys and girls. second day. would people please clean up their announcements so the rest of us can see if we have any bugs? thanks. randy --- From: stats(a)merit.edu Date: Sat, 22 Jul 2000 10:00:04 -0400 (EDT) Reserved Network and Host Announcements --------------------------------------- 10.0.0.0/8 at Mae-East from NetRail (AS4006) ASPATH=4006 INCOMPLETE 10.0.0.0/8 at Mae-West from NetRail (AS4006) ASPATH=4006 INCOMPLETE 10.0.0.0/8 at Paix from NetRail (AS4006) ASPATH=4006 INCOMPLETE 128.88.250.0/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP 128.88.250.32/29 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP 137.236.241.0/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 137.236.241.0/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 IGP 140.32.132.128/27 at Mae-East from ATT-DISC (AS7170) ASPATH=7170 1655 IGP 140.32.132.128/27 at Mae-West from ATT-DISC (AS7170) ASPATH=7170 1655 IGP 192.108.209.0/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.209.0/27 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.213.16/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.108.213.16/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1755 1755 1880 1877 IGP 192.76.71.32/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 193.122.136.4/30 at Mae-East from CableInet (AS5462) ASPATH=5462 IGP 193.133.206.64/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 2856 8718 IGP 193.133.206.64/28 at Mae-West from BBN-Planet (AS1) ASPATH=1 2856 8718 IGP 193.58.0.16/29 at Mae-East from CableInet (AS5462) ASPATH=5462 IGP 194.251.192.96/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 1755 1759 5574 IGP 194.251.192.96/27 at Mae-West from BBN-Planet (AS1) ASPATH=1 1755 1759 5574 IGP 195.89.15.160/27 at Mae-East from INS (AS6660) ASPATH=6660 5378 5378 12359 IGP 195.89.15.160/27 at Mae-East from INS (AS6660) ASPATH=6660 5378 5378 12359 IGP 198.41.0.12/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.12/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.12/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.12/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.128/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.16/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.160/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.17/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.192/28 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.22/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.224/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.24/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.29/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.30/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.4/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.6/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.64/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.7/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.8/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.9/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.0.96/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.13/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.14/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.15/32 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.1.224/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from Comstor (AS6082) ASPATH=6082 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-East from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 198.41.2.32/27 at Mae-West from ConXion (AS4544) ASPATH=4544 6245 INCOMPLETE 207.175.63.128/28 at Mae-East from BBN-Planet (AS1) ASPATH=1 IGP 207.82.242.48/28 at Mae-West from Exodus (AS3967) ASPATH=3967 13362 IGP 208.151.16.96/28 at Mae-East from Comstor (AS6082) ASPATH=6082 IGP 208.208.6.200/32 at Mae-East from Comstor (AS6082) ASPATH=6082 IGP 209.1.49.160/27 at Mae-West from Exodus (AS3967) ASPATH=3967 13362 IGP 209.141.222.96/27 at Mae-East from GoodNet (AS5696) ASPATH=5696 INCOMPLETE ***** Too many entries. List Truncated! *****

3 2

Re: 07/21/00 Internet Routing Problems
by Sean Donelan 04 Aug '00

04 Aug '00

On Thu, 03 August 2000, Mark Milhollan wrote: > >Reserved Network and Host Announcements > >--------------------------------------- > >128.88.250.0/27 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP > >128.88.250.32/29 at Mae-East from BBN-Planet (AS1) ASPATH=1 5727 2915 151 IGP > > This looks okay -- not stellar, but acceptable. Does merit's service > hate the inconsistent announcements, or am I missing something? I asked Merit about this last year. Apparently it thinks any announcement between a /25 and /32 is a "host" announcement. As far as I know no IP registry has issued any address longer than a /24 split between more than one organization. Given that both 128.88.250.0/27 and 128.88.250.32/29 are being announced by the identical ASN and identical upstreams, perhaps they could aggregate it into a single announcement.

3 2

California now at Stage Two due to power-plant failure.
by rdobbins＠netmore.net 04 Aug '00

04 Aug '00

http://news.excite.com/news/r/000803/19/energy-power-california ----------------------------------------------------------- Roland Dobbins <rdobbins(a)netmore.net> // 818.535.5024 voice

2 1

RE: California electric power on the ragged edge
by Sean Donelan 04 Aug '00

04 Aug '00

On Thu, 03 August 2000, Karyn Ulriksen wrote: > It appears that SCE has been seriously degrading voltage in an attempt to > keep most of us in SoCal happy, but some of the datacenters have already > leaned into generator power due to low voltage (10% down). It ain't pretty. > There was some brown outs occuring in the San Fernando Valley that I noticed > weren't highly publicized. I wonder if CAISO is smart-enough to do this on purpose. If you drop the voltage 15% for 5 seconds you could coerce several datacenters off the grid onto backup generators. Its possible CAISO could free up several megawatts of power for 30 minutes or so, depending on the size of the datacenters in the area. But most people wouldn't notice the brief brownout, and I've noticed utilities don't seem to track events less than 5 seconds in length. It would be nicer if they called and asked.

1 0

RE: California electric power on the ragged edge
by Karyn Ulriksen 04 Aug '00

04 Aug '00

It appears that SCE has been seriously degrading voltage in an attempt to keep most of us in SoCal happy, but some of the datacenters have already leaned into generator power due to low voltage (10% down). It ain't pretty. There was some brown outs occuring in the San Fernando Valley that I noticed weren't highly publicized. We've powered down the unnecessaries in our datacenter to minimize impact and have defined plans to further power down secondary power supplies *when* (as in not *if*) the rolls hit so that we can extend what our Lieberts can deliver. LA and the Coachella valley are just starting to hit the triple digits on the thermometer, so by the end of August and throughout September when we regularly his 105 - 120 F, the rolling blackouts are highly likely to be a reality. Refer to http://www.caiso.com/awe/systemstatus.html or simply http://www.caiso.com. Note that on http://www.caiso.com/thegrid/ they state: "Power plants meeting up to 45,000 megawatts of peak demand are connected to the Grid. " Yesterday we hit 44776 per (http://www.caiso.com/marketops/OASIS/moload/ISO_Load_20000802.pdf) although the system status page reported an even higher number. > -----Original Message----- > From: Sean Donelan [mailto:sean@donelan.com] > Sent: Thursday, August 03, 2000 5:09 PM > To: nanog(a)merit.edu > Subject: California electric power on the ragged edge > > > > As you may remember in may the NERC, the National Electrical > Reliablility Council issued a press release announcing that > generation and transmission resources are expected to be > adequate in most areas this summer. > > Today's New York Times has a story about the close call > in California yesterday. Available electrical capacity > dropped near 3% reserve in the afternoon, leading to concern > CAISO would need to declare a "stage three emergency" and > begin controlled rolling blackouts across california. > > http://www.nytimes.com/library/national/080300ca-power.html > > In June, PG&E used rolling blackouts around the San Francisco > Bay area. > > >

1 0