
Alan, Hiro: I agree with the approach you're taking. Having a draft charter in advance of the BOF is probably the best way to build interest and focus the discussion. As Hiro notes, you should follow the charter format in GFD-C.3 including the 7 questions. Though you may not be able to complete all the info until after the BOF. I have a few thoughts you may want to consider: 1. The identified deliverables are both very research oriented. The implication is that this work is necessary for you to determine what, if any, standards work might be required in this area. If that's the case, then should this initial effort be done in an RG rather than a WG? 2. I think you should add a list of the key documents that will guide the work under #1 below. It seems critically important to establish the OGSA authentication requirements and the highest priority use cases/scenarios. If you feel this has been adequately addressed, then the appropriate doc(s) should be referenced. It not, then writing such a doc should be part of this deliverable. It pretty hard to decide what authZ profile may be missing or incomplete without that. 3. I would agree that #3 below is more of an exit criteria. If this work is successful, I would expect to see a new charter to developed one or more recommendations. Regards, Blair Dillaway
-----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Monday, October 23, 2006 7:29 PM To: Alan Sill Cc: ogsa-wg WG; David Groep; Blair Dillaway Subject: Re: URL for OGSA-AuthN-WG charter (URL for OGSA-WG charter)
Thanks Alan,
I agree to have charter BoF at OGF19 in order to complete WG creation. Thus I prefer to bring draft charter including concrete deliverables and detailed milestones (and use BoF session to adjust or improve them).
The following is my thoughts off the top of my head.
1) Review existing security profiles resulting from previous efforts of the Security area and security design group from the OGSA-WG effort
a) Compare them to existing technology and best practices in the community and check for consistency of coverage
b) Document authentication profiles that may be missing or incomplete
c) Review mature and maturing technologies likely to affect the above best practices for grid services
The above topics will end up to "OGSA AuthN Community Practice document (GFD-C)."
2) Provide an AuthN development roadmap to compare with the overall OGSA roadmap
This should also include OGSA Authentication architecture and will be informational document (GFD-I).
3) Spawn any subgroups and/or suggest associated research groups that may be necessary for consistent development in this area.
Since it is not output document. It may be optional or a part of exit strategy.
Since this is working group, you also need to answer the following 7 questions.
-------------------------------------------------------------------- The Seven Questions
1. Is the scope of the proposed group sufficiently focused?
2. Are the topics that the group plans to address clear and relevant for the Grid research, development, industrial, implementation, and/or application user community?
3. Will the formation of the group foster (consensus-based) work that would not be done otherwise?
4. Do the group's activities overlap inappropriately with those of another OGF group or to a group active in another organization such as IETF or W3C? Has the relationship, if any, to the Open Grid Services Architecture (OGSA) been determined?
5. Are there sufficient interest and expertise in the group's topic, with at least several people willing to expend the effort that is likely to produce significant results over time?
6. Does a base of interested consumers (e.g., application developers, Grid system implementers, industry partners, end-users) appear to exist for the planned work?
7. Does the OGF have a reasonable role to play in the determination of the technology?
Thanks, ---- Hiro Kishimoto
Alan Sill wrote:
Comments: BOF at GGF 19 can be used to set deliverables and provide detailed milestones for this work group.
Leadership and charter should be reviewed by new Security Area Directors.
http://www.ggf.org/gf/group_info/charter.php?review&group=OGSA-AuthN-W
G
Alan Sill TIGRE Senior Scientist High Performance Computing Center TTU
==================================================================== : Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 : : e-mail: Alan.Sill@ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================
-- ogsa-wg mailing list ogsa-wg@ogf.org http://www.ogf.org/mailman/listinfo/ogsa-wg