IETF Logo Mail Archive

Re: [apps-discuss] Feedback on draft-moonesamy-smtp-ipv6-00

S Moonesamy <sm+ietf@elandsys.com> Tue, 15 November 2011 08:09 UTC

Return-Path: <sm@elandsys.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9639211E8114 for <apps-discuss@ietfa.amsl.com>; Tue, 15 Nov 2011 00:09:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.577
X-Spam-Level:
X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=-0.022, BAYES_00=-2.599, DATE_IN_PAST_03_06=0.044, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id huF+Rjn1fsdL for <apps-discuss@ietfa.amsl.com>; Tue, 15 Nov 2011 00:09:33 -0800 (PST)
Received: from mail.elandsys.com (mail.elandsys.com [208.69.177.125]) by ietfa.amsl.com (Postfix) with ESMTP id 7999F11E80E9 for <apps-discuss@ietf.org>; Tue, 15 Nov 2011 00:09:33 -0800 (PST)
Received: from sm-THINK.elandsys.com (dhcp-16fb.meeting.ietf.org [130.129.22.251]) (authenticated bits=0) by mail.elandsys.com (8.13.8/8.13.8) with ESMTP id pAF89Rrj000769; Tue, 15 Nov 2011 00:09:32 -0800
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=elandsys.com; s=mail; t=1321344573; bh=efoOHNLu02hZv37cWsVZtB7FS6M=; h=Message-Id:Date:To:From:Subject:Cc:In-Reply-To:References: Mime-Version:Content-Type; b=IQWY7y9hLa1usCyxDSqDH/8qvf88qnEJ8xDNx6I7vbEFrtfbdo9pkyKG631qEpiCX D5OnW2m0fHavusU1KsmFHNT+yM4ThPSOM69VSqyXng/bgtNdv55t7awTYmqJxCctMm 3cOQ73yBsDYXJfGSome2MCeKorUxgKmS4rWizu/M=
Message-Id: <6.2.5.6.2.20111114202257.08a2c6b0@elandnews.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Mon, 14 Nov 2011 20:46:25 -0800
To: John Levine <johnl@taugh.com>
From: S Moonesamy <sm+ietf@elandsys.com>
In-Reply-To: <20111115025746.26808.qmail@joyce.lan>
References: <6.2.5.6.2.20111114142451.09b74390@elandnews.com> <20111115025746.26808.qmail@joyce.lan>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] Feedback on draft-moonesamy-smtp-ipv6-00
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Nov 2011 08:09:37 -0000

Hi John,
At 06:57 PM 11/14/2011, John Levine wrote:
>Looks mostly reasonable.

Thanks for the feedback.

>In step (9), you say "If a transient failure condition is reported,
>try the next MX RR" which looks wrong to me.  If you get a 4xx, you
>requeue the message and try it again later.

I agree that it looks wrong.  I was going to suggest "going to Step 
7" instead of Step 3.  The problem though is that you cannot retry 
against the same IP address in all cases as you have to take into 
account the DNS TTL.  The workaround I see is:

(9)  Attempt to deliver the email over the connection established, as
      specified in RFC 5321.  If a transient failure condition is
      reported, try again as defined in RFC 5321 Section 4.5.4.1.

Regards,
S. Moonesamy

v2.28.0 | Report a Bug | By Email | System Status