Hi Stewart,
Thank you very much for your comments.
Answers to your comments are inline below with prefix [HC].
Would you mind reviewing them to see if they address the issues?
Best Regards,
Huaimo
-Original Message-
From: Stewart Bryant [mailto:stewart.bry...@gmail.com]
Reviewer: Peter Yee
Review result: Ready with Issues
I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair. Please treat these comments just
like any other last call comments.
For more
Hi Qin, see in line:
On 24/02/2018 04:16, Qin Wang wrote:
> Hi Brian,
> Thank you very much for your comments. Please see inline.
>
> On Monday, February 19, 2018 6:22 PM, Brian Carpenter
> wrote:
>
> Reviewer: Brian Carpenter
> Review result: Ready with Issues
Dear Authors,
Now that Last Call for this draft has ended, could you folks take a look at
Dale's comments and respond?
Thanks!
Spencer, as responsible AD
On Mon, Feb 19, 2018 at 11:30 AM, Dale Worley wrote:
> Reviewer: Dale Worley
> Review result: Ready with Issues
>
> I
I am the assigned Gen-ART reviewer for this draft. The General Area Review Team
(Gen-ART) reviews all IETF documents being processed by the IESG for the IETF
Chair. Please treat these comments just like any other last call comments.
For more information, please see the FAQ at
Hi Brian,
Thank you very much for your comments. Please see inline.
On Monday, February 19, 2018 6:22 PM, Brian Carpenter
wrote:
Reviewer: Brian Carpenter
Review result: Ready with Issues
Gen-ART Last Call review of draft-ietf-6tisch-6top-protocol-09
I am
Yes, that is what I was looking for.
Thank you,
Joel
On 2/23/18 9:38 AM, Göran Selander wrote:
How about this (see the last and third to last edit):
https://github.com/core-wg/oscoap/commit/8f277d83
where the reference is made to COSE instead of AEAD?
Best
Göran
On 2018-02-23 15:32, "Joel
How about this (see the last and third to last edit):
https://github.com/core-wg/oscoap/commit/8f277d83
where the reference is made to COSE instead of AEAD?
Best
Göran
On 2018-02-23 15:32, "Joel Halpern Direct"
wrote:
>I guess it is up to you. Personally, I like
I guess it is up to you. Personally, I like the idea of the verify
description including some reference to how one actually does verify.
I will leave it to the authors and WG to decide what degree of clarity
is called for here.
Yours,
Joel
On 2/23/18 9:30 AM, Göran Selander wrote:
Hi Joel,
Hi Joel,
Thanks for quick feedback, inline.
On 2018-02-23 14:59, "Joel M. Halpern" wrote:
>In terms of my concerns, if Step 7 said "Verify and Decrypt the COSE
>object using the Recipient Key as per RFC 5116 Section 2.2" that would
>fill in the confusion for this reader.
In terms of my concerns, if Step 7 said "Verify and Decrypt the COSE
object using the Recipient Key as per RFC 5116 Section 2.2" that would
fill in the confusion for this reader.
Yours,
Joel
On 2/23/18 5:26 AM, Göran Selander wrote:
Hi Joel,
Thanks for your review. Comments inline.
On
Hi Joel,
Thanks for your review. Comments inline.
On 2018-02-22 04:51, "Joel Halpern" wrote:
>Reviewer: Joel Halpern
>Review result: Ready with Nits
>
>I am the assigned Gen-ART reviewer for this draft. The General Area
>Review Team (Gen-ART) reviews all IETF documents
12 matches
Mail list logo