[httpapi] YAML media type: further interoperability considerations on booleans
Roberto Polli <robipolli@gmail.com> Mon, 19 June 2023 08:20 UTC
Return-Path: <robipolli@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 3CEB7C1522A0 for <httpapi@ietfa.amsl.com>; Mon, 19 Jun 2023 01:20:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 hB41xrgYS1Bq for <httpapi@ietfa.amsl.com>; Mon, 19 Jun 2023 01:20:19 -0700 (PDT)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 731A5C1522AF for <httpapi@ietf.org>; Mon, 19 Jun 2023 01:20:19 -0700 (PDT)
Received: by mail-lf1-x134.google.com with SMTP id 2adb3069b0e04-4f87592eccfso176283e87.2 for <httpapi@ietf.org>; Mon, 19 Jun 2023 01:20:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1687162817; x=1689754817; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=ZrEDMN7E/KKmcypiuQKvOtQhUvwSaRFRpXk1/ukzybs=; b=X4h2+CMkPQptKiVoRr2jH52bYz2NaLq4n4213ROzu4D1uaz/Lbq1hm+/Ie29QX/FmB 4kIHlUfC9RfBNbaKJOS7+x4Dv3WiTjrHmgwk0xt02roJKRXB0ApCoT4McmyyyjdNTsld PonnZnobkRix629vQweo1NN9DTwrU6UEybVOG8+jAFGfrhfdrsVni1k+WHf00cu0dtqW zVhbm4z09EofKQmbdlRdaUZ7hoqChFBBp7+6ASf2poryyEg3rCtlp5Q9ift3+yXESQrX nr+jXoqJ4bjSbmR6P5GkPx+nWUOew/ZeAPctYCaBHdjSSmBpilwoKvnh7AI0o4XrSt0t GYsg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1687162817; x=1689754817; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=ZrEDMN7E/KKmcypiuQKvOtQhUvwSaRFRpXk1/ukzybs=; b=TuF49IDj7ZOoT5PyJ9LvXMICFBZI9GmmZ/nT42XgdDehgbc6JMmdCN6tzMhCIr5ZaE 9N4LgotOQI1S+Y18tu0ZFXSiBh62Wi6eZOQ7OcA4Mskzzylz9mFZpCjqwi65rxhCtoCK 8yzy6CSKKce8pFatSLvhAWv1+4RbyR/e5FsWBabLh0CT+ymsNFoHBQ7pA9UMu6f3dWrL 3q+Fzmhj0M0jAg6cvahvKUSusm/Zzh9jNDp1BbBVTrI1Hl7lEkCTZumgU9xqN4VFTer6 M1+O7bB3UTCWA1CL66VYPZjn+ADajfzg4hY56GzjXTh1xPqkHQ9fxjuPZY98jxf+Sz+B kqbg==
X-Gm-Message-State: AC+VfDwdMb9u80n1RDztW1WcTssRmEYXX/1imADIyJ0Jh0ZebdBvrdxM +0DYUlUj6CVIzk+PxPJPCz6PmQArHorf3n6khsrCQDNvjEz1hg==
X-Google-Smtp-Source: ACHHUZ6ZxkcJZmVziBicWmXtfhSZKRYXuwUyhVHBhQ0nUGX0IrTs/F+enZau2kg5rGSkcbHuIDWT+4DKE4jcYcuhQcQ=
X-Received: by 2002:a05:6512:3129:b0:4ed:b263:5e64 with SMTP id p9-20020a056512312900b004edb2635e64mr5850806lfd.27.1687162816992; Mon, 19 Jun 2023 01:20:16 -0700 (PDT)
MIME-Version: 1.0
From: Roberto Polli <robipolli@gmail.com>
Date: Mon, 19 Jun 2023 10:20:05 +0200
Message-ID: <CAP9qbHX=4cHYn0Lid4Z9aXyAQAjLzCycZJSH39Xg3rpciW6HrA@mail.gmail.com>
To: "httpapi@ietf.org" <httpapi@ietf.org>, eemeli@gmail.com
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/1jl7QNTzeCZUARbYuesVM9c0rfo>
Subject: [httpapi] YAML media type: further interoperability considerations on booleans
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: Mon, 19 Jun 2023 08:20:21 -0000
Dear all, I was asked to add a paragraph in the Security Considerations regarding boolean behavior. In YAML 1.1, the /yes|no/ mapped to boolean while according to YAML 1.2.2 I understand that only /true|false/ maps to boolean. The proposal is not invasive https://github.com/ietf-wg-httpapi/mediatypes/issues/97 and I think it is quite valuable, given the widespread of yes/no in YAML files (e.g., in IaC descriptor). Have a nice day, R.
- [httpapi] YAML media type: further interoperabili… Roberto Polli
- Re: [httpapi] YAML media type: further interopera… Roberto Polli
- Re: [httpapi] YAML media type: further interopera… Roberto Polli