Re: Last Call: draft-klensin-rfc2821bis

Ned Freed <ned.freed@mrochek.com> Wed, 26 March 2008 02:47 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 0601028C22B; Tue, 25 Mar 2008 19:47:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.412
X-Spam-Level:
X-Spam-Status: No, score=-100.412 tagged_above=-999 required=5 tests=[AWL=0.025, 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 6qB0rUS0Ssh3; Tue, 25 Mar 2008 19:47:20 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F3C5E3A69CA; Tue, 25 Mar 2008 19:47:19 -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 087563A6A5D for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 19:47:18 -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 T4YURT3Om2QW for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 19:47:17 -0700 (PDT)
Received: from mauve.mrochek.com (dsl-66-59-230-40.static.linkline.com [66.59.230.40]) by core3.amsl.com (Postfix) with ESMTP id 560D93A69CA for <ietf@ietf.org>; Tue, 25 Mar 2008 19:47:17 -0700 (PDT)
MIME-version: 1.0
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MSUMABLCKG0008CO@mauve.mrochek.com> for ietf@ietf.org; Tue, 25 Mar 2008 19:44:56 -0700 (PDT)
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MSTEIPBSLS00007A@mauve.mrochek.com>; Tue, 25 Mar 2008 19:44:53 -0700 (PDT)
Message-id: <01MSUMAAFHKW00007A@mauve.mrochek.com>
Date: Tue, 25 Mar 2008 19:38:33 -0700
From: Ned Freed <ned.freed@mrochek.com>
Subject: Re: Last Call: draft-klensin-rfc2821bis
In-reply-to: "Your message dated Tue, 25 Mar 2008 19:32:44 -0700" <20080326023244.GB26917@boreas.isi.edu>
References: <20080325133807.GA12616@boreas.isi.edu> <200803252230.m2PMURNF072389@drugs.dv.isc.org> <20080326023244.GB26917@boreas.isi.edu>
To: Bill Manning <bmanning@ISI.EDU>
DKIM-Signature: a=rsa-sha1; c=nowsp; d=mrochek.com; s=mauve; t=1206499495; h=Date: From:Subject:MIME-version:Content-type; b=OMvBqblhQ48yQdScl8RI9wIZ6 wW89Lk6fnwU83rylprnZKIer8DjVH/QJv6kDTpJl6UiuxH9zt5OCGRORZ/7PA==
Cc: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, Mark Andrews <Mark_Andrews@isc.org>, ietf@ietf.org, Bill Manning <bmanning@ISI.EDU>
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

> 	er...  what about zones w/ A & AAAA rr's and no MX's?
> 	when I pull the A rr's, you are telling me that SMTP
> 	stops working?  That is so broken.

That's exactly the issue that's being debated now: The issue of what happens
when a domain has one or more AAAA records and no MX. RFC 2821 was ambiguous as
to what to do in this case. 2821bis currently says that AAAAs work the same as
As in this case. Several folks have expressed the opinion that this is wrong
and the right thing to do is to only allow the address record fallback for A
records. Othere have even gone so far as to say that fallback behavior should
be deprecated and eventually phased out in favor of requiring an MX entry for
SMTP transfer, although I don't believe anyone is advocating for making that
change in 2821bis.

You seem to be of the opinion that fallback behavior should be extended to
AAAA, and you seem to be the first one to express that opinion. (I myself have
no opinion on how to resolve this other than believing it has to be resolved -
the present ambigiuty is unacceptable.)

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