Mohit, Kathleen,
I’d suggest editing the current milestones as follows. The edit and schedule
suggestions are based in part on what I think the 3GPP schedules are going
to be. They need some stuff soon (e.g., any fixes to existing EAP-AKA’;
there’s a technical specification with a few paragraphs l
Hi Ben,
And thanks for your feedback.
> First bullet point: "or other new concerns." makes this very open ended. Is
> this planned to be a standing working group? If not, can we put some
> constraints around "other new concerns”?
Understood.
Note that the sentence starts with “Update the securi
Mirja,
> I would actually rather like to see milestones for when the work is supposed
> to
> be finished (send to IESG for publication) than when it is supposed to start
> (wg adoption) as the first is probably harder to achieve in time than the
> second.
I suggested edits to the milestones in a
> "This working group has been chartered to provide updates to some
> commonly used EAP method."
>
> really singular? Or should it be "commonly used EAP methods”?
Uh… a bug. Thanks for the careful read.
For Kathleen:
OLD:
This working group has been chartered to provide updates to some
common
Thanks, Jari, this all looks good to me.
Ben.
> On Feb 18, 2018, at 5:46 AM, Jari Arkko wrote:
>
> Hi Ben,
>
> And thanks for your feedback.
>
>> First bullet point: "or other new concerns." makes this very open ended. Is
>> this planned to be a standing working group? If not, can we put some
