[Iot-onboarding] RFC 8366: voucher artifact error in example?
"M. Ranganathan" <mranga@gmail.com> Mon, 10 February 2020 03:28 UTC
Return-Path: <mranga@gmail.com>
X-Original-To: iot-onboarding@ietfa.amsl.com
Delivered-To: iot-onboarding@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 2375012008C
for <iot-onboarding@ietfa.amsl.com>; Sun, 9 Feb 2020 19:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001,
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 ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 2w0Q_QverfQt for <iot-onboarding@ietfa.amsl.com>;
Sun, 9 Feb 2020 19:28:26 -0800 (PST)
Received: from mail-il1-x135.google.com (mail-il1-x135.google.com
[IPv6:2607:f8b0:4864:20::135])
(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 A3443120041
for <iot-onboarding@ietf.org>; Sun, 9 Feb 2020 19:28:26 -0800 (PST)
Received: by mail-il1-x135.google.com with SMTP id i7so4523048ilr.7
for <iot-onboarding@ietf.org>; Sun, 09 Feb 2020 19:28:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=8oaH+K8z5hfkGgWPSGZlQOdDaJvoePOmq3dxZv9Bdz8=;
b=ol2scXPhvwe2PPkI5UBL6EmPLAPcwfNOzw0pq2X1wp+2+Tn916m/zkOQYvq2NbSm0J
zwhZSdt5z6cYEwU/j4NYRGB0M9sxknimCsiDTymoMmdLAWTr4E+1WvTCsiWVmohQoaiK
eGMbAx0GpaiqBzhKsT6Lrmj35YOuGvJXeVvmXnCXd8Bsl+sezjsRswaE0qD0ac7ts0F4
bLvPz/dG2IvUvrvkwOeHcNSm0qe76jsH9npB0v9Nn09ft2RXgeRhmgteKMMEpFA8n4Pj
HayWHbMNnNWOz8KfnsG8pED/j+idqvnn91Qdnnw0wiO2bsBp/xSVapOrt2Aj1dC/vyjM
F9Tw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=8oaH+K8z5hfkGgWPSGZlQOdDaJvoePOmq3dxZv9Bdz8=;
b=ZwyMN+ExxC/SdFicd+WMHF9bLEEY2LHiujXwQkkmkXjVbRrX9h18W/z0STzE4VPTDJ
EMK7F1EBj1cQ0Nc1HHfGxzAc4LWI0/jDgZdc37OIWVn5INzm3BJoBWfhFgKi0x1Kr2tQ
51A2IGIOlDkoVSqK9H4jTJkRZBOvSuR900fStkryF+Ls4qgcw2e9B0594klzA7SZzVAo
tZDTr5MWpf7QDTQqhY1wSJ8lXGdUGWRgXhcj9Uz5d1oV+WilHjhd+ff/1DSwNq9B5VWA
hPTBgETyoPZvAy3wGh8+tM6DVTT7JMUlNgT7XyB7ByqWOT+0WqCvJS5nddmRzXJwMY00
gJgA==
X-Gm-Message-State: APjAAAW43SGHx4KKkYfgMUrxNv4Vef57GKBtCulCpP+gz5xAbnSw1NiU
UJwcdfxonLd7++KjOoC/JHWeJtVup7y0z/z4JD74rXAnXS542Ae7
X-Google-Smtp-Source: APXvYqwp3kjjTF2ZFn2qDT5Xr0p97I2LUSAfqUXAdOvVdNF1FlymllkT1O+QbeE+AYDyX9DVTgViRrvpgxKyOjVvasM=
X-Received: by 2002:a92:50a:: with SMTP id q10mr8157175ile.294.1581305305496;
Sun, 09 Feb 2020 19:28:25 -0800 (PST)
MIME-Version: 1.0
From: "M. Ranganathan" <mranga@gmail.com>
Date: Sun, 9 Feb 2020 22:27:49 -0500
Message-ID: <CAHiu4JOMfY2oZb1TG5Lbbyb=Wd09+Ju9fOcBU5VcvmvmCQ7_ZQ@mail.gmail.com>
To: iot-onboarding@ietf.org
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/iot-onboarding/nhPu4DT6wQlkgBV5wLULURnGhVA>
Subject: [Iot-onboarding] RFC 8366: voucher artifact error in example?
X-BeenThere: iot-onboarding@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussion of IoT onboarding mechanisms <iot-onboarding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/iot-onboarding>,
<mailto:iot-onboarding-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/iot-onboarding/>
List-Post: <mailto:iot-onboarding@ietf.org>
List-Help: <mailto:iot-onboarding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/iot-onboarding>,
<mailto:iot-onboarding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2020 03:28:28 -0000
Hello,
I am wondering if the format of the example should be
{
"ietf-voucher:voucher-artifact": {
"voucher": {
"created-on": "2016-10-07T19:31:42Z"
......
instead of
{ "ietf-voucher:voucher":
{ "created-on": "2016-10-07T19:31:42Z",
"assertion": "logged",
Based on the yang hierarchy (tree diagram).
I am going by what ygot is producing. I had to change the yang-data to
a container for ygot to work - perhaps this is the reason why the
output is different? Not sure if this is quite right but I thought
I'd just point it out.
Ranga
--
M. Ranganathan
- [Iot-onboarding] RFC 8366: voucher artifact error… M. Ranganathan
- Re: [Iot-onboarding] RFC 8366: voucher artifact e… Michael Richardson
- Re: [Iot-onboarding] RFC 8366: voucher artifact e… Kent Watsen
- Re: [Iot-onboarding] RFC 8366: voucher artifact e… Michael Richardson
- Re: [Iot-onboarding] [Anima] RFC 8366: voucher ar… Kent Watsen
- Re: [Iot-onboarding] [Anima] RFC 8366: voucher ar… Michael Richardson
- Re: [Iot-onboarding] [Anima] RFC 8366: voucher ar… Kent Watsen