[Acme] new acme draft -- rats identifier and challenge

Hi folks, Recently I submitted a new ACME draft that extends "rats" identifier and challenge type. The purpose of this work is to provide a means that allows an ACME server to test if an ACME client possess a valid remote attestation result (and an identifier to that), before issuing a certific

[Acme] Re: new acme draft -- rats identifier and challenge

I gave the draft a quick skim. I realize it is understood that much work remains but wanted to point out a few terminology issues and perhaps some gaps in the specs that might underpin this mechanism. 1)    That you have different challenge types to sustain the passport model and the

[Acme] Re: new acme draft -- rats identifier and challenge

Hi Peter! Thanks for your submission to the ACME working group. I'll start by admitting I don't really have much background knowledge on RATS so my comments may be mis-informed. Feel free to tell me I got it wrong. I think your draft is a good start - but needs a lot of work. First, some editori

[Acme] Re: [EXTERNAL] Re: new acme draft -- rats identifier and challenge

Hi Peter. I have not reach your draft yet (too-many-draft-overload syndrome). But @Thomas Fossati and I talked at the last IETF meeting about submitting a draft that extends draft-bweeks-acme-device-attest-00 to be more generic by supporting generic CMWs in a si

[Acme] ACME@ietf121: time slot requesting for 1 new ACME draft:

Hi ACME chairs, We would like to request a time slot for presenting 1 new drafts as follows: * Draft(s) to be presented: draft-geng-acme-public-key-00 * Presenter's name and email: Liang Xia, frank.xiali...@huawei.com * Desired duration: 15 minutes