- acs-wg - lists.ogf.org

RE: [acs-wg] Agenda for the Call on Aug 24 Wed 20:00 EDT/Aug 25 Thu 9:00 JST
by Ziu, Peter 24 Aug '05

24 Aug '05

My appologies Keisuke and group, I will not be able to attend the meeting. Pete -----Original Message----- From: owner-acs-wg(a)ggf.org [mailto:owner-acs-wg@ggf.org] On Behalf Of Keisuke Fukui Sent: Wednesday, August 24, 2005 5:58 AM To: acs-wg(a)ggf.org Subject: [acs-wg] Agenda for the Call on Aug 24 Wed 20:00 EDT/Aug 25 Thu 9:00 JST Folks, Here is an agenda for the call tomorrow. See you there! * Watch out for the irregular call number. Dial-in Number: **** 1-605-528-8800 (Hartford, SD) **** ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. OGSA F2F updates (10 min) Find action items. 3. Data transport with SOAP. (10 min) Discussion toward the ARI spec. See the previous post from me titled as "Data transport with SOAP". 4. Schedule for drafting a specification (5 min) Check the status for the schedule. 5. GGF15 DEADLINEs and sessions (5 min) The DEADLINE for submitting working drafts for GGF15 is Friday, 26 August 2005. The DEADLINE for scheduling requests for WG/RGs is Friday, 2 September 2005. We can send the latest working draft and update by GGF15. Check the proposals for sessions. See my previous post on Aug 17 in Japan time. 6. Updates (5 min) If any others,... 7. Wrap up, Next meeting(5 min) Total: 45 min ### Logistics for the call Date & Time: Aug 24 Wed 20:00 EDT/Aug 25 Thu 9:00 JST Dial-in Number: 1-605-528-8800 (Hartford, SD) Participant Access Code: 7771111 P.S. I got a regrets from Sachiko for this call. -Keisuke

1 0

[Fwd: BOUNCE acs-wg@ggf.org: Non-member submission from ["Stephen Davey" <sdavey@nesc.ac.uk>]]
by Keisuke Fukui (on the road) 15 Aug '05

15 Aug '05

Forwarding a bounced-email regarding to ogsa-data. -Keisuke

1 0

RE: [ogsa-d-wg] [acs-wg] Data Use Case Scenarios document
by Stephen Davey 15 Aug '05

15 Aug '05

