Re: [Anima] Potential Milestones for ANIMA new charter

Hi, Eliot,

As you know, the charter text is different from the milestones. In charter text, we will have a paragraph to describe the BRSKI relevant works. In principle, all BRSKI works, even those have not been mentioned, would be covered. So, BRSKI works, no matter they are listed as milestones or not, are in WG scope.

Milestones are these work items that WG MUST deliver in a limited time, say a year or one and half years. So, as WG chairs, we would like to have a shorter list for each period, for which every work item has enough energy to complete in time. This is also IESG would like to see. We could easily add milestones later when the WG had shown enough interests and energy for new in-scope works.

“+ One BRSKI document” means newly adopt one more BRSKI document. The reason that we do not want too many new BRSKI document immediately is that the WG need energy to guarantee the current adopted BRSKI works, including the main BRSKI document and constrained voucher, to be completed as soon as possible with high quality.

Regards,

Sheng

From: Eliot Lear [mailto:lear@cisco.com]
Sent: Friday, March 15, 2019 11:18 PM
To: Sheng Jiang <jiangsheng@huawei.com>
Cc: Toerless Eckert <tte@cs.fau.de>; Toerless Eckert <toerless.eckert@huawei.com>; anima@ietf.org
Subject: Re: [Anima] Potential Milestones for ANIMA new charter

Hi Sheng,

Forgive me, but I believe that the charter text above the milestones needs a touch up.  I also see somewhere around six drafts worth of BRSKI work coming down the pike on their own.  They are:

  *   draft-ietf-anima-constrained-voucher
  *   draft-ietf-anima-contrained-voucher
  *   draft-fries-anima-brski-async-enroll
  *   draft-lear-eap-teap-brski
  *   draft-vanderstok-anima-constrained-join-proxy
  *   draft-richardson-anima-smarkarklink

And I expect that draft-lear-brski-pop will live to see another day.

Now it may be the right thing to split off this work into a separate WG, or it may be the right thing to continue in ANIMA.  I expect that some of the above can also consolidate, but there’s still a lot of work to be done, and cramming all of that into one draft would be inadvisable ;-)

Eliot

On 15 Mar 2019, at 07:51, Sheng Jiang <jiangsheng@huawei.com<mailto:jiangsheng@huawei.com>> wrote:

Hi, Toerless,

I am working on the charter text. It is not difficult to categetied the work items into 4 classes: ANI+, ASA, BRSKI, Use cases. I am intending to put NOCs into ANI+. I will send you a reword version on next Monday.

For milestones, giving that we have a long document waiting list as long as 20. It would not sufficient to satisfy everyone for just 5 milestones by saying everyone should have no more than one document through. We would face more than 10 individuals asking for adoption. Anyway, here are my choice for the first 5:

ASA Lifecycle (Lucent)
ASA guideline (Brian C)
GRASP Distribution (Bing Liu)
Constrained Join Proxy for Bootstrapping Protocols (Michael R.)
+ One BRSKI document

This would looks good when we face IESG. Then, we may able to adopt 2 or 3 more document out of written milestones, I guess. But it would looks bad if we have more than 10 WG document parallel. PS: we still have 7 WG documents showing now, though 3 of them passed IESG review and waiting by MISREF – ACP!

Cheers,

Sheng
_______________________________________________
Anima mailing list
Anima@ietf.org<mailto:Anima@ietf.org>
https://www.ietf.org/mailman/listinfo/anima