Re: Last Call: draft-klensin-rfc2821bis

Keith Moore <moore@network-heretics.com> Wed, 26 March 2008 07:05 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 5E59F28C379; Wed, 26 Mar 2008 00:05:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.623
X-Spam-Level:
X-Spam-Status: No, score=-100.623 tagged_above=-999 required=5 tests=[AWL=-0.186, 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 COAvP7bGpUrq; Wed, 26 Mar 2008 00:05:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 751D93A6D7F; Wed, 26 Mar 2008 00:05:42 -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 010743A6D7F for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 00:05:41 -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 TNkq89w8rge6 for <ietf@core3.amsl.com>; Wed, 26 Mar 2008 00:05:40 -0700 (PDT)
Received: from m1.imap-partners.net (m1.imap-partners.net [64.13.152.131]) by core3.amsl.com (Postfix) with ESMTP id F3EB53A6CBB for <ietf@ietf.org>; Wed, 26 Mar 2008 00:05:39 -0700 (PDT)
Received: from lust.indecency.org (user-119b1dm.biz.mindspring.com [66.149.133.182]) by m1.imap-partners.net (MOS 3.8.4-GA) with ESMTP id APC01261 (AUTH admin@network-heretics.com) for ietf@ietf.org; Wed, 26 Mar 2008 00:03:14 -0700 (PDT)
Message-ID: <47E9F52B.7010606@network-heretics.com>
Date: Wed, 26 Mar 2008 03:03:07 -0400
From: Keith Moore <moore@network-heretics.com>
User-Agent: Thunderbird 2.0.0.12 (Macintosh/20080213)
MIME-Version: 1.0
To: Markku Savela <msa@moth.iki.fi>
Subject: Re: Last Call: draft-klensin-rfc2821bis
References: <20080325133807.GA12616@boreas.isi.edu> <200803252230.m2PMURNF072389@drugs.dv.isc.org> <20080326023244.GB26917@boreas.isi.edu> <01MSUMAAFHKW00007A@mauve.mrochek.com> <200803260645.m2Q6j3JX024997@burp.tkv.asdf.org>
In-Reply-To: <200803260645.m2Q6j3JX024997@burp.tkv.asdf.org>
Cc: hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com, Mark_Andrews@isc.org, Ned Freed <ned.freed@mrochek.com>, ietf@ietf.org, 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


Markku Savela wrote:
> 
> The goal should be to make IPv4 and IPv6 easily replaceable anywhere,
> whithout any reduced functionality.

I don't see how requiring MX lookups for IPv6 mail relaying reduces 
functionality.  As far as I can tell, it increases functionality because 
it provides (as a side effect) an easy, low-overhead way to say "this 
domain doesn't accept mail" in an IPv6 world.  Just don't list any MX or 
A records for it.

I guess the case that isn't being given much attention is the one where 
you have an IPv6 address assigned to a host, and you have a domain name 
associated with that address, and you want that host to be able to 
receive mail - but you don't have write permission for the DNS RRs for 
that domain, so you can't create MX records for it.  But to me the 
solution to that is easy - get your own domain name.

(IMHO the idea that some other party besides the one that runs a host 
should be able to make assertions in DNS about that host's domain name 
has always been fairly broken - we have ended up with a tussle between 
DNS administrators and host owners/administrators as a result.)

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