[26276] in North American Network Operators' Group
Re: ORBS block
daemon@ATHENA.MIT.EDU (Greg A. Woods)
Fri Dec 17 14:25:41 1999
Message-Id: <m11z2yZ-000g9zC@most.weird.com>
Date: Fri, 17 Dec 1999 14:23:39 -0500 (EST)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: woods@most.weird.com (Greg A. Woods)
To: nanog@merit.edu
In-Reply-To: <Pine.LNX.4.10.9912170845300.29560-100000@mail.clipper.net>
Reply-To: nanog@merit.edu (North America Network Operators Group)
Errors-To: owner-nanog-outgoing@merit.edu
[ On Friday, December 17, 1999 at 08:49:17 (-0800), Tim Wolfe wrote: ]
> Subject: Re: ORBS block
>
> If Provider X wants to listen to Dean's loony conspiracy theories and block
> ORBS from going through their network, how is that thef of service? That
> would only be true if ORBS pays Provider X for some type of service and then
> they could fall back to whatever options (arbitration, etc) that their
> contract allows.
It's simple: I find ORBS a valuable service, both for ensuring my own
mail servers are secure, as well as for telling me about the issues with
my neighbours servers, as well as all the rest around the world. If my
provider, or an upstream provider from them, were blocking ORBS, even
just their inbound tests, then they would be stealing a service I value.
ORBS is not doing anything whatsoever to affect the network layer and
network operators and providers should not even see them on their
horizon.
If e-mail operators are having some kind of trouble with ORBS then
that's a different issue, but *not* one that requires network-level
intervention, especially not upstream from *anyone*.
It is most important that people not confuse these issues. ORBS is not
a network thing -- it only affects a single service.
--
Greg A. Woods
+1 416 218-0098 VE3TCP <gwoods@acm.org> <robohack!woods>
Planix, Inc. <woods@planix.com>; Secrets of the Weird <woods@weird.com>
