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

--On Thursday, 22 May, 2014 07:17 -0700 Ned Freed
<ned.freed@mrochek.com> wrote:

> This looks correct to me, although it's right at the edge of
> what's acceptable in an errata.

Yeah.  Reluctantly concur.  I am not aware of any impulses
toward updating 6409 and do not believe this report changes that.

    john

>> 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
> 
>> _______________________________________________
>> yam mailing list
>> yam@ietf.org
>> https://www.ietf.org/mailman/listinfo/yam