draft-ietf-ace-extend-dtls-authorize
Just reminding other co-authors
.
Yours,
Daniel
On Tue, Mar 15, 2022 at 11:00 AM Olaf Bergmann
mailto:bergm...@tzi.org>> wrote:
Hi Logan and Daniel,
On 2022-02-28, Daniel Migault mailto:mglt.i...@gmail.com>>
wrote:
> For all co-authors, please
Just reminding other co-authors
.
Yours,
Daniel
On Tue, Mar 15, 2022 at 11:00 AM Olaf Bergmann wrote:
> Hi Logan and Daniel,
>
> On 2022-02-28, Daniel Migault wrote:
>
> > For all co-authors, please provide an IPR statement and let us
> > know of any known implementations.
>
> I am not aware
Hi Logan and Daniel,
On 2022-02-28, Daniel Migault wrote:
> For all co-authors, please provide an IPR statement and let us
> know of any known implementations.
I am not aware of any IPR related to this document.
Our implementation (WIP) at [1] supports CoAP transport over DTLS
and TLS using
Hi Marco,
On 2022-03-04, Marco Tiloca wrote:
> On 2022-03-04 13:04, Olaf Bergmann wrote:
> Maybe this text?
>
> "... as unsupported ACE profiles. If the Client is modified
> accordingly or it learns that the Resource Server has been, the Client
> may try to connect to the Resource Server using
Hi Marco,
thanks again for the quick response. I will add your suggested
change and submit a new version.
Grüße
Olaf
On 2022-03-04, Marco Tiloca wrote:
> Hi Olaf,
>
> On 2022-03-04 13:04, Olaf Bergmann wrote:
>> Hi Marco,
>>
>> On 2022-03-03, Marco Tiloca wrote:
>>
>>> Thanks! It looks good
Hi Olaf,
On 2022-03-04 13:04, Olaf Bergmann wrote:
Hi Marco,
On 2022-03-03, Marco Tiloca wrote:
Thanks! It looks good overall, please see below some suggestions.
Thanks. I have merged the changes into the main branch together with
the changes proposed in this email (see Editor's copy [2]).
Hi Marco,
On 2022-03-03, Marco Tiloca wrote:
> Thanks! It looks good overall, please see below some suggestions.
Thanks. I have merged the changes into the main branch together with
the changes proposed in this email (see Editor's copy [2]).
More comments inline.
[2]
Hi Olaf,
Thanks! It looks good overall, please see below some suggestions.
* s/connect the Resource Server/connect to the Resource Server
* "SHOULD be prepared that no communication channel with the Resource
Server can be established"
Suggested alternative text: "might fail in
Hi Marco,
as you have suggested before, I have now included more test in
draft-ietf-ace-extend-dtls-authorize that elaborates on the caveats
of session establishment for the extended DTLS profile.
Please see [1] for the new text. (To use keywords from BCP14 and ACE
terminology, I also had to add
This email closes the WGLC.
If anyone is willing to shepherd the document please let us know. For all
co-authors, please provide an IPR statement and let us know of any known
implementations.
Yours,
Logan and Daniel
On Fri, Feb 18, 2022 at 9:22 AM Olaf Bergmann wrote:
> Marco,
>
> Thanks. I
Marco,
Thanks. I have removed the reference to DTLS1.3 and will propose
text to address the interoperability issues asap.
Grüße
Olaf
On 2022-02-18, Marco Tiloca wrote:
> Please, see my replies inline (trimming the solved points)
>
>
> On 2022-02-18 13:42, Olaf Bergmann wrote:
>> Hi Marco,
>>
Hi Olaf,
Thank you for the quick update!
Please, see my replies inline (trimming the solved points)
On 2022-02-18 13:42, Olaf Bergmann wrote:
Hi Marco,
thanks for the thorough review. I have done most of the suggested
updates (see Editor's copy [1]).
Just a few comments and questions
Thanks for the review and fast response.
Yours,
Daniel
On Fri, Feb 18, 2022 at 7:42 AM Olaf Bergmann wrote:
> Hi Marco,
>
> thanks for the thorough review. I have done most of the suggested
> updates (see Editor's copy [1]).
>
> Just a few comments and questions inline.
>
> [1]
>
Hi Marco,
thanks for the thorough review. I have done most of the suggested
updates (see Editor's copy [1]).
Just a few comments and questions inline.
[1]
https://ace-wg.github.io/ace-extend-dtls-authorize/draft-ietf-ace-extend-dtls-authorize.html
On 2022-02-18, Marco Tiloca wrote:
>
Hi all,
Please, see below my WGLC comments.
Best,
/Marco
[General]
* In the document header, "Network Working Group" should be replaced by
"ACE Working Group".
* Looking at the phrasing in Section 2 of draft-ietf-ace-dtls-authorize,
it would be more consistent to use "Extension of the
Hi all,
This email starts a WGLC for Extension of the ACE CoAP-DTLS Profile to TLS.
If you think the document is ready or have any comments please indicate it
by Feb 22 on the mailing list.
The document is available here:
https://datatracker.ietf.org/doc/draft-ietf-ace-extend-dtls-authorize/
16 matches
Mail list logo
