Microsoft's NOC is best accessed via the msnnoc@microsoft.com e-mail alias. The peering@microsoft.com alias handles (what else) peering inquiries and internal communication. thanks, kurt- Kurt Parent kparent@microsoft.com
-----Original Message----- From: Reid B. Fishler [SMTP:redhead@cloudy.lightning.net] Sent: Thursday, May 07, 1998 3:44 PM To: kit@connectnet.com Cc: nanog@merit.edu Subject: Re: Microsoft NOC?
try writing peering@microsoft.com. I got a live person there...In their networking dept.
Reid
425-882-8080 as listed by whois for Microsoft is not their NOC. When
you
call this number you are told that they will only transfer by a persons name or extension and offer no other assitance.
If anyone has any other contact information it would be appreciated.
--
Kit Knox [kit@connectnet.com] - CONNECTnet INS, Inc.
From: Kurt Parent <kparent@microsoft.com> Date: Thu, 7 May 1998 15:59:25 -0700 Sender: owner-nanog@merit.edu
Microsoft's NOC is best accessed via the msnnoc@microsoft.com e-mail alias. The peering@microsoft.com alias handles (what else) peering inquiries and internal communication.
Clueless in Seattle (or nearby). Let's see... My customers can't get to MSN. I see that I don't seem to have a route to them. I send them e-mail to tell them there is a problem. The e-mail uses the network to ... sit in the outgoing queue until the problem is fixed. Oops! The reason it is imperative that there be a telephone number for an ISP is that it's really hard to use e-mail to contact an ISP if the network connectivity to the ISP is not working. It does make it easy to say that you are not getting any reports of problems when you want to go home early, though. :-) R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman@es.net Phone: +1 510 486-8634
The reason it is imperative that there be a telephone number for an ISP is that it's really hard to use e-mail to contact an ISP if the network connectivity to the ISP is not working.
This ought to make one a little less sanguine about the prospect of unifying the packet data and voice networks in a "one pipe carries it all" model. I suppose there's always smoke signals. regards, -- Robert
At 07:52 AM 5/8/98 -0700, Kevin Oberman wrote:
The reason it is imperative that there be a telephone number for an ISP is that it's really hard to use e-mail to contact an ISP if the network connectivity to the ISP is not working.
Which will certainly be interesting when/if Voice Over IP happens. Hmm, whats next, network down, please use snail mail? Justin W. Newton
My personal backup has always been carrier-pigeon. Let's not forget voice-over-cable and other voice-over-(pudding...) solutions that haven't been proven in mission-critical ways yet. -Deepak. On Fri, 8 May 1998, Justin W. Newton wrote:
At 07:52 AM 5/8/98 -0700, Kevin Oberman wrote:
The reason it is imperative that there be a telephone number for an ISP is that it's really hard to use e-mail to contact an ISP if the network connectivity to the ISP is not working.
Which will certainly be interesting when/if Voice Over IP happens. Hmm, whats next, network down, please use snail mail?
Justin W. Newton
On Thu, May 07, 1998 at 03:59:25PM -0700, Kurt Parent wrote:
Microsoft's NOC is best accessed via the msnnoc@microsoft.com e-mail alias. The peering@microsoft.com alias handles (what else) peering inquiries and internal communication.
Another typical Microsoft BFI. Why not noc@, like the rest of the known universe? Cheers, -- jra -- Jay R. Ashworth jra@baylink.com Member of the Technical Staff Unsolicited Commercial Emailers Sued The Suncoast Freenet "Two words: Darth Doogie." -- Jason Colby, Tampa Bay, Florida on alt.fan.heinlein +1 813 790 7592 Managing Editor, Top Of The Key sports e-zine ------------ http://www.totk.com
participants (6)
-
Deepak Jain -
Jay R. Ashworth -
Justin W. Newton -
Kevin Oberman -
Kurt Parent -
Robert Sanders