From nobody Mon Apr 17 18:46:59 2023
Return-Path: <sayrer@gmail.com>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
 by ietfa.amsl.com (Postfix) with ESMTP id CA9CBC137364;
 Mon, 17 Apr 2023 18:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 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, FREEMAIL_FROM=0.001,
 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
 header.d=gmail.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 8p0Z-tWIZb55; Mon, 17 Apr 2023 18:46:53 -0700 (PDT)
Received: from mail-ej1-x629.google.com (mail-ej1-x629.google.com
 [IPv6:2a00:1450:4864:20::629])
 (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 D9054C16952B;
 Mon, 17 Apr 2023 18:46:52 -0700 (PDT)
Received: by mail-ej1-x629.google.com with SMTP id xd13so35268437ejb.4;
 Mon, 17 Apr 2023 18:46:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=gmail.com; s=20221208; t=1681782411; x=1684374411;
 h=cc:to:subject:message-id:date:from:in-reply-to:references
 :mime-version:from:to:cc:subject:date:message-id:reply-to;
 bh=G3R4+ohC/ExISYSdlVvm8ubftAu+LDBRTMZQESE/VPU=;
 b=IXMsJSyJUi7GaDvgcQ75o/2KgzYEnEGXSoJ5Q6wUjY8zj1pjCVRUR312GB7DdE/a7H
 g/+zaeiAgN4DNmrzyHT4Wvqcrx/yqyezZ6T5wMdIBH708HAcDQfC+0KTqb928Ez0pNb+
 lzH1es4lzD3wO26Pl6qyoEFEOs1JpQueUMv81J1eNV9YfcYIZy8QNdwWGSX1Gz7P1YqS
 k7iqVR7M8RTP4N4dMUSaCipepIrn5HZ33KpYzxiWC4UZUFLRfckagz8vPxLotx/pIrWy
 3tqoCfXssEhbXibFW38HFJgOBi4A/Sc4opzuTJaTMHtwEMCmBDjrJYTiZLrusYCtl+v3
 moew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20221208; t=1681782411; x=1684374411;
 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=G3R4+ohC/ExISYSdlVvm8ubftAu+LDBRTMZQESE/VPU=;
 b=dx/N48h308mKnDqW6E5dhPQYGLAlTcvZ4I4B7fo7I4NisYX8kK2R3dl3DxgKhHINNf
 bUvqMgjkW05VSVgWwG+emz05kRxI1siLCWhNnA5CvwOUs6gkE3XMg9CdB/Jlp+mUveAQ
 zndR++dVmemAseNaBUkuX4J3Ax02YeHVnWXKOzc0FZiQd25DSp6Jt2aARrQby32KnD5E
 qUU9eXuKJ73GKwaJGZTh4ZKemI2wZd7BUDl9JqHBSJkxWv/ba2IPa/bLUQ/eo8lNmLpT
 00pvUTft0SB+UZHHmh5gJpiXds+UoSEhPcow43xa92kvrT8iHJYmjZSKJYJePVa/O3VQ
 Yxfg==
X-Gm-Message-State: AAQBX9cmxYVaO2wKigOVI9NSWHyBaqlN3h7OHkFtuwlFdQK8h5t29b7R
 4JdUJun6gUz4JAz/iSfw96WzQjzoDnZEcMVqdBZxKl5L5IPNSQ==
X-Google-Smtp-Source: AKy350YKtlF71L8MsFysH9t/pYbA2LRQKqkxFMAnBJy/Q7hp0q78AAzM29wEO0cnfSqbUb/d7Msd8V420r903BNScCY=
X-Received: by 2002:a17:907:91d3:b0:94e:e35f:6fed with SMTP id
 h19-20020a17090791d300b0094ee35f6fedmr8109378ejz.75.1681782410441; Mon, 17
 Apr 2023 18:46:50 -0700 (PDT)
MIME-Version: 1.0
References: <168096297107.16829.5001344342205514297@ietfa.amsl.com>
 <CAP9qbHU-Pbt-kczPdXdbP8nzKDdgeeJQJTpC==6=sKF4uG1LLA@mail.gmail.com>
 <CAChr6Sw1cj8kNRZ24xKyBpps42F60LQp0v1i6Y-Zv8WnQWgXJQ@mail.gmail.com>
In-Reply-To: <CAChr6Sw1cj8kNRZ24xKyBpps42F60LQp0v1i6Y-Zv8WnQWgXJQ@mail.gmail.com>
From: Rob Sayre <sayrer@gmail.com>
Date: Mon, 17 Apr 2023 18:46:39 -0700
Message-ID: <CAChr6SyewvuBdPpL=pWfapGTHO5HsyiRqY=Q0bb6kOJUNhnG1w@mail.gmail.com>
To: Roberto Polli <robipolli@gmail.com>
Cc: Qin Wu <bill.wu@huawei.com>, ops-dir@ietf.org, 
 draft-ietf-httpapi-yaml-mediatypes.all@ietf.org, httpapi@ietf.org, 
 last-call@ietf.org
Content-Type: multipart/alternative; boundary="00000000000029f87705f9927b72"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/MbdCtLbDfc4_gDtsCubQPheFiIo>
Subject: Re: [httpapi] [Last-Call] Opsdir last call review of
 draft-ietf-httpapi-yaml-mediatypes-04
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>,
 <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>,
 <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Apr 2023 01:46:54 -0000

--00000000000029f87705f9927b72
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Apr 17, 2023 at 5:22=E2=80=AFPM Rob Sayre <sayrer@gmail.com> wrote:

>
> Here, the document defines a Media Type, so that's presumably for
> interchange. The issue is that both ES404 and RFC8259 describe or allow
> unpaired surrogates, with ES404 making some other additional processing
> requirements.
>

Hi, sorry, it should have been "... with ECMA-262 and later making some
other additional processing requirements."

I know some people don't like what those specs do, but it's not
"unpredictable". If you have to deal with browsers, it's best to follow the
ECMAScript spec for the JSON object.

Maybe the YAML media type shouldn't get into that.

thanks,
Rob

--00000000000029f87705f9927b72
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Apr 17, 2023 at 5:22=E2=80=AFPM R=
ob Sayre &lt;<a href=3D"mailto:sayrer@gmail.com">sayrer@gmail.com</a>&gt; w=
rote:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:=
solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"=
><div><br></div><div>Here, the document defines a Media Type, so that&#39;s=
 presumably for interchange. The issue is that both ES404 and RFC8259 descr=
ibe or allow unpaired surrogates, with ES404 making some other additional p=
rocessing requirements.</div></div></blockquote><div><br></div><div>Hi, sor=
ry, it should have been &quot;... with ECMA-262 and later making some other=
 additional processing requirements.&quot;</div><div><br></div><div>I know =
some people don&#39;t like what those specs do, but it&#39;s not &quot;unpr=
edictable&quot;. If you have to deal with browsers, it&#39;s best to follow=
 the ECMAScript spec for the JSON object.</div><div><br></div><div>Maybe th=
e YAML media type shouldn&#39;t get into that.</div><div><br></div><div>tha=
nks,</div><div>Rob</div><div><br></div></div></div>

--00000000000029f87705f9927b72--

