Re: Last Call: draft-klensin-rfc2821bis

Bill Manning <bmanning@ISI.EDU> Wed, 26 March 2008 02:34 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 BEAAB28C16B; Tue, 25 Mar 2008 19:34:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.243
X-Spam-Level:
X-Spam-Status: No, score=-100.243 tagged_above=-999 required=5 tests=[AWL=-0.406, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_17=0.6, 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 8Mlh4l5ZxVqj; Tue, 25 Mar 2008 19:34:42 -0700 (PDT)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2FB23A69AE; Tue, 25 Mar 2008 19:34: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 612123A69AE for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 19:34: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 LnP13DCY9fTk for <ietf@core3.amsl.com>; Tue, 25 Mar 2008 19:34:40 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by core3.amsl.com (Postfix) with ESMTP id 81A283A6816 for <ietf@ietf.org>; Tue, 25 Mar 2008 19:34:40 -0700 (PDT)
Received: from boreas.isi.edu (localhost [127.0.0.1]) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id m2Q2VHYd002612 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 25 Mar 2008 19:31:18 -0700 (PDT)
Received: (from bmanning@localhost) by boreas.isi.edu (8.13.8/8.13.8/Submit) id m2Q2VHOF002607; Tue, 25 Mar 2008 19:31:17 -0700 (PDT)
Date: Tue, 25 Mar 2008 19:31:17 -0700
From: Bill Manning <bmanning@ISI.EDU>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
Subject: Re: Last Call: draft-klensin-rfc2821bis
Message-ID: <20080326023117.GA26917@boreas.isi.edu>
References: <01MSSXWZKKZ800007A@mauve.mrochek.com> <fs9blg$9in$1@ger.gmane.org> <20080325133807.GA12616@boreas.isi.edu> <fsb3lo$gsd$1@ger.gmane.org>
Mime-Version: 1.0
Content-Disposition: inline
In-Reply-To: <fsb3lo$gsd$1@ger.gmane.org>
User-Agent: Mutt/1.4.2.2i
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: bmanning@boreas.isi.edu
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 Tue, Mar 25, 2008 at 03:56:14PM +0100, Frank Ellermann wrote:
> Bill Manning wrote:
> 
> >> FWIW, I'd like that...
>  
> >>>> Clarity can be established and interoperability _improved_ 
> >>>> by limiting discovery to just A and MX records.  Perhaps a
> >>>> note might be included that at some point in the future MX
> >>>> records may become required.
>   
> >>> Again, I have no problem with this approach if that's what
> >>> the consensus is.
>  
> >> ...and that, too.  
>  
> > so what is supposed to happen when I remove all "A" RR's from
> > my zones?
> 
> I'm not sure if we are talking about the same issue.  For SMTP
> as it used to be since RFC 821 clients trying to find a server
> accepting mail for x@y.example look for y.example MX records,
> and if they got something they locate corresponding servers
> "by name" (A or AAAA), all details as explained in 2821bis.  
> 
> If they got nothing with their MX query RFC (2)821 and 2821bis
> said that the client should try y.example directly "by name",
> it could be an ordinary host with an SMTP server at port 25.

	right.

example.com.  soa (
	stuff
	)

	ns foo.
	ns bar.
;
mailhost   aaaa  fe80::21a:92ff:fe99:2ab1

	is what i am using today.

the RFC's have the right idea.


> For various reasons mentioned in this thread this "fallback"
> or "implicit MX rule" isn't a good idea today, and some folks
> like to get rid of it for AAAA.   RFC 2821 didn't say that
> this is also supposed to work for IPv6, and therefore 2821bis
> isn't forced to stick to it.

	its not a bad idea either, just that some folks
	are feeling grumpy. 
	RFC 2821 didn't say - and the presumption should be
	that since IPv6 is just like IPv4... then the IPv4
	methods shoudl work.

> For the domain with only one SMTP host also almost nothing is
> new, it is only encouraged (by the proposed note) to publish
> this name in an MX record.

	what is being proposed is -FORCING- people to use
	an RR type they may not want to use.

> You are not supposed to remove any A records from your zones.
> You are not supposed to do anything at all, because you have
> MX records as it should be... :-)

	er, NO.  SMTP has no dependence on what may or may
	not exist in the DNS.  Forcing SMTP to depend on DNS
	is a huge mistake.  And yes Virginia, I plan on removing
	A rr's from my zones (eventually)

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

-- 
--bill

Opinions expressed may not even be mine by the time you read them, and
certainly don't reflect those of any other entity (legal or otherwise).

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