Re: Last Call: draft-klensin-rfc2821bis

Ned Freed <ned.freed@mrochek.com> Wed, 26 March 2008 05:17 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 A172328C135; Tue, 25 Mar 2008 22:17:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.422
X-Spam-Level:
X-Spam-Status: No, score=-100.422 tagged_above=-999 required=5 tests=[AWL=0.015, 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 9bHH+RShfmXj; Tue, 25 Mar 2008 22:16:59 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A7DF63A6C93; Tue, 25 Mar 2008 22:16:59 -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 B5D0528C1F0 for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 22:16:56 -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 wih5H1nCS1Fk for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 22:16:55 -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 B26B228C4A0 for <ietf@ietf.org>; Tue, 25 Mar 2008 22:15:57 -0700 (PDT)
MIME-version: 1.0
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01MSURGKOABK0008UE@mauve.mrochek.com> for ietf@ietf.org; Tue, 25 Mar 2008 22:13:31 -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 22:13:27 -0700 (PDT)
Message-id: <01MSURGHV8XQ00007A@mauve.mrochek.com>
Date: Tue, 25 Mar 2008 22:10:30 -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 23:40:12 -0400" <AADD02274043C6E6681E0407@p3.JCK.COM>
References: <01MSSXWZKKZ800007A@mauve.mrochek.com> <fs9blg$9in$1@ger.gmane.org> <20080325133807.GA12616@boreas.isi.edu> <fsb3lo$gsd$1@ger.gmane.org> <20080326023117.GA26917@boreas.isi.edu> <01MSUMMIXZRA00007A@mauve.mrochek.com> <47E9C09D.8020900@network-heretics.com> <AADD02274043C6E6681E0407@p3.JCK.COM>
To: John C Klensin <john-ietf@jck.com>
DKIM-Signature: a=rsa-sha1; c=nowsp; d=mrochek.com; s=mauve; t=1206508411; h=Date: From:Subject:MIME-version:Content-type; b=xH+ZG2pVV/mE9v77XEfFSvT1q tYCAOEds7ow51ejlvPClMxcDhvcUMh35ImSoGvPgyEI92gt+fPZSL+UxXnVkg==
Cc: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>, Bill Manning <bmanning@ISI.EDU>, Ned Freed <ned.freed@mrochek.com>, Keith Moore <moore@network-heretics.com>, 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 Tuesday, 25 March, 2008 23:18 -0400 Keith Moore
> <moore@network-heretics.com> wrote:

> >> You know, that's a very interesting point. One of more common
> >> configuration variations we see is to disable MX lookups and
> >> just use address records.
> >
> > how does anyone expect that to work across administrative
> > domains?

> Sorry, I'm now completely confused.  Maybe it has just been a
> long day, but...

> Ned, by "disable MX lookups", do you mean "don't put MX records
> into the DNS zone and therefore force a fallback to the address
> records" or "ignore the requirement of the standard that
> requires using MX records if they are there"?

I'm talking about having the ability to disable DNS MX lookups entirely
and fall back to address information.

> If the latter,
> the behavior, however useful (or not) is, IMO, so far outside
> the standard that it is irrelevant to any discussion about how
> DNS records are used in a standard way.

I'm sorry, but i don't see it that way. I was close to convinced that this sort
of fallback behavior was no longer useful under any circumstances until Bill
reminded me that's not the case.

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