Re: [yam] Issue #10: RFC 5321 3.9: add tiny subsection

Alessandro Vesely <vesely@tana.it> Sun, 06 December 2009 16:59 UTC

Return-Path: <vesely@tana.it>
X-Original-To: yam@core3.amsl.com
Delivered-To: yam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CCEFB3A68FC for <yam@core3.amsl.com>; Sun, 6 Dec 2009 08:59:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.719
X-Spam-Level:
X-Spam-Status: No, score=-4.719 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RCVD_IN_DNSWL_MED=-4]
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 8HJecM3kPAIo for <yam@core3.amsl.com>; Sun, 6 Dec 2009 08:59:12 -0800 (PST)
Received: from wmail.tana.it (wmail.tana.it [62.94.243.226]) by core3.amsl.com (Postfix) with ESMTP id EF2583A68F4 for <yam@ietf.org>; Sun, 6 Dec 2009 08:59:11 -0800 (PST)
Received: from [172.25.197.158] (pcale.tana [172.25.197.158]) (AUTH: CRAM-MD5 ale@tana.it, TLS: TLS1.0, 256bits, RSA_AES_256_CBC_SHA1) by wmail.tana.it with esmtp; Sun, 06 Dec 2009 17:59:01 +0100 id 00000000005DC033.000000004B1BE2D5.00005048
Message-ID: <4B1BE2D5.9010405@tana.it>
Date: Sun, 06 Dec 2009 17:59:01 +0100
From: Alessandro Vesely <vesely@tana.it>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23) Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <6.2.5.6.2.20091206014538.033cdcc8@elandnews.com>
In-Reply-To: <6.2.5.6.2.20091206014538.033cdcc8@elandnews.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: yam@ietf.org
Subject: Re: [yam] Issue #10: RFC 5321 3.9: add tiny subsection
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/yam>
List-Post: <mailto:yam@ietf.org>
List-Help: <mailto:yam-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/yam>, <mailto:yam-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 06 Dec 2009 16:59:12 -0000

> There is a proposal to rename Section 3.9 of RFC 5321 to "Forwarding" 
> (Issue #10) and to add a "Backup MX" subsection.  I do not support this 
> change as:
> 
>  (i) It would be a significant change to Section 3.9 between the Draft 
> and Full Standard.

Yes, it would. However, it implies no protocol changes. In addition, 
it would be a really tiny subsection.

>  (ii) There isn't any relationship between "Backup MX" and "Forwarding".

I agree that "Backup MX" is a poor title, and I apologize for having 
transferred it as-is from my notes to this list. Its most notable 
defect is that it does not include smart hosts nor other servers along 
the outgoing path. I'd amend the tentatively proposed titles to be

   Forwarding
     Relaying   <-- "Backup MX" was here
     Aliases
     Mailing lists

The relationship among these server's activities may now be clearer.

The subsection would be tiny because relaying is already explained in 
Section 3.6. It should just say that the envelope addresses are left 
intact. Since envelope addresses are the point of Section 3.9, such a 
simple observation would make it complete in this respect.