[Anima] My comments about : draft-richardson-anima-voucher-delegation-01

"Yangjie (Jay, IP Standard)" <jay.yang@huawei.com> Tue, 30 June 2020 12:03 UTC

Return-Path: <jay.yang@huawei.com>
X-Original-To: anima@ietfa.amsl.com
Delivered-To: anima@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id BBB963A07AA for <anima@ietfa.amsl.com>; Tue, 30 Jun 2020 05:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id M7t5-0vjVcZv for <anima@ietfa.amsl.com>; Tue, 30 Jun 2020 05:03:20 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 105DC3A07A5 for <anima@ietf.org>; Tue, 30 Jun 2020 05:03:20 -0700 (PDT)
Received: from lhreml724-chm.china.huawei.com (unknown []) by Forcepoint Email with ESMTP id EEB60B1CD166CCCD5959; Tue, 30 Jun 2020 13:03:16 +0100 (IST)
Received: from nkgeml706-chm.china.huawei.com ( by lhreml724-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 30 Jun 2020 13:03:15 +0100
Received: from nkgeml704-chm.china.huawei.com ( by nkgeml706-chm.china.huawei.com ( with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Tue, 30 Jun 2020 20:03:13 +0800
Received: from nkgeml704-chm.china.huawei.com ([]) by nkgeml704-chm.china.huawei.com ([]) with mapi id 15.01.1913.007; Tue, 30 Jun 2020 20:03:13 +0800
From: "Yangjie (Jay, IP Standard)" <jay.yang@huawei.com>
To: Michael Richardson <mcr@sandelman.ca>
CC: "anima@ietf.org" <anima@ietf.org>
Thread-Topic: My comments about : draft-richardson-anima-voucher-delegation-01
Thread-Index: AdZOw4Y4FeGqxEZ1SS6icxY5jL+EVw==
Date: Tue, 30 Jun 2020 12:03:13 +0000
Message-ID: <c0b9640b000646698804adc2a45efc41@huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_c0b9640b000646698804adc2a45efc41huaweicom_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/anima/JRwYHvRi8gyMWcIH7osLcoc276A>
Subject: [Anima] My comments about : draft-richardson-anima-voucher-delegation-01
X-BeenThere: anima@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Autonomic Networking Integrated Model and Approach <anima.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/anima>, <mailto:anima-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/anima/>
List-Post: <mailto:anima@ietf.org>
List-Help: <mailto:anima-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/anima>, <mailto:anima-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Jun 2020 12:03:22 -0000

Hi, Michael,

Resale scenario for IoT device are very common in market. So the delegated voucher solution is very practical.

And here, I have a question to ask for you:

If the pledge may have several intermediates, then whether need to list their identities in this pledge's voucher at the same time?
If yes, how to process the multiple CA reference? For example as the following:
One customer bought two batch of pledges from two different intermediates, so for the same operator, they are no difference.
But if for some reason, one pledge fail to get its voucher, maybe one intermediate forget set the right voucher, then how the operator confirm which intermediate fail?
I don't know whether there are available solution.  Thanks.

Certainly, if WG give some feedback for this, it will better.

Best Regards,