Folks, While you may be going through the requirements doc, I compiled a list of requirements from the doc to facilitate the discussion. I found some minor points to be fixed which I added comments in the list. Please take a look at the attached list. I made it with excel to make it easier to maintain the list. If anybody find it difficult to view it, please let me know. -Keisuke Keisuke Fukui wrote:

Folks,

I'd like to restart a discussion on the strawman requirements for ACS after the holiday break. Please take a look at the document attached to the last message and give us a feedback. You can pick any one of the issues/questions you have.

Thanks in advance!

P.S. We are still waiting for the approval of the ACS-WG from the GGF office.

-Keisuke

Keisuke Fukui wrote:

...

Hello Folks,

We are now in a waiting state for the approval of the WG by GFSG and I hope it will be approved soon. Meanwhile I'd like move forward the discussion about the ACS.

I think we should refine our requirements on ACS in the draft spec at first. Also, we may proceed creating UML diagrams for the use case and interaction as Mike suggested in his last message. It's already in a Christmas holiday season out there, but we may have busy days next month; GGF13 is scheduled in March and there will be discussions about Solution Installation standard in relation with ACS, too. So let me put the strawman on the table right now for those who are ready for it and carry discussions in January.

Please express your idea, comments, issues or concerns using this paper.

Mike, if you can demonstrate UML diagrams for this strawman or for anything you have in mind, I think it will help us.

-Keisuke