[dmarc-ietf] Mail regarding draft-ietf-dmarc-eaiauth
Spenser Truex <web@spensertruex.com> Mon, 01 July 2019 03:28 UTC
Return-Path: <web@spensertruex.com>
X-Original-To: dmarc@ietfa.amsl.com
Delivered-To: dmarc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7C211201F0; Sun, 30 Jun 2019 20:28:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=spensertruex.com
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 Vkz8AM5FMLgC; Sun, 30 Jun 2019 20:28:07 -0700 (PDT)
Received: from spensertruex.com (spensertruex.com [66.70.189.182]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C73612019D; Sun, 30 Jun 2019 20:28:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=spensertruex.com; s=myselector; t=1561951678; bh=XVniAjsq7yEPxImOdUVF9MjdinTy0UyivjvqaacZqOI=; h=From:To:Cc:Subject:Date; b=NjwV+/eEh9ZqCfLJjB1/0KGmJyCTNjqgXB6JnqQRfTrUYlPmYIKU0VVYfkdySp3+d 6SsP0cUaaE0pIxKbS0uyQLg7vKRWp52EfHzVGYhnyXAakRBezBr+hk9rRLNTn4Wfpe /SlUd2PyMT4tmFYcAz0mSI+pteQNfLhLzpWNgPYkYSBUMCTmzynZbvWsYrVg8CJvg+ mGYMYyvCvdcwRnXhG4hxHW/7M02NhETb7L0OPfvgeqHgSYXOQ+iqiuaZ+F2a/mZoUl MgtQU1zy8EKmSqsl/TC9uzz58LD2fsmtvbTK4tZKzXW454bIOzypT7aA95BcLFaRGr 755hxeQLwaOHA==
From: Spenser Truex <web@spensertruex.com>
To: "John R. Levine" <standards@taugh.com>, draft-ietf-dmarc-eaiauth@ietf.org
Cc: dmarc@ietf.org
Date: Sun, 30 Jun 2019 20:28:55 -0700
Message-ID: <87a7dymo08.fsf@spensertruex.com>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/dmarc/qBTe4Y_lNR2e9E1kwLWzyGlXYgY>
X-Mailman-Approved-At: Mon, 01 Jul 2019 21:51:25 -0700
Subject: [dmarc-ietf] Mail regarding draft-ietf-dmarc-eaiauth
X-BeenThere: dmarc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Domain-based Message Authentication, Reporting, and Compliance \(DMARC\)" <dmarc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmarc>, <mailto:dmarc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dmarc/>
List-Post: <mailto:dmarc@ietf.org>
List-Help: <mailto:dmarc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmarc>, <mailto:dmarc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Jul 2019 03:37:44 -0000
> 4. SPF and Internationalized Mail
> [...]
> SPF macros %{s} and %{l} expand the local part of the sender's
> mailbox. If the local part contains non-ASCII characters, terms that
> include %{s} or %{l} do not match anything, because non-ASCII local
> parts cannot be used as the DNS labels the macros are intended to
> match. Since these macros are rarely used, this is unlikely to be an
> issue in practice.
Wouldn't it be better to suggest the possibility of doing the right
thing in that situation? Perhaps:
If the local part contains non-ASCII characters, terms that include %{s}
or %{l} MAY not match anything but SHOULD match, because non-ASCII local
parts cannot be used as the DNS labels the macros are intended to match.
A standard for internationalized mail perhaps should have support for
internationalized local postmaster addresses, even if weak.
--
Spenser Truex
https://spensertruex.com/
San Francisco, USA
- [dmarc-ietf] Mail regarding draft-ietf-dmarc-eaia… Spenser Truex