Hi Michael, Thanks for the email. The Data Use Case Scenarios document is just an early draft at this stage and so is not yet on the OGSA Data WG site (I don't think). But we are hoping to add more scenarios to it over the next few weeks and months. However, since the document might well be a "work in progress" for quite a while, it would probably be a good idea if a version is put on GridForge fairly shortly. I intend to do a bit more work on it over the next couple of weeks, so will try to put a version on GridForge at the beginning of September. Cheers, Stephen. -----Original Message----- From: Michael Behrens [mailto:behrens@r2ad.com] Sent: 10 August 2005 01:39 To: Stephen Davey Cc: ogsa-d-wg(a)ggf.org; acs-wg(a)ggf.org Subject: Re: [ogsa-d-wg] [acs-wg] Data Use Case Scenarios document Albiet a bit late, I just read the use-case document - looks good. With regard to replication, it seems that the ACS-WG might need to consider that portion so I'm also CC'ing this to the ACS team. I presume the use-case is available from the OGSA-D-WG site. Thanks! Stephen Davey wrote: >Hi everyone, >Attached is the beginnings of a list of Data Use Case Scenarios, which >also includes the template sub-sections for each use case described. > >I have basically taken the original OGSA use case template and merged >the "Use Case Situation Analysis" section into the "Summary" section 2.1 >and renamed section 2.4 slightly. I have also deleted sections 2.5 & 2.6 >since security and performance considerations will be part of the Data >Architecture document and would probably have just led to repetition. >This then leaves the sections: >2.1 Summary >2.2 Scenarios >2.3 Involved Resources >2.4 Functional Design >2.5 References > >Hopefully these sections will be all that is needed for the Data >(infrastructure) Use Cases that we have. >Any comments can be discussed on Wednesday 15th June. > >Cheers, >Stephen. > >------------------------------------------------------------------- >Stephen Davey, NextGrid Software Architect, >National e-Science Centre, >15 South College St., Edinburgh, EH8 9AA, UK >Tel: +44 131 6 509820 > -- Michael Behrens R2AD, LLC Cell: 571-594-3008 --------------090800040909030808080200--

1 0

Teleconference minutes - June 15
by Sachiko Wada 15 Aug '05

15 Aug '05

Hi team, Here is the minutes of the last teleconf. Please review it and point out where the record is not correct, if any. It is also available at Gridforge: https://forge.gridforum.org/projects/acs-wg/document/minutes-20050810/en/1 Sachiko ====================================================================== ACS Teleconference ----------------------------------------------------------------------- Date and Time: August 10 20:10-21:40 EDT 2005 / August 11 9:10-10:40 JST, 2005 Participants: Keisuke Fukui (Fujitsu) Tom Studwell (IBM) Peter Ziu (Northrop) Michael Behrens (R2AD) Sachiko Wada (ASCADE) - minutes ------------------------------------------------------------------------ * Review of the minutes of day 2 for F2F Minutes approved. * Data replication use case We glanced over the replication use case of OGSA-D. It seems that there are no conflicts between OGSA-D and ACS. We should learn data area specs, including another relevant WG such as ByteIO, so that ACS can get along with those specs. We continue this discussion on the ml. * Security updates We agreed on the basic security policy of ACS as Keisuke summarized in the previous post on Aug 10 JST. ------------------------------------------------------------------- - We may simply specify to reserve an extension point for access constraint information, such as XACML, in AAD. Optionally, we may describe our considerations as an informational part demonstrating how this can be utilized. - We will not specify the security features for ARI (SOAP message exchange) since this should be covered by existing standard spec or profile. We will refer to the external relevant specs or profiles, such as OGSA Basic Profile. - We may include description about the *optional* AA signature, in consideration mainly for when AA Document is handled out of secured path. Though we may define the range of contents that the signature will cover, the technologies to be used for signature, such as an XML signature or signature used in Jar file, may be left unspecified or just listed as candidates. - Authentication detail is up to the security entity in the system, both for specification and for design. The implementation of ACS may have interface to it, but the ACS specification will not specify it. (example interaction may be demonstrated as an informational description.) - ACS implementation can be one of the security PEP in the system, in a sense it may accept or reject the service request to the repository, depending on the Authorization Decision Assertion returned from the Policy Decision Point, which I assume the security entity (or service) in the system is. ACS may simply match the security token presented in the request (in a SOAP header part) and the Assertion, in order to enforce the policy. ------------------------------------------------------------------- Mike mentioned that ByteIO covers security issues in moving around files and we may find an input from it. Action: Mike, to look down into the ByteIO. * Meta data discussion The proposal from Keisuke and Sachiko is to sort out meta data for AA into two classes. It includes the below information for each: a) Static description for the AA, for example, - File list of the Application Contents with key information for GetContents. (REQUIRED) - AA Identifier, which contains name of the AA and version information. (REQUIRED) - Access control policy for each Application Content. (OPTIONAL) (Can be a pointer to actual file in ACs.) - Human-readable description of the AA (OPTIONAL) - Extension point, i.e. xsd:any (OPTIONAL) b) Live meta data that can be dynamically augmented by ACS repository. - Owner of the the AA instance (OPTIONAL ? ) This may be retrieved from the security token in the SOAP header or Create parameter (administrative information) in case of this process is done by the proxy service. - Creation datetime of the AA instance (REQUIRED) - Change history information for the AA instance. The static description may be augmented by ACS in the resource property of the AA instance. It may depend on what it is for. We continue this discussion on the ml. * Schedule for drafting a specification We agreed on the proposed TOC with some modification and made assignment of some of the sections. The proposed schedule is an aggressive one and we may need adjustment depending on the progress. Action: Keisuke, to post the latest TOC with the name in charge on the ml. (Done on Aug 11 JST) * Updates (NAREG PSE) Keisuke posted NAREGI PSE diagram on Aug 3 JST, which confirms that there is not issues between our spec. and their design. No issues or questions were raised. * Wrap up, Next meeting We agreed that we will skip the call for next week. Date: Aug 24 Wed 20:00 EDT/Aug 25 Thu 9:00 JST Calling #: will be announced later NOTE: Next regular meeting will be skipped.

1 0

Proposed detailed TOC of the spec.
by Keisuke Fukui 15 Aug '05

15 Aug '05

Folks, Attached is an proposed TOC of the spec. with more detail sections inserted considering the latest status of the discussion. Please comment on this. -Keisuke

2 3

Replication discussion material
by Sachiko Wada 12 Aug '05

12 Aug '05

Pete and all, Here is the input material for the replication discussion. The purpose of this document is to examine the feasibility of constructing a replication service on top of ACS. There are the two scenarios: Scenario 1: One-way synchronization, triggered by modification of the master ACS. Scenario 2: Two-way synchronization, triggered periodically. Conclusion: The replication service can work with ACS if it supports the update event notification as far as considering the two scenarios. My impression and proposal: The replicator is supported to be highly sophisticated especially in case of bi-directional synchronization. So I propose that ACS should provide infrastructural functionalities such as notification mechanism for the outer replication services instead of supporting replication capability by itself. This time I examined two scenarios to find out that the event mechanism is required to realize them. There may be more replication scenarios which have requirements for ACS spec. For example, the capability to get change histories of an AA should be useful. Your comments are very much welcomed. Sachiko

2 1

***SPAM*** Update your account information
by service＠intl.paypal.com 11 Aug '05

11 Aug '05

1 0

acs - toc
by pete＠ziu.net 11 Aug '05

11 Aug '05

Just captured some comments from the meeting tonight on the outline (toc). Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms)

