IETF Logo Mail Archive

[Jmap] Re: [art] Re: Artart telechat review of draft-ietf-jmap-contacts-09

Tim Bray <tbray@textuality.com> Mon, 20 May 2024 19:25 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: jmap@ietfa.amsl.com
Delivered-To: jmap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65176C180B44 for <jmap@ietfa.amsl.com>; Mon, 20 May 2024 12:25:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=textuality.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uJo9Gpyv4NoF for <jmap@ietfa.amsl.com>; Mon, 20 May 2024 12:25:45 -0700 (PDT)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA008C18DB8E for <jmap@ietf.org>; Mon, 20 May 2024 12:25:45 -0700 (PDT)
Received: by mail-pj1-x1031.google.com with SMTP id 98e67ed59e1d1-2b38f2e95aeso1861350a91.0 for <jmap@ietf.org>; Mon, 20 May 2024 12:25:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality.com; s=google; t=1716233145; x=1716837945; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=wowub0Rz7JnJVEcnqZ7YgtJOZ0O4pJJDYtaTLpfwzpQ=; b=G0b95xMPVhdMAyxFQDatlqwk9ckybsdHlddrTAyfSXgReQGQWw0tunLU3HSoQGC+Qx HXL5itMdK+bpVobilihmrMITcf0gYqAN1AK9o3wXMLANSsKtRBbUdI/rislO2QVKYQWF Cbw82H8vtTlOgWyqE7/Prz4hbpKTfsV7CmHsM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1716233145; x=1716837945; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=wowub0Rz7JnJVEcnqZ7YgtJOZ0O4pJJDYtaTLpfwzpQ=; b=ICIit+7nV7ZnWj005vvxd4OFt5IvPOdAvIgQfnIwAJQU8ayA4ogLPiu0ZDpEOiN17V qubZQhcVL58YcC1tc+lfdlyBQ89abdN9WkflPTbTFMyDuTjC5CytBfrjUT8M5zxCHu/P MRZh8U9wNrJtuSaxmvIYzBzs4HIWJsC0WDCOKtu6JB4QFz4FUki0HPApWzPEMGuX83Cu Vc2temqiupS446HwN11tC+E0BmAlTvgDMO0TfN7RDaxdhOiEW5Npx9fp8upP5BRhU1Ic 9rSlQ4YKhbsvoXLogK2CJ2CDnjHbPGK/V1u7wUcJq/RrtOqz53M0PW1C/v8VaUgO7lku 4v6w==
X-Forwarded-Encrypted: i=1; AJvYcCVN9+rfh8sCusO+Pqow7yVLpV7LtRjW5DvjtGgiU3/TEF4I9u7EguAUEsIE2cvLhFtKkr5GTW28CSE2+YIh
X-Gm-Message-State: AOJu0Yyh728KiDYA7i36dbIa5LraXM9Klu8SD5P+1xFw/1YOzkE/cddW 7fSE9tuc3lqvIzg0PboJBJ1+fx6Oify9XgP+0YanrOCvNDy7+dS3RrUCUiWJ/MDJv2n4uKcME9T Vl8yGhefyHBIA/arUOlkhTau+x2C6+mMqWxV6tA==
X-Google-Smtp-Source: AGHT+IEqDqy60r9BFvFjwggxiB8s2bTb8ogHEWXcWTifh7ZYKd0Q+4nEHxyMAn9bIwhO5by+pwQmaFx/LMcJn5EcDdQ=
X-Received: by 2002:a17:90a:7101:b0:2bd:9256:bbe2 with SMTP id 98e67ed59e1d1-2bd9256bd22mr24054a91.22.1716233144884; Mon, 20 May 2024 12:25:44 -0700 (PDT)
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Mon, 20 May 2024 14:25:44 -0500
Received: from 1064022179695 named unknown by gmailapi.google.com with HTTPREST; Mon, 20 May 2024 19:25:40 +0000
MIME-Version: 1.0 (Mimestream 1.3.2)
References: <874jase3h7.fsf@hobgoblin.ariadne.com>
In-Reply-To: <874jase3h7.fsf@hobgoblin.ariadne.com>
From: Tim Bray <tbray@textuality.com>
Date: Mon, 20 May 2024 14:25:44 -0500
Message-ID: <CAHBU6iuzrYqy-ZQV61PpAJxMfEryAT-z=QCZyyKZMEiErCi7TA@mail.gmail.com>
To: "Dale R. Worley" <worley@ariadne.com>
Content-Type: multipart/alternative; boundary="000000000000f40c2c0618e7aace"
Message-ID-Hash: QOOPCZTO2ZNDUPW47BMXHRPPU2IAD76U
X-Message-ID-Hash: QOOPCZTO2ZNDUPW47BMXHRPPU2IAD76U
X-MailFrom: tbray@textuality.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jmap.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: sayrer@gmail.com, art@ietf.org, draft-ietf-jmap-contacts.all@ietf.org, jmap@ietf.org, last-call@ietf.org, steffen@sdaoden.eu
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Jmap] Re: [art] Re: Artart telechat review of draft-ietf-jmap-contacts-09
List-Id: JSON Message Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/orDORatdN9_CwSVEqOp0VaBdSE0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Owner: <mailto:jmap-owner@ietf.org>
List-Post: <mailto:jmap@ietf.org>
List-Subscribe: <mailto:jmap-join@ietf.org>
List-Unsubscribe: <mailto:jmap-leave@ietf.org>

 JSON had already existed for a long time, as defined by json..org and
4627. There was/is a huge amount of deployed software that conformed to
those definitions, which all allowed surrogates. 4627 was informative and
thus couldn’t be cited, we needed a standards-track RFC for people to cite,
but we totally couldn’t retroactively change the definition of JSON given
the existence of all that deployed software.

You may also find this interesting:
https://www.ietf.org/archive/id/draft-bray-unichars-08.html

On May 20, 2024 at 11:35:16 AM, Dale R. Worley <worley@ariadne.com> wrote:

> Tim Bray <tbray@textuality.com> writes:
>
> 4627 has been obsoleted by the current operative specification of JSON,
>
> RFC8259 (disclosure: editor), from which:
>
>
> Well, ugh.  I have to take it all back.
>
> Uh, is there a coherent explanation why RFC 8259 allows non-character
> code points?  Or specifically why it allows surrogate code points?
> "net-yet-assigned" code points I can see as plausibly allowing, but
> surrogate code points will never be assigned characters.
>
> Dale
>

v2.29.0 | Report a Bug | By Email | System Status