[Ace] EST over CoAP PKCS#10 encoding

2017-03-30 Thread Julien Vermillard
Hi, I'm currently implementing EST over CoAP. I wonder why, on simple enrollment, the payload is put in a CBOR binary string? I understand why dropping base64, but just putting the PKCS#10 binary in the CoAP payload is technically enough. What is the benefit of CBOR encapsulation? BTW you have a

Re: [Ace] EST over CoAP PKCS#10 encoding

2017-03-30 Thread peter van der Stok
HI Julien, Julien Vermillard schreef op 2017-03-30 09:08: Hi, I'm currently implementing EST over CoAP. Great, that is good news. I wonder why, on simple enrollment, the payload is put in a CBOR binary string? I understand why dropping base64, but just putting the PKCS#10 binary in the CoA

Re: [Ace] EST over CoAP PKCS#10 encoding

2017-03-30 Thread Julien Vermillard
Hi, Thanks for your answer. I think content negotiation should be done using the Content-Format option like other CoAP based protocols. And would also match the HTTP way to do it. -- Julien Vermillard On Thu, Mar 30, 2017 at 4:16 PM, peter van der Stok wrote: > HI Julien, > > > Julien Vermilla

Re: [Ace] EST over CoAP PKCS#10 encoding

2017-03-30 Thread peter van der Stok
Hi, Right, will look into it. The github address is: https://github.com/SanKumar2015/EST-coaps Peter Julien Vermillard schreef op 2017-03-30 09:23: Hi, Thanks for your answer. I think content negotiation should be done using the Content-Format option like other CoAP based protocols. And would