* Figure 7 makes no sense. This appears to be mapping a string to a keyed
object. I think however, that the error here is used as a value not a key.
* Is there a recommendation for behavior if a new item is posted to the
authz-info endpoint which has the same key id as a previous one? I can
thi
On 2017-06-24 02:00, Jim Schaad wrote:
* Figure 7 makes no sense. This appears to be mapping a string to a keyed
object. I think however, that the error here is used as a value not a key.
Indeed that figure needs clarification. The errors are values not keys.
* Is there a recommendation f
Hi Ludwig,
Ludwig Seitz writes:
> On 2017-06-24 02:00, Jim Schaad wrote:
>> * We communicate the profile to be used to the client, however it is not
>> currently being communicated to the server. If the server wants to keep the
>> OSCOAP and DTLS keys separate, this needs to be done. Does it
On 2017-07-24 13:36, Olaf Bergmann wrote:
Hi Ludwig,
Ludwig Seitz writes:
On 2017-06-24 02:00, Jim Schaad wrote:
* We communicate the profile to be used to the client, however it is not
currently being communicated to the server. If the server wants to keep the
OSCOAP and DTLS keys separa
Ludwig Seitz writes:
> If you replace "server" with "RS" in my previous comment does it make
> more sense?
Sorry, my fault! Forget my comment.
Grüße
Olaf
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace
