Definition for "unattended operation"
Although some companies claim to "man" their POPs or NOCs 24 hours a day, seven days a week; I've found other industries have run into some problems with the definition of "unattended operation." It may not be in the Oxford English Dictionary, but it does show up in some safety standards and government regulations. Unattended Operation - A procedure or operation at which there is no person present who is knowledgeable regarding the operation and emergency shutdown procedures. Just having a warm body present isn't enough to claim an attended operation from a safety or government regulation perspective. And I suspect also from a network operations perspective. As far as listing additional contact information in the WHOIS database. I encourage providers to exchange contact information for the person(s) who is knowledgeable about the process and emergency shutdown procedures. However, I am beginning to think the WHOIS database operated by NSI no longer best serves the network operation community. I see little purpose in adding additional fields to a database which is so full of useless information already. Listing good contact information just results in those contacts becoming overwhelmed by spammers, vigilantes and UUNET telemarketing. The occasional appropriate message is likely to be lost, or not acted upon because of contact fatigue. -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation
On Sun, Feb 28, 1999 at 06:31:25AM -0600, Sean Donelan wrote:
As far as listing additional contact information in the WHOIS database. I encourage providers to exchange contact information for the person(s) who is knowledgeable about the process and emergency shutdown procedures. However, I am beginning to think the WHOIS database operated by NSI no longer best serves the network operation community. I see little purpose in adding additional fields to a database which is so full of useless information already. Listing good contact information just results in those contacts becoming overwhelmed by spammers, vigilantes and UUNET telemarketing. The occasional appropriate message is likely to be lost, or not acted upon because of contact fatigue.
So, what do you suggest as an alternative? -- Steve Sobol sjsobol@nacs.net (AKA support@nacs.net and abuse@nacs.net) "The world is headed for mutiny/When all we want is unity" --Creed, "One"
At 04:19 PM 2/28/99 -0500, Steven J. Sobol wrote:
On Sun, Feb 28, 1999 at 06:31:25AM -0600, Sean Donelan wrote:
As far as listing additional contact information in the WHOIS database. I encourage providers to exchange contact information for the person(s) who is knowledgeable about the process and emergency shutdown procedures. However, I am beginning to think the WHOIS database operated by NSI no longer best serves the network operation community. I see little purpose in adding additional fields to a database which is so full of useless information already. Listing good contact information just results in those contacts becoming overwhelmed by spammers, vigilantes and UUNET telemarketing. The occasional appropriate message is likely to be lost, or not acted upon because of contact fatigue.
How about a whois that requires the requestor to be a tech contact for a domain? ___________________________________________________ Roeland M.J. Meyer - e-mail: mailto:rmeyer@mhsc.com Internet phone: hawk.lvrmr.mhsc.com Personal web pages: http://staff.mhsc.com/~rmeyer Company web-site: http://www.mhsc.com ___________________________________________________ KISS ... gotta love it!
"Roeland M.J. Meyer" wrote:
How about a whois that requires the requestor to be a tech contact for a domain?
This sounds pretty good to me. It would certainly prevent a lot of unneeded phone calls. The InterNIC's whois database would have to check for RIPE etc. domain tech contacts too though, and some kind of authentication would have to be done. Authentication based on IP address (ie. extracted from the domain info) is not acceptable. I believe whois should include passwords for account authentication then.
MAE-East Looking Glass Results Query: trace Addr: rs.internic.net Translating "rs.internic.net"...domain server (206.205.242.132) [OK] Tracing the route to rs.internic.net (198.41.0.6) 1 * * * 2 * * * 3 * * * [snip] MAE-West Looking Glass Results Query: trace Addr: rs.internic.net Translating "rs.internic.net"...domain server (206.205.242.132) [OK] Tracing the route to rs.internic.net (198.41.0.6) 1 * * * 2 * * * 3 * * * [snip] FROM www.csu.net TO rs.internic.net. traceroute to rs.internic.net (198.41.0.6), 30 hops max, 40 byte packets 1 wested-FE-0-0-0 (205.154.240.1) 1 ms 1 ms 1 ms 2 4CNet-UUNet-GW.CSU.net (137.145.11.6) 2 ms 42 ms 12 ms 3 33.ATM3-0-0.GW1.LAX4.ALTER.NET (157.130.226.205) 12 ms 3 ms 3 ms 4 * * * 5 * * * Jim __________________________________________________________________ Jim Dawson jdawson@navi.net GCN Communications, Inc. http://www.navi.net 618 NW Glisan St. Ste. 407 voice: +1.503.943.0400 Portland, Or 97209 USA fax: +1.503.943.0404 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
participants (5)
-
Jan P Tietze
-
Jim Dawson
-
Roeland M.J. Meyer
-
Sean Donelan
-
Steven J. Sobol