I have lost my copy of the contact list for the NOCs. Can someone supply the contact ingo for he.net?
(408) 282-1540 - noc@ | -----Original Message----- | From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of | Roy | Sent: Thursday, July 03, 2003 2:18 AM | To: nanog@merit.edu | Subject: NOC contact for he.net | | | I have lost my copy of the contact list for the NOCs. Can someone | supply the contact ingo for he.net? |
The correct phone number for the he.net NOC is 510 580 4100. I'll make sure where ever that 408 (very old) number shows up is updated. On Thu, 3 Jul 2003, Todd Mitchell - lists wrote:
(408) 282-1540 - noc@
| -----Original Message----- | From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu] On Behalf Of | Roy | Sent: Thursday, July 03, 2003 2:18 AM | To: nanog@merit.edu | Subject: NOC contact for he.net | | | I have lost my copy of the contact list for the NOCs. Can someone | supply the contact ingo for he.net? |
+----------------- H U R R I C A N E - E L E C T R I C -----------------+ | Mike Leber Direct Internet Connections Voice 510 580 4100 | | Hurricane Electric Web Hosting Colocation Fax 510 580 4151 | | mleber@he.net http://www.he.net | +-----------------------------------------------------------------------+
On Wed, 2 Jul 2003, Roy wrote:
I have lost my copy of the contact list for the NOCs. Can someone supply the contact ingo for he.net?
Please use noc@he.net to contact the he.net NOC. Mike. +----------------- H U R R I C A N E - E L E C T R I C -----------------+ | Mike Leber Direct Internet Connections Voice 510 580 4100 | | Hurricane Electric Web Hosting Colocation Fax 510 580 4151 | | mleber@he.net http://www.he.net | +-----------------------------------------------------------------------+
I have lost my copy of the contact list for the NOCs. Can someone supply the contact ingo for he.net?
This is probably as good a time as any to mention that we have just inaugurated our ISPWL (dns-based ISP whitelist), the "HISP". It's relevant to this because members provide both standard business and urgent contact information, as well as "member to member only" contact information, for sharing with other members [note, we do *not* get involved in issues, we simply make the contact information available to other HISP members.] So in this case, if he.net is a HISP member, Roy could have gone to the HISP members contact page and looked up the information, including urgent contact information. Obviously the primary thrust of the HISP is to allow sites to query a DNS whitelist of ISPs who they can know to be whitehat, and who live up to a certain level of abuse-handling and other criteria (defined in the free license). There is no charge whatsoever for being listed on the HISP, or for querying it. If you're interested in reviewing the criteria for acceptance onto the HISP (contained in a HISP license which, again, is free), contact me off-list. Anne amitchell@habeas.com
On Thu, 3 Jul 2003, Anne P. Mitchell, Esq. wrote:
If you're interested in reviewing the criteria for acceptance onto the HISP (contained in a HISP license which, again, is free), contact me off-list.
Gosh, didn't the AGIS lawyers once try to save the net? Licenses, licenses, licenses. There are several ISP contact lists available. IOPS, Puck, ISAC (pick one or 10), INOC-DBA, Norton's Peering contacts, etc.
On Thu, 3 Jul 2003, Anne P. Mitchell, Esq. wrote:
If you're interested in reviewing the criteria for acceptance onto the HISP (contained in a HISP license which, again, is free), contact me off-list.
Gosh, didn't the AGIS lawyers once try to save the net? Licenses, licenses, licenses.
Heh, I'm here not as a lawyer, but as CEO of Habeas. The HISP is a companion to our HUL whitelist, which is a list of the IP addresses of our customer/licensees (bulk mail guaranteed to be confirmed opt- in), and our HIL (DNS blocklist of those who breach our license or otherwise infringe our trademark by using it to try to get spam through). Anne
On Thu, 3 Jul 2003, Anne P. Mitchell, Esq. wrote:
Heh, I'm here not as a lawyer, but as CEO of Habeas. The HISP is a companion to our HUL whitelist, which is a list of the IP addresses of our customer/licensees (bulk mail guaranteed to be confirmed opt- in), and our HIL (DNS blocklist of those who breach our license or otherwise infringe our trademark by using it to try to get spam through).
I hope you've provisioned a bit more bandwidth onto your various DNS servers that are handling your whiet/blacklists. About a 2 months ago there seemed to be some sort of confusion where you took your HIL list down, changed it's name and then changed it to zone-xfer only. Not a lot of fun for Spamasassin users which had it configured in by default (and others no doubt). Services that people are going to configure into their mail configs must be have a high uptime and preferable not change without warning (never change is even better). -- Simon Lyall. | Newsmaster | Work: simon.lyall@ihug.co.nz Senior Network/System Admin | Postmaster | Home: simon@darkmere.gen.nz Ihug Ltd, Auckland, NZ | Asst Doorman | Web: http://www.darkmere.gen.nz
I hope you've provisioned a bit more bandwidth onto your various DNS servers that are handling your whiet/blacklists. About a 2 months ago there seemed to be some sort of confusion where you took your HIL list down, changed it's name and then changed it to zone-xfer only. Not a lot of fun for Spamasassin users which had it configured in by default (and others no doubt).
That query configuration in SpamAssassin was incorrect, and has been fixed in 2.60. While I apologize that it caused you an inconvenience, it was in fact set up like that without our knowledge. It was querying the HIL even if there were no Habeas headers present in the inbound email in question, so it was querying the HIL for every single piece of email going through SA. In fact, it was the mass querying (8000 queries per second) even with no Habeas indicator present which caused us to have to make that change. Our servers are set up properly, and are stable. Anne
Anne P. Mitchell, Esq. wrote:
That query configuration in SpamAssassin was incorrect, and has been fixed in 2.60. While I apologize that it caused you an inconvenience, it was in fact set up like that without our knowledge. It was querying the HIL even if there were no Habeas headers present in the inbound email in question, so it was querying the HIL for every single piece of email going through SA.
In other words, the HIL is designed to only counteract the Mark, and not operate as a bl(a|o)cklist. I've seen a lot of confusion concerning people's perceptions on that (read the iCop interview. haha). -Jack
That query configuration in SpamAssassin was incorrect, and has been fixed in 2.60. While I apologize that it caused you an inconvenience, it was in fact set up like that without our knowledge. It was querying the HIL even if there were no Habeas headers present in the inbound email in question, so it was querying the HIL for every single piece of email going through SA.
In other words, the HIL is designed to only counteract the Mark, and not operate as a bl(a|o)cklist. I've seen a lot of confusion concerning people's perceptions on that (read the iCop interview. haha).
<cough> Correct, although if people choose to use it as a blocklist, that is their business. But the only IP addresses on there are those for which we have in hand email infringing our mark, and we remove the listing as soon at the infringement stops. Anne
participants (7)
-
Anne P. Mitchell, Esq.
-
Jack Bates
-
Mike Leber
-
Roy
-
Sean Donelan
-
Simon Lyall
-
Todd Mitchell - lists