[Vcon] Errata
Thomas Howe <ghostofbasho@gmail.com> Fri, 31 May 2024 13:33 UTC
Return-Path: <ghostofbasho@gmail.com>
X-Original-To: vcon@ietfa.amsl.com
Delivered-To: vcon@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16DD4C14F696 for <vcon@ietfa.amsl.com>; Fri, 31 May 2024 06:33:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.094
X-Spam-Level:
X-Spam-Status: No, score=-7.094 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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 (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 yz8QXEuAGMr8 for <vcon@ietfa.amsl.com>; Fri, 31 May 2024 06:32:55 -0700 (PDT)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 E943EC169414 for <vcon@ietf.org>; Fri, 31 May 2024 06:32:55 -0700 (PDT)
Received: by mail-vk1-xa2f.google.com with SMTP id 71dfb90a1353d-4e4efbc3218so966392e0c.0 for <vcon@ietf.org>; Fri, 31 May 2024 06:32:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1717162374; x=1717767174; darn=ietf.org; h=date:subject:to:message-id:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=E+e/MdgbkV/mYwNul+zNO1FGFae8MTyBBL1/RorAVTU=; b=m+OTLhKj3W+ntKIUR4hQEiB7JGyfymbNnlKvI2/EZWYQ+F1ktK+LEXdrjQFi+0kihq KznpHU0V5Y5YUgp9YOM00RFvEVr2t8gC2h3YM4RqN+cFlKJ2TFbE0ipuQTC+6RYL9XBo BkLeNNPXjSvv+dm/+E/a2e9CmAtlaBM4ID6UctHCOKjsPywUGXebkUon8SMiVXRXt94N z9M/+wFx1YlZ8d1FNwA5+G5NiLUbGIxsCjE4/6YHE6FwAFDk5AVEg0WlamhBUSc4tsF3 EMQmgdTzNUygPXeJ1maLINTW2B6f2Nv6xEfkaJMVJEHziS5UWmFSkNTHv+polQBnjLh7 1+eA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717162374; x=1717767174; h=date:subject:to:message-id:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=E+e/MdgbkV/mYwNul+zNO1FGFae8MTyBBL1/RorAVTU=; b=hm1bVIuaEyDTBVzSsiIIvbjA4RZMA+4A+DdTh+IMBoUmPsdlfGCLZAdpJoAXREx/0u abBxHOx6ZSAQmDyEbWezpp1cn9oy1TwITrx9Ol87xDA7/tt+UJe+6DkR2eHENj79cDp+ cOfT47c5zXNODak6qu3dO+WWrcqGN3H+JzCjRK+39BZUg0UmHX4iNbGDpVwE6CLQujDp YEK7nhSyEUCgJPmsHthwhDZTiWtSAahe2IpN4jPf/YGEZ9wJkjp9RqPdyQJCFiYuOtmf /tcIkNj72OGyR5N5qjF6bHzxOP5MJRJKAHVy/YOR3+h8DtnBVFI0sM6WPxC7liCgTxdn n01A==
X-Gm-Message-State: AOJu0Yw5IKLZEIauGf6XBJ8qA6JuzHjx5mUOqSOQNft5dRgf5hmOmv/F uWO/naL04TwwakzAEzMH/XwCi6kGCw2xyF9n4IrUQKUfOAGFXXCu+cNN7g==
X-Google-Smtp-Source: AGHT+IGOjg1XZ96QOGyx2CpBDgQEBDmjL6YFdfyRpQxu/OuJS5Fea1138+8OA4zoYousBcEP/Ei9yA==
X-Received: by 2002:a05:6122:155:b0:4eb:9f0:afa9 with SMTP id 71dfb90a1353d-4eb09f0b2a8mr362394e0c.6.1717162372454; Fri, 31 May 2024 06:32:52 -0700 (PDT)
Received: from localhost (0.92.231.35.bc.googleusercontent.com. [35.231.92.0]) by smtp.gmail.com with UTF8SMTPSA id 71dfb90a1353d-4eaffcb2beesm204182e0c.26.2024.05.31.06.32.51 for <vcon@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 31 May 2024 06:32:51 -0700 (PDT)
Mime-Version: 1.0
X-Superhuman-Thread-ID: draft006289fe583f7031
From: Thomas Howe <ghostofbasho@gmail.com>
Message-ID: <lwupv9j4.2b54812c-8536-4cfc-97e9-f937485db44d@we.are.superhuman.com>
To: VCon BOF/WG <vcon@ietf.org>, Dan Petrie <dan.ietf@sipez.com>
X-Mailer: Superhuman Desktop (2024-05-30T21:44:03Z)
X-Superhuman-Draft-ID: draft00b303c6f7b8444b
X-Superhuman-ID: lwuq4jym.a9e6135a-fef2-4d34-8c81-12c63948ff2c
Date: Fri, 31 May 2024 13:32:50 +0000
Content-Type: multipart/alternative; boundary="2ddba6dc853410576b798de6f1c67d814ac6d108c0a01b42c44c1b9863a2"
Message-ID-Hash: 23PED25EM5DTWIGK6OMCVP5JKSUASZLT
X-Message-ID-Hash: 23PED25EM5DTWIGK6OMCVP5JKSUASZLT
X-MailFrom: ghostofbasho@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Vcon] Errata
List-Id: container for conversation data <vcon.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/vcon/bAjGHL0En5Qoi75v4jw4D09y3b8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vcon>
List-Help: <mailto:vcon-request@ietf.org?subject=help>
List-Owner: <mailto:vcon-owner@ietf.org>
List-Post: <mailto:vcon@ietf.org>
List-Subscribe: <mailto:vcon-join@ietf.org>
List-Unsubscribe: <mailto:vcon-leave@ietf.org>
Dan et al, Can you double check this? I think we got it backwards. The current draft says this in section 2.3 about inline files: 2.3.2. ( https://www.ietf.org/archive/id/draft-petrie-vcon-03.html#section-2.3.2 ) encoding ( https://www.ietf.org/archive/id/draft-petrie-vcon-03.html#name-encoding ) The encoding parameter describes the type of encoding that was performed on the string value of the body parameter. * encoding: "String" This *MUST* be one of the following strings: * "base64url": The payload of the file has been base64url encoded and provided as the string value of the body parameter. * "json": The value of the body string is a JSON object. * "none": The payload of the file is a valid JSON string and can be included without modification as the string value to the body parameter. Is this backwards? A "JSON" is a string representation of an object. Thus, if the body payload is a stringified object in JSON notation, the encoding would be "json". If the body payload is a normal object (not encoded as string), the encoding would be "none". So, wouldn't this be the right definition? : 2.3.2. ( https://www.ietf.org/archive/id/draft-petrie-vcon-03.html#section-2.3.2 ) encoding ( https://www.ietf.org/archive/id/draft-petrie-vcon-03.html#name-encoding ) The encoding parameter describes the type of encoding of the body parameter. * encoding: "String" This *MUST* be one of the following strings: * "base64url": The payload of the file has been base64url encoded and provided as the string value of the body parameter. * "json": The payload of the file has been JSON encoded and provided as the string value of the body parameter. * none": The payload of the file is not encoded. Thus, if my payload were originally a Python dict or a Javascript Object, and the encoding were "none", no further decoding is required to use it directly. Right? ===================== Thomas Howe ( http://www.lightandelectric.com ) +1 (508) 364-9972 Sent via Superhuman ( https://sprh.mn/?vip=ghostofbasho@gmail.com )
- [Vcon] Errata Thomas Howe