Re: [EAI] [Technical Errata Reported] RFC6532 (6036)

John Levine <johnl@taugh.com> Wed, 01 April 2020 16:34 UTC

Return-Path: <johnl@iecc.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 3CA043A12AB for <ima@ietfa.amsl.com>; Wed, 1 Apr 2020 09:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.85
X-Spam-Level:
X-Spam-Status: No, score=-1.85 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=U1qBsKaM; dkim=pass (1536-bit key) header.d=taugh.com header.b=MDF0ief6
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 aN5UnR3vNdNP for <ima@ietfa.amsl.com>; Wed, 1 Apr 2020 09:34:52 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A653A129A for <ima@ietf.org>; Wed, 1 Apr 2020 09:34:52 -0700 (PDT)
Received: (qmail 7322 invoked from network); 1 Apr 2020 16:34:51 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1c98.5e84c2ab.k2004; bh=xUnG0M4uyZtOa0IsDKFuoI8S2nA/UusuKxMsYmTjHck=; b=U1qBsKaMB7fjEmVaw9F6WO+upL0Kt2RPmnnRQ1t+z93KWzB9LCKpjbZ2wBxJPWHO/JOq3QiT3OGgzsMHDXU1Jti8pzefhYQH2RkvrlqizQZfPiEBDjBDZYFJpi/wGPd4RCCmHUsVZoADoxO4kzSI2sFBIux200T/dDOfrNGXpdJJ+K6/Q4oXsafNQWsTcBB2IQxIGLfbztFnbxGG4VFTW/HTkRA42PadPvamqr2/knArNdlLjDnF1O41h8v+TJxz
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding; s=1c98.5e84c2ab.k2004; bh=xUnG0M4uyZtOa0IsDKFuoI8S2nA/UusuKxMsYmTjHck=; b=MDF0ief6f8UK7pbA8DkfU8kbl9I7SEJz1KmejrYY/j+k9fHnK6Kq3bGJEfF05JF4KK1kg7ZYA4CYZWfs1+VVZNPHOrh6vJkFNUR7UWj8Uft4JG+ZL4v6Vaivk3e3spQfkJQnY9UjWenx4jH+ONzpka3tTMeOeD9O61MqKx44jhHZ7aHnNCmP4ZM9af5DrwqCutyzfvm9of4KAsRB/KIX/0vEoFphghybmLZthWXsMYcoV/IHrKsUNHhaTk1n1aY4
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTP via TCP6; 01 Apr 2020 16:34:50 -0000
Received: by ary.qy (Postfix, from userid 501) id AC54716DE75A; Wed, 1 Apr 2020 12:34:50 -0400 (EDT)
Date: 1 Apr 2020 12:34:50 -0400
Message-Id: <20200401163450.AC54716DE75A@ary.qy>
From: "John Levine" <johnl@taugh.com>
To: ima@ietf.org
In-Reply-To: <20200401083756.5D051F40723@rfc-editor.org>
Organization: Taughannock Networks
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ima/ikLtSOeHEM2hM86vazLsDXBcLZA>
Subject: Re: [EAI] [Technical Errata Reported] RFC6532 (6036)
X-BeenThere: ima@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 01 Apr 2020 16:35:00 -0000

This erratum is wrong.  The MIME definition of "token" is fine.

In RFC 8601 we misused "token" in the Authenticated-Results header for
what really is a domain name.  That's what needs to be fixed, and we're
discussing what the least bad fix is.

R's,
John



In article <20200401083756.5D051F40723@rfc-editor.org> you write:
>The following errata report has been submitted for RFC6532,
>"Internationalized Email Headers".
>
>--------------------------------------
>You may review the report below and at:
>https://www.rfc-editor.org/errata/eid6036
>
>--------------------------------------
>Type: Technical
>Reported by: Alessandro Vesely <vesely@tana.it>
>
>Section: GLOBAL
>
>Original Text
>-------------
>A section 3.2bis, "Syntax Extensions to RFC 2045", is missing.
>
>
>Corrected Text
>--------------
>In particular, Section 5.1 of RFC 2045, "Syntax of the Content-Type Header Field", deserves an extension:
>
>    token /= UTF8-non-ascii
>
>similar to the extensions given to various text types given in Section 3.2.
>
>Notes
>-----
>Various header fields are defined in terms of the grammar defined in RFC 2045.  In particular, the missing extension of
>token was reported for Authentication-Results:
>https://mailarchive.ietf.org/arch/msg/dmarc/g1U__axJW5I6OenEuwD48nwptzU
>
>Instructions:
>-------------
>This erratum 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  
>can log in to change the status and edit the report, if necessary. 
>
>--------------------------------------
>RFC6532 (draft-ietf-eai-rfc5335bis-13)
>--------------------------------------
>Title               : Internationalized Email Headers
>Publication Date    : February 2012
>Author(s)           : A. Yang, S. Steele, N. Freed
>Category            : PROPOSED STANDARD
>Source              : Email Address Internationalization
>Area                : Applications
>Stream              : IETF
>Verifying Party     : IESG
>