RE: Last Call: draft-klensin-rfc2821bis

John C Klensin <john-ietf@jck.com> Thu, 27 March 2008 19:54 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietfarch-ietf-archive@core3.amsl.com
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D0EB73A68FC; Thu, 27 Mar 2008 12:54:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.541
X-Spam-Level:
X-Spam-Status: No, score=-100.541 tagged_above=-999 required=5 tests=[AWL=-0.104, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vSgGxcaVSLIg; Thu, 27 Mar 2008 12:54:03 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A71CB3A6956; Thu, 27 Mar 2008 12:54:03 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 659C528C2F0 for <ietf@core3.amsl.com>; Thu, 27 Mar 2008 12:54:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1G2c7cMoQajL for <ietf@core3.amsl.com>; Thu, 27 Mar 2008 12:54:01 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 4C88828C196 for <ietf@ietf.org>; Thu, 27 Mar 2008 12:54:01 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1Jey8L-0000oE-7G; Thu, 27 Mar 2008 15:51:33 -0400
Date: Thu, 27 Mar 2008 15:51:31 -0400
From: John C Klensin <john-ietf@jck.com>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>
Subject: RE: Last Call: draft-klensin-rfc2821bis
Message-ID: <9244C576801FF983C8E9BA80@p3.JCK.COM>
In-Reply-To: <2788466ED3E31C418E9ACC5C316615572EEF4A@mou1wnexmb09.vcorp.ad.vrsn.com>
References: <2788466ED3E31C418E9ACC5C316615572EEF4A@mou1wnexmb09.vcorp.ad.vrsn.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: Keith Moore <moore@network-heretics.com>, alh-ietf@tndh.net, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org


--On Thursday, 27 March, 2008 12:31 -0700 "Hallam-Baker,
Phillip" <pbaker@verisign.com> wrote:

> The key issue here is whether people who rely on AAAA are
> likely to achieve their desired result. Today it does not
> matter because anyone who relies on AAAA alone with no A
> fallback is going to receive almost no mail.

Phillip,

This is true iff you believe that there are too few IPv6-enabled
mail senders to transmit such mail.  It ultimately has nothing
to do with whether there are MX records present, since having an
explicit MX record that pointed to a mail exchanger host that
only had a AAAA record would leave the sender in exactly the
same situation -- deliver over IPv6 or don't deliver at all.
That parallelism moves the discussion entirely out of the scope
of whether the text in rfc2821bis is correct or not.

More important, I suspect that belief is false.   Installations
who run IPv6-only generally know their correspondents.  The
correspondent would presumably need to be running dual-stack, or
have a submission server or equivalent that is running
dual-stack (or IPv6 only as well), but, in many parts of the
world, those are not rare.

A statement I believe would be true is that a mail server that
only supported incoming connections over IPv6 would receive
almost no spam, at least until IPv6 becomes much more popular.
But, the last I heard, that would usually be considered an
advantage.

   john


_______________________________________________
IETF mailing list
IETF@ietf.org
https://www.ietf.org/mailman/listinfo/ietf