Folks,
The authors of this draft have informed me this document is required by the wg
charter. So, I withdraw any criticisms about this document's limited scope. The
scope was dictated by the charter.
Ron
> -Original Message-
> From:
> On Dec 7, 2015, at 1:31 PM 12/7/15, Stephane Bortzmeyer
> wrote:
>
> On Tue, Dec 01, 2015 at 01:55:46PM +,
> Ralph Droms (rdroms) wrote
> a message of 128 lines which said:
>
>> Would you consider adding a little text somewhere to make it clear
>>
Mike proposes the following:
"Using "crit" with "b64"
If a JWS using "b64" with a value of "false" might be processed by
implementations not implementing this extension, then the "crit" Header
Parameter MUST be included with "b64" in its set of values to cause such
implementations to
Thanks for your review, Alexey!
Authors, what say you?
Jari
On 15 Dec 2015, at 14:23, Alexey Melnikov wrote:
> I deleted an incorrect recipient in my original review. Sorry about that.
>
>> On 15 Dec 2015, at 11:19, Alexey Melnikov
Mike,
draft-ietf-jose-jws-signing-input-options-08 says:
if used in environments in which all participants implement this extension,
then "crit" need not be included
The clash here is whether such "environments" are reality, and if they are the
audience of this IETF spec.
This sentence
> On Dec 13, 2015, at 4:44 PM, Elwyn Davies wrote:
>
> 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
James, as I see it, your proposal optimizes the Header Parameter requirements
for the case in which the JWS isn't useful, rather than case in which it is.
This seems backwards, from an engineering point of view.
The new "crit" language in -08 already ensures clean failure in all the cases
in
Thanks for your thoughtful comments, Robert. Replies are inline below...
> -Original Message-
> From: Robert Sparks [mailto:rjspa...@nostrum.com]
> Sent: Monday, December 14, 2015 5:12 PM
> To: Mike Jones ; General Area Review Team
> ;
Hey Richard,
See my reply to Robert and the language being added to the spec. I believe
that the text requiring "crit" in all situations other than when it adds no
value should address the point you're making.
Best wishes,
--
Hi Matt,
Thank you for your review! The editors will take these comments into
consideration and discuss any updates. I'll note that the draft was
pulled from the telechat and will likely not go through last call
again until sometime around Buenos Aires due to some other changes
that came up.
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 Jim,
Please see my replies to Robert and Richard. I believe they cover the point
you're making below.
-- Mike
-Original Message-
From: Jim Schaad [mailto:i...@augustcellars.com]
Sent: Monday, December 14, 2015 10:42 PM
To: Mike Jones
Matt
Thanks for the great review. As Kathleen mentioned, there are some other
changes we have to make that will push the draft back. Never-the-less I will
take into account all the reviewer comments in the next draft.
All your comments seem very reasonable to me.
Thanks,
Phil
> On Dec 17,
Thanks for your review, Brian. I propose:
We note that [I-D.chen-ippm-coloring-based-ipfpm-framework] proposes
a method similar to [I-D.tempia-opsawg-p3m], as ippm-list discussion
revealed.
hope that does it,
Al
> -Original Message-
> From: Brian E Carpenter
Hi Ralph,
Thank you for your review. Sorry I missed it earlier.
On 09/12/2015 20:47, Ralph Droms (rdroms) wrote:
Nits/editorial comments:
Nicely written, very clear document.
Thank you.
idnits reports some lines too long and an unused reference.
I fixed the reference in my copy. I hope RFC
> On Dec 16, 2015, at 10:47 AM 12/16/15, Alexey Melnikov
> wrote:
>
> Hi Ralph,
> Thank you for your review. Sorry I missed it earlier.
You're welcome. Looks like we have agreement on my editorial comments and
suggestions. Will the edits you mention below appear
16 matches
Mail list logo