1 0

ML archive URL
by Keisuke Fukui 11 Aug '05

11 Aug '05

Here is an url for our ML archive. http://www-unix.gridforum.org/mail_archive/acs-wg/threads.html Here is an url for the ogsa-d ML archive. http://www-unix.gridforum.org/mail_archive/ogsa-d-wg/threads.html

1 0

Re: [acs-wg] Agenda for the Call on Aug 10 Wed 20:00 EDT/Aug 11 Thu 9:00 JST
by pete＠ziu.net 11 Aug '05

11 Aug '05

My apologies to my wrong arrangement in wrong day. This should be the real one. The agenda will be posted later. This is the info for the call tonight... Date: Wednesday, August 10, 2005 Start Time: 08:00 PM Eastern Daylight Time End Time: 10:55 PM Eastern Daylight Time Dial-in Number: 1-831-600-1000 (Santa Cruz, California) Access Code: 7771111 Pete Ziu 571.235.0208 (c) mailto:pete@ziu.net (h) mailto:5712350208@tmomail.net (sms) To acs-wg(a)ggf.org cc bcc Subject [acs-wg] Agenda for the Call on Aug 10 Wed 20:00 EDT/Aug 11 Thu 9:00 JST Keisuke Fukui <kfukui(a)labs.fujitsu.com> Sent by: owner-acs-wg(a)ggf.org 08/10/2005 07:19 PM ZE9 <font size=-1></font> Folks, Here is an agenda for the call tomorrow. See you there! * Watch out for the irregular call number. Dial-in Number: **** 1-949-373-0345 (Irvine, CA) **** ### Proposed Agenda 1. Role call, note taker & time keeper, agenda bashing. (5 min) 2. Review of the minutes of day 2 for F2F. (5 min) - Correction and approval for the minutes. 3. Security updates from Aug 3 meeting by Mike (10 min) - We will conclude what needed to be specified as a normative part in ACS. See more detail in my previous post on this. Date: Wed, 10 Aug 2005 19:01:59 +0900 (Japan time) - Does it confirm our understanding at Aug F2F? 4. Data replication use case (10 min) - Does the use case presented by OGSA-DATA WG go with our specifications? If it does, what is potentially missing in our specification? Please refer to my previous post on this in reply to Pete's message. Date: Wed, 10 Aug 2005 18:13:50 +0900 (Japan time) - Review the data replication diagram to be posted by Sachiko. 5. Schedule for drafting a specification (10 min) - Proposed schedule attached. - Who can contribute to what part in drafting? 6. Updates (10 min) Questions and Answer for the NAREGI PSE diagram (posted by KF on Aug. 3 JST). If any others,... 7. Wrap up, Next meeting(5 min) Sachiko and I cannot make it for next week. Can we skip the one for next week? Total: 55 min ### Logistics for the call Date & Time: Aug 10 Wed 20:00 EDT/Aug 11 Thu 9:00 JST Dial-in Number: 1-949-373-0345 (Irvine, CA) Participant Access Code: 7771111 -Keisuke - 20050810ACS_Schedule.xls

1 0