RE: Need routing engineer from Verio
Yes, I did send to peering and noc a few minutes later. I was not sure how quickly the peering email addressed was polled so I was looking for some help sooner from a clueful person on this list. (Which I have mostly received, minus the few requisite hate mails) Mark EA.COM -----Original Message----- From: TTSG [mailto:ttsg@ttsg.com] Sent: Sunday, February 27, 2000 2:53 PM To: rbush@bainbridge.verio.net Cc: MRizzo@eahq-exchange.ea.com; nanog@merit.edu Subject: Re: Need routing engineer from Verio
Hello, I need to contact someone from Verio that can help me sort out a routing issue between Verio and my company.
posted two minutes after mail sent to peering@verio.net and no mail sent
to
noc@verio.net. brilliant.
Ya blame him? With the response times and cluelessness factor I've run into with various Verio departments, I'm suprised he bothered at all. Tuc/TTSG
Well it's happened again. It was easy to see this one coming. I think we all know when and what we should post. It's important to try and email and yes even a PHONE call the the repective NOC. That is why we have them 24x7 with lots of fancy screen. What I think is import for the new engineers is to have a list of those phone numbers handy. Lauren Nowlin was nice enough to import her list of every noc into my Palm. I think it would be wonderfully useful to make such a Palm list public so every engineer can have it handy everywhere they are. Backbone web sites dont always do a job of making the number easy to find. Not to mention when we experience an outage with that backbone we cant reach the web page. Just wanted to turn something negative into a possible positive. For the record Randy responded within minutes. Impressive. dd At 3:40 PM -0800 2/27/00, Rizzo, Mark wrote:
Yes, I did send to peering and noc a few minutes later. I was not sure how quickly the peering email addressed was polled so I was looking for some help sooner from a clueful person on this list. (Which I have mostly received, minus the few requisite hate mails)
Mark EA.COM
-----Original Message----- From: TTSG [mailto:ttsg@ttsg.com] Sent: Sunday, February 27, 2000 2:53 PM To: rbush@bainbridge.verio.net Cc: MRizzo@eahq-exchange.ea.com; nanog@merit.edu Subject: Re: Need routing engineer from Verio
Hello, I need to contact someone from Verio that can help me sort out a routing issue between Verio and my company.
posted two minutes after mail sent to peering@verio.net and no mail sent
to
noc@verio.net. brilliant.
Ya blame him? With the response times and cluelessness factor I've run into with various Verio departments, I'm suprised he bothered at all.
Tuc/TTSG
Thank you, David Diaz Chief Technical Officer Netrail, Inc email: davediaz@netrail.net, davediaz@fla.net, cougar@mail.rockstar.org pager: davediaz@bellsouthips.com NOC: 404-522-1234 Fax: 404 522-2191 ----------------------------------- Build 1: 46 cities nationwide -- COMPLETE Build 2: 80 OC48s Nationwide [no typo] ++ FAILURE IS NOT AN OPTION! ++ ------------------------------------
On Sun, Feb 27, 2000 at 08:36:01PM -0500, David Diaz wrote:
Well it's happened again. It was easy to see this one coming. I think we all know when and what we should post. It's important to try and email and yes even a PHONE call the the repective NOC. That is why we have them 24x7 with lots of fancy screen.
What I think is import for the new engineers is to have a list of those phone numbers handy. Lauren Nowlin was nice enough to import her list of every noc into my Palm. I think it would be wonderfully useful to make such a Palm list public so every engineer can have it handy everywhere they are.
Backbone web sites dont always do a job of making the number easy to find. Not to mention when we experience an outage with that backbone we cant reach the web page.
a web page exists with a list of contacs for many of the NOCs. http://puck.nether.net/netops/
Just wanted to turn something negative into a possible positive. For the record Randy responded within minutes. Impressive.
dd
At 3:40 PM -0800 2/27/00, Rizzo, Mark wrote:
Yes, I did send to peering and noc a few minutes later. I was not sure how quickly the peering email addressed was polled so I was looking for some help sooner from a clueful person on this list. (Which I have mostly received, minus the few requisite hate mails)
Mark EA.COM
-----Original Message----- From: TTSG [mailto:ttsg@ttsg.com] Sent: Sunday, February 27, 2000 2:53 PM To: rbush@bainbridge.verio.net Cc: MRizzo@eahq-exchange.ea.com; nanog@merit.edu Subject: Re: Need routing engineer from Verio
Hello, I need to contact someone from Verio that can help me sort out a routing issue between Verio and my company.
posted two minutes after mail sent to peering@verio.net and no mail sent
to
noc@verio.net. brilliant.
Ya blame him? With the response times and cluelessness factor I've run into with various Verio departments, I'm suprised he bothered at all.
Tuc/TTSG
Thank you, David Diaz Chief Technical Officer Netrail, Inc
email: davediaz@netrail.net, davediaz@fla.net, cougar@mail.rockstar.org pager: davediaz@bellsouthips.com NOC: 404-522-1234 Fax: 404 522-2191
----------------------------------- Build 1: 46 cities nationwide -- COMPLETE Build 2: 80 OC48s Nationwide [no typo]
++ FAILURE IS NOT AN OPTION! ++ ------------------------------------
For the record Randy responded within minutes.
but i learned my lesson. it was not even a fellow isp / network operator, but an end customer of someone else. and on sunday. also, he did not need a verio engineer. he just wanted to confirm what his isp had already told him that our route filtering policies were, which have been public for a good while, see <http://info.us.bb.verio.net/routing.html>, i thought were pointed to by the nanog routing filter policy web page at <http://www.nanog.org/filter.html> but seem not to be, were discussed on this list and a panel at the recent nanog, ... i know we're doomed to repeat ourselves every six months, but three weeks seems a bit short. cluonphagy runs rampant, news at 11. randy
On Sun, 27 Feb 2000, Randy Bush wrote: [cut]
... he just wanted to confirm what his isp had already told him that our route filtering policies were, which have been public for a good while, see <http://info.us.bb.verio.net/routing.html>, i thought were pointed to by the nanog routing filter policy web page at <http://www.nanog.org/filter.html> but seem not to be, were discussed on this list and a panel at the recent nanog, ...
just for grins I tried to find this information starting from www.verio.net. Can this be done?? --- Douglas Denault doug@safeport.com
just for grins I tried to find this information starting from www.verio.net. Can this be done??
i would be surprised if so. www.verio.net is done by marketing folk. i imagine an engineer would be hard pressed to find anything they considered to be content. and we're proud of it. :-) randy
What I think is import for the new engineers is to have a list of those phone numbers handy. Lauren Nowlin was nice enough to import her list of every noc into my Palm. I think it would be wonderfully useful to make such a Palm list public so every engineer can have it handy everywhere they are.
Or how about just text. I've often thought it would be a good idea to share the various phone numbers we all have -- the only problem is keeping the list up to date. As these numbers change quite a bit, some verification needs to be put in place. Perhaps a text based list, in a given format, with a "last verified" date included. That would give the person using it some expectation of the validity of the number. If each contributor of a number would verify the numbers before contributing them, the work would be distributed, and would stand some chance of making the idea a reality. If the format (schema) is set to something specific, people can do what they want with the information -- push it on to pilots, etc.
Hi Dave, Dave & NANOGrs, I keep NOC info current from Jared's wonderful site at http://puck.nether.net/ The incentive should be to update your peers with the 'human' sources via e-mail and update Jared's page with the 'role' sources. Palm-to-Palm beaming limits the distribution to those who should have a valid reason for the data (i.e. no sales/vendor). Yes, the updates are awkward... but I also have 'human' peering & NAP contacts subdivided out into Asia/Pac, US & Europe that I will not share unless you are a peer in that region. During APRICOT this week in Seoul I'll gladly beam NOC details to non-peers and peer details to peers after you give your details to add to the mix. Offer stands at each NANOG, RIPE, JPIX mtg., etc. BTW, Randy's network handles 'peering@' very well. Unfortunately too many other networks around the world haven't learned how standardization can help... Take care, -Ren Lauren F. Nowlin, ren@onyx.net / peering@onyx.net Director, Peering & Interconnects - http://www.onyx.net/peering/ Onyx Networks, Inc., a wholly owned subsidiary of Pacific Gateway Exchange Voice: 650-558-3262, Fax: 650-558-3160, Cellphone: 650-281-6963 At 09:34 PM 2/27/00 -0500, Dave Curado wrote:
What I think is import for the new engineers is to have a list of those phone numbers handy. Lauren Nowlin was nice enough to import her list of every noc into my Palm. I think it would be wonderfully useful to make such a Palm list public so every engineer can have it handy everywhere they are.
Or how about just text. I've often thought it would be a good idea to share the various phone numbers we all have -- the only problem is keeping the list up to date. As these numbers change quite a bit, some verification needs to be put in place.
Perhaps a text based list, in a given format, with a "last verified" date included. That would give the person using it some expectation of the validity of the number. If each contributor of a number would verify the numbers before contributing them, the work would be distributed, and would stand some chance of making the idea a reality.
If the format (schema) is set to something specific, people can do what they want with the information -- push it on to pilots, etc.
On Mon, 28 Feb 2000, Lauren F. Nowlin wrote:
Palm-to-Palm beaming limits the distribution to those who should have a valid reason for the data (i.e. no sales/vendor).
Maybe it's time to have a "Palm data exchange" BoF at the next nanog... - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ----------------------------------------------------------------------
On Mon, 28 Feb 2000, Forrest W. Christian wrote:
On Mon, 28 Feb 2000, Lauren F. Nowlin wrote:
Palm-to-Palm beaming limits the distribution to those who should have a valid reason for the data (i.e. no sales/vendor).
Maybe it's time to have a "Palm data exchange" BoF at the next nanog...
I think we already run that BoF, but it's known as "The Bar" :-) Mike
</operational-value> On Mon, Feb 28, 2000 at 02:01:15AM -0700, Forrest W. Christian wrote:
On Mon, 28 Feb 2000, Lauren F. Nowlin wrote:
Palm-to-Palm beaming limits the distribution to those who should have a valid reason for the data (i.e. no sales/vendor).
Maybe it's time to have a "Palm data exchange" BoF at the next nanog...
Sounds kinky to me. Do things like this take place on the floor, or is this one of those "hey why dont you come back to my room.. we'll.. trade noc lists.."
At 10:51 AM -0800 2/28/2000, Jamie Rishaw wrote:
</operational-value>
On Mon, Feb 28, 2000 at 02:01:15AM -0700, Forrest W. Christian wrote:
On Mon, 28 Feb 2000, Lauren F. Nowlin wrote:
Palm-to-Palm beaming limits the distribution to those who should have a valid reason for the data (i.e. no sales/vendor).
Maybe it's time to have a "Palm data exchange" BoF at the next nanog...
Sounds kinky to me. Do things like this take place on the floor, or is this one of those "hey why dont you come back to my room.. we'll.. trade noc lists.."
Palm data exchange is the cyber equivalent of dogs sniffing one another.
Jamie Rishaw wrote:
Sounds kinky to me. Do things like this take place on the floor, or is this one of those "hey why dont you come back to my room.. we'll.. trade noc lists.."
Why don't you ask Howard Berkowitz? Judging from his previous comment on the matter, it sounds like he might know. :P -- North Shore Technologies, Cleveland, OH http://NorthShoreTechnologies.net Steve Sobol, President, Chief Website Architect and Janitor sjsobol@NorthShoreTechnologies.net - 888.480.4NET - 216.619.2NET
On Sun, Feb 27, 2000 at 08:36:01PM -0500, David Diaz wrote:
Well it's happened again. It was easy to see this one coming. I think we all know when and what we should post. It's important to try and email and yes even a PHONE call the the repective NOC. That is why we have them 24x7 with lots of fancy screen.
What I think is import for the new engineers is to have a list of those phone numbers handy. Lauren Nowlin was nice enough to import her list of every noc into my Palm. I think it would be wonderfully useful to make such a Palm list public so every engineer can have it handy everywhere they are.
For the love of god! Don't give away secrets.. like the wonders of Her Holiness the Dalai Lauren. If others find out, they may try to exploit this precious resource, and, who knows, She may go into hiding... And it will all be YOUR FAULT
participants (12)
-
Dave Curado -
David Diaz -
Douglas Denault -
Forrest W. Christian -
Howard C. Berkowitz -
Jamie Rishaw -
john heasley -
Lauren F. Nowlin -
Mike Hughes -
Randy Bush -
Rizzo, Mark -
Steve Sobol