Implicit MX and A RRs (was: Re: Last Call: draft-klensin-rfc2821bis)

John C Klensin <john-ietf@jck.com> Wed, 26 March 2008 13:20 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 00C043A6D75; Wed, 26 Mar 2008 06:20:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.528
X-Spam-Level:
X-Spam-Status: No, score=-100.528 tagged_above=-999 required=5 tests=[AWL=-0.091, 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 Ddc0+wx471Dk; Wed, 26 Mar 2008 06:20:29 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1283428C21E; Wed, 26 Mar 2008 06:20:29 -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 D332D28C1C1 for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 06:20:27 -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 bEftUHlpZKnS for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 06:20:27 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id CA3EA3A6B63 for <ietf@ietf.org>; Wed, 26 Mar 2008 06:20:26 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1JeVVw-000KZG-6T; Wed, 26 Mar 2008 09:18:00 -0400
Date: Wed, 26 Mar 2008 09:17:58 -0400
From: John C Klensin <john-ietf@jck.com>
To: Mark Andrews <Mark_Andrews@isc.org>, SM <sm@resistor.net>
Subject: Implicit MX and A RRs (was: Re: Last Call: draft-klensin-rfc2821bis)
Message-ID: <98BB1843C1A06A1A50D6F2DA@p3.JCK.COM>
In-Reply-To: <200803261141.m2QBfJbT091722@drugs.dv.isc.org>
References: <200803261141.m2QBfJbT091722@drugs.dv.isc.org>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
Cc: 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 Wednesday, 26 March, 2008 22:41 +1100 Mark Andrews
<Mark_Andrews@isc.org> wrote:

>...
>> It would be needed until IPv6 takes over.
> 
> 	It will be needed even *after* IPv6 takes over.  There will
> 	be lots of queries for A records long after the majority
> 	of hosts don't have A records.
> 
> 	We need to remove the implict MX from A to prevent the A
> 	record lookups occuring as things currently stand.

Mark,

Whether that proposal is a good one or a bad one, it can't be
done in 2821bis because that is a document moving from Proposed
to Draft Standard and the implicit MX feature is _very_ widely
deployed and used.  So, IMO, this discussion is not directly
relevant to the (already closed) Last Call on 2821bis and should
probably be move to the ietf-smtp mailing list.

Second, no matter what is done with standardization, it will be
many, many years before one could count on those A RR lookups
not occurring -- too much software out that that is very rarely
updated.   The advantage of the "MX 0 ." approach over getting
rid of the implicit MX from A is that, if there were consensus
for it, it can be deployed in less than geological time.

But, either way, it seems to me that the correct (and only
feasible) actions start with an I-D that says something useful
and is discussed on, at least, the ietf-smtp list.

Just my opinion, of course.
   john

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