Re: Last Call: draft-klensin-rfc2821bis

Henning Schulzrinne <hgs@cs.columbia.edu> Mon, 31 March 2008 13:11 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CA1F53A6E54; Mon, 31 Mar 2008 06:11:25 -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 435353A6D18 for <ietf@core3.amsl.com>; Mon, 31 Mar 2008 06:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 5+ApWz8thQyP for <ietf@core3.amsl.com>; Mon, 31 Mar 2008 06:11:23 -0700 (PDT)
Received: from brinza.cc.columbia.edu (brinza.cc.columbia.edu [128.59.29.8]) by core3.amsl.com (Postfix) with ESMTP id D6C933A6CB5 for <ietf@ietf.org>; Mon, 31 Mar 2008 06:11:22 -0700 (PDT)
Received: from dhcp31.cs.columbia.edu (dhcp31.cs.columbia.edu [128.59.19.231]) (user=hgs10 mech=PLAIN bits=0) by brinza.cc.columbia.edu (8.14.1/8.14.1) with ESMTP id m2VDB8Mr016692 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Mon, 31 Mar 2008 09:11:08 -0400 (EDT)
Message-Id: <24CB25C4-C6D3-4FD2-9486-4B6D213645E6@cs.columbia.edu>
From: Henning Schulzrinne <hgs@cs.columbia.edu>
To: Tony Finch <dot@dotat.at>
In-Reply-To: <alpine.LSU.1.00.0803311253110.8138@hermes-1.csi.cam.ac.uk>
Mime-Version: 1.0 (Apple Message framework v919.2)
Subject: Re: Last Call: draft-klensin-rfc2821bis
Date: Mon, 31 Mar 2008 09:11:09 -0400
References: <20080329152651.34365.qmail@simone.iecc.com> <alpine.LSU.1.00.0803311253110.8138@hermes-1.csi.cam.ac.uk>
X-Mailer: Apple Mail (2.919.2)
X-No-Spam-Score: Local
X-Scanned-By: MIMEDefang 2.63 on 128.59.29.8
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

I don't think this is a major issue, for two reasons: By the time that  
IPv6 mail becomes common, mail clients (and MTAs) will have been  
updated numerous times to deal with the security issue de jour.  
Secondly, even if a mail client or MTA were to erroneously implement  
this behavior, this causes no particular harm to the world at large,  
except bad error behavior for that particular MTA or MUA.

Henning

On Mar 31, 2008, at 7:58 AM, Tony Finch wrote:

> On Sat, 29 Mar 2008, John Levine wrote:
>>
>> Getting rid of the AAAA fallback flips the default to be in line with
>> reality -- most hosts don't want to receive mail directly, so if
>> you're one of the minority that actually does, you affirmatively
>> publish an MX to say so.
>
> I agree that this is the right thing to do in an ideal world.
>
> However there's a lot of old running code out there that implements  
> the
> AAAA fallback. Is IPv6 still enough of a toy that the stability of its
> specifications doesn't matter?
>
> Tony (in two minds).
> -- 
> f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
> ROCKALL MALIN: SOUTHERLY VEERING WESTERLY, 4 IN MALIN AT FIRST,  
> OTHERWISE 7 TO
> SEVERE GALE 9. ROUGH BECOMING VERY ROUGH OR HIGH. RAIN OR SHOWERS.  
> MODERATE OR
> GOOD, OCCASIONALLY POOR.
> _______________________________________________
> IETF mailing list
> IETF@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

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