IETF Logo Mail Archive

RE: [Asrg] seeking comments on new RMX article

Vernon Schryver <vjs@calcite.rhyolite.com> Tue, 06 May 2003 18:50 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 OAA02854 for <asrg-archive@odin.ietf.org>; Tue, 6 May 2003 14:50:50 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46IxRU18028 for asrg-archive@odin.ietf.org; Tue, 6 May 2003 14:59:27 -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 h46IxR818025 for <asrg-web-archive@optimus.ietf.org>; Tue, 6 May 2003 14:59:27 -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 OAA02820; Tue, 6 May 2003 14:50:20 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D7Y9-0001N0-00; Tue, 06 May 2003 14:52:25 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19D7Y9-0001Mx-00; Tue, 06 May 2003 14:52:25 -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 h46Io4817514; Tue, 6 May 2003 14:50:04 -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 h46InV817477 for <asrg@optimus.ietf.org>; Tue, 6 May 2003 14:49:31 -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 OAA02544 for <asrg@ietf.org>; Tue, 6 May 2003 14:40:24 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D7OX-0001Ia-00 for asrg@ietf.org; Tue, 06 May 2003 14:42:29 -0400
Received: from calcite.rhyolite.com ([192.188.61.3]) by ietf-mx with esmtp (Exim 4.12) id 19D7OW-0001IX-00 for asrg@ietf.org; Tue, 06 May 2003 14:42:29 -0400
Received: (from vjs@localhost) by calcite.rhyolite.com (8.12.9/8.12.9) id h46IhITl027718 for asrg@ietf.org env-from <vjs>; Tue, 6 May 2003 12:43:18 -0600 (MDT)
From: Vernon Schryver <vjs@calcite.rhyolite.com>
Message-Id: <200305061843.h46IhITl027718@calcite.rhyolite.com>
To: asrg@ietf.org
Subject: RE: [Asrg] seeking comments on new RMX article
References: <01C313DC.6A676640.eric@infobro.com>
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: Tue, 06 May 2003 12:43:18 -0600

> From: "Eric D. Williams" <eric@infobro.com>

> I stand corrected.  I do not see that as a best practice (esp. related to 
> secure configuration of an IP).

I don't understand the second sentence.  How is a system's security
affected by having more than one PTR RRs for an IP address? 

I would agree that because many applications and support tools don't
understand multiple PTR RRs per IP address, it would be unwise to
build a large scale protocol or application that depends on them being
widely supported immediately.


Vernon Schryver    vjs@rhyolite.com
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg

v2.23.0 | Report a Bug | By Email