Re: [Asrg] Could/Should/Must law require mechanism?

Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> Wed, 21 May 2003 13:10 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19301 for <asrg-archive@odin.ietf.org>; Wed, 21 May 2003 09:10:56 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4LCbiv15899 for asrg-archive@odin.ietf.org; Wed, 21 May 2003 08:37:44 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4LCbhB15896 for <asrg-web-archive@optimus.ietf.org>; Wed, 21 May 2003 08:37:43 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA19256; Wed, 21 May 2003 09:10:25 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ITL6-0006Es-00; Wed, 21 May 2003 09:09:04 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19ITL6-0006Ep-00; Wed, 21 May 2003 09:09:04 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4LCSIB14435; Wed, 21 May 2003 08:28:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4LCR8B14312 for <asrg@optimus.ietf.org>; Wed, 21 May 2003 08:27:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18490 for <asrg@ietf.org>; Wed, 21 May 2003 08:59:50 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19ITAr-0005yf-00 for asrg@ietf.org; Wed, 21 May 2003 08:58:29 -0400
Received: from 216-220-241-233.midmaine.com ([216.220.241.233] helo=nic-naa.net) by ietf-mx with esmtp (Exim 4.12) id 19ITAq-0005yb-00 for asrg@ietf.org; Wed, 21 May 2003 08:58:28 -0400
Received: from nic-naa.net (localhost.nic-naa.net [127.0.0.1]) by nic-naa.net (8.12.9/8.12.9) with ESMTP id h4LCsWdn021852; Wed, 21 May 2003 08:54:32 -0400 (EDT)
Message-Id: <200305211254.h4LCsWdn021852@nic-naa.net>
To: Tom Thomson <tthomson@neosinteractive.com>
cc: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>, Jeffrey Race <jrace@attglobal.net>, asrg@ietf.org, brunner@nic-naa.net
Subject: Re: [Asrg] Could/Should/Must law require mechanism?
In-Reply-To: Your message of "Wed, 21 May 2003 13:11:30 BST." <IOEPKAPPDKHPENCKFNNGIEBKCFAA.tthomson@neosinteractive.com>
From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net>
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Wed, 21 May 2003 08:54:32 -0400

> Anyway, rfc954 is irrelevant ...

The issues of bulk-, and :42-access to whois data are balloted in the
membership body of registrars for the COM/NET/ORG/BIZ/INFO/NAME set
of top-level domains.
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg