[EAI] RFC 5335

Alan Ayres <adayres@monicals.com> Tue, 19 April 2016 13:11 UTC

Return-Path: <adayres@monicals.com>
X-Original-To: ima@ietfa.amsl.com
Delivered-To: ima@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 15C7212EC5B for <ima@ietfa.amsl.com>; Tue, 19 Apr 2016 06:11:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.895
X-Spam-Level:
X-Spam-Status: No, score=-2.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.996] autolearn=ham autolearn_force=no
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 L2_79RmHJ6Vt for <ima@ietfa.amsl.com>; Tue, 19 Apr 2016 06:11:32 -0700 (PDT)
Received: from mx.monicals.com (mx.monicals.com [63.144.69.5]) by ietfa.amsl.com (Postfix) with ESMTP id 9C4C612EA7A for <ima@ietf.org>; Tue, 19 Apr 2016 06:11:32 -0700 (PDT)
Received: from mail.monicals.com ([172.25.1.6]) by mx.monicals.com (8.14.7/8.14.7) with ESMTP id u3JDBUd7027788 for <ima@ietf.org>; Tue, 19 Apr 2016 08:11:30 -0500
X-Footer: bW9uaWNhbHMuY29t
Received: from localhost ([127.0.0.1]) by mail.monicals.com for ima@ietf.org; Tue, 19 Apr 2016 08:11:30 -0500
Date: Tue, 19 Apr 2016 08:11:30 -0500
X-User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_5) AppleWebKit/601.5.17 (KHTML, like Gecko) Version/9.1 Safari/601.5.17
Message-ID: <782609480-681267200@mail.monicals.com>
From: Alan Ayres <adayres@monicals.com>
To: ima@ietf.org
X-Priority: 3
Importance: Normal
In-Reply-To: <rt-4.0.8-9879-1461015967-379.119754-6-0@www.ietf.org/rt>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="=-WyzVAnkKl6V4JUNNjhNn"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ima/Km8pMUkdlr0bDfk4GjafYv6ZESs>
X-Mailman-Approved-At: Tue, 19 Apr 2016 06:25:56 -0700
Subject: [EAI] RFC 5335
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "EAI \(Email Address Internationalization\)" <ima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ima>, <mailto:ima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ima/>
List-Post: <mailto:ima@ietf.org>
List-Help: <mailto:ima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ima>, <mailto:ima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Apr 2016 13:11:42 -0000




 From:   Cindy Morgan via RT <iesg-secretary@ietf.org> 
 To:    <adayres@monicals.com> 
 Sent:   4/18/2016 4:46 PM 
 Subject:   [www.ietf.org/rt #119754] RFC 5335 

Alan, 
 
You have reached the IETF Secretariat, and as such, we are not qualified to 
answer your question. 
 
It looks like RFC 5335 was product of the Email Address Internationalization 
Working Group, which concluded back in 2013. However, the mailing list for that 
group is still active, and you may have better luck if you try your question 
there. The address for that mailing list is: ima@ietf.org 
 
You may also want to note that RFC 5335 was obsoleted by RFC 6532 
<http://www.rfc-editor.org/info/rfc6532> in 2012. 
 
Best regards, 
Cindy 
 
On Fri Apr 08 08:14:58 2016, adayres@monicals.com wrote: 
> Recently a part by iSHERIFF titled "Office 365 Security: Why you need 
> to be worried" came across my desk slamming Office 365. 
> 
> 
> Per the article, a claim is made that Office 365 does not follow 
> current RFC standards for email headers. The claim goes on to 
> suggest that a lack of RFC 5335 exposes anyone to unauthorized 
> intercept, editing and the ability to resend these messages with 
> malicious content within the headers of the message. As you appear 
> to be an authority of RFC 5335, I was hoping you would add your 
> input to these claims as pertaining to RFC 5335. 
> 
> 
> - Alan