You know that all this stuff was standardized long ago at an IETF working group? The group was called Network Joint Management. We all agreed that there should be a trouble mailing list for each NOC and I believe we agreed on AS mailing lists as well. It is a shame, but I don't believe that that group ever put out an RFC specifying this. There was also a group that worked on inter-NOC communications and sharing trouble tickets, etc. ---Cathy From: Alan Hannan <alan@gi.net> Subject: Re: Out of date contact information Jonathan Heileger and myself are doing some work on issues similar and inclusive to this, having to do w/ inter-NOC communication, and we are planning a presentation at the next NANOG. FYI... -alan ......... Dorian Kim is rumored to have said: ] ] This would be something we could probably standardize. I wonder how many folks ] have mail aliases like routing@xxx.net, noc@xxx.net, etc to bounce messages ] right ways. At the ver least, it'll make /etc/alias file shorter for good ] number of people. :) ] ] -dorian (trouble@cic.net) ] ] On Thu, 2 May 1996, Nevin Williams wrote: ] ] > We here like trouble@ans.net. It's an all-purpose group, like ] > support, but has a sense of urgency to it. ] > ] > Nevin ] > ] > ] > -Nevin Williams ] > ANS Network Operations ] > ] > ] > ] > Andrew Partan writes: ] > > ] > > > I have found that, with only one unnamed exception, if you write ] > > > to support@isp.net ] > > ] > > How about folks use: ] > > routing@isp.net ] > > to reach people? ] > > ] > > [Is there any consensus on various support aliases that an ISP 'should' ] > > have? noc, help, hostmaster, support, postmaster, routing, info, sales, ] > > trouble, others?] ] > > --asp@partan.com (Andrew Partan) ] > > ] > ] > ] > ] > ] ]