[yam] [Technical Errata Reported] RFC6409 (3995)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 22 May 2014 10:59 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: yam@ietfa.amsl.com
Delivered-To: yam@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE1C61A018A for <yam@ietfa.amsl.com>; Thu, 22 May 2014 03:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.853
X-Spam-Level:
X-Spam-Status: No, score=-104.853 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NvwrVCa_Bq4v for <yam@ietfa.amsl.com>; Thu, 22 May 2014 03:59:46 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 45F7B1A017F for <yam@ietf.org>; Thu, 22 May 2014 03:59:46 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 779E218000D; Thu, 22 May 2014 03:59:30 -0700 (PDT)
To: rg+ietf@qualcomm.com, john-ietf@jck.com, barryleiba@computer.org, presnick@qti.qualcomm.com, tony@att.com, sm+ietf@elandsys.com
X-PHP-Originating-Script: 6000:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20140522105930.779E218000D@rfc-editor.org>
Date: Thu, 22 May 2014 03:59:30 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/yam/6imdUysXyMdAsg2j3j3g9tiggsU
Cc: yam@ietf.org, rfc-editor@rfc-editor.org
Subject: [yam] [Technical Errata Reported] RFC6409 (3995)
X-BeenThere: yam@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Yet Another Mail working group discussion list <yam.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 22 May 2014 10:59:48 -0000

The following errata report has been submitted for RFC6409,
"Message Submission for Mail".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=6409&eid=3995

--------------------------------------
Type: Technical
Reported by: Tony Finch <dot@dotat.at>

Section: 8.7

Original Text
-------------
   NOTE: SMTP [SMTP-MTA] prohibits the use of domain name aliases in
   addresses and the session-opening announcement.  As with other SMTP
   requirements, RFC 5321 effectively prohibits an MSA from forwarding
   such messages into the public Internet.  Nonetheless, unconditionally
   resolving aliases could be harmful.  For example, if www.example.net
   and ftp.example.net are both aliases for mail.example.net, rewriting
   them could lose useful information.


Corrected Text
--------------
   NOTE: RFC 821 and RFC 1123 prohibited the use of domain name
   aliases in addresses and the session-opening announcement.
   Because of this it is still common for MTAs to canonicalize
   domains in email addresses.  However this requirement was dropped
   during the development of RFC 2821.  The current rules about 
   domain name aliases are set out in RFC 5321 section 2.3.5.

Notes
-----


Instructions:
-------------
This errata is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party (IESG)
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC6409 (draft-ietf-yam-rfc4409bis-03)
--------------------------------------
Title               : Message Submission for Mail
Publication Date    : November 2011
Author(s)           : R. Gellens, J. Klensin
Category            : INTERNET STANDARD
Source              : Yet Another Mail
Area                : Applications
Stream              : IETF
Verifying Party     : IESG