[ietf-822] (no subject)

Peter Occil <poccil14@gmail.com> Tue, 24 July 2018 04:02 UTC

Return-Path: <poccil14@gmail.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id D2284130FCE for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:02:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Dmvx14rG0UW1 for <ietf-822@ietfa.amsl.com>; Mon, 23 Jul 2018 21:02:04 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 14192130E0A for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:02:04 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id y203-v6so1054381ywd.9 for <ietf-822@ietf.org>; Mon, 23 Jul 2018 21:02:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:from:subject:date:importance; bh=ovOGDUtY3688Vbs35hKhrquURMovFy3bHXQvPGctfyk=; b=EekObQ9df8ZKT62vrtpeqxOeGIEVpM8808c7q6BAVzn7nXitySDry9q/mqO1SodJ9E QL9aarNDOqQg+tZR+QMBSFmNxH41DVP9E0A8/hCkYLQDCHgpfxSfG/RXuuEQZPe2qD7J cJNs7qCSP4uSVRnM3znp+Fe2l4ML3gacHjyOg/HYMZSSESVqLRD6u0LY/2tLhEk9W+QD Uj5Y6WR9RwSxfCIvQ0t731QqreNRx5URyjrmFtzHN7O7UqZZL+ZOlJzedoApkad4a5Wd y2mYiSlLfTS+z/B8Ms8So106t/T4PZ51aEJSSUPCeoxEJVrlre1VsAts69c2FMcI9NnN zfsw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:from:subject:date :importance; bh=ovOGDUtY3688Vbs35hKhrquURMovFy3bHXQvPGctfyk=; b=ZNzine3ApdJs2oOoMxe2K0yVqlvJqt6Am6lf2C+peNRayoq1bsuFm4PJZU7yg6Ni/u mcEsPh3owtDVPlw9M2+wtaRhfaG0HyJZnHzA/haFgYirzC85f41bm2tMCCxcX/1MBXg8 axkwQo+ncGybD2OV2HGB9wDrKHmv9c58YcvOtWP4h89FeBu8/cfTRuwPUEMmT2rAI+xH 0icu4Uo+Xg7X3yNOV3uoeLBuKTbox9lF6/m5phh9gCrtAzQSu0iUEjAtwqCJ68FBGS4E Nj20OkAfyKU7gWom34S4WSx03wZXWzKmqZSuhVb/qz/frYsnac5UkQeLoT9P+OXx72pu ZOJA==
X-Gm-Message-State: AOUpUlEP/ueiewguuKxIHpSGaJB4DTIAdj60jeyZhitoOiCNFf0BrwHL XWc+9Qa+o2vhi9/zhIVQCtG6dCOb2Wk=
X-Google-Smtp-Source: AAOMgpe5huuQzNw4gCA/fDLKuKwhnq1p7JwIT8KdKWo3XNoSpxuPbUdwmBaKHQN+kON8/JTE6qYthg==
X-Received: by 2002:a81:3603:: with SMTP id d3-v6mr8021555ywa.295.1532404922941; Mon, 23 Jul 2018 21:02:02 -0700 (PDT)
Received: from ?IPv6:2601:192:4e00:596:22:8b71:4eb9:6006? ([2601:192:4e00:596:22:8b71:4eb9:6006]) by smtp.gmail.com with ESMTPSA id o204-v6sm5639276ywd.16.2018. (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Jul 2018 21:02:02 -0700 (PDT)
Message-ID: <5b56a4ba.1c69fb81.836c0.d955@mx.google.com>
MIME-Version: 1.0
To: "ietf-822@ietf.org" <ietf-822@ietf.org>, "johnl@taugh.com" <johnl@taugh.com>
From: Peter Occil <poccil14@gmail.com>
Date: Tue, 24 Jul 2018 00:02:04 -0400
Importance: normal
X-Priority: 3
Content-Type: multipart/alternative; boundary="_90526788-B888-4660-B007-0467FFAF91A5_"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-822/JGv-d_MzjKrk699yPN1r3MkBqbo>
Subject: [ietf-822] (no subject)
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jul 2018 04:02:06 -0000

>Remember that MUST means "do this if you want to interoperate", not "do this or die."
> Plan A: update RFC 2369 to say MAY add spaces, send out a press release, wait for
everyone in the world to update their software to remove spaces when parsing List-x
> Plan B: figure out how to make your URLs short enough that your List-Unsubscribe
headers are under 998 characters.
> I know what I'd do.

Plan A is not what I suggest at all; I suggest rather that whitespace "SHOULD NOT" be generated between the angle brackets (compare with RFC 2557 sec. 4.4, which applies to the Content-Location header field, which uses URLs similarly to how List-Unsubscribe and certain other list header fields do).

Plan B is only feasible if the same person provides the URL _and_ writes the code to generate the List-Unsubscribe header field (or any other list header field) for the corresponding message; not so if a software library generates a message containing the value of a List-Unsubscribe (or other) header field provided by a (third-party) user that, while otherwise syntactically valid, could exceed 998 characters in length.  The software library would then have to either—

- reject the user-provided value (even though it’s otherwise syntactically valid – note that RFC 2369 neither specifies nor mandates a character limit), or 
- be forced to generate a message with a line exceeding 998 characters or to fold lines to fit that character limit, or
- take some other error-handling action.