- ogsa-wg - lists.ogf.org

Updated: OGSA Teleconference
by Andreas Savva 27 Nov '06

27 Nov '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061127T220000Z DTEND:20061128T000000Z TRANSP:OPAQUE SEQUENCE:2 UID:040000008200E00074C5B7101A82E00800000000D05E9F6D1612C7010000000000000000100 00000AB610ADED6AE0947A689DCF91A3B9530 DTSTAMP:20061127T024223Z DESCRIPTION:When: 2006年11月28日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Nov. 27th\nMonday from 4pm to 6pm (CST).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1127\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Nov. 6)\n - https://forge.gridforum.org/sf/go/doc14002\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) OGSA roadmap v1.1 update (Chris Jordan\, 20 min)\n revised draft review\n\n3) F2F and SC06 debriefing (20 min)\n Feedback and impression on F2F and SC06.\n Minutes approval\n\nDocuments>Meeting Materials...>Interim Meetings>OGSA-16 - 2006 Nov\n\n If you have not yet upload your materials\, please\n do so before the call.\n\n4) OGSA secure channel document final review (Takuya Mori\, 30 min)\n\n> Takuya has updated the SP - Secure Channel profile as we discussed in the\n> Nov 2 conference call and has uploaded it onto GridForge.\n> \n> OGSA Security Profile 1.0 - Secure Channel:\n> https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg /docman.root.working_drafts.security_profile_1_0/doc13560/22\n> \n> The major changes are:\n> - deleted the references to the NIST guideline document\n> - added restrictions to recommend the use of recommended ciphersuites\n> in 3.2.2\n> - added non-normative tables which list some insecure and acceptable\n> ciphersuites in Appendex C\n> \n> P.S.:\n> Takuya has updated the referenced specification tables and have uploaded\n> the revised one.\n> https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg /docman.root.working_drafts.roadmap_1_1/doc13557/4\n\n5) EMS Arch scenarios document review (Andreas Savva\, 30 min)\n\n6) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477\n\nNov. 30 (Thu) Information/data modeling (Ellen and Fred)\n OGSA workflow (Andrew Grimshaw)\nDec. 4 (Mon) <No call> Management Developer Conference\nDec. 7 (Thu) <No call> GFSG F2F meeting\nDec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong)\n Roadmap document (Chris Jordan)\n EMS Arch scenarios document review (Andreas Savva)\nDec. 14 (Thu) Information/data modeling (Ellen and Fred)\n OGSA security (Alan Sill and Andrew Grimshaw)\n OGSA workflow (Andrew Grimshaw)\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Nov. 9 pm F2F.\n AI.11.09.pm-a: Ellen and Tom to write up a "Information Model\n profile document: BES Container"\n AI.11.09.pm-b: Andrew Grimshaw to persuade the BES group that\n the BES spec version used for the interop should\n be the very one that is returned to the ADs to\n get published\n AI.11.09.pm-c: Andrew to produce a document drafting the definition\n of QoS\n AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future\n involvement to create profile(s) on\, e.g. BES\, JSDL\n etc.\n\n > From Nov. 2nd call.\n AI-1102a: Hiro to ask whole group by email if it is OK to have\n one-way (presentation only\, no discussion)\n SML session on future telecon.\n\n > From Oct. 30 call.\n AI-1030a: Ellen will contact the DAIS-WG chairs and request they\n arrange a review DSP0225\n\n > From Sept. 15 OGSA F2F\n AI-0915d: Tom will post BP base faults issue to tracker\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next reference model call (Nov. 20):\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Nov. 27th call
by Hiro Kishimoto 27 Nov '06

27 Nov '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Nov. 27th Monday from 4pm to 6pm (CST). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1127 See more explanation: https://forge.gridforum.org/sf/go/wiki1584 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Nov. 6) - https://forge.gridforum.org/sf/go/doc14002 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA roadmap v1.1 update (Chris Jordan, 20 min) revised draft review 3) F2F and SC06 debriefing (20 min) Feedback and impression on F2F and SC06. Minutes approval Documents>Meeting Materials...>Interim Meetings>OGSA-16 - 2006 Nov If you have not yet upload your materials, please do so before the call. 4) OGSA secure channel document final review (Takuya Mori, 30 min) > Takuya has updated the SP - Secure Channel profile as we discussed in the > Nov 2 conference call and has uploaded it onto GridForge. > > OGSA Security Profile 1.0 - Secure Channel: > https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg/… > > The major changes are: > - deleted the references to the NIST guideline document > - added restrictions to recommend the use of recommended ciphersuites > in 3.2.2 > - added non-normative tables which list some insecure and acceptable > ciphersuites in Appendex C > > P.S.: > Takuya has updated the referenced specification tables and have uploaded > the revised one. > https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg/… 5) EMS Arch scenarios document review (Andreas Savva, 30 min) 6) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477 Nov. 30 (Thu) Information/data modeling (Ellen and Fred) OGSA workflow (Andrew Grimshaw) Dec. 4 (Mon) <No call> Management Developer Conference Dec. 7 (Thu) <No call> GFSG F2F meeting Dec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong) Roadmap document (Chris Jordan) EMS Arch scenarios document review (Andreas Savva) Dec. 14 (Thu) Information/data modeling (Ellen and Fred) OGSA security (Alan Sill and Andrew Grimshaw) OGSA workflow (Andrew Grimshaw) <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Nov. 9 pm F2F. AI.11.09.pm-a: Ellen and Tom to write up a "Information Model profile document: BES Container" AI.11.09.pm-b: Andrew Grimshaw to persuade the BES group that the BES spec version used for the interop should be the very one that is returned to the ADs to get published AI.11.09.pm-c: Andrew to produce a document drafting the definition of QoS AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future involvement to create profile(s) on, e.g. BES, JSDL etc. > From Nov. 2nd call. AI-1102a: Hiro to ask whole group by email if it is OK to have one-way (presentation only, no discussion) SML session on future telecon. > From Oct. 30 call. AI-1030a: Ellen will contact the DAIS-WG chairs and request they arrange a review DSP0225 > From Sept. 15 OGSA F2F AI-0915d: Tom will post BP base faults issue to tracker > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next reference model call (Nov. 20): AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

3 2

BES Comments
by Strong, Paul 24 Nov '06

24 Nov '06

All, I have been attempting to catch up on BES and was reading the v1.0 document. I have some questions and comments. Please note that I have no context from meetings or discussions about BES so please forgive my ignorance, I may be missing important context or details :o) i) Why are there 2 client focused interfaces (3 interfaces in total)? It is very natural for there to be 2 interfaces to a service/component, one focused on delivering client functionality and one for manageability. It is also natural to minimize the number of interfaces and the calls across them so as to aid maintainability. It would appear to me that the difference between the two BES client interfaces is that one allows activities to be created and for collections of activities to be monitored and managed. The other is focused on individual activities, but includes very similar functionality. There seems to be a lot of commonality. What are the reasons for them not being combined? Indeed as I read further I note that BES-Activity exposes no operations, so perhaps this interface is being deprecated and the document is in the process of being edited? ii) Why does the state model not end in one terminated state? Are there any real differences between the 3 enumerated end states other than how the activity ended up in the state? iii) Also it seems somewhat counter intuitive that if one is going to have three termination states, one should end up in the one state which reflects both success and failure (Finished) and a separate one for failures that prevent the activity from exiting in a controlled fashion. It seems like the transitions to the terminated state should be something like - a. Completed Successfully b. Failed c. Cancelled iv) Is there any notion of a retry, given that the state machine captures failure? Or perhaps rescheduling? For example one could imagine additional useful transitions - a. Pending to Pending - i.e. rescheduling b. Running to Pending - i.e. failed/retrying Having these in the base profile or basic model would enable greater flexibility in implementing future profiles where one could request that the BES container implement retries or allow rescheduling. Or are you categorically stating that users will never be able to reschedule or request automatic retries. Again if this is the case, it should probably be explicitly stated. I would actually urge you to make the base specification as broad as possible in terms of the acceptable state changes at this level to avoid unnecessarily constraining yourself down the line. I think this is especially important given what is stated in 4.2. v) Labeling of the state transitions would be most helpful, together with the adoption of standard UML statechart representation. Included is a state transition diagram which includes a few additional transitions which may, or may not be helpful/appropriate. :o) vi) 4.2 - State Specialization really seems to be indicating that this specification makes no assumptions with respect to sub-states that may be incorporated within an implementation but that such sub-states are acceptable as long as they do not introduce new state transitions between the standard, specified states. It would be very helpful to simply state this before all of the examples. vii) Do you expect to extend the BES model to activities that are not binaries running on operating systems? Regards Paul

2 1

Call for papers:DeSeGov 2007- The 2nd International Workshop "Dependability and Security in e-Government"-Submission Deadline 15-12-2006
by Nguyen Manh Tho 24 Nov '06

24 Nov '06

Apologies for multiple copies due to cross postings. Please send to interested colleagues and students) --------------------------------------------------------------------- The 2nd International Workshop "Dependability and Security in e-Government" (DeSeGov 2007) http://desegov.ares-conference.eu/ http://www.ares-conference.eu/conf/ --> Workshop -->DeSeGov --------------------------------------------------------------------- Vienna, April 10 -13 2007 in conjunction with The Second International Conference on Availability, Reliability and Security ( ARES 2007 ) http://www.ares-conference.eu/conf/ Call for Papers --------------- Many governments have now significant e-government applications that offer more and more the day-to-day services to the citizen. ICT infrastructure has become as important as government offices and its officials: crucial for the functioning of the state. Modern government is today dependent on its functioning ICT: the systems must be available, reliable, safe, confidential, integer and secure. The aim of this workshop is to foster a forum for discussing and presenting recent research results on dependability and security in e-Government applications. Scientific rigor and discussions of state of the art of dependability and security in e-Government are strongly encouraged. Besides, innovative research work in progress and studies of dependability aspects of practical e-Government projects and systems implementation are also welcome. Topics of interest include, although not limited to, the following: . Trust and security: provisions and instruments . Online availability of public services . Service survivability and maintainability . Interoperability of services . Security in e-democracy (including e-participation and e-voting) . E-justice (administration and workflow security for legal processes) . Secure federating information access (from different government and third party agencies) . Security and reliability in media integration . Secure e-government and Identity Management . Security and reliability of Smart Card System . Availability and reliability of mobile services . Data protection and data privacy (e.g. e-health and e-education) . Intrusion detection and prevention . Anti-spam legislation and solution . Public-private- partnerships management . Role-based management and usage restriction Important Dates --------------- Submission Deadline: December, 15th 2006 Author Notification: January, 14th 2007 Author Registration: January, 21st 2007 Proceedings Version: January, 21st 2007 Conference/Workshop: April 10-13th, 2007 Submission Guidelines --------------------- The proceedings of this workshop will be published by IEEE. Authors are invited to submit their papers in the IEEE Computer Society Proceedings Manuscripts format (two columns, single-spaced, including figures and references, using 10 fonts, and number each page). The IEEE Computer Society Proceedings Author Guidelines are available at the following web page: URL: http://computer.org/cspress/instruct.htm or http://www.tinmith.net/tabletop2006/IEEE/Format/instruct.htm Submission are classified into 3 categories (1) full paper (8 pages), (2) short paper (5 pages), and (3) poster (2 pages) representing original, previously unpublished work. Submitted papers will be carefully evaluated based on originality, significance, technical soundness, and clarity of exposition. Contact author must provide the following information: paper title, authors' names, affiliations, postal address, phone, fax, and e-mail address of the author(s), about 200-250 word abstract, and about five keywords and register at our ARES website: http://www.ares-conference.eu/conf/. Prepare your paper in PDF or MS Word file and submit it to our site at http://www.ares-conference.eu/conf/ The online submission system will be available at the begining of October 2006. Submission of a paper implies that should the paper be accepted, at least one of the authors will register and present the paper in the conference. Accepted papers will be given guidelines in preparing and submitting the final manuscript(s) together with the notification of acceptance. Publication ----------- All accepted papers (full and short papers) will be published by IEEE Computer Society. Workshop Chairpersons --------------------- A Min Tjoa, Vienna University of Technology, Austria Erich Schweighofer, University of Vienna, Austria Tho Manh Nguyen, Vienna University of Technology, Austria Programme Committee ------------------- Nabil Adam, Rutgers University, USA Jaro Berce, University Of Ljubljana, Slovenia Jean Camp, Indiana University, USA Eugene Christov Nickolov, Sofia University, Bulagaria Matthew J. Dovey, JISC Executive, UK Jos Dumortier, Interdisciplinary Centre for Law & ICT (ICRI), Belgium Dieter Fensel, Deri Innsbruck, Austria Fernando Galindo, University of Zaragoza, Spain Panagiotis Georgiadis, University of Athens, Greece Lepouras Georgios, University of Peloponnese, Greece Dimitris Gouscos, University of Athens, Greece Juris Jon Bing, University of Oslo, Norway Robert Krimmer, Competence Center for Electronic Participation and Electronic Voting, Austria Ram Kumar, Sakthisoft Pty. Ltd, Australia Mike Lavine, Johns Hopkins University, USA Mark Little, Redhat, USA Yannis Manolopoulos, Aristotle University of Thessaloniki, Greece Carl Mattocks, MetLife Consultant, USA Scott Midkiff, Virginia Tech, USA Tho Manh Nguyen, Vienna University of Technology, Austria Mourad Ouzzani, Purdue University, USA Erich Schweighofer, University of Vienna, Austria Gavenraj "Raj" Sodhi, CA, Inc., USA Efthimios Tambouris, CERTH/ITI, Greece A Min Tjoa, Vienna University of Technology, Austria Costas Vassilakis, University of Peloponnese, Greece Tanja Zseby, Fraunhofer Institute for Open Communication System, Germany

1 0

Paul Strong's HPC usecase DAG
by Hiro Kishimoto 24 Nov '06

24 Nov '06

Hi all, I've upload Paul's DAG and State Transition UML diagram to the GridForege which was reviewed on Nov. 20th call. https://forge.gridforum.org/sf/go/doc14034 > 1) Powerpoint of one (of several) possible DAGs for > HPC. This is one of potentially several different renderings. > > 2) HPC State Transition In UML - UML representation of > the diagram in the BES v1.0 doc > > 3) HPC State Transition 2 In UML - UML pulling this > together with EGA Ref Model showing an implied state (Defined) and > implied transitions. Thanks, -- Hiro Kishimoto

1 0

Some more glossary terms
by Treadwell, Jem 23 Nov '06

23 Nov '06

Hi, On Monday's call we discussed definitions for data center, state and a combined definition of grid (form OGSA) and grid computing (from EGA). The results: Data center was agreed with only minor modification: A facility that houses critical computer systems and associated components. Data centers generally include environmental controls (air conditioning, fire suppression, etc.), backup power supplies, redundant network connections and high security. Larger enterprises may have multiple data centers, often geographically distant but connected by high-capacity network connections. Conversely, in an outsourcing environment multiple enterprises may share resources housed in a single data center. State: The definition I proposed in the working doc was considered to be OK but not satisfying, so Jay's on the hook to come up with a better one. Grid, grid computing: My suggestion was to combine the very formal OGSA definition with the EGA's longer, bulleted description. The consensus was that the detail of the EGA definition was fine, but that we should try to reduce it to a shorter (non-bulleted) form. My attempt to do that is below. I think I captured pretty much everything that was in the bullets, but I have *not* attempted to go beyond that. If you have comments or suggestions, please try to avoid making it taller (column-inches do matter!). Also note that I didn't consider changing the first para, which is the original OGSA formal definition, and nobody on the call suggested that we should. Here's what I have: A grid is a system that is concerned with the integration, virtualization, and management of services and resources in a distributed, heterogeneous environment that supports collections of users and resources (virtual organizations) across traditional administrative and organizational domains (real organizations). Less formally, a grid computing environment combines distributed pools of resources onto which applications or services may be dynamically provisioned and re-provisioned, to improve economy, efficiency, agility, performance, scaling, resilience and utilization. The contributed resources are often consolidated from numerous smaller pools, where they may have been under-utilized, and as a result grids tend to be heterogeneous. Grids offer great flexibility, as resources can be re-purposed or re‑provisioned in line with an organization’s changing goals. They typically focus on services rather than components, and are built using architectural styles such as service-oriented architecture, which are disaggregated or distributed in nature and can leverage the properties of the available resources. Key requirements for successful grid implementation and management include standardization of the interfaces of common components, and the use of standardized information and data models. Grid computing is related to, but subtly different from, utility computing. Thanks: for those on holiday tomorrow, have a great one, and for those who aren't, have a great one too! - Jem ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

3 2

Call for papers:Workshop "Dependability Aspects on Data WArehousing and Mining applications" (DAWAM 2007)- Submission Deadline 17-12-2006
by Nguyen Manh Tho 23 Nov '06

23 Nov '06

(Apologies for multiple copies due to cross postings. Please send to interested colleagues and students) CALL FOR PAPERS --------------------------------------------------------------------- Second International Workshop "Dependability Aspects on Data WArehousing and Mining applications" DAWAM 2007. http://dawam.ares-conference.eu/conf/ http://www.ares-conference.eu/conf/ --> Workshop -->DAWAM --------------------------------------------------------------------- in conjunction with The Second International Conference on Availability, Reliability and Security - ARES 2007 (http://www.ares-conference.eu/conf/) Overview -------- Nowadays, the rapid growth of information technologies has brought tremendous opportunities for data sharing, integration, and analysis across multiple distributed, heterogeneous data sources. In the past decade, data warehousing and mining are the well-known technologies used for data analysis and knowledge discovery in vast domain of applications. Data mining technology has emerged as a means of identifying patterns and trends from large quantities of data. Data mining has used a data warehousing model of gathering all data into a central site, then running an algorithm against that data. A growing attention has been paid to the study, development and application of data warehousing and mining. Nevertheless, dependability aspects in these applications such as availability, reliability, integrity, privacy, and security issues are still being investigated. For example, in data warehousing applications, privacy considerations may prevent the approach of collecting data into the centralized warehouse because each data source has different privacy policy. Furthermore, the complexity of security increases as different sources of information are combined. Reliable, consistent and trustworthy of information are also significant requirements in data warehousing applications. Data mining has been shown to be beneficial in confronting various types of attacks to computer systems such as fraud detection, intrusion prevention. In some applications, e.g. clinic information system, government management, business competitive information, it is required to apply the mining algorithms without observing the confidential data values thus demands the privacy preservation. There are also many challenging issues that need further investigation in the context of data mining from both privacy and security perspectives such as mining of imbalanced data, bioinformatics data, streaming data, ubiquitous computing data, grid computing data etc. The goals of this workshop are to bring together users, engineers and researchers (from industry and academy) alike to present their recent work, discuss and identify problems, synergize different views of techniques and policies, and brainstorm future research directions on various dependability aspects of data warehousing and data mining applications. We strongly encourage researchers and practitioners with interest in the areas of reliability, availability, privacy and security, databases, data warehousing, data mining, and statistics to submit their experience, and/or research results. Topics related to any of dependability aspects in data warehousing and mining, theory, systems and applications are of interest. These include, but are not limited to the following areas: · Dependability and fault tolerance · High Availability and Disaster Recovery · Survivability of evaluative systems · Reliability and Robustness Issues · Accuracy and reliability of responses · Reliable and Failure Tolerant Business Process Integration · Reliable Event Management and Data Stream Processing · Failure Tolerant and trustworthy Sensor Networks · Highly available data warehouses for business processes integration · Handling different or incompatible formats, and erroneous data · Privacy and security policies and social impact of data mining · Privacy preserving data integration · Access control techniques and secure data models · Encryption & Authentication · Pseudonymization and Encryption · Anonymization and pseudonymization · Trust management, and security · Security in Aggregation and Generalization · User Profile Based Security · Secure multi-party computation · Secondary use of personal data, clinic data, credit record · Fraud and misuse detection · Intrusion detection and tolerance · Data mining applications for terrorist detection · Private queries by a (semi-trusted) third party · Query authentication, logging, auditing, access control and authorization policies The program of the workshop will be a combination of invited talks, paper/poster presentations and discussions. Important Dates --------------- Submission Deadline: December, 17th 2006 Author Notification: January, 14th 2007 Author Registration: January, 21st 2007 Proceedings Version: January, 21st 2007 Conference/Workshop: April 10-13th, 2007 Submission Guidelines --------------------- Authors are invited to submit research and application papers in IEEE Computer Society Proceedings Manuscripts style (two columns, single-spaced, including figures and references, using 10 fonts, and number each page). You can confirm the IEEE Computer Society Proceedings Author Guidelines at the following web page: URL: http://computer.org/cspress/instruct.htm or http://www.tinmith.net/tabletop2006/IEEE/Format/instruct.htm Submission are classified into 2 categories (1) full paper (8 pages) and (2) short paper (5 pages) representing original, previously unpublished work. Submitted papers will be carefully evaluated based on originality, significance, technical soundness, and clarity of exposition. Contact author must provide the following information: paper title, authors' names, affiliations, postal address, phone, fax, and e-mail address of the author(s), about 200-250 word abstract, and about five keywords and register at our ARES website: http://www.ares-conference.eu/conf/ You can also prepare your paper in PDF file and send it to the workshop co-chair: Dr. Nguyen Manh Tho, Institute of Software Technology, Vienna University of Technology, via email: tho(a)ifs.tuwien.ac.at Submission of a paper implies that should the paper be accepted, at least one of the authors will register and present the paper in the conference. Accepted papers will be given guidelines in preparing and submitting the final manuscript(s) together with the notification of acceptance. Publication ----------- All accepted papers (full and short papers) will be published as ISBN proceedings published by IEEE Computer Society. Based on quality and referee reviews, some papers not suitable for acceptance as full paper will be accepted for presentation at DAWAM 2007 as short paper or Poster presentation category and will be also included in the IEEE Proceedings. A selected number of papers will be nominated to be published as special issues in appropriate journals such as Journal of automatic and trusted computing (JoATC). Workshop Organizer Co-chairs ---------------------------- Jimmy Huang, Prof., School of Information Technology, York University, Toronto, Ontario Canada M3J 1P3 jhuang(a)yorku.ca Josef Schiefer, Ph.D. Senactive IT-Dienstleistungs GmbH, Phorusgasse 8 A1040 Vienna, Austria josef.schiefer(a)senactive.com Nguyen Manh Tho, Ph.D. (main contact) Institute of Software Technique and Interactive System, Vienna University of Technology, Favoriten strasse 9-11/188 A1040 Vienna, Austria tho(a)ifs.tuwien.ac.at Program Committee ----------------- Jemal Abbawajy, Deakin University, Australia Mikhail Atallah, Purdue University, USA Barbara Carminati, University of Insubria at Varese, Italy Pawan Chowdhary, IBM T. J. Watson Research Center, USA Hervé Debar, France Télécom R&D, France Josep Domingo-Ferrer, Rovira i Virgili University of Tarragona, Spain Ulrich Flegel, University of Dortmund, Germany Tyrone Grandison, IBM Almaden Research, USA Jimmy Huang, York University, Canada James Joshi, University of Pittsburgh, USA Christopher Kruegel, Vienna University of Technology, Austria Xue Li, The University of Queensland Brisbane, Australia Zongwei Luo, The University of Hong Kong, China Henrique Madeira, University of Coimbra, Portugal Michael May, Fraunhofer AIS, Germany Nasrullah Memon, Aalborg University Esbjerg, Denmark Taneli Mielikäinen, University of Helsinki, Finland Tho Manh Nguyen, Vienna University of Technology, Austria Daniel O'Leary, University of Southern California, USA Torsten Priebe, Capgemini Consulting Österreich AG, Vienna, Austria Raghav Rao, SUNY at Buffalo, USA Yücel Saygin, Sabanci University, Turkey Josef Schiefer, Senactive IT-Dienstleistungs GmbH, Austria Ben Soh, La Trobe University, Australia Toshihiro Tabata, Okayama University, Japan David Taniar, Monash University, Australia Vassilios S. Verykios, University of Thessaly, Greece Duminda Wijesekera, George Mason University, USA Yanjiang Yang, Singapore Management University, Singapore Justin Zhan, Carnegie Mellon University, USA Sheng Zhong, SUNY at Buffalo, USA

1 0

Blog about OGSA
by Thomas Soddemann 22 Nov '06

22 Nov '06

Hi folks, Has anybody seen this blog about OGSA: http://go.techtarget.com/r/763634/2740371 I fear the author does not completely correct in his view of OGSA. E.g. he does not mention GGF/OGF at all. Regards, Thomas

1 0

Re: [ogsa-wg] HPC profile questionaire draft
by Subramaniam, Ravi 22 Nov '06

22 Nov '06

Hi Andrew, One question could be "Is the profile as it stands complete from your perspective? At least for the focus/business areas or types of customers that you plan to implement for?" The motivation is that depending on the verticals (e.g. financial, pharma) there may be some issue that may need to be resolved to be successful. In this way at least some target constituencies that can best benefit from what is currently there can be determined. We can also begin more targeted campaign at the OGF level towards consumers/customers/end-users and providers in that segments. Building traction in one of more specific segments may help build momentum for others. Ravi ________________________________ From: ogsa-wg-bounces(a)ogf.org [mailto:ogsa-wg-bounces@ogf.org] On Behalf Of Maguire_Tom(a)emc.com Sent: Friday, November 17, 2006 11:12 AM To: grimshaw(a)cs.virginia.edu; ogsa-wg(a)gridforum.org; ogsa-hpcp-wg(a)ggf.org; ogsa-bes-wg(a)ggf.org Subject: Re: [ogsa-wg] HPC profile questionaire draft Is there enough specificity in the profile for your engineers to successfully implement? If not what do you need? Tom _______________________________________________ Tom Maguire +1(845) 729-4806 ________________________________ From: ogsa-wg-bounces(a)ogf.org [mailto:ogsa-wg-bounces@ogf.org] On Behalf Of Andrew Grimshaw Sent: Friday, November 17, 2006 10:21 AM To: 'Ogsa-Wg'; ogsa-hpcp-wg(a)ggf.org; ogsa-bes-wg(a)ggf.org Subject: [ogsa-wg] HPC profile questionaire draft All, At the OGSA F2F I was tasked with coming up with a series of questions about the HPC profile experiences to go into a zoomerang, so that an experiences paper could be generated - either for HPC profile, JSDL, and/or BES. Here is a start. Note - comment on/add questions. Do NOT answer them!!! That will come later. 1) Will the HPC-Profile be useful to your organization/company? Explain. 2) Will you engineer your products to be hpc-profile compliant? 3) In your opinion, are there any unresolved ambiguities? Explain? 4) Thoughts on the next profile? Anything in particular from BES or JSDL (or other specification) that you would like to include. 5) Approximately how many person-days did it take you to implement the HPC-profile? 6) What would you change in the HPC-profile? Why? Remember this is a STRAWMAN ONLY for discussion! Please add, suggest removal, or modify the above. A Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw(a)cs.virginia.edu

7 12

Proposed agenda for Nov. 20th call
by Hiro Kishimoto 21 Nov '06

21 Nov '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Nov. 20th Monday from 4pm to 6pm (CST). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1120 See more explanation: https://forge.gridforum.org/sf/go/wiki1584 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Nov. 6) - https://forge.gridforum.org/sf/go/doc14002 Action Items status review (see the bottom of this email) Agenda bashing 2) F2F and SC06 debriefing (20 min) Feedback and impression on F2F and SC06. Minutes approval Documents>Meeting Materials...>Interim Meetings>OGSA-16 - 2006 Nov If you have not yet upload your materials, please do so before the call. 3) EGA reference model (Paul and Hiro, 60 min) > Discussed whether the HPC Cluster use case is too simple. Though > some aspects look simple (submit/run) other aspects (pre-, post-) > should provide a good target for further refinement. > > AI-1023e: Hiro will send out references to relevant OGF specs, > e.g., BES and CDDLM > AI-1023f: Paul will review relevant OGF specs and give feedback to > Hiro for the next version of the use case slide deck. > AI-1023g: Hiro will look at other parts of slide 5 and identify > further possible refinements of this use case. See minutes from Oct. 23rd: - https://forge.gridforum.org/sf/go/doc13966 HPC usecase slides: - https://forge.gridforum.org/sf/go/doc13939 4) Glossary (Jem, 20 min) > So here are the remaining two definitions that we did discuss - I hope > these are general enough to be acceptable. > > Enterprise: > > In common use, a business organization. > > Within OGSA and the EGA Reference Model the term is applied to any > organization whose IT facilities and operations follow enterprise > computing practices, even if the organization does not have a > literal business focus. > > Enterprise computing: > > Computing to support the operation of an enterprise or other > organization. Characteristics typically include some subset of > the following: > > * Concentration of IT resources into one or more data centers. > * Operation of enterprise applications. > * Emphasis on satisfying customer expectations through the use > of SLOs. > * The need to be able to deploy and re-deploy resources rapidly > in response to business changes. > * Attention to maximizing value through effective use of resources, > and often by assigning operating costs to customer organizations > such as business units or departments. > > Notes: > - As I'm not writing in HTML here I can't show the italics, but > "enterprise applications" and others are references to other > definitions. > - We will probably need to change the phrase "EGA Reference > Model" at some point, and that is noted as a comment in the > document. Jem has uploaded an update to the discussion document - it's at - https://forge.gridforum.org/sf/go/doc13958 3) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477 Nov. 23 (Thu) <No call> Thanksgiving Nov. 27 (Mon) OGSA secure channel document final review (Takuya Mori) Roadmap document (Chris Jordan) EMS Arch scenarios document review (Andreas Savva) Nov. 30 (Thu) Information/data modeling (Ellen and Fred) OGSA workflow (Andrew Grimshaw) Dec. 4 (Mon) <No call> Management Developer Conference Dec. 7 (Thu) <No call> GFSG F2F meeting Dec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong) Roadmap document (Chris Jordan) EMS Arch scenarios document review (Andreas Savva) Dec. 14 (Thu) Information/data modeling (Ellen and Fred) OGSA security (Alan Sill and Andrew Grimshaw) OGSA workflow (Andrew Grimshaw) <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Nov. 9 pm F2F. AI.11.09.pm-a: Ellen and Tom to write up a "Information Model profile document: BES Container" AI.11.09.pm-b: Andrew Grimshaw to persuade the BES group that the BES spec version used for the interop should be the very one that is returned to the ADs to get published AI.11.09.pm-c: Andrew to produce a document drafting the definition of QoS AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future involvement to create profile(s) on, e.g. BES, JSDL etc. > From Nov. 2nd call. AI-1102a: Hiro to ask whole group by email if it is OK to have one-way (presentation only, no discussion) SML session on future telecon. > From Oct. 30 call. AI-1030a: Ellen will contact the DAIS-WG chairs and request they arrange a review DSP0225 > From Sept. 15 OGSA F2F AI-0915d: Tom will post BP base faults issue to tracker > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next reference model call (Nov. 20): AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

3 2

No call on Nov. 23rd
by Hiro Kishimoto 21 Nov '06

21 Nov '06

Hi all, Since Nov. 23rd is Labor Day in Japan and Thanksgiving Day in US, we have no call on this Thursday. Next call will be Nov. 27 (Mon). Nov. 27 (Mon) OGSA secure channel document final review (Takuya Mori) Roadmap document (Chris Jordan) EMS Arch scenarios document review (Andreas Savva) Nov. 30 (Thu) Information/data modeling (Ellen and Fred) OGSA workflow (Andrew Grimshaw) Dec. 4 (Mon) <No call> Management Developer Conference Dec. 7 (Thu) <No call> GFSG F2F meeting Dec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong) Roadmap document (Chris Jordan) EMS Arch scenarios document review (Andreas Savva) Dec. 14 (Thu) Information/data modeling (Ellen and Fred) OGSA security (Alan Sill and Andrew Grimshaw) OGSA workflow (Andrew Grimshaw) Have a great holiday and a happy and safe Thanksgiving! -- Hiro Kishimoto

1 0

data centers and eating away 38 percent of the country's electricity
by Hiro Kishimoto 20 Nov '06

20 Nov '06

Hi all, During today's glossary discussion (Data Center definition), I asked if this is true or not... > In the United States alone, there are some 9 million servers running > nonstop in data centers and eating away 38 percent of the country's > electricity. http://www.eweek.com/article2/0,1895,2060403,00.asp -- Hiro Kishimoto

1 0

Updated: OGSA Teleconference
by Andreas Savva 20 Nov '06

20 Nov '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061120T220000Z DTEND:20061121T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E008000000008095C13EB00CC7010000000000000000100 00000F9B0E8EE48BD1546A7824A2BB6E64542 DTSTAMP:20061120T063229Z DESCRIPTION:When: 2006年11月21日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Nov. 20th\nMonday from 4pm to 6pm (CST).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1120\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Nov. 6)\n - https://forge.gridforum.org/sf/go/doc14002\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) F2F and SC06 debriefing (20 min)\n Feedback and impression on F2F and SC06.\n Minutes approval\n\nDocuments>Meeting Materials...>Interim Meetings>OGSA-16 - 2006 Nov\n\n If you have not yet upload your materials\, please\n do so before the call.\n\n3) EGA reference model (Paul and Hiro\, 60 min)\n\n> Discussed whether the HPC Cluster use case is too simple. Though\n> some aspects look simple (submit/run) other aspects (pre-\, post-)\n> should provide a good target for further refinement.\n> \n> AI-1023e: Hiro will send out references to relevant OGF specs\,\n> e.g.\, BES and CDDLM\n> AI-1023f: Paul will review relevant OGF specs and give feedback to\n> Hiro for the next version of the use case slide deck.\n> AI-1023g: Hiro will look at other parts of slide 5 and identify\n> further possible refinements of this use case.\n\n See minutes from Oct. 23rd:\n - https://forge.gridforum.org/sf/go/doc13966\n\n HPC usecase slides:\n - https://forge.gridforum.org/sf/go/doc13939\n\n4) Glossary (Jem\, 20 min)\n\n> So here are the remaining two definitions that we did discuss - I hope \n > these are general enough to be acceptable.\n> \n> Enterprise: \n> \n> In common use\, a business organization.\n> \n> Within OGSA and the EGA Reference Model the term is applied to any \n > organization whose IT facilities and operations follow enterprise\n > computing practices\, even if the organization does not have a\n> literal business focus.\n> \n> Enterprise computing:\n> \n> Computing to support the operation of an enterprise or other \n > organization. Characteristics typically include some subset of\n > the following:\n> \n> * Concentration of IT resources into one or more data centers.\n> * Operation of enterprise applications.\n> * Emphasis on satisfying customer expectations through the use \n > of SLOs.\n> * The need to be able to deploy and re-deploy resources rapidly \n > in response to business changes.\n> * Attention to maximizing value through effective use of resources\, \n > and often by assigning operating costs to customer organizations\n > such as business units or departments.\n> \n> Notes:\n> - As I'm not writing in HTML here I can't show the italics\, but \n> "enterprise applications" and others are references to other \n > definitions.\n> - We will probably need to change the phrase "EGA Reference \n > Model" at some point\, and that is noted as a comment in the\n > document.\n\n Jem has uploaded an update to the discussion document - it's at\n - https://forge.gridforum.org/sf/go/doc13958\n\n3) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477\n\nNov. 23 (Thu) <No call> Thanksgiving\nNov. 27 (Mon) OGSA secure channel document final review (Takuya Mori)\n Roadmap document (Chris Jordan)\n EMS Arch scenarios document review (Andreas Savva)\nNov. 30 (Thu) Information/data modeling (Ellen and Fred)\n OGSA workflow (Andrew Grimshaw)\nDec. 4 (Mon) <No call> Management Developer Conference\nDec. 7 (Thu) <No call> GFSG F2F meeting\nDec. 11 (Mon) EGA reference model(Hiro Kishimoto and Paul Strong)\n Roadmap document (Chris Jordan)\n EMS Arch scenarios document review (Andreas Savva)\nDec. 14 (Thu) Information/data modeling (Ellen and Fred)\n OGSA security (Alan Sill and Andrew Grimshaw)\n OGSA workflow (Andrew Grimshaw)\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Nov. 9 pm F2F.\n AI.11.09.pm-a: Ellen and Tom to write up a "Information Model\n profile document: BES Container"\n AI.11.09.pm-b: Andrew Grimshaw to persuade the BES group that\n the BES spec version used for the interop should\n be the very one that is returned to the ADs to\n get published\n AI.11.09.pm-c: Andrew to produce a document drafting the definition\n of QoS\n AI.11.09.pm-d: Andrew to contact the HPCP WG regarding future\n involvement to create profile(s) on\, e.g. BES\, JSDL\n etc.\n\n > From Nov. 2nd call.\n AI-1102a: Hiro to ask whole group by email if it is OK to have\n one-way (presentation only\, no discussion)\n SML session on future telecon.\n\n > From Oct. 30 call.\n AI-1030a: Ellen will contact the DAIS-WG chairs and request they\n arrange a review DSP0225\n\n > From Sept. 15 OGSA F2F\n AI-0915d: Tom will post BP base faults issue to tracker\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next reference model call (Nov. 20):\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

HPC profile questionaire draft
by Andrew Grimshaw 17 Nov '06

17 Nov '06

All, At the OGSA F2F I was tasked with coming up with a series of questions about the HPC profile experiences to go into a zoomerang, so that an experiences paper could be generated - either for HPC profile, JSDL, and/or BES. Here is a start. Note - comment on/add questions. Do NOT answer them!!! That will come later. 1) Will the HPC-Profile be useful to your organization/company? Explain. 2) Will you engineer your products to be hpc-profile compliant? 3) In your opinion, are there any unresolved ambiguities? Explain? 4) Thoughts on the next profile? Anything in particular from BES or JSDL (or other specification) that you would like to include. 5) Approximately how many person-days did it take you to implement the HPC-profile? 6) What would you change in the HPC-profile? Why? Remember this is a STRAWMAN ONLY for discussion! Please add, suggest removal, or modify the above. A Andrew Grimshaw Professor of Computer Science University of Virginia 434-982-2204 grimshaw(a)cs.virginia.edu

3 2

OGSA Roadmap
by Michael Behrens 16 Nov '06

16 Nov '06

I've updated the web service description area in the Roadmap document and updated the matching graphic. The pen is now in Christopher's hand: https://forge.gridforum.org/sf/go/doc13733 -- Michael Behrens R2AD, LLC (www.r2ad.com)

1 0

No call on Nov. 13 and 16
by Hiro Kishimoto 13 Nov '06

13 Nov '06

Hi all, Thank you very much for all of you who came or dial-in to interim F2F meeting in Tampa last week. We had very lively and productive meeting. Since many people are still in Tampa at SC06 this week, we won't have conf calls on Nov. 13 (Mon) and Nov. 16 (Thu). Thanks, -- Hiro Kishimoto

1 0

F2F minutes 9 Nov 2006 *afternoon*
by Michel Drescher 13 Nov '06

13 Nov '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I uploaded the minutes of the OGSA F2F 9 November *afternoon* session to Gridforge: http://forge.gridforum.org/sf/go/doc14016?nav=1 Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFWImuk0lMZTNKw4QRApdtAJwMxPHcXABPNCNRaT35UkYnuVaPNgCfQkIt MOAtUaMODtX2Imw360SDDBg= =AxR7 -----END PGP SIGNATURE-----

1 0

ARES 2007 - Submission Deadline Extension: 30-11-2006 (firm deadline)
by Nguyen Manh Tho 13 Nov '06

13 Nov '06

Due to numerous requests, the submission deadline of ARES 2007 conference was extended to Nov. 30. It is a firm deadline and could not be extended anymore. Apologies for multiple copies due to cross postings. Please send to interested colleagues and students. Call for Papers +--------------------------------------------------------------------------------------------------------+ The Second International Conference on Availability, Reliability and Security (AReS) ARES 2007 - "The International Security and Dependability Conference" April 10th – April 13th,2007 Vienna University of Technology, Austria http://www.ares-conf.org http://www.ares-conference.eu +-------------------------------------------------------------------------------------------------------+ Conference ---------------- The 1st International Conference on Availability, Reliability and Security conference (ARES 2006) has been successfully organized in Vienna, AUSTRIA from April 20 to April 22, 2006 by the Technical University of Vienna in cooperation with the European Network and Security Agency (ENISA). We have attracted 250 participants for this conference with its 3 keynotes speakers and its 9 workshops held in conjunction with. In continuation of the successful 1st ARES conference, The Second International Conference on Availability, Reliability and Security (“ARES 2007 – The International Security and Dependability Conference”) will bring together researchers and practitioners in the area of IT-Security and Dependability. ARES 2007 will highlight the various aspects of security – with special focus on secure internet solutions, trusted computing, digital forensics, privacy and organizational security issues. ARES 2007 aims at a full and detailed discussion of the research issues of security as an integrative concept that covers amongst others availability, safety, confidentiality, integrity, maintainability and security in the different fields of applications. Important Dates ---------------------- * Submission Deadline: November, 30th 2006 (firm deadline) * Author Notification: January, 7th 2007 * Author Registration: January, 21st 2007 * Proceedings Version: January, 21st 2007 Workshops -------------- In conjunction with the ARES 2007 conference, a number of workshops will be organized. We are very indebted for the effort of workshop's organizers and workshop's PC members. Proceedings of the ARES 2007 workshops will be published by IEEE Computer Society Press. * Workshop 1: Second International Workshop “Dependability Aspects on Data WArehousing and Mining applications” (DAWAM 2007), Jimmy Huang, York University, Canada + Josef Schiefer, Senactive IT-Dienstleistungs GmbH, Austria + Nguyen Manh Tho, Vienna University of Technology, Austria .DAWAM 2007 http://dawam.ares-conference.eu/ Submission Deadline: December, 17th 2006 * Workshop 2: Second Workshop on “Dependability and Security in e-Government” (DeSeGov 2007), A Min Tjoa, Vienna University of Technology, Austria + Erich Schweighofer, University of Vienna, Austria + Nguyen Manh Tho, Vienna University of Technology, Austria DeSeGov 2007 http://desegov.ares-conference.eu/ Submission Deadline: December, 15th 2006 * Workshop 3: Workshop on Foundations of Fault-tolerant Distributed Computing (FOFDC 2007), Wilhelm Hasselbring, University of Oldenburg, Germany + Matthias Rohr, University of Oldenburg, Germany + Christian Storm, University of Oldenburg, Germany + Oliver Theel, University of Oldenburg, Germany + Timo Warns, University of Oldenburg, Germany. FOFDC 2007 http://trustsoft.uni-oldenburg.de/fofdc07/ Submission Deadline: December, 1st 2006 * Workshop 4: "Secure Software Engineering" (SecSE 2007), Torbjørn Skramstad, Norwegian University of Science and technology (NTNU) + Lillian Røstad, Norwegian University of Science and technology (NTNU) + Martin Gilje Jaatun, SINTEF ICT, Norway. SecSE 2007 http://secse.ares-conference.eu/ Submission Deadline: December, 17th 2006 * Workshop 5: Workshop on "Event-Based IT Systems", Modeling, Designing, and Testing Correct, Secure, and Dependable Event-Based System, Stefan Biffl, Vienna University of Technology + Eva Kühn, Vienna University of Technology + Alexander Schatten, Vienna Univeristy of Techology EBITS http://ebits.ares-conference.eu/ Submission Deadline: November, 19th 2006 * Workshop 6: "Distributed Healthcare Availability, Reliability and Security" (DIHARES 2007), Thomas Clark, Complete Cardiology Services Ltd, USA. DIHARES 2007 http://dihares.ares-conference.eu/ Submission Deadline: November, 17th, 2006 * Workshop 7: "First International Workshop on Advances in Information Security" (WAIS 2007), Leonard Barolli, Fukuoka Institute of Technology, Japan + Arjan Durresi, Louisiana State University, USA + Hiroaki Kikuchi, Tokai university, Japan.WAIS 2007 http://www.csc.lsu.edu/~durresi/wais2007/index.html Submission Deadline: December 1st, 2006 * Workshop 8: Second International Workshop on Bioinformatics and Security (BIOS 2007), Hochreiter Sepp, University of Linz, Bioinf, Austria + Küng Josef, University of Linz, FAW Austria + Wagner Roland, University of Linz, FAW Austria. BIOS 2007 http://bios.ares-conference.eu/ Submission Deadline: November 20, 2006 * Workshop 9: Second International Workshop on Security and E- Learning, Edgar Weippl, Secure Business Austria. SEL 2007 http://sel.ares-conference.eu/ Submission Deadline: November 19, 2006 * Workshop 10: Second Workshop on Information Security Risk Management (ISRM), Professor Dr. D. Karagiannis, University of Vienna, Austria + Dr. L. Marinos, ENISA, Greece . ISRM http://www.ares-conference.eu/ares2006/www.ares-conf.org/index47da.html?q=i… * Workshop 11: The First International Workshop on Spoofing, Digital Forensics and Open Source Tools (SDFOST), Judie Mulholland, Florida Cybersecurity Institute, USA. SDFOST http://www.ares-conference.eu/conf/index.php?option=com_content&task=view&i… Submission Deadline: November 20, 2006 Topics of interest include, but are not limited to: ------------------------------------------------------------ * Process based Security Models and Methods * Autonomous Computing * Authorization and Authentication * Availability and Reliability * Common Criteria Protocol * Cost/Benefit Analysis * Cryptographic protocols * Dependability Aspects for Special Applications (e.g. ERP-Systems, Logistics) * Dependability Aspects of Electronic Government (e-Government) * Dependability administration * Dependability in Open Source Software * Designing Business Models with security requirements * Digital Forensics * E-Commerce Dependability * Failure Prevention * IPR of Security Technology * Incident Response and Prevention * Information Flow Control * Internet Dependability * Interoperability aspects * Intrusion Detection and Fraud Detection * Legal issues * Mobile Security * Network Security * Privacy-enhancing technologies * RFID Security and Privacy * Risk planning, analysis & awareness * Safety Critical Systems * Secure Enterprise Architectures * Security Issues for Ubiquitous Systems * Security and Privacy in E-Health * Security and Trust Management in P2P and Grid applications * Security and privacy issues for sensor networks, wireless/mobile devices and applications * Security as Quality of Service * Security in Distributed Systems / Distributed Databases * Security in Electronic Payments * Security in Electronic Voting * Software Engineering of Dependable Systems * Software Security * Standards, Guidelines and Certification * Survivability of Computing Systems * Temporal Aspects of Dependability * Trusted Computing * Tools for Dependable System Design and Evaluation * Trust Models and Trust Management * VOIP/Wireless Security Submission Guidelines ------------------------------- Authors are invited to submit research and application papers following the IEEE Computer Society Proceedings Manuscripts style: two columns, single-spaced, including figures and references, using 10 fonts, and number each page. You can confirm the IEEE Computer Society Proceedings Author Guidelines at the following web page: URL: http://computer.org/cspress/instruct.htm The Web site for paper registration and electronic submission is available at: http://www.ares-conf.org/confdriver/?q=confdriver/papers/add Please refer to ARES website (http://www.ares-conf.org or http://www.ares-conference.eu) for update information. If you have any difficluty in submitting the papers, please do not hesitate to send them to tho(a)ifs.tuwien.ac.at Honorary Co-Chairs --------------------------- Norman Revell, Middlesex University, United Kingdom Roland Wagner, University of Linz, Austria General Co-Chairs ------------------------ Guenther Pernul, University of Regensburg, Germany Makoto Takizawa, Tokyo Denki University, Japan Program Co-Chairs ------------------------ Gerald Quirchmayr, University of Southern Australia, Australia A Min Tjoa, Vienna University of Technology, Austria Workshops Co-Chairs --------------------------- Nguyen Manh Tho, Vienna University of Technology, Austria Abdelkader Hameurlain, University of Toulouse, France Leonard Barolli, Fukuoka Institute of Technology (FIT), Japan International Liaison Co-Chairs --------------------------------------- Maria Wimmer, University of Koblenz-Landau, Germany Charles Shoniregun, University of East London, United Kingdom Publicity Chair ------------------ Vladimir Marik, Czech Technical University, Czech Republic Publication Chair --------------------- Monika Lanzenberger, Norwegian University of Science and Technology, Trondheim, Norway Local Organizing Chairs ------------------------------ Maria Schweikert, Vienna University of Technology, Austria Markus Klemen, Vienna University of Technology, Austria Programme Committee ------------------------------ Jemal H. Abawajy, Deakin University, Australia Karl Aberer, EPFL, Switzerland Abiola Abimbola, Napier University, UK Rafael Accorsi, University of Freiburg, Germany Alessandro Acquisti, Carnegie Mellon University, USA Andre Adelsbach, Telindus PSF S.A., Luxembourg Vasilis Aggelis, PIRAEUS Bank (WINBANK), Greece John Andrews, Loughborough, University, UK Michael Backes, Saarland University, Germany Leonard Barolli, Fukuoka Institute of Technology (FIT), Japan Lisa Bartlett, Loughborough University, UK Massimo Bartoletti, Universita' di Pisa, Italy Darcy G. Benoit, Acadia University, Wolfville, Canada Helmut Berger, E-Commerce Competence Center - EC3, Austria Bharat Bhargava, Purdue University, USA Christophe Blanchet, CNRS IBCP, France Alexander Böhm, University of Mannheim, Germany Stephane Bressan, National University of Singapore, Singapore Luciano Burgazzi, ENEA, Italy Kevin Butler, Pennsylvania State University, USA Jesper Buus Nielsen , University of Aarhus, Denmark Catharina Candolin, The Finnish Defence Forces. Finland Jiannong Cao, Hong Kong Polytechnic University, Hongkong Jordi Castellà-Roca, Rovira i Virgili University of Tarragona, Spain David Chadwick, University of Kent, UK Surendar Chandra, University of Notre Dame, USA Guihai Chen, Nanjing University, China Simon Christophe, Nancy University, France Soon-Ae Chun, City University of New York, USA Nathan Clarke, University of Plymouth, UK Joey Coleman, University of Newcastle upon Tyne, UK Gao Cong, University of Edinburgh, UK Ricardo Corin, INRIA-MSR & University of Twente, The Netherlands George Davida, University of Wisconsinat Milwaukee, USA Robert H. Deng , Singapore Management University, Singapore Jochen Dinger, Universität Karlsruhe (TH), Germany Lucia Draque Penso, University of Mannheim, Germany Schahram Dustdar, Vienna University of Technology, Austria Christian Engelmann, Oak Ridge National Laboratory, USA Yung-Chin Fang, Dell Inc., USA Hannes Federrath, University of Regensburg, Germany Pascal Felber, Université de Neuchâtel, Switzerland Elena Ferrari, University of Insubria, Italy Sergio Flesca, DEIS – University of Calabria, Italy Vincenzo De Florio, University of Antwerp, Belgium Vladimir Fomichov, K.E. Tsiolkovsky Russian State Technological University, Russia Jordi Forné, Technincal Universtiy of Catalonia, Spain Huirong Fu, Oakland University, MI, USA Steven Furnell, University of Plymouth, UK Javier Garcia-Villalba, Complutense University of Madrid, Spain Matthew Gebski, University of New South Wales, Australia Karl Goeschka, Vienna University of Technology, Austria Swapna S. Gokhale, University of Connecticut, USA Marcin Gorawski, Silesian University of Technology, Poland Stephan Groß, Technische Universität Dresde, Germany Daniel Grosu, Wayne State University, USA Michael Grottke, Duke University, USA Le Gruenwald, University of Oklahoma, USA Qijun Gu, Texas State University, USA Yong Guan, Iowa State University, USA Ibrahim Haddad, Open Source Development Labs, USA Abdelkader Hameurlain, Paul Sabatier University, France Marit Hansen, Independent Centre for Privacy Protection, USA Naohiro Hayashibara, Tokyo Denki University, Japan Xubin (Ben) He, Tennessee Technological University, USA Yanxiang He, Wuhan University, China Rattikorn Hewett, Texas Tech University, USA Chin-Tser Huang, University of South Carolina, USA Jimmy Huang, York University, Canada Thomas Jensen, IRISA/CNRS, France Zhen Jiang, West Chester University, USA Hai Jin, Huazhong University of Science and Technology, China Oliver Jorns, ftw. Forschungszentrum Telekommunikation Wien, Austria Audun Josang, School of Software Engineering and Data Communications, Australia Jan Jurjens, Munich University of Technology, Germany and Open University, UK Holger Kenn, University of Bremen, Germany Dogan Kesdogan, RWTH Aachen, Germany Brian King, Indiana University Purdue University Indianapolis, USA Ted Krovetz, California State University, USA Raphael Kunis, Chemnitz University of Technology, Germany Helmut Kurth, Atsec Information Security, USA Marc Lacoste, France Télécom R&D, France Kwok-Yan Lam, Tsinghua University, China Chokchai Box Leangsuksun, Louisiana Tech University, USA Yih-Jiun Lee, Department of Information Management, CTU, Taiwan Chin-Laung Lei, National Taiwan University, China Philippe Leray, INSA (National Institute of Applied Sciences) of Rouen, France Jun Li, University of Oregon, USA Sam Lightstone, IBM Canada Ltd., Canada Chae-Hoon Lim, Sejong University, Korea Ching Lin, Macquarie University, Australia Man Lin, St. Francis Xavier University, Canada Alex Zhaoyu Liu, University of North Carolina at Charlotte, USA Tong Liu, Dell Inc, USA Hua Liu , Xerox labs, USA Javier Lopez, University of Malaga, Spain Sanglu Lu, Nanjing University, China Jianhua Ma, Hosei University, Japan Qiang Ma, NEC, Japan Josef Makolm, Federal Ministry of Finance, Austria Carsten Maple, University of Luton, UK Keith Martin , University of London, UK Fabio Martinelli, National Research Council - C.N.R, Italy BeniaminoDi Martino, Second University of Naples, Italy Santiago Melia, University of Alicante, Spain Nasrullah Memon, Aalborg University Esbjerg, Denmark Geyong Min, University of Bradford, UK George Mohay, Queensland University of Technology, Australia Marina Mongiello, Technical University of Bari, Italy Stefania Montani, Universita' del Piemonte Orientale, Italy Yi Mu, University of Wollongong, Australia Junghyun Nam, Sungkyunkwan University, Korea Priya Narasimhan, Carnegie Mellon University, USA Tho Manh Nguyen, Vienna University of Technology, Austria Jesper Nielsen, University of Århus, Denmark Thomas Nowey, University of Regensburg, Germany Tomas Olovsson, Chalmers University of Technology, Sweden Hong Ong, Oak Ridge National Laboratory, USA Maria Papadaki, University of Plymouth, UK Manish Parashar, Rutgers University, USA Fernando Pedone, University of Lugano, Switzerland MariaS. Perez, UPM, Spain Günther Pernul, University of Regensburg, Germany Rob Peters, University of Amsterdam, The Neitherland Thomas Phan, IBM Research, USA Mario Piattini, University of Castilla-La Mancha, Spain Makan Pourzandi, Ericsson Canada, Canada Christopher Price, University of Wales Aberystwyth, UK Jean-Jacques Quisquater, Universite catholique de Louvain, Belgium Wenny Rahayu, La Trobe University, Australia Indrajit Ray, Colorado State University, USA Domenico Rosaci, University "Mediterranea" of Reggio Calabria, Italy Heiko Rossnagel, Johann Wolfgang Goethe University Frankfurt, Germany Bimal Roy, Indian Statistical Institute, India Kenji Saito, Keio University, Japan Kouichi Sakurai, Kyushu University, Japan BiplabK. Sarker , University of New Brunswick, Fredericton, Canada Ingrid Schaumüller-Bichl, FH OÖ Campus Hagenberg, Austria Stephen L. Scott, Oak Ridge National Laboratory - USA Dharmaraja Selamuthu, Indian Institute of Technology Delhi, India Tony Shan, Wachovia Bank, USA Thomas Shrimpton, Portland State University, USA Richard Sinnott, University of Glasgow, UK Amund Skavhaug, Norwegian University of Science and Technology, Norway Agusti Solanas, Rovira i Virgili University, Spain Alexander Speirs, University of Newcastle upon Tyne, UK Katarina Stanoevska-Slabeva, University St. Gallen, Switzerland Ketil Stølen, SINTEF & University of Oslo, Norway Aaron Striegel, University of Notre Dame, USA Peter Struss, Munich University of Technology, Germany Tsuyoshi Takagi, Future University - Hakodate, Japan Makoto Takizawa, Tokyo Denki University, Japan Oliver Theel, University of Oldenburg, Germany Björn Thuresson, KTH Computer Science and Communication, Sweden A Min Tjoa, Vienna University of Technology, Austria Kishor Trivedi, Duke University, USA Juan Trujillo, University of Alicante, Spain Alexander W. Tsow, Indiana University, USA Tomas Uribe, SRI International, USA Kalyan Vaidyanathan, Sun Microsystems, USA Luca Vigano, ETH Zurich, Switzerland Umberto Villano, Universita' del Sannio, Italy Melanie Volkamer, DFKI - German Research Center for Artificial Intelligence, Germany Michael Waidner, IBM Software Group, Switzerland Carine Webber, Universidade de Caxias do Sul, Brazil Edgar Weippl, Vienna University of Technology, Austria Robert Willison, Copenhagen Business School, Denmark Maria Wimmer, University of Koblenz-Landau, Germany Matthew Wright, University of Texas at Arlington, USA Qinghan Xiao , Defence R&D Canada, Canada Liudong Xing, University of Massachusetts, USA Cheng-Zhong Xu, Wayne State University, USA Mariemma.I. Yagüe, University of Malaga, Spain Jeff Yan, Newcastle University, UK Laurence Yang, St. Francis Xavier University, Canada Alec Yasinsac, Florida State University, USA George Yee, National Research Council, Canada Sung-Ming Yen, National Central University, Taiwan Xun Yi, Victoria University, USA Meng Yu, Monmouth University, USA William Yurcik, University of Illinois, USA Nicola Zannone, University of Trento, Italy Jianhong Zhang, North China University of Technology, China Liqiang Zhang, Indiana University South Bend, USA Jianying Zhou, Institute for Infocomm Research, Singapore Xudong Zhu, Alcatel shangHai Bell Co. LTD., China Enrico Zio, Polytechnic of Milan, Italy

1 0

FINAL CALL: OGSA Basic Security Profile 1.0 - Core
by Takuya Mori 12 Nov '06

12 Nov '06

Dear All, Final draft of the OGSA BSP 1.0 - Core document is available on Gridforge. The draft were updated according to the AI-0928a and with an update of the reference to the latest WS-I's BSP 1.0 draft document dated August 17, 2006. Please comment on the list, or in next Thursday's call. The plan is to submit back to the GGF Editor in the week of November 4. OGSA Basic Security Profile 1.0 - Core: http://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg/d… Regards, ---- Takuya Mori NEC Corporation

2 4

Revised Secure Channel Profile is available.
by Takuya Mori 12 Nov '06

12 Nov '06

Dear All, I have updated the SP - Secure Channel profile as we discussed in the Nov 2 conference call and have uploaded it onto GridForge. OGSA Security Profile 1.0 - Secure Channel: https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg/… The major changes are: - deleted the references to the NIST guideline document - added restrictions to recommend the use of recommended ciphersuites in 3.2.2 - added non-normative tables which list some insecure and acceptable ciphersuites in Appendex C P.S.: I have updated the referenced specification tables and have uploaded the revised one. https://forge.gridforum.org/sf/docman/do/downloadDocument/projects.ogsa-wg/… Thank you, Takuya ---- Takuya Mori moritaku(a)bx.jp.nec.com / tk-mori(a)isd.nec.co.jp System Platform Software Development Division NEC Corporation, Tokyo Japan

1 0

OGSA F2F Nov 10 is starting at 1pm eastern
by Ellen Stokes 10 Nov '06

10 Nov '06

Folks, I'm sending this for Hiro..... We will be starting the Nov 10 afternoon at 1pm (instead of 1:30pm) eastern. We encourage Chris Jordan to dial in at 1pm....if he can't we'll start with the futures discussion and then switch to Chri's roadmap discussion when he dials in. Ellen

1 0

Future schedule session slide
by Hiro Kishimoto 10 Nov '06

10 Nov '06

Hi all, I've uploaded slide presentation for future schedule session on Friday. https://forge.gridforum.org/sf/go/doc14010 It turns out we don't have network connection in the meeting room and thus cannot run glance session this time. Please download meeting materials from the F2F folder. Thanks, -- Hiro Kishimoto

1 0

slide deck for today's welcome session
by Hiro Kishimoto 09 Nov '06

09 Nov '06

Hi all, I've created new OGSA-16 interim F2F meeting material folder and uploaded slide deck for welcome session and doc status review session. Please upload presentation material to this new folder preferably before your session. Folder: > Meeting Materials and Minutes > Interim Meetings > OGSA-16 - 2006 Nov Slide deck: https://forge.gridforum.org/sf/go/doc14007 Thanks, -- Hiro Kishimoto

2 1

Slides uploaded
by Michel Drescher 09 Nov '06

09 Nov '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, I uploaded my slides for tomorrow morning regarding XQuery into the OGSA Documents section: http://forge.gridforum.org/sf/go/doc14008?nav=1 Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFUz8Nk0lMZTNKw4QRAiM9AKDcEmuOtK3QtLYxfDakLcFbQVA20gCgp6k0 jcir9RRVapo7rePC/ZuF0SI= =mbTX -----END PGP SIGNATURE-----

1 0

Late tomorrow morning
by Maguire_Tom＠emc.com 09 Nov '06

09 Nov '06

Just arrived in Tampa. Lots of delays out of the NY area. Will be a couple of hours late in the morning Tom +1 (845) 729-4806 Blackberry Connect for Palm

1 0

Latest roadmap draft - v7, uploaded
by Christopher Jordan 09 Nov '06

09 Nov '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've updated the OGSA Roadmap document with several OGSA-DMI working group documents, reworked the security profile sections, and made several other minor changes. The latest version is now on GridForge. I am now passing the pen on the document to Hiro, who will update Sections 7 and 8 and then return the pen to me. One new item I need more information on is the referenced documents for the OGSA-DMI profiles. https://forge.gridforum.org/sf/go/doc13733?nav=1 Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFQCzfPCVtcXn6kg8RAvqjAKDPjoh7TCtLfNiFOvKTod5UkMzueQCg7+lk jkwGjpD/BpS++spRRHq6ioE= =EYul -----END PGP SIGNATURE-----

2 1

List invitation: OGSA-AuthN-BoF for grid services authentication issues
by Alan Sill 08 Nov '06

08 Nov '06

This is the last in a series of messages intended to announce a requested Birds-of-a-Feather session (BoF) at the Open Grid Forum OGF-19 meeting for discussion of Open Grid Services Architecture Authentication topics and activities. The list and its associated BoF are intended to carry out the steps for formation of an OGSA- AuthN work group. This message is being sent out widely to call your attention to the existence of a mailing list specific to this purpose. You may subscribe to the ogsa-authn-bof(a)ogf.org mailing list by sending a message to me or to David Groep <davidg(a)nikhef.nl> , or by visiting the following page: http://www.ogf.org/mailman/listinfo/ogsa-authn-bof Your participation is appreciated. This announcement will be sent to several relevant lists and people to extend the invitation as broadly as possible, but subsequent communication about the BoF will proceed through the above list. Subscription to the above list will be your method to ensure involvement in this process. Best, Alan Sill, Ph.D TIGRE Senior Scientist High Performance Computing Center TTU ==================================================================== : Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

Call for papers - CISIS 2007: First International Conference on Complex, Intelligent and Software Intensive Systems
by Nguyen Manh Tho 07 Nov '06

07 Nov '06

(Apologies for multiple copies due to cross postings. Please send to interested colleagues and students) Call for Papers ##################################################################### First International Conference on Complex, Intelligent and Software Intensive Systems (CISIS-2007) http://www.cisis-conference.eu/ April 10 - April 13, 2007 Vienna, Austria ##################################################################### To be held in conjunction with: ARES-2007 International Conference http://www.ares-conference.eu/ Aim ====== The aim of the conference is to deliver a platform of scientific interaction between the three interwoven challenging areas of research and development of future ICT-enabled applications: - Software Intensive Systems - Complex systems - Intelligent Systems Software Intensive Systems are systems which heavily deal with other systems, sensors, actuators, devices, other software systems and users. More and more domains are involved with software intensive systems, i.e. automotive, telecommunication systems, embedded systems in general, industrial automation systems, business applications. The outcome of web services delivers a new platform for enabling software intensive systems. The conference will focus on tools, practically relevant and heoretical foundations for engineering software intensive systems. Complex Systems Research is focused on the overall understanding of systems rather than its components. The ICT-enabling aspect of Complex Systems is the focus of the contributions to be presented at CISIS 2007. Complex Systems are very much characterised by the changing environments in which they act and by their multiple internal and external interactions. They evolve and adapt through internal and external dynamic interactions. The development of Intelligent Systems and agents which is more and more characterised by the use of ontologies and their logical foundations build a fruitful impulse for both Software intensive Systems and Complex Systems. Recent research in the field of intelligent systems –robotics, neuroscience, artificial intelligence, and cognitive sciences- builds an important factor for the future development and innovation of software intensive and complex systems. CISIS 2007 is aiming at delivering a forum for in-depth scientific discussions amongst the three communities leading to significant contributions in areas such as: - Monitoring and Control of Large Systems or Environments. - Managing the hetrogeneity of knowledge by means of ontologies - Use of Sevice Oriented Architectures for complex applications in business and industries - The consideration of Software Intensive Systems as Complex Systems - Enabling of Systems Biology concepts as software intensive conmplex systems - Knowledge management of complex IT-systems etc. Scope ========= Networks of today are going through a rapid evolution. Different kinds of systems with different characteristics are emerging and they are integrating in heterogeneous networks. For these reasons, there are many interconnection problems which may occur at different levels in the hardware and software design of communicating entities and communication networks. These kinds of networks need to manage an increasing usage demand, provide support for a significant number of services, guarantee their QoS, and optimize the utilization of network resources. Therefore, architectures and algorithms in these networks become very complex and it seems imperative to focus on new models and methods as well as mechanisms, which can enable the network to perform adaptive behaviors. Many new computing technologies have emerged as new paradigms for solving complex problems by enabling large-scale aggregation and sharing of computational, data and other geographically distributed resources. Rapid advances are being reported by many researchers and forums as regards understanding numerous issues in such paradigms, from theoretic to application aspects. Moreover, the continuous development of Internet and the construction of new infrastructures are making possible the development of large scale applications from many fields of science and engineering. To deal with complexity, we should construct physically instantiated systems that can perceive, understand, and interact with their environment – but also evolve in order to achieve human-like performance in activities requiring context-specific knowledge. This is far beyond the current state of the art and will remain so for many years to come. Therefore, many research efforts are required to make headway towards this vision. The strategic challenges are motivated by recent research in the field of intelligent systems – robotics, neuroscience, artificial intelligence, and cognitive sciences. In recent years, a large community of researchers has begun to realize the importance of brain-body interaction for understanding intelligence and its central role in a wide range of processes including perception, object manipulation, movement, and high-level cognition. The research challenges include theoretical frameworks based on the notions of embodiment, the dynamical systems metaphor, complete agents rather than individual components, self-reconfiguration and self-repair, morphology and development. Progress in the theoretical underpinnings of embodied intelligence will have strong technological implications in areas including robotics, actuator technology, materials, self-assembling systems. Research in intelligent and cognitive systems is an interdisciplinary field requiring the cooperation of researchers from artificial intelligence, neuroscience (including cognitive and computational), psychology (cognitive and developmental), linguistics, developmental biology, robotics (and engineering in general), biomechanics, and dynamical systems. Software has become a central part of a rapidly growing range of applications, products and services from all sectors of economic activity. Systems in which software interacts with other software, systems, devices, sensors and with people are called software- intensive systems. Examples include large-scale heterogeneous systems, embedded systems for automotive and avionics applications, telecommunications, wireless ad hoc systems, business applications with an emphasis on web services. Our daily activities increasingly depend on complex software-intensive systems that are becoming ever more distributed, heterogeneous, decentralized and inter-dependent, and that are operating more and more in dynamic and often unpredictable environments. There exist different kinds of complexity in the development of software. Software systems grew larger, the focus shifted from the complexity of developing algorithms to the complexity structuring large systems, and then to the additional complexities in building distributed, concurrent systems. In the next ten to fifteen years we will have to face another level of complexity arising from the fact that systems have to operate in large, open and non- deterministic environments: the complexity of knowledge, interaction and adaptation. Instead of developing computer-oriented systems where people have to adapt to the computer we have to develop human- oriented systems into which computers integrate seamlessly. Also, the requirements for software quality will dramatically increase. But our current methods are not sufficient to deal with adaptive software in a dynamic environment, especially not for large systems with complex interactions. We need to develop practically useful and theoretically well founded principles, methods and tools for engineering future software-intensive systems. All the complex systems depend on software that controls the behavior of individual components and the interaction between components, and on software which interacts with other software, systems, devices, sensors and with people. In other words: they depend on software- intensive systems. The CISIS-2007 seeks original contributions in all relevant areas, including but not limited to the following topics. Topics of interest ====================== • Agent Technology • Human-Oriented Systems • Evolving Systems • Intelligent and Cognitive Systems and Applications • Genetic Programming and Algorithms • Fuzzy Logic and Fuzzy Systems • Neuro-computing and Applications • Knowledge-based Systems • Dynamic Systems • Parallel and Distributed Algorithms • Databases and Data Mining • Grid and P2P Infrastructures • Data Intensive and Computing Intensive Applications • Scheduling, Resource Discovery and Allocation • JXTA-based Applications • Large-scale Collaborative Problem Solving Environments • Methodology and Practice of Semantic Grid and Web • Web and Grid Service-based Applications • Ubiquitous Computing Applications • Pervasive Computing and Applications • Multimedia Systems and Applications • Human-Robots • Embedded Systems • Overlay Networks for P2P Systems • Autonomous Systems • Autonomic Computing • Bio-inspired Systems and Applications • Fault-Tolerant Systems • Heterogeneous Networks • Heterogeneous Wireless Networks • Sensor Networks • Ad Hoc Networks • Sensor and Actor Networks • High-Speed Networks • Routing Algorithms • Software QoS • Adaptive Software-Intensive Systems • Self-Modifying Software Systems • Self-Designing and Self-Maintaining software Important Dates ================== • Submission Deadline: November 30, 2006 • Author Notification: January 10, 2007 • Author Registration: January 21, 2007 • Proceedings Version: January 21, 2007 • Workshop Dates: April 10-April13, 2007 Submission Guidelines ========================= Authors are invited to submit research and application papers following the IEEE Computer Society Proceedings Manuscripts style: two columns, single-spaced, including figures and references, using 10 fonts, and number each page. You can confirm the IEEE Computer Society Proceedings Author Guidelines at one of the following web pages: * http://www.ieee.org/portal/pages/pubs/transactions/stylesheets.html * or http://www.tinmith.net/tabletop2006/IEEE/Format/instruct.htm Submission papers are classified into 3 categorizes (1) full paper (8 pages), (2) short paper (5 pages), and (3) poster (2 pages) representing original, previously unpublished work. Submitted papers will be carefully evaluated based on originality, significance, technical soundness, and clarity of exposition. Contact author must provide the following information at the CISIS- 2007 web site: paper title, authors' names, affiliations, postal address, phone, fax, and e-mail address of the author(s), about 200- 250 word abstract, and about five keywords. Submission of a paper implies that should the paper be accepted, at least one of the authors will register and present the paper in the conference. Accepted papers will be given guidelines in preparing and submitting the final manuscript(s) together with the notification of acceptance. Proceedings of the CISIS-2007 conference will be published by IEEE Computer Society Press. Based on quality and referee reviews, some papers not suitable for acceptance as full paper will be accepted for presentation at CISIS-2007 in Poster category and will be also included in the IEEE Proceedings. The best papers selected by CISIS- 2007 program committee out of papers accepted for presentation at CISIS-2007 will be further published in some International Journals. The submission site for CISIS-2007 paper is available at http://www.ares-conf.org/confdriver/?q=confdriver/papers/add If you have any difficluty in submitting the papers, please do not hesitate to send them to tho(a)ifs.tuwien.ac.at. Conference Chairpersons ============================ Leonard Barolli, Fukuoka Institute of Technology, Japan A Min Tjoa, Vienna University of Technology, Austria International Liaison Co-Chairs ================================= Makoto Takizawa, Tokyo Denki University, Japan Arjan Durresi, Louisiana State University, USA Publicity Chairs ===================== Nguyen Manh Tho, Vienna University of Technology, Austria Fatos Xhafa, Polytechnic University of Catalonia, Spain Publication Co-Chairs ======================== Yoshitaka Shibata, Iwate Prefectural University, Japan Roland Wagner, University of Linz, Austria Local Organizing Chairs ========================== Maria Schweikert, Vienna University of Technology, Austria Markus Klemen, Vienna University of Technology, Austria Program Committee ===================== • Chandra Krintz, University of California, USA • Andrew Rau-Chaplin, Dalhousie University, Canada • Mukesh Mohania, IBM India Research Laboratory, India • Tomoya Enokido, Risho University, Japan • Joan Manel Marquès, Open University of Catalonia, Spain • Akio Koyama, Yamagata University, Japan • Nguyen Manh Tho, Vienna University of Technology, Austria • Fatos Xhafa, Polytechnic University of Catalonia, Spain • Arjan Durresi, Louisiana State University, USA • Naohiro Hayashibara, Tokyo Denki University, Japan • Claudi Paniagua Maci, IBM GTS, Virtualization and Grid Computing EBO, Spain • Irfan Awan, University of Bradford, UK • Hui-huang Hsu, Tamkang University, Taiwan • Jin Hwan Park, State University of New York New Paltz, USA • Kuo-Ming Chao, Coventry University, UK • Muhammed Younas, Oxford Brookes University, UK • Bhed Bahadur Bista, Iwate Prefectural University, Japan • Minoru Uehara, Toyo University, Japan • Elhadi Shakshuki, Acadia Univiversity, Canada • David Taniar, Monash University, Australia • Nobuyoshi Sato, Toyo University, Japan • Hiroaki Kikuchi, Tokai University, Japan • Sajid Hussain, Acadia University, Canada • Fumiaki Sato, Toho University, Japan • Kaoru Sugita, Fukuoka Institute of Technology, Japan • Timothy K. Shih, Tamkang University, Taiwan • Markus Aleksy, University of Mannheim, Germany • Takahiro Hara, Osaka University, Japan • Takuo Suganuma, Tohoku University, Japan • Wenny Rahayu, La Trobe University, Australia • Ismail Khalil Ibrahim, Johannes Kepler University Linz, Austria • Giuseppe De Marco, Fukuoka Institute of Technology, Japan • Günther Pernul, University of Regensburg, Germany • Andrei Doncesku, University Paul Sabatier, France • Lin Guan, Loughborough University, UK • Frank Ball, Bournemouth University, UK • Ahmed Al-Dubai, Napier University, UK • Qiang Ni, Brunel University, UK • Juan Jose Alcaraz Espin, Polytechnic University of Cartagena, Spain • Winston Seah, Institute for Infocomm Research, Singapore • Antonio Pescape, University of Napoli, Italy • Leonid Kalinichenko, Russian Academy of Science, Russia • Lawrence Y. Deng, St. John's and St.Mary's Institute of Technology, Taiwan • Xiangen Hu, University of Memphis, USA • Ching-Sheng Wang, Aletheia University, Taiwan • Kuei-Ping Shih Tamkang University, Taiwan • Been-Chian Chien, National University of Tainan, Taiwan • Wen-Yang Lin, National University of Kaohsiung, Taiwan • Vincent Lee, Monash University, Australia • Michael Sheng, CSIRO ICT Centre, Australia • Soraya Kouadri M., Oxford Brookes University, UK • S.C. Cheung, Hong Kong University of Science and Technology (HKUST), Hong Kong • Karl R.P.H. Leung, Hong Kong Institute of Vocational Education (Tsing Yi) HKIVE, Hong Kong • Victor C.S. Lee, City University of Hong Kong, Hong Kong • Henry Chan, Hong Kong Polytechnic University, Hong Kong • Hon-Va Leong, Hong Kong Polytechnic University, Hong Kong • Qing Lu, Hong Kong Polytechnic University, Hong Kong • Thomas Grill, University of Linz, Austria • Fabio Postiglione, University of Salerno, Italy • Said Mirza, Advanced Institute of Science and Technology, Japan • Ajith Abraham, Yonsei University, Korea • Takuo Nakashima, Kyushu Tokai University, Japan • Helen Karatza, Aristotle University of Thessaloniki, Greece • Paul G. Spirakis, Research and Academic Computer Technology Institute (RACTI) and Patras University , Greece • Yijun Yu, The Open University, UK • Robin Laney, Open University, UK • Matthias Hölzl, Ludwig-Maximilians-Universität München, Germany • John Mylopoulos, University of Toronto, Canada • Stefan Jaehnichen, Technical University Berlin, Fraunhofer FIRST, Germany • Bosiljka Tadic, J. Stefan Institute, Ljubljana, Slovenia • Albert Diaz-Guilera,Universitat de Barcelona, Spain • David H. Wolpert, NASA Ames Research Center, USA • Mohand-Said Hacid, Universite Claude Bernard Lyon 1, France • Andrea Cali, Free University of Bozen-Bolzano, Italy For any further questions or inquiries please contact Conference Organizers: Conference Organizers: ========================= Leonard Barolli Department of Information and Communication Engineering Faculty of Information Engineering Fukuoka Institute of technology (FIT) 3-30-1 Wajiro-Higashi, Higashi-ku, Fukuoka 811-0295 Japan Email: barolli at fit.ac.jp A Min Tjoa Institute for Software Technology and Interactive Systems Vienna University of Technology, Austria Favoritenstrasse 9-11/188 A-1040 Vienna, Austria E-mail: tjoa(a)ifs.tuwien.ac.at Nguyen Manh Tho Institute for Software Technology and Interactive Systems Vienna University of Technology, Austria Favoritenstrasse 9-11/188 A-1040 Vienna, Austria E-mail: tho(a)ifs.tuwien.ac.at

1 0

F2F meeting on Nov. 9th and 10th
by Hiro Kishimoto 07 Nov '06

07 Nov '06

Hi all, OGSA-WG will have interim F2F meeting in Tampa. Meeting information including proposed agenda is on wiki page. https://forge.gridforum.org/sf/go/wiki1620 Dial-in information * US Toll number: +1 408-961-6509 (San Jose) and +1 718-354-1071 (New York) * UK Toll number: +44 (0)207 365-5269 * JP Toll number: +81 (0)3 3570 8225 * The pass code: 4371991 -- Hiro Kishimoto

1 0

Teleconference minutes - 6 November 2006
by Andreas Savva 07 Nov '06

07 Nov '06

Attached. https://forge.gridforum.org/sf/go/doc14002?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Regrets: Overlapping internal telecon for today
by Maguire_Tom＠emc.com 06 Nov '06

06 Nov '06

0 *H÷ 010 +0 *H÷ $±Content-Type: multipart/mixed; boundary="----=_NextPart_000_0057_01C701BE.02C49480" X-MS-TNEF-Correlator: A00896EBE701C701 This is a multi-part message in MIME format. ------=_NextPart_000_0057_01C701BE.02C49480 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit See you in Tampa on Thursday Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 ------=_NextPart_000_0057_01C701BE.02C49480 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IgAVAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgAsFwAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAHQAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAANAAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAACwAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAEUAAgEJEAEAAAAPFAAACxQAAMorAABM WkZ165EJEwcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3wKDAFAD1BXPFttiF7EYIJ8XghzEGKAHEwKDMzcaH18bLxw3 F+QcohigVgSQZNUAcGEd1DgVXjIich9yoiAHbSBDRR3UOSKfpxgQI88k1XlyAoM0GgG5FXwxNhoB Jx8DgkcJ0X5rKJQPICkfLFEqXwOCVM8IcCiUE5ASoWRpAzYpeA43HjEtvwOCKEhlYvkJcHcpKJQm 4S/PMNQjv38yRgcQAaAOsDMlDhAsfjjWNjVPJNRCB0B0DrAolF84wSkuL5E4/zJzVgiQdPsiAAeB ZTMlIoEebCOYBxN9JSY0JbE/DSbXQIUodTX/Gg8qCECEK6gPEUQvLYZAhH0vBjUvmEQ9MSdAhDK7 Ne8zmEoOQAw2uzU3kUQ9OLf7QIQ6STU4wUQ+PDZLhT3P3jA+3yOYIbVA1zBBbybI/1fnKHdEDyoI V+YrqQ7wW9/3LXdX5i8HMVAvOKhX5jpKfyoAYZ88J1fmVQwCkQjmO9UJbzBoT2UOADVpemqR/2pP a1lpZGuCae9tv219bP/nay9pfxQwMjhzSnRhdB//dSlpZHVSc793j3dNds90//14xDkPIHwUfXF1 k31wAoKpEFB5bAeQaAngdAAAenEDIWwSwQUQAUAD8GS4Y3RsCrGAUDbQcAEB7GF1OmAAYHMKsICw HuBRgbJudW0CAGGBcHQybw1RanUQUAUQZ2hfgaAFEAoBf+AKAWkBkHA2MAMwACBsEMAesXMx/QMw YQExhcAL8CbgB0ANtf9/wYOAhTSE0YYTEycT6AjQ5wnAM9CIE25wiGmKBAMw8HNuZXgfMAewBbAA wH8CcxbghXGE0Q1gM+A6cHbnF1AQQB8QbWkSAIzwCfCkIESBVCBQCsBhCcDxgSBoIEYCIYwkEGBb sTsQYANgdwswg4ABgHNX8TPQdGhCE5CDgAqwjPDubA3gIoCRlHKSCA2QkXYrAYCTd2KTd3KRcmNi /wqwKfCVYh9glcMCYAuACZEzlpR+8HBlkXEE8GVs3myAYZFAkOGW8XONQAAg/zpRj/Ey4JKQmVYJ UJl0DLHnmYOA4Jl0ZGeaVpvQm1b7hUCZdHYDMH+vgL+Bz4Lf/4PvhP+GAqLxhx2iQQ20iAT/FCKG MYlspgenhIs1W7CNbP+LxDygAaB/EIwnhuGM6KMtt6R8n6AI0GY8kBBAYp/gvwmAAiCMon7hHwAz 0DkloOEtcDk4IEiXgZpAC4D7K+OMYzarj6yfraqvIq6v/6+3j2CYEJCACYCwTzEQsX//hVcAUaQ/ GeQMAbQ/jYoQQD2wYXMCIECxEEAFoG1w2xcyr05FAMADEFN+8jEQ92dzFuALYHQJ8BBgfvOd8Mxz ZBBQB3BheGFwOMDbwXERUWsJgAEBMIwzaGBidgJRIHtVsLAXIHf/GaHDFK+Rw5LEsyOQOvAeMFnF UzY2OLGvgjg3gDH/JuCvgscAQ/AtccVTxjAO8LsTkMfkNw8QAFCvgjNJUPfHAMh0yYA2r+AOEK+C KOB+MA3wxnQ68AHQDxHLVTdmOSWwyqM4OMmgyoU4/6/AyRVJUCWgQ/GvghfAF8C/zoDEswHAyaA4 oM9lODUg754hz4LN0cyFNyxAKgDQtN44xwA4sMXUfXAwAcDSxv9QEMvVDeBD8NEQzJQN4NBh/yjh xzMB0MhRxxXTMcmgyHTvDvDPAUlR1cQ3ywDQgMck/8mg0THVpc3RyODUJSJwF+D/zRDYta/AQ/DU JTrwxaDa1n/Jkc6AxnTcwRggKhHchDnsNDfHtd5BOFAQ1OUXwftBUNclNi+AQ/DU5TUgdeD7HiHh BDkYEN6A4bav4OFg/8ck4iDhYccV0yEXsNclr+C/xcDdFuLx20HjNd8hM8Z0/8ux3PHMlMux5pHI dVuwViD/ylDoda/AQVDJJMggF+Lm5f8OANCgynXPwdNA4NUjkNHA/9HA62UvgNCg6pY3gMeRxxTv DgBWIDiwyHU11vE68cX0/0lQywDIdewAKhDwl8XA6BH/xUTG0BOAz/XVcUywsADyNf/MgM3QxnQX 4MyA3mDKhM0h/8bQ85XJoCoQJaD1586AzHD/yTThcbAByTQX4cxwxdQTgP/KcDrw9GVWEc0A+OUv gC+A/6/gyTTMUflB+zXhgcZlHiD/+VHeYPy1M4APEP1n0RH45f/I8MhR/uY8IMpwx8QicDiw/9fG InDbYtAEVhHRMcvl0fH/sADF1CxA7AA3gANn5UHKhf/hcdzxypQYIPWRAeXdsse1/wbCM4AHJt6A F9HKlA8QHiD/zIbPAX1wySQ68FAQz9HLRf/gkOzGxbHaocvmxtLMlc+w/yxA79X+otkRDTXNsNNA AeX/0KDRMQil3zCGwc1GUBA1IP8KJdCBF8AB5dlQxkD4FenB/86AuyHOE/ihxtDF1OqBN4D/+NUY AOFR2VVGsMpQ/RHOBf+7IM2wzfb30scU8GDScMsQ/8fE8GDeYNhxGTd14M31RrD/GYHIdFAQzQAZ B+CQDzHMlP/vkOOhxlAc9y+AzfXNEIiA/zEhHoQVwdZVH4ENgcqE3lD/xcAjkBzlzIDLAMcFIcLO cf/OtDigyjHHxCNCsBDGdK/y/6/AJGXywc8hzrQsQLAAM4H/JgSIgEywJeYXgQQVHJHXEP/YYM60 EWLaFcpwAyEglcZA/8jgLEDIdPHh9xEo5QARM4D/JqXegMXAz/XjAe4CLXXdoP/MYc60IeGvwNAF KjLhldhg/9cB00Avtc2wzQHPZNSxXpL/z3TT4AbQMeXm0MvBz1XVkP/OcTQmyPAtRtHA+NDhQNC1 /xJBX9DPVVzgfWHQBdCgHkH/MeXrMc6AxxQRgdYg3zA5dv/UgTomxjIypdKhykE39a/A/x4hz2TM gNEQ0cDGhNNB+ND/0haIgMjRxoTkYcjwyHQ/wf/hQM/1AmFWIM01HXEfEPdV/x1ysBA95dtQCIE/ ZQ/BYWL/xpMWgTPhxoQqAephRXg91v/KcAASRXXsAM8RxoTPsH1g/+wAxoTQoOLxQaXpAQxG+kH/ r8AIlc2xzHAQ1fQR6nDhlf/iIeCRxxRMooiATafREN0V/+IgB7HJgNLUW7AWkcfE2VD/xjHs1Sih 4UAPVdlQ0qEmlf99cCyByPDS1eCQ14BNpQ5h/yLGr8XS1OzQxlDNsNLUynD/1xAEFT6B4jDqlTYh +JLS1P828YYwySTi4dHAiIHURIhw/9HA3dbWIdzB1OZikPNhWmb/OgFZYVwXHVHQBBjy30HKhP+G sR7x/hWl4t8RYBcUQKXy/16VFrHg1jDR01HQtIrxuyD/yDFilk7x7NWK8dCgybaK8P8H0FZh1OZm QfKRZdbJgFKB/9Q24JAJ4dQ1ylDmkWNWNWH/+NBfRsbRZWHHJGsCJpDVpf+K8N5gWyBfRQrQDMHY ltkh//xB3SV10W5ia4Xm0E7xbEb/MEHfR80w83HTZQrQzyHpkf9yBhMBCtVyUd0B+ZUK0N6B/yih a4XrMfTBdUdDAWNVXiD/x6H9Vc/hCfHiMHVGGOHMhf940gbQYAZ44TlBXnUXYXzw/15mbmEVwdZm xwD40BSVW7P/MaHVtRaRc3fI0pICfkXScP/jkX/XHxDU1lThZNFdpVTh/0phgWYG0RRBgxbrIH04 DYH/3aCD1tSh0dGFh8bQEBWF0f/OgFfhhyfQgHRWyDEscYI2/yfBwhDVpspw2qLX9nhRdfb/+6E6 wYsn/JDNsNZmOFHdB/+OAR8Q1iCNpxISjabzYXk2/9BxxaGBZlBB3+CItmmxCcH/2LXLACBh2WbT QJPRxxXP0f/MgNcWUeHbUJQHI1EnMZaX/wnx1OXc4cmAl0eDcmTm+IH/HKB2xs5h4jBwRttx52Kb dv/T4PHBm3YfwVpWyYCIgXX2/2fxheLYteSQ3QGTRtfB6Eb/KLLecHeWX+GbMZnGz7DcIf+YJilx Q5Ha9k1RT9XbQd6Q/8Wh2vbegFaG20HNERGVpyP/MobHAM8xaMHHJXtCZICpRv/fQQ9VqZHlIdWW AwHeYAKV/8cA6kEZsMcWMQFIIa1WZiH/4xbgodhgaPavUubQq6aeQf/FwK+3xkBIMa1W4WChsccl /yZRBJGzB9HBxxbSkd5ws8f/45JaZbXRHxCl5msxN9DKdf/HchFxtwclgqumpbEh4bmH//W33AHV kLUh27ZBgeSWvFL/HVHbtg8xapaRgYRxt9aPAf/40K+2QYEdQccl3mASMcDH/9ShuWfOgLYRtjZV oNrBY1X/FEBSktilFEAhEfCVm/EP4f/bls6Q7hGHBpvh8IHFp/lx/9oW1KGOIdxm6MAtEsnG+VH/ 3FcWkeaRycYxoWj21BDT0f8MVciRYZGU1jMxdrHMJtWQ//jBzpeHgVzGCqHiEcQGXLH/WJHRFgHB 1NYjgUjRzCYsQf+YB1Zjc4adgjtx1fgCYdX2/wYRBwDV9sIRpRbrIFyB2Ef/+jHxId32JQEBFQMR XyGztv8203+23QH0wV2l5JCZcVzG/5/xOeFgFRUhs4HeBohh0Of/C1J8ZwDx3bFutXRBXiD0VQOr UkLhOX17XCpcAHhtbG5zdGJsBiDkoOTjMSB1cm4AOnNjaGVtYXMALW1pY3Jvc2+AZnQtY29tOucg Gmbm0GXmMOaAcnR0AGFnc319XHBhcHBlcnd+gXbB6NNoZ/WSY1DoIWdsdaHqNHIt6qd0s1HqNGLr 42d1J+hQ6QBjUGx0WoBlY5B0IFx3WqBvd+2gCHJsXOcwbmJqXBBhZW5k7gBjXG6Qb3hsYehQb3nu 8MBcZXhwc2joQPAARe9gde1RbHNw70Bkxm7lMeUQYmRi71HxIOJh5+Bmb3Lw0O5w8pCCbfBQYWRl XGjykNJ67yJkZ+pSafAA9ABuaPIzdaHz8Xb0yfOBaf/0UTZBWzD1UfZFQwL0kvOA1+kg9UP4E2rw IWHvAPFQGe8wdHno8F2gdmllPHdr9GAYsPnz5kBhbEv1ALoxcOxgcmTp0GVH80D7ZfKAb3Rc8SBs 8Hl0d270YPNg7oH89/xodOaA7ODxIO9R5QD+QGXzQGrlMVx17YDtUGL/+wDwAAAB5TH6Ue1A/QD6 8fvtoOVAdwDD5THoQOsg7UB57qBya/Kh82DvYAKBd+RycP9ic27o4O/A6yC3WqD0YOfgbO5g+wBs 7hB/58D/wPNQ7wD/se3QA2Bw7nUEcPyw5pBp+TAChlqCb+bw/KBVhv1Qd+Ux5SB5ffKhc+9R6yDu EP5x5yBpoe2xZmV0MOSid+sgueewbXTnwO1Q6QAgZZD8M2bosAsQ8oDmgPrwAQD55QB1cO0z6NAL UPzA7ZHeZO3A7VXtQP1BeGNQ7vH//wDpAPNg7YIOQgQiM9ENRP/ycP5w7VAMYPzA7oPlYeTAZnDl EO2QbHbqkBHBdf3m4G0Rwuhg6EASUvpR7vDOdIuhEcHzMG5n5WER0OR0eOhgIC7ooBGaXaD/EnLt URLfE+8U/xIwWmAR0N/zUO9AFs8X3xjvbGAQEdDvATAWjxtfHGUpFUxfQBov4x8fHEViICjkkSBP EgP/brAd7yK/I88k3xIhn3AmMv8SvyefKK8gvV5wJj8rzyzf/y3vEiFxICrPMG8xfzKF6ME/+6Do wO+Q9GANow0BXHH/5VAOMWNROQHt4Q9hOHIDUP/o4BCFBmHo0DnA8zA6wgyA/zQgEKAJgu7Q/0D/ oO1g9mB7/kA5IW7tMT0SCdDo4DDX7cDoQAEwaO5wY+XR7tD2ZmNQPtBzYAH7ABwBYUL/DaM+RD3h PyM/hFpRP4IKEM1Bc2MEIkEjbnBBeUMU/+VhPhxbMD8SPeFAK1swRYIXQmA+4fRgc1VJIFNlaGUg efDAIDgB5KVvv+jw8ADllOSgEKDtoG9aoP0D0G1IcDfR5+AVRElPSlnqQwnQeeigVErA6NDkpU8M YOcAS0BOKyBvOBBU4mjmAHNkYU2gRF9Fby9Gf0eKQmDzMHJHmg0K/zdyVYY3ZDgvOT86RzvVPQ7/ UJ6hgFGvQLJb8VMXP4VBFNdCAmGh72BwB4FmR17kohBia21rNGMgX03pN/BsQQmRU/ZgTcDncP9Q j1GT3mBSD2PyU1FtAV4v+18/VQ5faQ9qH2rqYr8+of9kXV3vZr9nz1ZCbA9j32Tvb25/b49H1mKB IGHA7NBpfw8QVZVIUP0w8pBP8O2QaIv+0QQQaeUgLCBP57PlT8BmTWBUT3GPbQ9uH/91f3A/cU9y X3NvdH9970eL+EVNQ4A/gU+CX4NvtIHecwyQ6QCEn0flMoZPe7+/fM+EL37vf/UFI+SiZgVQf0dh 7bCMr42/js+P30eLSABZUEVSTElOS8wgIuaACxFvOuaAd8OSX+/AbUDmcGMu52H+IoyflG+Vf5aP U79Uw+ABf75ArcBgtFBQ6GAFI+3AYgP0YMwAIADQyep5APm6zhGMggCqQABLqQsCAKNwAxWjceCi fTajcW0AYQAAaQBsAHQAb0QAOqUTZwB1pVFysABlAF+lk6UgQKax8aUgYwAup7GnIqNw6KD/kiIF UKog7VCTX4dfiGrysf+JL54PR3yZn2KRFUKbD5wf/50vrZ+RD4Avqk+IX7MPtB8RR7grMSj3oDUp IMnI0DktwVAwNlWfVq//V786HzsvPD9aPz5KQAxTaf/pMMgAy+DfUGDH7vFhrL2GBH0AyZAAHgBw AAEAAAAwAAAAUmVncmV0czogT3ZlcmxhcHBpbmcgaW50ZXJuYWwgdGVsZWNvbiBmb3IgdG9kYXkA AgFxAAEAAAAWAAAAAccB5+tDmkhLRVUQQ5CWntRkPbCXVgAAAwAmAAAAAAALAAIAAQByAAsAAQ4A ACAAAgEKDgEAAAAuAAAAAAAAAEcAeBfHkKxKr+8LploFF7ABAPwVTdjvdXlKhysGywQ4l68AAAAD rAUAAAAAAwAJWQMAAAADAN4/n04AAAIBfwABAAAAEQAAAEEwMDg5NkVCRTcwMUM3MDEAAAAAAwAG EDK0e/kDAAcQZgAAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAGUAAABTRUVZT1VJTlRBTVBBT05U SFVSU0RBWVRPTVRPTU1BR1VJUkVTRU5JT1JURUNITk9MT0dJU1QsT0ZGSUNFT0ZDVE9FTUMyTUFH VU]lSRVRPTUBFTUNDT00rMSg4NDUpNzI5LTQ4AAAAAPpo ------=_NextPart_000_0057_01C701BE.02C49480-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 061106211000Z0# *H÷ 1ñý=/ão¥|GàIÍv$ÀÂ0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ gÚPõÆË7žå[TÛ§ÌäOó|"Í×Ù¶út»Ý¥Æ²?L9ìA÷ÉÁF%ÃÌÓã\~uß1)eúlU¥¿'œÖÅ/Ý[D|Í¥|f2km6ß->À$Àð1 ®ZUaÃg /ÕßÐbŠÊ,

1 0

Planning attendance for OGF-19 BoF: OGSA-AuthN WG
by Alan Sill 06 Nov '06

06 Nov '06

I am working on the session form for OGF-19 for the BoF we would like to have on the OGSA-AuthN charter to set its initial direction and specific deliverables. Anyone who would like to give a talk, keeping in mind that the session is short, is welcome. A draft charter in short form for this group is at: http://www.ggf.org/gf/group_info/charter.php?review&group=OGSA-AuthN-WG and other related documents will be published shortly. If you are interested in working on the topic of authentication for OGSA grid services, please do contact me. All interested parties are welcome to this effort so we can keep grid services architecture authentication on a good design basis and in touch with the best current and future practices in the field. I am also specifically recruiting help in the form of co-conveners to help with the leadership of this work group. Please also welcome our new OGF Security Area Directors Blair Dillaway and David Groep, and give them the benefit of your communication on various related topics, and every possible cooperation, suggestions, work on documents and standards, etc. If you are going to be in North Carolina for the OGF-19 conference and are interested in these topics, I would like to hear from you. Best, Alan Alan Sill, Ph.D TIGRE Senior Scientist, High Performance Computing Center Adjunct Professor of Physics TTU ==================================================================== : Alan Sill, Texas Tech University Office: Admin 233, MS 4-1167 : : e-mail: Alan.Sill(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

ARES 2007 - Call for papers and workshops papers - Submission Deadline approaches in 2 weeks: 19-11-2006
by Nguyen Manh Tho 06 Nov '06

06 Nov '06

1 0

Updated: OGSA Teleconference
by Andreas Savva 06 Nov '06

06 Nov '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061106T220000Z DTEND:20061107T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E0080000000040EBEDF29201C7010000000000000000100 00000D09B2327E245AB4292875ECCB43B9E6F DTSTAMP:20061106T023406Z DESCRIPTION:When: 2006年11月7日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n\n*ATTENTION*: Summer time ends October and we will use\n new time slot for Monday and Thursday\n\nMon: 5-7pm ET\, 4-6pm CT\, 2-4pm PT\, 7-9am JST\, 10pm-midnight UK\nThu: 8-10am ET\, 7-9am CT\, 5-7am PT\, 10pm-midnight JST\, 1-3pm UK\n\nThe following is a proposed agenda for OGSA-WG telecon on Nov. 6th\nMonday from 4pm to 6pm (CST).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1106\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584\n\n1) Early discussion (10 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Nov. 2nd)\n - https://forge.gridforum.org/sf/go/doc13996\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F update (20 min)\n Review and agree on F2F meeting agenda.\n - https://forge.gridforum.org/sf/go/wiki1620\n\n3) DMTF work register review (Ellen Stokes and Tom Roney\, 30 min)\n> The following URL contains a revision\n> of the DMTF-OGF work register.\n> https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/doc man.root.design_teams.resource_management.input_materials/doc13991?_message =1162335209252\n> \n> It contains\n> - the changes from OGSA 10/30\n> call review\n> - an additional milestone on\n> profiles from 10/31 dmtf alliance committee review\n> \n> Please review and submit any requested\n> changes/comments to me or bring to the OGSA call on Monday Nov 6.\n> \n> My goal is to get consensus on the Monday\n> Nov 6 call so we can get this balloted at DMTF and OGF.\n\n4) OGSA and reference model (Hiro and Paul Strong\, 30 min)\n> Discussed whether the HPC Cluster use case is too simple. Though\n> some aspects look simple (submit/run) other aspects (pre-\, post-)\n> should provide a good target for further refinement.\n> \n> AI-1023e: Hiro will send out references to relevant OGF specs\,\n> e.g.\, BES and CDDLM\n> AI-1023f: Paul will review relevant OGF specs and give feedback to\n> Hiro for the next version of the use case slide deck.\n> AI-1023g: Hiro will look at other parts of slide 5 and identify\n> further possible refinements of this use case.\n\n5) Glossary session (Jem Treadwell\, 20 min)\n\n6) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nNov. 9 & 10: F2F meeting in Tampa\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Nov. 2nd call.\n\n AI-1102a: Hiro to ask whole group by email if it is OK to have\n one-way (presentation only\, no discussion)\n SML session on future telecon.\n AI-1102b: Takuya to file revised BSP core draft to OGF Editor\n project with Hiro's help.\n AI-1102c: Takuya to revise and send out Secure Channel for review.\n AI-1102d: Hiro to send an email to arrange best time for glossary.\n\n > From Oct. 30 call.\n AI-1030a: Ellen will contact the DAIS-WG chairs and request they\n arrange a review DSP0225\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil Nov. F2F (Nov. 9):\n AI-1023b: Tom and Ellen will start working on an introductory\n example for the F2F.\n - The exact topic is not decided. It may be good to make\n sure that it aligns with the XQuery examples that Michel\n is using. (Tom will contact Michel.)\n - Michel and Fred should be involved in this work.\n\nUntil next reference model call (Nov. 6?):\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n----\nHiro Kishimoto\n\n\n--\n ogsa-wg mailing list\n ogsa-wg(a)ogf.org\n http://www.ogf.org/mailman/listinfo/ogsa-wg\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Nov. 6th call
by Hiro Kishimoto 05 Nov '06

05 Nov '06

Hi all, *ATTENTION*: Summer time ends October and we will use new time slot for Monday and Thursday Mon: 5-7pm ET, 4-6pm CT, 2-4pm PT, 7-9am JST, 10pm-midnight UK Thu: 8-10am ET, 7-9am CT, 5-7am PT, 10pm-midnight JST, 1-3pm UK The following is a proposed agenda for OGSA-WG telecon on Nov. 6th Monday from 4pm to 6pm (CST). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1106 See more explanation: https://forge.gridforum.org/sf/go/wiki1584 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (Nov. 2nd) - https://forge.gridforum.org/sf/go/doc13996 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F update (20 min) Review and agree on F2F meeting agenda. - https://forge.gridforum.org/sf/go/wiki1620 3) DMTF work register review (Ellen Stokes and Tom Roney, 30 min) > The following URL contains a revision > of the DMTF-OGF work register. > https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… > > It contains > - the changes from OGSA 10/30 > call review > - an additional milestone on > profiles from 10/31 dmtf alliance committee review > > Please review and submit any requested > changes/comments to me or bring to the OGSA call on Monday Nov 6. > > My goal is to get consensus on the Monday > Nov 6 call so we can get this balloted at DMTF and OGF. 4) OGSA and reference model (Hiro and Paul Strong, 30 min) > Discussed whether the HPC Cluster use case is too simple. Though > some aspects look simple (submit/run) other aspects (pre-, post-) > should provide a good target for further refinement. > > AI-1023e: Hiro will send out references to relevant OGF specs, > e.g., BES and CDDLM > AI-1023f: Paul will review relevant OGF specs and give feedback to > Hiro for the next version of the use case slide deck. > AI-1023g: Hiro will look at other parts of slide 5 and identify > further possible refinements of this use case. 5) Glossary session (Jem Treadwell, 20 min) 6) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Nov. 9 & 10: F2F meeting in Tampa <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Nov. 2nd call. AI-1102a: Hiro to ask whole group by email if it is OK to have one-way (presentation only, no discussion) SML session on future telecon. AI-1102b: Takuya to file revised BSP core draft to OGF Editor project with Hiro's help. AI-1102c: Takuya to revise and send out Secure Channel for review. AI-1102d: Hiro to send an email to arrange best time for glossary. > From Oct. 30 call. AI-1030a: Ellen will contact the DAIS-WG chairs and request they arrange a review DSP0225 > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Nov. F2F (Nov. 9): AI-1023b: Tom and Ellen will start working on an introductory example for the F2F. - The exact topic is not decided. It may be good to make sure that it aligns with the XQuery examples that Michel is using. (Tom will contact Michel.) - Michel and Fred should be involved in this work. Until next reference model call (Nov. 6?): AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

1 0

container model document for OGSA call Nov 2
by Ellen Stokes 02 Nov '06

02 Nov '06

Folks, Here's the container model document for the OGSA call Nov 2. https://forge.gridforum.org/sf/go/doc13994?nav=1 I suspect most of you won't have time to read it prior to the call, so I'll provide a general overview at the Nov 2 call. The XML section still needs to be written (plan to have for OGSA F2F Nov 9-10). Ellen

2 2

Updated: OGSA Teleconference
by Andreas Savva 02 Nov '06

02 Nov '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061102T130000Z DTEND:20061102T145900Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000903F315772FEC6010000000000000000100 0000078ABB4A5808D8744815423F8094E4E67 DTSTAMP:20061102T023346Z DESCRIPTION:When: 2006年11月2日木曜日 22:00-23:59 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Nov. 2nd\nThursday from 7am - 9am (CST).\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: <MMDD>\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Oct. 30th)\n - http://forge.gridforum.org/sf/go/doc13989\n Nov. F2F meeting update\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Security Profile discussion (30 min)\n Basic Security Profile 1.0 - core is on the final call.\n\n> Please comment on the list\, or in next Thursday's call.\n> The plan is to submit back to the GGF Editor in the week of \n> November 4.\n\n - https://forge.gridforum.org/sf/go/doc13561\n\n> - It was mentioned that TLS 1.1 obsoletes TLS 1.0. The Profile\n> however is intended to also take into account current adoption\n> levels. It is not clear how widely implemented TLS 1.1 is.\n> \n> AI-0928b: Takuya will get another opinion on TLS 1.1 and\n> ciphersuites (probably ask Frank Siebenlist)\n> \n> Takuya will prepare a new version. Since there are a number of\n> unresolved issues the Secure Channel will not go to final call until\n> the issues raised during this review are closed.\n\n3) EMS Architecture scenarios review (30 min)\n\n> AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n> presented into the scenarios document\n> AI-0913a: Andreas to update function names of BES.\n> AI-0913b: Andrew to write-up a couple of such JM functionalities\n> (short paragraph for each\, e.g. time constraint as JSDL\n> extension.)\n> AI-0913c: Andreas to add another scenario to use this “terminate”\n> method of activity interface.\n> AI-0913e: Andreas to separate un-deployment as a separate scenario.\n> AI-0913f: Andreas to describe relation between ACS and CDDLM.\n> AI-0913g: Donal to provide his proposal on\n> "ActivityExecutionCandidate."\n> AI-0831e: (A Savva) Talk to ACS working group for refining this\n> scenario.\n> AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n> Scenarios document\n\n4) Info/data modeling discussion (20 min)\n\n Container model document review.\n\n5) DMTF CIM profile education (20 min)\n\n> Here are some slides on CIM & SNIA profiles (provided by Mike Walker - an \n> active SNIA participant).\n - https://forge.gridforum.org/sf/go/doc13992\n\n6) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nNov. 6 (Mon): EGA reference model\n\nNov. 9 & 10: F2F meeting in Tampa\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Oct. 30 call.\n AI-1030a: Ellen will contact the DAIS-WG chairs and request they\n arrange a review DSP0225\n AI-1030b: Ellen will check when the DMTF documents are expected to\n become Final.\n AI-1030c: Ellen will make the necessary revisions and then send the\n document to Mark Carlson (DMTF) for review\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil Nov. F2F (Nov. 9):\n AI-1023b: Tom and Ellen will start working on an introductory\n example for the F2F.\n - The exact topic is not decided. It may be good to make\n sure that it aligns with the XQuery examples that Michel\n is using. (Tom will contact Michel.)\n - Michel and Fred should be involved in this work.\n\nUntil next reference model call (Nov. 6?):\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Nov. 2nd call
by Hiro Kishimoto 01 Nov '06

01 Nov '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Nov. 2nd Thursday from 7am - 9am (CST). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: <MMDD> See more explanation: https://forge.gridforum.org/sf/go/wiki1584 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 30th) - http://forge.gridforum.org/sf/go/doc13989 Nov. F2F meeting update Action Items status review (see the bottom of this email) Agenda bashing 2) Security Profile discussion (30 min) Basic Security Profile 1.0 - core is on the final call. > Please comment on the list, or in next Thursday's call. > The plan is to submit back to the GGF Editor in the week of > November 4. - https://forge.gridforum.org/sf/go/doc13561 > - It was mentioned that TLS 1.1 obsoletes TLS 1.0. The Profile > however is intended to also take into account current adoption > levels. It is not clear how widely implemented TLS 1.1 is. > > AI-0928b: Takuya will get another opinion on TLS 1.1 and > ciphersuites (probably ask Frank Siebenlist) > > Takuya will prepare a new version. Since there are a number of > unresolved issues the Secure Channel will not go to final call until > the issues raised during this review are closed. 3) EMS Architecture scenarios review (30 min) > AI-0914a (Andreas Savva): Integrate the simple Data scenario just > presented into the scenarios document > AI-0913a: Andreas to update function names of BES. > AI-0913b: Andrew to write-up a couple of such JM functionalities > (short paragraph for each, e.g. time constraint as JSDL > extension.) > AI-0913c: Andreas to add another scenario to use this “terminate” > method of activity interface. > AI-0913e: Andreas to separate un-deployment as a separate scenario. > AI-0913f: Andreas to describe relation between ACS and CDDLM. > AI-0913g: Donal to provide his proposal on > "ActivityExecutionCandidate." > AI-0831e: (A Savva) Talk to ACS working group for refining this > scenario. > AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch > Scenarios document 4) Info/data modeling discussion (20 min) Container model document review. 5) DMTF CIM profile education (20 min) > Here are some slides on CIM & SNIA profiles (provided by Mike Walker - an > active SNIA participant). - https://forge.gridforum.org/sf/go/doc13992 6) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Nov. 6 (Mon): EGA reference model Nov. 9 & 10: F2F meeting in Tampa <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Oct. 30 call. AI-1030a: Ellen will contact the DAIS-WG chairs and request they arrange a review DSP0225 AI-1030b: Ellen will check when the DMTF documents are expected to become Final. AI-1030c: Ellen will make the necessary revisions and then send the document to Mark Carlson (DMTF) for review > From Sept. 21 call. AI-0921c: Dave S (as Standards VP) to talk to the next Security ADs (Blair Dillaway and David Groep) about the Security Area task list. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Nov. F2F (Nov. 9): AI-1023b: Tom and Ellen will start working on an introductory example for the F2F. - The exact topic is not decided. It may be good to make sure that it aligns with the XQuery examples that Michel is using. (Tom will contact Michel.) - Michel and Fred should be involved in this work. Until next reference model call (Nov. 6?): AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

1 0

some slides on CIM & SNIA profiles
by Ellen Stokes 01 Nov '06

01 Nov '06

Folks, Here are some slides on CIM & SNIA profiles (provided by Mike Walker - an active SNIA participant). https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… Ellen

1 0

revised DMTF-OGF work register - action required by Mon Nov 6
by Ellen Stokes 31 Oct '06

31 Oct '06

Folks, The following URL contains a revision of the DMTF-OGF work register. https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… It contains - the changes from OGSA 10/30 call review - an additional milestone on profiles from 10/31 dmtf alliance committee review Please review and submit any requested changes/comments to me or bring to the OGSA call on Monday Nov 6. My goal is to get consensus on the Monday Nov 6 call so we can get this balloted at DMTF and OGF. Ellen

1 0

Glossary terms: enterprise, enterprise computing and e-Science
by Treadwell, Jem 31 Oct '06

31 Oct '06

Hi, Per Monday's call I've updated the glossary working document with the three definitions we discussed - enterprise, enterprise computing, and e-Science. The working document is at http://tinyurl.com/yb5kp2. All three definitions are below - note that enterprise is as agreed on the call, I developed the enterprise computing defintion based on the discussion (and please do note the final sentence that begins "Note that..."), and e-Science is abbreviated from the intro in wikipedia. Also note that the terms in italics also have entries in the glossary, and don't need to be spelled out here. If you have any comments please let me know; otherwise I'll move these to the main draft document before next Monday's call. Thanks! - Jem Enterprise: An organization whose primary activities are commercial. Enterprise computing: Computing to support the operation of an enterprise. Characteristics typically include: · Concentration of IT resources into one or more large-scale data centers. · Operation of enterprise applications such as CRM and ERP. · Emphasis on satisfying customer expectations through the use of SLOs. · The need to be able to deploy and re-deploy resources rapidly in response to business changes. · Attention to profitable operation by optimizing resource utilization and by assigning operating costs to business units. Note that many of these characteristics can also be found in non‑enterprise domains. e-Science: Computationally intensive science that is carried out in highly distributed network environments, or science that uses immense data sets that require grid computing. For more information see http://en.wikipedia.org/wiki/E-Science. ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

6 10

Teleconference minutes - 30 October 2006
by Andreas Savva 31 Oct '06

31 Oct '06

Also attached. http://forge.gridforum.org/sf/go/doc13989?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

DMTF-OGF work register and profile docs for 10/30 OGSA call agenda
by Ellen Stokes 30 Oct '06

30 Oct '06

DMTF-OGF work register https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… DMTF profiles (slightly outdated but good enough for education) https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… Ellen

1 0

Updated: OGSA Teleconference
by Andreas Savva 30 Oct '06

30 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061030T220000Z DTEND:20061031T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E0080000000030855F0E1DFCC6010000000000000000100 000009E5E753160DB2C4DA09DDC7C57E76E5E DTSTAMP:20061030T032058Z DESCRIPTION:When: 2006年10月31日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n\n*** ATTENTION: NEW time slot for Monday and Thursday ***\n\nMon: 5-7pm ET\, 4-6pm CT\, 2-4pm PT\, 7-9am JST\, 10pm-midnight UK\nThu: 8-10am ET\, 7-9am CT\, 5-7am PT\, 10pm-midnight JST\, 1-3pm UK\n\nThe following is a proposed agenda for OGSA-WG telecon on Oct. 30th\nMonday from 4pm to 6pm (CST).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1030\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584\n\n1) Early discussion (10 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Oct. 26th)\n - https://forge.gridforum.org/sf/go/doc13975\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F meeting aganda (Hiro\, 15 min)\n Review and agree on F2F meeting agenda.\n - https://forge.gridforum.org/sf/go/wiki1620\n\n I've already got a couple of requests:\n o Move EMS sessions to Thursday afternoon (Andrew)\n o Add Service Modeling Language education session (Ellen)\n\n3) OGSA roadmap document v1.1 update (Chris Jordan\, 15 min)\n ChrisJ will report out the status of roadmap v1.1.\n\n The latest roadmap document:\n - https://forge.gridforum.org/sf/go/doc13733\n List of included documents and associated contacts:\n - https://forge.gridforum.org/sf/go/wiki1486\n Minutes from Oct. 26th roadmap call:\n - https://forge.gridforum.org/sf/go/doc13973\n\n4) OGF DMTF work register review (Ellen Stokes and Tom Roney\, 20 min)\n\n> Ellen reviewed slides Current dmtf-ggf work register status\n> answers.ppt: Notes/answers included in slides. One notable: WSDM/CIM\n> and WS-MAN/CIM drafts are works in progress and versions are\n> available. Work regisiter can be updated.\n> \n> Tom raised a question about Security/Auth-model which might have been\n> left out of the interaction: The dropping of attributes from\n> attribute certificates. Hiro suggested that this is security team\n> work. If CIM model has semantics\, then need to track security\n> attribute (delegated) for storage services access model (current impl\n> do not do this right). Hiro suggests that perhaps this belongs in\n> charter of new WG or in design team. Tom will document this issue.\n> \n> Tom/Ellen agreed to review this topic again on the Oct 30th telecon\n> call.\n\n5) CIM profile introduction (Ellen Stokes and Tom Maguire\, 40 min)\n\n> - Though normative work is the goal some educational work on what is\n> a CIM profile is needed.\n> \n> AI-1023a: Tom and Ellen will do a CIM Profile Introduction for\n> Oct.30 (45-60 minutes session)\n\n6) Glossary term discussion (Jem Treadwell\, 20 min)\n\n Discuss and seek rough consensus on Enterprise\, Enterprise\n computing\, and e-Science.\n - https://forge.gridforum.org/sf/go/doc13958\n\n7) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nNov. 2 (Thu): Information/data modeling\,\n EMS Architecture scenarios\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\n\nNov. 9 & 10: F2F meeting in Tampa\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil Nov. F2F (Nov. 9):\n AI-1023b: Tom and Ellen will start working on an introductory\n example for the F2F.\n - The exact topic is not decided. It may be good to make\n sure that it aligns with the XQuery examples that Michel\n is using. (Tom will contact Michel.)\n - Michel and Fred should be involved in this work.\n\nUntil next reference model call (Nov. 6?):\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Oct. 30th call
by Hiro Kishimoto 29 Oct '06

29 Oct '06

Hi all, *ATTENTION*: Summer time ends this weekend and we will use new time slot for Monday and Thursday Mon: 5-7pm ET, 4-6pm CT, 2-4pm PT, 7-9am JST, 10pm-midnight UK Thu: 8-10am ET, 7-9am CT, 5-7am PT, 10pm-midnight JST, 1-3pm UK The following is a proposed agenda for OGSA-WG telecon on Oct. 30th Monday from 4pm to 6pm (CST). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1030 See more explanation: https://forge.gridforum.org/sf/go/wiki1584 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (Oct. 26th) - https://forge.gridforum.org/sf/go/doc13975 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F meeting aganda (Hiro, 15 min) Review and agree on F2F meeting agenda. - https://forge.gridforum.org/sf/go/wiki1620 I've already got a couple of requests: o Move EMS sessions to Thursday afternoon (Andrew) o Add Service Modeling Language education session (Ellen) 3) OGSA roadmap document v1.1 update (Chris Jordan, 15 min) ChrisJ will report out the status of roadmap v1.1. The latest roadmap document: - https://forge.gridforum.org/sf/go/doc13733 List of included documents and associated contacts: - https://forge.gridforum.org/sf/go/wiki1486 Minutes from Oct. 26th roadmap call: - https://forge.gridforum.org/sf/go/doc13973 4) OGF DMTF work register review (Ellen Stokes and Tom Roney, 20 min) > Ellen reviewed slides Current dmtf-ggf work register status > answers.ppt: Notes/answers included in slides. One notable: WSDM/CIM > and WS-MAN/CIM drafts are works in progress and versions are > available. Work regisiter can be updated. > > Tom raised a question about Security/Auth-model which might have been > left out of the interaction: The dropping of attributes from > attribute certificates. Hiro suggested that this is security team > work. If CIM model has semantics, then need to track security > attribute (delegated) for storage services access model (current impl > do not do this right). Hiro suggests that perhaps this belongs in > charter of new WG or in design team. Tom will document this issue. > > Tom/Ellen agreed to review this topic again on the Oct 30th telecon > call. 5) CIM profile introduction (Ellen Stokes and Tom Maguire, 40 min) > - Though normative work is the goal some educational work on what is > a CIM profile is needed. > > AI-1023a: Tom and Ellen will do a CIM Profile Introduction for > Oct.30 (45-60 minutes session) 6) Glossary term discussion (Jem Treadwell, 20 min) Discuss and seek rough consensus on Enterprise, Enterprise computing, and e-Science. - https://forge.gridforum.org/sf/go/doc13958 7) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Nov. 2 (Thu): Information/data modeling, EMS Architecture scenarios Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 & 10: F2F meeting in Tampa <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Sept. 21 call. AI-0921c: Dave S (as Standards VP) to talk to the next Security ADs (Blair Dillaway and David Groep) about the Security Area task list. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Nov. F2F (Nov. 9): AI-1023b: Tom and Ellen will start working on an introductory example for the F2F. - The exact topic is not decided. It may be good to make sure that it aligns with the XQuery examples that Michel is using. (Tom will contact Michel.) - Michel and Fred should be involved in this work. Until next reference model call (Nov. 6?): AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

1 0

Nov. F2F meeting agenda draft
by Hiro Kishimoto 27 Oct '06

27 Oct '06

Hi all, Andreas and I have written up first cut agenda draft for Nov. F2F meeting and put it on wiki page. https://forge.gridforum.org/sf/go/wiki1620 Please give us your feedback by email or at the next Monday OGSA-WG call. Thanks, -- Hiro Kishimoto -------------------------------------------------------------------------- Thursday Morning (9am - 12:30pm) * Welcome (Tom Maguire and Hiro Kishimoto, 0.5 H) * EMS architecture scenarios (Andreas Savva, 1 H) o final document review * EMS roadmap discussion (Andreas Savva, 1 H) o Future EMS scenarios (capabilities) * Next generation profiles (Andrew Grimshaw, 2 H) o I would like to suggest that we discuss the HPC-profile - and whether a next generation profile should be done as well. Thursday Afternoon (1:30-6pm) * Security (Alan Sill, 1 H) o OGSA-AuthN-WG charter o other security business * Information modeling document review (Ellen Stokes and Fred Machiel, 1.5 H) o Container model document o Modeling guideline * Info model & sercice interface integration discussion (Ellen Stokes and Tom Maguire, 2 H) o Motivating example o The subject is really about the linkage between the services we define in OGSA (of course as guided by the reference model) and the information model that is exposed through those services. In general this has been addressed in the way that SNIA and DMTF build Profiles. Terminology is a bit overloaded here... the way we (OGSA) use profiles is in the WS-I sense. Profiles in the SNIA and DMTF are about refining information models to instance based models (cardinality restrictions on relationships, required and optional properties, etc) and the tie of those instances to tasks (service interfaces). We should consider how we are going to accomplish the same thing in OGSA. Friday Morning (9am - 12:30pm) * JSDL/XQuery/Info Model discussion (Ellen Stokes and Michel Drescher, 3.5 H) Friday Afternoon (1:30-5pm) * OGSA roadmap v1.1 review (Chris Jordan, 1.5 H) * document status review (Hiro Kishimoto, 0.5 H) * Future schedule (Tom Maguire and Hiro Kishimoto, 1.5 H) o Identify tasks and priorities o Gaps and holes o OGF19 session plan o Telecon scheudle

1 0

Teleconfeerence minutes - 26 October 2006
by Michel Drescher 26 Oct '06

26 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ... available on Gridforge at https://forge.gridforum.org/sf/go/doc13975?nav=1 Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFQMl5k0lMZTNKw4QRAgppAJ484nVqz6IQ1mMT1pLGUFFiquRrOwCfYf9e Odiyt6dSYfDNZHPvoYLfPCs= =DuKl -----END PGP SIGNATURE-----

1 0

URL for OGSA-WG charter
by Alan Sill 26 Oct '06

26 Oct '06

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-WG 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

4 6

Regrets today
by Maguire_Tom＠emc.com 26 Oct '06

26 Oct '06

0 *H÷ 010 +0 *H÷ $Content-Type: multipart/mixed; boundary="----=_NextPart_000_00A3_01C6F8DF.4D82EFE0" X-MS-TNEF-Correlator: 60758ED400F9C601 This is a multi-part message in MIME format. ------=_NextPart_000_00A3_01C6F8DF.4D82EFE0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 ------=_NextPart_000_00A3_01C6F8DF.4D82EFE0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IiYNAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBgFgAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAAAAAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAJUdAgEJEAEAAAB5EwAAdRMAACcrAABM WkZ1yqYfQwcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3wKDAFAD1BXPFttiF7EYIJ8XghzEGKAHEwKDMzcaH18bLxw3 F+QcohigVgSQZDUAcGECgzQaARV8MjOKOB9UIAdtIENFIiSfDyAirhgQI88k1XlyIiRzJuEVfDE2 GgEnHwOCR/0J0WsiJA4QKR8lsSpfA4I2VAhwIiQ2AgASsGRpOwM2KXg3HjEtvwOCKEjkZWIJcHcp IiQeMS/P/zDUI78yRgcQAaAOsDMlNTFdKS04L5E1bwOCQgdAdOsOsCIkOTevNhOQOO8yZFpWCJB0 IgAHgWUzJDX/Gg8jmAcTJSYPET7+JtdAhX0odTUm4R5sKghAhCuoNd8sUUQ+LYZAhC8GNS+YRD33 MSdAhDK7NTOYSg5ADDa7vjU1MUQ9OLdAhDpJNTsB/0Q+PDZLhT3OInA+3yOYIbW/JScO8FZPJtdX 5yh2MUQP9yoIV+YrqTFGzy1oV+YvB984oF7POLdX5jpKMVL/PBivV+ZVDAKRCOY7CW8waE/6ZQ4A NWl6apFqT2tZaWT/a4Jp722/bX1s/2svaX8UMPwyOHNKdGF0H3UpaWR1Ur9zv3ePd012z3T/eMQ5 DyA/fBR9cXWTfXACghBQeWxVB5BoCeB0AABxAyFsDxLBBRABQAPwZGN0bJcKsYBQNtBwAQFhdTpg PQBgcwqwgLAe4IGybnVKbQIAYYFwdG8NUWrmdRBQBRBnaIGgBRAKAct/4AoBaQGQcDADMAAgpmwQ wB6xczEDMGEBMf+FwAvwJuAHQA21f8GDgIU0/4TRhhMTJxPoCNAJwDPQiBMcbnCIaYoEAzBzbmX+ eB8wB7AFsADAAnMW4IVx74TRDWAz4DpwdhdQEEAfEJxtaRIAjPAJ8CBEgVQ0IFAKwGEJwIEgaCB+ RgIhjCQQYFYhEGADYHcnCzCDgAGAc1cz0HRo3kITkIOACrCM8GwN4DUwfZGUcpIIDZCRdgGAk3di 5ZN3cpFyY2IKsCnwlWJ/H2CVwwJgC4AJkZaUfvBwxmWRcQTwZWxsgGGRQPuQ4Zbxc41AACA6UY/x MuD/kpCZVglQmXQMsZmDgOCZdHxkZ5pWm9CbVoVAmXR2/wMwf6+Av4HPgt+D74T/hgL/ovGHHaJB DbSIBBQihjGJbP+mB6eEizVWII1si8Q8oAGg/38QjCeG4Yzooy2kfJ+gCND2ZjyQEEBin+AJgAIg jKJffuEfADPQKOA1IDlMsCC+SJeBmkALgCvjjGM2q4//rJ+tqq8irq+vt49gmBCQgP8JgLBPMRCx f4VXAFGkPxnk3wwBtD+NihBAsGFzAiBAsbMQQAWgbXAXMq9ORQDAfQMQU37yMRBncxbgC2B0zwnw EGB+853wc2QQUAdwvGF4XqAvkMFxEVFrCYAtAQEwjDNoYHYCUSB79lWwsBcgdxmhwxSvkcOSn8Sz I5AvgB4wxVM2Njix/a+COCxAW7GvgluwPsAtcd/FU8YwDvATkMfkNw8QAFBxr4IzNTNbsMh0yYA2 /Dk2DhCvgw3gDfDGdC+AZwHQDxHLVTc5OwCvgzhuOMmgyoWv8DPJFcmQM/+wAMkkF8AXwLAAxLMB wMmg+2Fxz3Q4NSCeIc+CzdHMhe43JaAqANC0OFuwOLDF1P19cDABwNLGRrDL1Q3gPsD/0RDMlA3g 0GEiccczAdDIUf/HFdMxyaDIdA7wzwHJkNW1/jfLANCAxyTJoNEx1aXN0f/I4NQlI6AX4M0Q2LXN wD7A/9QlL4DFoNrWyZGwAMZ03MF3GCAqEdyEOTOAx7XeQTjfRrDU5RfBOvDXJTbJwD7A39TlNSB1 4B4h4QQ5GBDegP/htspg4WDHJOIg4WHHFdMh/xew1yXKYMXA3Rbi8dtB4zX93yEzxnTLsdzxzJTL seaR/8h1ViCSEMpQ6HXNwDrwyST/yCAX4ublDgDQoMp1z8HTQP/g1SOQ0cDRwOtlycDQoOqW/yxA x5HHFA4AkhA4sMh1TLD/yaHm5dfBywDIdewAKhDwl//FwOgRxUTG0BOAz/V14MyA/83QxnQX4MyA 3mDKhM0hxtD+MsyUyaAqEM5w9SewAfUl/+Fx9RDQBBOAF/DMcMXUE4D/ynAvgPOlGCDNANiVxaD6 Af/KYMk0zFH4gfp14YHGZR4g//iR3mD79SjgDxD8p9ER+CX/yPDIUf4mPCDKcMfEI6A4sP/XxiOg 22LQBPlR0THL5dHx//UQxdQloOwALEACp+VByoX/4XHc8cqUGCD00QEl3bLHtf8GAijgBmbegBfR Bzav8sqU/w8QHiDMhs8BfXDJJC+ARrD/z9HLReCQ7MbFsdqhy+bG0v/Mlc+wJaDv1f3i2RHMpcsQ /+OBzKUYQUaxD4VMsNJwzKX/+8GSEa+D2VDGQPdV6cGwAP+7Ic4T9+HG0MXU6oEsQPgV/xgA4VHZ VUFQylD8Uc4FuyD/r/DN9vcSxxTwYNJwyxDHxP/wYN5g2HEYd3XgzfVBUBjB/8h0RrDNABhH4JDi IPaVTLD/46HGUBw3ycDN9c0QiIAxIf8dxBUB1lUewQ2ByoRS4MXA/yOQHCXMgMsAxwUhAs5xzrT/ OKDKMcfEIoLfIMZ0LXDfIP/NwCOl8sHPIc60BxD1ECjh/yVEiIBD8CUmFsEDVRvR1xD/2GDOtBCi 2hXKcAJhH9XGQP/I4AcQyHTx4fZRKCX/USXQ/yXl3oDFwM/14wHuAiy13aD/zGHOtCEhzcDQBSly 4ZXYYP/XAdNALvWv8M0Bz2TUsVjS/8900+AGEDEl5tDLwc9V1ZD/znEzZsjwLIbRwPgQ4UDQtf8R gV/Qz1Vc4H1h0AXQoB2B/zEl6zGwAMcUEMHWIN8wOLb/1IE5ZsYyMeXSocpBNzXNwP8dYc9kzIDR ENHAxoTTQfgQ/9IWiIDI0caE5GHI8Mh0PwH/4UDP9QGhkhDNNRyxHlD2lf8cst8gPSXOcAfBPqUP AV6S/8aTFcEzIcaEKUE9B8pw/1L/RLXsAM8RxoTPsGRw7ADGhP/QoOLxQOXpAQxG+YHNwAfV/82x 4hAQFfNR6nDhleIh4JH/xxRLIoiATCfREN0V4iAG8f/JgNLUViAV0cfE2VDGMezV/yfh4UCv4E51 0qEl1X1wK8H/yPDS1eCQ14BMJQ5hIgb0Qf/GUK/wE0tTKcNcQA1U9weIw/+qVNWH30tLUNjGGMNWk 4uH/0cCIgdREiHDRwN3W1iHcwf/U5mKQ7NDJxTkjVyFZ1xyR/9AEGDLfQcqEhrEeMf1VpeL/3xFd 1xOApfJcVRXx4NYwEf/TUdC0ivG7IMgxYFZNcezV/4rx0KDJtorwBxBUIVnGZAH/8pFjlsmAUQHU NuCQCeHU9v/38l0GxtFjIcckZ/Il0NWl/4rw3mBY4F0FCtAMwdiW2SH/+4HdJXXRa1JodebQTXFp Nv8vgd9HzTA4kD6GCtDPIemR/272EkEK1W9B3QH41QrQ3oH/J+Fodesx9AFyN0JBYRVb4P/HofyV z+EJ8eIwcjYYIcyF/3XCBhBdxnXROIFcNRahfPD/XCZrURUB1mbHAPgQE9VZc/8w4dW1FdFwZ8jS kgJ7NdJw/+ORfMceUNTWU2FikVtlU2H/SOF+VgYRE4GABusgeigNgf/doIDG1KHR0YJ3xtAPVYLB /7AAVaGEF9CAcUbIMSuxfyb/JwHCENWmynDaotf2dUFy5v/64ToBiBf70K/w1mY3kd0H/4rxHlDW IIqXEVKKllphdib/0HHFoX5W3yBL0WEV8HEfof/ZZtNAj/HHFc/RzIDXFlBh/85wkCcikSZxkrcJ 8VnF3OH/yYCTZ4BiYqb3wRvgc7bOYf/iMG0223HnYpeW0+DxwZeW/x8BWBbJgIVxcuZlsYLS2LX/ 5JDdAY9m18HoRifyE9B0hv9doZdRlebPsNwhlEYosULR/9r2S9FOVdtB3pDFodr23oD/VEbbQc0R ENWjQzHGxwDPMf9mgccleDJiQKVm30FQlaWx/+Uh1ZYCQd5gAdXJsYvhphf/69HM8KiXHIFmtqqi 5tCnxv+aYcXAqwfGQEaxqKbhYJ3R/8clJZED0a5X0cHHFtKRE9D/rxfjklglsSEeUKIGaCE3EP/K dcdyELGyVyTCp8ah0SEh/7TX9PfcAdWQsHHbtkDB5Jb/t6Ickdu2G/Fnho5xgWGzJv+L8fgQqwZA warBxyXeYBFx/7wX1KG0t/ZwsWGxhspg2sH/YRUTgFES2KUTgCBR8JWYEf8PIduWxvHfQb9Wv7Hf 4MD3/52x4BbJASxSxEb4kdxXFdH/5pHERjDhZrbUENPRDFXNMP920pD2MnFzocam1ZD4AckX/4Rx WoYKoeIRv1ZacVZRy5b/AQHU1iLBR1HGpiuBlCdUI/9wdpmiOrHQeAGh0HYFUQZA/9B2vWGhNusg WkHSx/lx8SH/3fYkQdfWMyH2cdilNhN8pv/XgfQBW2XkkJWRWoacETkh/13VFGGu0diG3xHLZwtS eVf/ADHYMWulcTFb4POVp3JCIQA5fXtcKlx4bQBsbnN0YmwgfYBccGFwZXJ3e3Ebc7HgE2j00mEQ bWFyrGdscpHhdHLh53SuoYXhdGLjI2d1dHTgQAlhEGx0WEBlY3QgJFx3WGBvd+TgcmwAXGZ0bmJq XGEIZW5k5UBjXG5vSHhsYeQwb3nmMFzAZXhwc2hy5dDmkSJ15JFsc3DmgGRuY9+x35BiZGLmkehg YeBjZWZvcugQ5bDp0IJt55BhZGVcaOnQ0nrmYmRn4ZJp50DrQG5o6XNykesxduwJ6sFp/+uRNYFY 8OyR7YVCQuvS6sDX4GDsg+9TaudhYeZA6JAZ5nB0eeAwW2B2aWUcd2vroBfw8TNzY2GWbOxAtYFw 46ByZOEQjmXqgPKl6cBvdFzoYOBseXR3buug6qDlwfn0N2h04ZDkIOhg5pHfgMv1gOqAat+xXHXk wOSQ/mLyQOdA90HfsfGR5ID0QPfyMeTg38B3+APfseew4mDz5IDl4HJr6eHqoOag+cHId3Jw9qJz buAg5wBv4mBYYOug6aBs5aDyQGz15VBm8VBs6pDmQPbx5RDZ+qBwdfuw8/BhWFDwcLv5xlhCcvPR CEb0kHffsfXfoHnp4XPmkeJg5VD1sYZv/GDk8WZldDDfIsJ34mBmZm10/GDkkOXgQCBjUDNm3/AC UOnAz+GQ8jD4QN+AdXDkc+AQ9wKQ9ADk0WTlAOSV5ID0gf54YRDmMfZA4EDqoOTCBYL/+2IzEQSE 6bD1sOSQA6D0ADXlwyDfInDfkOTQbHbz4dAJAXVj6kAJAvZg57B3CZLxkeYwdIiRCQHqcG4mZwjB CRB0ePZgIC7+fd8TCRZbYAmy5JEKHwsv/ww/CXBYIAkQ6pDmgA4PDx/9EC9sXdAJEPhwDc8SnxOl PikMjF0AEW8WXxOFYiD+KN8RF48JQ2ugFS8Z/xsP/xwfCWGbkB1yCf8e3x/vF/3/XDAdfyMPJB8l LwlhWcAiD/8nryi/KcXgAfLg4ADm0Oug8wTjBEFccd/QBXFhETBB/+UhBqEvsvqQ4CAHxf2h4BD/ MQDqcDICA8ArYAfgAMLmEL/2gPbg5KDtoPWAMGFu5HF3NFIBEOAgMOUA57D4cGiR5bBjczHlAGFm YRD9NhBzXcHyQBNBXwIE4zWEfzUhNmM2xFgRNsIBUDizY/P7YjhjbnA4uTpUCME1XP9Y8DZSNSE3 a1jwPMI5oDYhfeugc1hC/wY1gOGgPtkg/A0KLrJAhi6kL28wfzGH/zMVNE47nktRPL8BMUtRPhdf NsU4VDlCXcHmoHD+wWZDPp0Iw2JrbWsroyCkX00vMGxBANFT7aD8fVQDQN8RO782YNjgPQ+/TvI+ UWnxSS9KP0AOX1QP/1UfVepNvzXhT11I71G/Us//QUJXD07fT+9Zf1qPQBZNgbYgTMDkEGkGUECV U+Ywbmnp0GJQ5NBo9hH7UGlR36AsIE8CAGnpoCDhAPAgQ1RPXI9YD1kf/2B/Wz9cT11fXm9ff2jv Swv4RU1Daz9sT21fbm928d5zA9DgQG+fQCUycU9mv79nz28vae9q9fxj3yJm/JB/PqHk8HeveL95 z3rfSwtIAFlQRVJMSU5LzCAi4ZACUW864ZBiwwJf5wBtQGVtYy76YwNAIneff2+Af4GPPr/fP8O/ stagwxAIw2Tm4DYQG/xy5QBi66DGgCAA0ADJ6nn5us4RjACCAKoAS6kLAqoAjnADjnHgjX02jnEA bQBhAGkAbAAgdABvADqQE2cAgnWQUXIAZQBfkJONkCBAkbGQIGMALpKx/5IijnAMgH0i/JCVMOSQ fl//cl9zaunxdC+JD0r8hJ9Nkf8MgoYPhx+IL5iffA9rL5VPj3Nfng+fH6AoKzEo7uDINSkgLJA5 LbuwquD/QJ9Br0K15qBDL0Q/RU87//+iv0ifpO+l/6h/qY9DHzG//zLPM9+tPzXkN0w+acGwvnA/ xmDZ0EvH5jFMrLNWfQABv2AAAAAeAHAAAQAAAA4AAABSZWdyZXRzIHRvZGF5AAAAAgFxAAEAAAAW AAAAAcb5ANJiLA1AHGeVTQaYQE9wZSQeoAAAAwAmAAAAAAALAAIAAQCVHQsAAQ4AAAAAAgEKDgEA AAAuAAAAAAAAAEcAeBfHkKxKr+8LploFF7ABAPwVTdjvdXlKhysGywQ4l68AAAADrAUAAAAAAwAJ WQMAAAADAN4/n04AAAIBfwABAAAAEQAAADYwNzU4RUQ0MDBGOUM2MDEAAAAAAwAGEA03zI4DAAcQ TwAAAAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAFAAAABUT01UT01NQUdVSVJFU0VOSU9SVEVDSE5P TE9HSVNULE9GRklDRU9GQ1RPRU1DMk1BR1VJUkVUT01ARU1DQ09NKzEoODQ1KTcyOS00ODA2AHj+ ------=_NextPart_000_00A3_01C6F8DF.4D82EFE0-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 061026131538Z0# *H÷ 1kÃÂÚ=#j¬ªæfÈÿ0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ ¶ôòV}{<à³ÑÀšá.?oßÎ!sP€äáî$éeéJäqJ\IrL²ÍÎiK'@Á3û³ûYTì£¯ðdç0l~ôøònpHqe§NéQófP@¶xè6ŒxI2Ü3º3ªÜy

1 0

BES specs
by Hiro Kishimoto 26 Oct '06

26 Oct '06

Hi Paul and reference model design team members, > AI-1023e: Hiro will send out references to relevant OGF specs, > e.g., BES and CDDLM The following is BES related materials for reference model discussion. (1) OGSA-BES specification draft - https://forge.gridforum.org/sf/go/doc13793 (2) OGSA-HPC profile use case document - https://forge.gridforum.org/sf/go/doc13780 (3) OGSA-HPC profile specification draft - https://forge.gridforum.org/sf/go/doc13736 Thanks, -- Hiro Kishimoto

1 0

of reference models, services and information models....
by Maguire_Tom＠emc.com 26 Oct '06

26 Oct '06

0 *H÷ 010 +0 *H÷ $-Content-Type: multipart/mixed; boundary="----=_NextPart_000_000B_01C6F6C5.2E5ACA50" X-MS-TNEF-Correlator: 105D69B5E6F6C601 This is a multi-part message in MIME format. ------=_NextPart_000_000B_01C6F6C5.2E5ACA50 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I would like to broach the subject line on tonight's call. Preferably early in the agenda as Ellen Stokes will be able to join at that time. The subject is really about the linkage between the services we define in OGSA (of course as guided by the reference model) and the information model that is exposed through those services. In general this has been addressed in the way that SNIA and DMTF build Profiles. Terminology is a bit overloaded here... the way we (OGSA) use profiles is in the WS-I sense. Profiles in the SNIA and DMTF are about refining information models to instance based models (cardinality restrictions on relationships, required and optional properties, etc) and the tie of those instances to tasks (service interfaces). We should consider how we are going to accomplish the same thing in OGSA. Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_000B_01C6F6C5.2E5ACA50 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IiUVAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgD4GQAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAGkAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAB3AAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAGwAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAHQAAgEJEAEAAADOFgAAyhYAAHcyAABM WkZ1iAuT2AcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3wKDAFAD1BXPFttiF7EYIJ8XghzEGKAHEwKDMzkaH18bLxw3 F+QcohigVgSQZB0AcGECgxggFV4yMzjFH1QgB20gQ0UiJBoBzyK9GBAjzyTVeXIiJBOQuRVtMTYa AScfA4JHCdF+ayIkJuEpLg8gKk8Dc1TPCHAiJA4QEqFkaQM2KXgMNzctnyTUKEhlYukJcHcpIiQ2 L68wtiO/fzJGBxABoA6wMyUxMSktONczkTVvA4JCB0B0DrAiJF81MSkuKPE4/zJzVgiQdPsiAAeB ZTMkGAAeTiOYBxO9JSY1Gg8myECFKHU1KPHvHmwqCECEK6g1JuFEPi2G+0CELwY1L5hEPTEnQIQy u941M5hKDkAMNrs1MTFEPfc4t0CEOkk1NTFEPjw2S4W/Pc4o4D7fI5ghtSUnM0FvfybIV+cod0QP KghX5iupM+9Gzy1oV+YvBzNQLzioV+Z/OkojolMvV31VDAKRCOY71QlvMGhPZQ4ANWl6apH/ak9r WWlka4Jp722/bX1s/+drL2l/FDAyOHNKdGF0H/91KWlkdVJzv3ePd012z3T//XjEOQ8gfBR9cXWT fXACgqkQUHlsB5BoCeB0AAB6cQMhbBLBBRABQAPwZLhjdGwKsYBQNtBwAQHsYXU6YABgcwqwgLAe 4FGBsm51bQIAYYFwdDJvDVFqdRBQBRBnaF+BoAUQCgF/4AoBaQGQcDYwAzAAIGwQwB6xczH9AzBh ATGFwAvwJuAHQA21/3/Bg4CFNITRhhMTJxPoCNDnCcAz0IgTbnCIaYoEAzDwc25leB8wB7AFsADA fwJzFuCFcYTRDWAz4DpwducXUBBAHxBtaRIAjPAJ8KQgRIFUIFAKwGEJwHGBIGggRgIhjCQQYDF3 AFAQYANgdwswg4ABgHPiVzPQdGhCE5CDgAqw3YzwbA3gNTCRlHKSCA2QV5F2AYCTd2KTd3KRcmP+ YgqwKfCVYh9glcMCYAuAZwmRlpR+8HBlkXEE8GW8bGyAYZFAkOGW8XONQP8AIDpRj/Ey4JKQmVYJ UJl0zwyxmYOA4Jl0ZGeaVpvQ95tWhUCZdHYDMH+vgL+Bz/+C34PvhP+GAqLxhx2iQQ20/4gEFCKG MYlspgenhIs1kCD/jWyLxDygAaB/EIwnhuGM6G+jLaR8n6AI0GY8kBBAYn+f4AmAAiCMon7hHwAz 0DLjhjBY4DggSJeBmkALgPsr44xjNquPrJ+tqq8irq//r7aPYJgQkIAJgLA/MRCxb/+FVwBRpD8Z 5AwBtC+NihBAPbBRcwIgQLEQQAWgbXDbFzKvTUUAwAMQU37yMRD3Z3MW4AtgdAnwEGB+853wzHNk EFAHcGF4q2AzkNvBQRFRawmAAQEwjDNoYGJ2AlEge1WwoBcgd/8ZocLkr5HDYsSDI5AzgDEwWa+D NjY4sa+COC+AMf8m4K+CxtBBUC1xr4jHpSoQuyOQx6U3DxAAUK+CM0Pwx8bQyPTKADY5Ng4Qr4L9 JaAwDfDGRDOAAdAPEcvVzDc5HjDLIzg4WODLBfg4OTPJlUPwHiBBUa+C/xfAF8DPAMSDAcBY4Mg1 AcC+ODUgniHQAs5RzQU4xtD3OLDFpH1wMAHA0pZJUMxV/w3gQVDRkM0UDeDQ4SWhxwP/AdDI0cbl 0wFY4Mj0DvDPgftD8dWUN8uA0QDG9Fjg0bH/1XXOUclg0/UjoBfgzZDYhf/OQEFQ0/UzgF6g2qbK Ec8A38ZE3JEYICoR3FQ5N4DHhd3eEThJUNS1F8E0zkDfRX8o4EFQ1LU1IHXgYXHg1Dn/GBDeUOGG yuDhMMb04fDhMf/G5dLxF7DW9crgxZDc5uLB99sR4wXe8TPGRMwx3MHNFP/MMeZhyPWQIJIQytDo Rc5A/9/QyaSvwBfi5rUOANEgyvXv0EHTEOClI5A3N4Avga+D/2Rh5EHsxUlQ4FHFFBgAzYD/5GUO ANbBM4HFxEPwy4DI9f/r0CoQ8GfFkOfhxRTGoBOA/8g2zjDOQcZEF+DNAN4wywT7zaHGoDLNFFjg KhAeIPT3/88AzPDJtOFB9ODIRBOAF/D/zPDFpBOAyvAzgPN1GCDNgP/YZV6g+dHK4Mm0zNH4UfpF /+FRxjXsYS+AhjH71dGR9/X/yXDI0f02PCDK8MeUI6A4sP/XliOg2zLIRPkh0bHMZd+R//TgxaT0 0OvQL4ABt+URywX/4UHcwcsUGCD0oQA13YLHhf8FEixABXbeUBfRy8UXsH1w/8mkM4BJUNBRy8Xg YOyWxYH/2nHMZsaizRXQMPTQ76X88v/Y4c0lDfDjUc0lGEFJUQ0V/1AQ0kDNJfuRkhHLI9kgxhD/ 9yXpkc8AuwHOk/exxqDFpP/qUS+A9+UYAOEh2SXJgMrQ/9GQxkTwMLsAzjDOdvbixuT/8DDSQMuQ x5TwMN4w2EEWB/914M51yYAWUcj0SVDNgBXX/+Bg4fD2ZVAQ43HGIM6EzZD/W7AxIRqUEpHWJRuR CxHLBP/eIMWQI5AZtc0Ay4DG1R3S/87xzzQ4oMqxx5QfUt7wxkT/LXDe8M5AIHWv8c+hzzT00P/0 4CxBIhRbsEawIfYUUQJl/xlh1uDYMM80DjLZ5crwAXH/HKXGEMlg9NDI9PGx9iEk9f/+YSxAIrXe UMWQyDXi0e3S/ymF3XDM4c80HfHOQNCFJkL/4WXYMNbR0xArxc4wzYHP5P/Ugctgx5TQMNOwBSAt 9eag/8xBz9XLYM7xMDbJcClW7HD/9+DhENE1DxFf0M/VXOB9Yf/QhdEgWNEt9esBzwDG5A5R/9Xw 3wA1htRRNjbGAi610nH/ysE0Bc5AkhA1dc0A0ZDscP/GVNMR9+DRNOXBzlDTNeEw/8uAyXDI9DvR 4RDINQCxkhD/zbUaQRsg9mUaQt7wOfXUoP8G0Tt1DJHLYD21E1Ev8cZU/yYROdfK8P5iQYXr0M+R xlT/0DB9YOvQxlTRIOLBPbXo0f8J1vlRzkAG5c4x4eANpfMh/+pA4WXh8eBhxuRH8luwSPf/0ZDc 5eHwBgHKANKkkCATYf/HlNkgxgHspSSx4RDREEtF/9JxIqV9cCiRyXDSpeBg11D/SPUL8R7W9BHG IM4w0qTK8P/W4AJlOpHiAOplMjH3otKk/zMBhjDJpOKx7HBbsdQUiHD/7HDdptXx3JHUtmKQ7KDK Rf8181PxVqcaIchEFcLfEcsE/4axGwH8ZaXi3uFapxEQpfL/WSUTgeCmLOHTIdE0ivG7AP/IsV0m SkHspYrx0SDKNorw//TQ9LFgV8oATdHUBuBgB3H/1Mb3wlnWxqFf8cb0Y/IioP9VxYrw3jBVsFnV kCAKUdhm/9jx+1Hc9XXRZ1JkdeagSkH/ZTYsUd8Xq2A1YDtWkCDPof/pYWr2D9EIZWtB3NH4pZAg /95RJLFkdesB89FuNz8RXeX/WLDHcd4wbjYHgeIAbjYVsf/NBXHCBSBalnHRNVFZBRQx/3XgWPZn URKR1jbG0PfgEWX/VkMtsdWFE2FsZ8lSkgJ3Nf/SQONheMcbINSmUDFfYdP1/1AxRbF6VgUhERF8 Burwdij/CxHdcHzG1HH00NV2ABEZcf9+ds8AUnGAF9EAbUbIsSiB/3smI9HB4NV2yvDactfGcUH/ bub6sTbRhBf7oM4w1jY0Yf/c14bxGyDV8IaXDuKGllcx/3Im0PHFcXpW3vBIoV3l8EH/HHHZNtMQ i/HG5dBRzQDW5v9NMdSgjCcfYSNBjrcHgdS1/9yxygCPZ3xiX3b3kRlwb7b/zuHiAGk220HnMpOW 07Dxkf+TlhvRVObKAIFxbuZhsX7S/9iF5GDc0Ytm15HoFiTCEWD/cIZacZNRkebQMNvxkEYlgf8/ odrGSKFLJdsR3mDFcdrG/95QURbbEc2RDmWfQy6WxtD/z7Figcb1dDJfEKFm3xFNZf+hseTx1WYB Ud4wAOXKMYfh/6IX66HNcKSXGhFitqai5qD/o8aWYcWQpwfGEEOBpKbhMP+Z0cb1ImEC4apXJwHG 5tJh/xFgqxfjYlT1rSEbIJ4GZCH/M+DK9cdCDkGuVyGSo8ad0f8d8bDX9Mfb0ctgrHHbhj2R/+Rm s6IaIduGGYFjhopxfWH/ryaH8ffgpwY9kRoRxvXeMP8PAbgX1HGwt88ArWGthsrg/9qRXeUREE3i 2HUREB0h8GX/lBEMsdtmxsHfEbtWu7HfsP+895mx3+bJgSkiwEb4Ydwn/xNh5mHARi2xYrbJgNOh CeX/lBBy0oz2L0FvocKmy2D30f/FF4BxV1YIMeHhu1ZXQVMh/8eWABHUph+RRCHCpihRkCf/UPNs dpWiALHMdgRhBVDMdv+5YZ026vBXEc33+UHw8d3G/yER16Yv8fZB2HUy43im0rH/89FYNeRgkZFX VpgRNfFapf8R8arR07be4cdnCOJ1V/9Bf9NhZ6VtMViw82Wjcj7xOQB9e1wqXHhtbMBuc3RibCDa UNqTADEgdXJuOnNjAGhlbWFzLW1pAGNyb3NvZnQtUGNvbTrc0GbcgGUD2+DcMHJ0dGFncwB9fVxw YXBlcu53d3Fvsd6DaPSiXeDd0axnbG6R3+Ry4Fd0qqHl3+Ri4ZNndd4A3rBd4ARsdFUQZWN0IFwS d1Uwb3fjUHJsXAHc4G5ialxhZW4CZOOwY1xub3hsEmHeAG955KBcZXi4cHNo3fDlsOUQdeMByGxz cOTwZG7a4drAWGJkYuUB5tBh3ZBmXG9y5oDkIOhAbeYAYVBkZVxo6EB65NJk2mfgAmnlsOmwaOfj bpHt6aF26nnpMWnqAbShVcD/6wHr9T8S6kLpMN7Q6vPtwzpq5dFh5LDnAOTgdHmD3qBYMHZpZXdr 6hBnFYDvo9vwYWzqsLGBcOniEHJk34Bl6PDxFegwCG90XObQbHl0d55u6hDpEOQx8qdodNwwv+KQ 5tDlAdqw8/Do8Gra4excdeMw4wBi8LDlsPWxf9rh8AHi8PKw8KHjUNrwdz/2c9rh3fDg0OLw5FBy a4/oUekQ5RD4MXdycPUS/HNu3pDlcODQVTDqEN2Q9mzkEPCwbOPA3XD1cOkAz+Sw9WHjgPkQcHX6 IPJg/dxAae7g+DZVEtyg8lAp8V+fgeUA79Da4drQeehRc1/lAeDQ48D0IdzQaeNhZmhldDDaUnfg 0N1gbS503XDjAN6wIGAgM2Z/3mAAsOgw3DDwoPaw2rB1vnDi496AAPDycONBZONw9+MF4vDy8Xhd 4OSh9LDesP/pEOMyA+L50i/hAuToIPQgv+MAAgDycOQz2xHacHDawFnjQGx24EAHYXXckG2/B2Le EN3wB/LwAeSgdISRMwdh6OBuZ9sRB3B0ePneECAu3lAHOlgwCBLjAf8IfwmPCp8H0FTwB3DpAOTw 9wxvDX8Oj2xaoAdw9uAML/sQ/xIFKQrsWdAPzxS/EeX4YiAo2kEV7wejZ6ATj/8YXxlvGn8HwZeQ G9IIXx0//x5PFl1ZABvfIW8ifyOPB8H/YsAgbyYPJx8oJd5x8VDecM/lQOoQA0MCoVxx2wAD0f9d 4S6h45EFAS4S+QDekAYl//wR3oAvYOjgMGICICnABkD//yLkgPTw9VDjEOwQ8/Auwd5u4uEysv9w 3pAw43Dd8LX24GjkIGPbgeSAZl3g/TRwc1qR8LARoVvSA0Mz5H8zgTTDNSRU4TUi/7A3E2Pz+dI2 w25wNxk4tNsRM7z/VcA0sjOBNctVwDsiOAA0gQ3qEHNVEv10IEkgd0fmcQMw9kBrZSDlcCA18UBv 6ABoPqDcECBzznXkYONCA+Igby2w2kF/Oh87Lzw/PUjlcPLgMmNxfnXyUD9xQJ9Br0K/PRsgffCh bArQRa9Gv0fPSNsgnlAEsP+wL8Da8Hkg8ZD/5ABOoC2hP1LeIOShElDcQPsHI9qRb96g5bDbRNpQ BkCt41BvVTD5gG0+kFDesNncwG5OUfHeUEX6UOSg7CBT5XA+gHPaVQIA3LDvUsA98ACw2wBiT3Ha 8D6TvmpRsC2w5VA/QVXiaVIA6i5JgFQ/aWlQEASw+oG/TqBOcOZwVfI+kPZBa0+R+1TR8sBlUyE/ U96w77DdkDtQEFmAIAYhQCItoU9H/FNBJ6Dc0EmQ5nDjIU/y6+KAXiBlAzBiTqA/Uk4jI+Sg3ZAg bW/pAGwpv0+A5LA/Q+oQ6JLlUGlAYf9eI0CPSv9MD0O9ViJXkeXR91RBXrLcoHXqUD9BVEFaB/1W oUktsE+hTlHbAD9QV5H/6OBQEFTgUyHo8PFgU5Bk8r1PJXdgP2FPYl89G2FOoJ9pf2qPa59jb1NA TklboOFekkRNVEY+0FywPjHvThD/UfDAZoJU3rDccPSBL/nATwFQEBJQYv9xb3b/3rD6oOjxAzAE km2vbr9vz/09G4V2L3c/eE9IzGkjbXGdWqEoW3JecPVRIHBzReNXgk8lV1MtPeDjMAeB/1ahczZP Eno/e098X3Dddh//g2+Ef0i9cfzd4FTyWFJOIf/qEOoQEcBfH1AQPrE9Ad4Q713i9aBk8o11KPCg 8VDqEP/wsP9wTqBogTIx41BfkVAQv0BhBLDlQZDCZ4Dl8CxXsf1FIGkEsAMwXpJQoF+CZ0G/f6He oVZgU5CSEP/AY154f5PxQFBb4GW0jhaNw94Qc35rj1FaFU8R4rFRcVOQKf1WoVc/cekwPiLdENrA XMHvAPDtwVqSi4JnVaERwD6xf+gA3RHykFeQPzVR8mdxbv+Gn4eviL89G4ySW2NWoJyPX52fnq89 GjgA6OByPTkN/gotEqYWLQQtzy7fL+cxdf8yrqFOyeGib/+RyeGjxzUl/za0N6I04eUQf6Hc0Dz9 2lIYYmttlvAqEiBfTSktkGxB/zFT7BB9VP/dIKE/okPUEKK/tHKkAcCQ966vr7+lnl+5f7qPu1qz P/80QbTdrn+3P7hPpuG8f7Rf37Vvvu+//z11swEgskBcofsEsKYlU+SgX5AA8HPg3ABrdDNXkHSS EE/dY5VSQ/xUT8HvvX++j8XfwK/Bvx/Cz8PfxO/OTz05RU1D/9B/0Y/Sn9OvNOE/kN6h1N/9TZQy 1n/MD80f1G/PP9BE+/rTUDJm+wCOEqt/3c/e3wPf7z0bSFlQRVJMYElOSyAiX2AAsW8WOl9gyBNf +b3BtQGXobWMumyEi3L/kf+WPH+afpG/hEgEgpcA0NzB/q2JQUE/QjkD60/+QdPBuADk5IADQyep5 APm6zhGMggCqQABLqQsCAPNgAxXzYeDybTbzYW0AYQAAaQBsAHQAb0QAOvUDZwB19UFysABlAF/1 g/XwQPah8fXwYwAu96H3EvNgLPD/4jJzAOEQA2Djb9eP2JqY8P/ZT+3/PQzpn7MRCuLrD+wf/+0v /Y/hLwCP+k/YnwL/BA+BpaYrMSg4NDVecIEq8DktNDgwNqYtvwYfBy8IPAkvCj+llyJW0n9AYFgB j7DKMF21WVZP4HL3WGFekjggYXVAV4I/UiqwAZMQaC4iIC0gUtcwooDAj+BkPsBFUgBSUv8NvwGf EI8RnwTPpt+n68mA/6i/qc+q36GvGa+uLxt/HI//HZ8erx/fMC8xPzJPIl80U5M1rKQZMTI5wDY5 rIBPsUdPsbIsKFZ9ADRgAAAeAHAAAQAAADkAAABvZiByZWZlcmVuY2UgbW9kZWxzLCBzZXJ2aWNl cyBhbmQgaW5mb3JtYXRpb24gbW9kZWxzLi4uLgAAAAACAXEAAQAAABYAAAABxvbmtOW/YfL5435J 1b1LETanNJa0AAADACYAAAAAAAsAAgABAGEACwABDgAAbAACAQoOAQAAAC4AAAAAAAAARwB4F8eQ rEqv7wumWgUXsAEA/BVN2O91eUqHKwbLBDiXrwAAAAOsBQAAAAADAAlZAwAAAAMA3j+fTgAAAgF/ AAEAAAARAAAAMTA1RDY5QjVFNkY2QzYwMQAAAAADAAYQu86rSwMABxAsAwAAAwAQEAAAAAADABEQ AAAAAB4ACBABAAAAZQAAAElXT1VMRExJS0VUT0JST0FDSFRIRVNVQkpFQ1RMSU5FT05UT05JR0hU U0NBTExQUkVGRVJBQkxZRUFSTFlJTlRIRUFHRU5EQUFTRUxMRU5TVE9LRVNXSUxMQkVBQkxFVE9K T0kAAAAAWek= ------=_NextPart_000_000B_01C6F6C5.2E5ACA50-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 061023210337Z0# *H÷ 10ñ}5$ ªáŠòª 0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ #µÁçÍIí<Üè8$ŽúÉ:ÜyCó=ü¡" âH1ûWìbð¬ŸåÌŸ!Ý4<jÅL l××ôMø-{ñ(Uýôx<UÑ kÂ,Îž3 Ä@fÄçÖFê#ûámAGÈÚÛÁ¥Ó=d(Lwhœ:U¥ÂŒ

2 1

Roadmap Editors call minutes, 10/25
by Christopher Jordan 26 Oct '06

26 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes from today's call to GridForge: https://forge.gridforum.org/sf/go/doc13973?nav=1 Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFQCt3PCVtcXn6kg8RAmwxAJ90ryg6HC0wEpak9Nc2DNDJeWIyOQCg6uI8 DTYdXxegzQuo5HXN4FI55u4= =FeSR -----END PGP SIGNATURE-----

1 0

OGSA Roadmap Editors Call Today
by Christopher Jordan 25 Oct '06

25 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There will be an OGSA Roadmap editors call today at 3PM PDT, 6PM EDT. Please join us if you have comments or other input for the OGSA Roadmap document, as we are fast approaching final draft status. To Join Audio Conference Primary Dial-In: 1 (877) 218-2986 Alternate Dial-In: 1 (847) 619-6049 Enter Passcode: 9435289# Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFP38CPCVtcXn6kg8RAr/NAKDEVFgHynP7xJkuLZNIAV2jLPuJWwCfQsrJ CRNFqQkBPYliliYVWDJiB5s= =ypCD -----END PGP SIGNATURE-----

1 0

Updated: OGSA Teleconference
by Andreas Savva 25 Oct '06

25 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061026T133000Z DTEND:20061026T153000Z TRANSP:OPAQUE SEQUENCE:2 UID:040000008200E00074C5B7101A82E0080000000090FC1D0965ECC6010000000000000000100 000002731B8671369CD478D172B3E1AC845AA DTSTAMP:20061025T103730Z DESCRIPTION:When: 2006年10月26日木曜日 22:30 to 2006年10月27日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1026\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Oct. 23)\n - https://forge.gridforum.org/sf/go/doc13966\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov F2F update (Hiro)\n\n3) OGSA-AuthN-WG charter discussion (Alan Sill\, 60 min)\n\nMinutes from Oct. 5th call\n> * What is the best low hanging fruit to attack\n> - Authentication?\n> - Do we want to narrowly profile SAML for point \n > to point authorization?\n> -- Next step to be delegation\n> - What use cases should we consider?\n> - What other profiles for authentication should we look at?\n> -- SAML?\n> -- X509 Varient in which we conote identify \n > with regards to WS-Naming (EPI)\n> -- Federation of identity\n> --- There are people solving this problem \n > and we shouldn't re-invent\n> --- SAML\n> - What in the OGSA use case space. If you plan to federate \n > identity.\n> - If your site has user name password\, how do you federate that\n> - One of the nice things about SAML is that you can have \n > assertions that consolodate authentication domains.\n> -- You may not have to have an X509 for that \n > username/password\n> - Equally important is authenticating the service to the user.\n> - Need Auth Working group.\n> - Shibolith\n> -- You still need a source of identity (X509\, or something)\n> - Auth Schemes\n> -- X509\n> -- Kerberos\n> -- Member Integrated Credential Service\n> --- AD\, LDAP\, etc.\n> - WS-Trust falls short of the mark\n> - Seems optimistic to say that Shibolith does Auth\, but \n > it's being looked into seriously.\n> * BoF\n> - Need to start preparation for a BoF\n> - Alan Sill willing to take responsibility for pushing \n > the process for getting a charter ready\n> - AI-1005a: Alan Sill to have draft Charter ready before \n > next security telecon (Dave to help and only as stand\n > in for new area director).\n> - Do we need more covereage if we have an active authorization \n > and authentication working groups\n> -- No\, we need more covereage\n> -- AI-1005b: People to send Dave Snelling more \n > information\, ideas for more\n > security calls to complete coverage\n> - Two weeks from today is the next security call.\n\n Alan's charter draft:\nhttp://www.ggf.org/gf/group_info/charter.php?review&group=OGSA-Aut hN-WG\n\n People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 30 (Mon): OGSA roadmap\, DMTF work register\,\n CIM profile introduction\nNov. 2 (Thu): Information/data modeling\,\n EMS Architecture scenarios\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\n\nNov. 9 & 10: F2F meeting in Tampa\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Oct. 23 call\n AI-1023a: Tom and Ellen will do a CIM Profile Introduction for\n Oct.30 (45-60 minutes session)\n AI-1023b: Tom and Ellen will start working on an introductory\n example for the F2F.\n - The exact topic is not decided. It may be good to make\n sure that it aligns with the XQuery examples that Michel\n is using. (Tom will contact Michel.)\n - Michel and Fred should be involved in this work.\n AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case\n slides and make appropriate changes to indicate where the\n CIM Profile would fit in and how it would link into the\n Reference Model.\n AI-1023d: Paul will add more items to list on slide 6 of the HPC\n Cluster use case\n AI-1023e: Hiro will send out references to relevant OGF specs\,\n e.g.\, BES and CDDLM\n AI-1023f: Paul will review relevant OGF specs and give feedback to\n Hiro for the next version of the use case slide deck.\n AI-1023g: Hiro will look at other parts of slide 5 and identify\n further possible refinements of this use case.\n\n > From Oct. 5 call.\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 26)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next EMS call (Nov. 2):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Oct. 26th call
by Hiro Kishimoto 25 Oct '06

25 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 26th Thursday from 8:30am - 10:30am (CDT). Attention: Summer time ends Oct. 29. New time slot in next week and after. Mon: 5-7pm ET, 4-6pm CT, 2-4pm PT, 7-9am JST, 10pm-midnight UK Thu: 8-10am ET, 7-9am CT, 5-7am PT, 10pm-midnight JST, 1-3pm UK Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1026 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 23) - https://forge.gridforum.org/sf/go/doc13966 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov F2F update (Hiro) 3) OGSA-AuthN-WG charter discussion (Alan Sill, 60 min) Minutes from Oct. 5th call > * What is the best low hanging fruit to attack > - Authentication? > - Do we want to narrowly profile SAML for point > to point authorization? > -- Next step to be delegation > - What use cases should we consider? > - What other profiles for authentication should we look at? > -- SAML? > -- X509 Varient in which we conote identify > with regards to WS-Naming (EPI) > -- Federation of identity > --- There are people solving this problem > and we shouldn't re-invent > --- SAML > - What in the OGSA use case space. If you plan to federate > identity. > - If your site has user name password, how do you federate that > - One of the nice things about SAML is that you can have > assertions that consolodate authentication domains. > -- You may not have to have an X509 for that > username/password > - Equally important is authenticating the service to the user. > - Need Auth Working group. > - Shibolith > -- You still need a source of identity (X509, or something) > - Auth Schemes > -- X509 > -- Kerberos > -- Member Integrated Credential Service > --- AD, LDAP, etc. > - WS-Trust falls short of the mark > - Seems optimistic to say that Shibolith does Auth, but > it's being looked into seriously. > * BoF > - Need to start preparation for a BoF > - Alan Sill willing to take responsibility for pushing > the process for getting a charter ready > - AI-1005a: Alan Sill to have draft Charter ready before > next security telecon (Dave to help and only as stand > in for new area director). > - Do we need more covereage if we have an active authorization > and authentication working groups > -- No, we need more covereage > -- AI-1005b: People to send Dave Snelling more > information, ideas for more > security calls to complete coverage > - Two weeks from today is the next security call. Alan's charter draft: http://www.ggf.org/gf/group_info/charter.php?review&group=OGSA-AuthN-WG People to send Dave Snelling more information, ideas for more security calls to complete coverage 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 30 (Mon): OGSA roadmap, DMTF work register, CIM profile introduction Nov. 2 (Thu): Information/data modeling, EMS Architecture scenarios Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 & 10: F2F meeting in Tampa <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Oct. 23 call AI-1023a: Tom and Ellen will do a CIM Profile Introduction for Oct.30 (45-60 minutes session) AI-1023b: Tom and Ellen will start working on an introductory example for the F2F. - The exact topic is not decided. It may be good to make sure that it aligns with the XQuery examples that Michel is using. (Tom will contact Michel.) - Michel and Fred should be involved in this work. AI-1023c: Tom volunteered to review Hiro's HPC Cluster use case slides and make appropriate changes to indicate where the CIM Profile would fit in and how it would link into the Reference Model. AI-1023d: Paul will add more items to list on slide 6 of the HPC Cluster use case AI-1023e: Hiro will send out references to relevant OGF specs, e.g., BES and CDDLM AI-1023f: Paul will review relevant OGF specs and give feedback to Hiro for the next version of the use case slide deck. AI-1023g: Hiro will look at other parts of slide 5 and identify further possible refinements of this use case. > From Oct. 5 call. AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 26) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 21 call. AI-0921c: Dave S (as Standards VP) to talk to the next Security ADs (Blair Dillaway and David Groep) about the Security Area task list. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next EMS call (Nov. 2): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

1 0

Teleconference minutes - 23 October 2006
by Andreas Savva 24 Oct '06

24 Oct '06

https://forge.gridforum.org/sf/go/doc13966?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

CDDLM intro
by Hiro Kishimoto 24 Oct '06

24 Oct '06

Hi Paul and reference model design team members, The following is CDDLM related materials for reference model discussion. (1) OGSA EMS architecture scenarios document draft See "deploying an application scenario (section 4.1)" - https://forge.gridforum.org/sf/go/doc12749 (2) CDDLM specs presentation by Dejan CDDLM overview slides presentation - https://forge.gridforum.org/sf/go/doc12763 (3) CDDLM specifications CDDLM Foundation Document (GFD.50) - http://www.ggf.org/documents/GFD.50.pdf CDDLM Component Model v 1.0 (GFD.65) - http://www.ggf.org/documents/GFD.65.pdf CDDLM Deployment API (GFD.69) - http://www.ggf.org/documents/GFD.69.pdf CDDLM XML-CDL spec draft - http://www.ogf.org/pipermail/cddlm-wg/2006-August/000656.html Hope it helps, -- Hiro Kishimoto

1 0

Proposed agenda for Oct. 23rd call
by Hiro Kishimoto 23 Oct '06

23 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 23rd Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1023 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (if available) Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F update (20 min) 3) HPC cluster usecase for EGA reference model (Paul and Hiro, 60 min) In order to clarify relationship between OGSA architecture and EGA reference model, design team is trying to write-up HPC cluster usecase for EGA reference model assuming that OGSA is SOA and Web-service based instantiation of EGA reference model. Hiro's draft slides: - https://forge.gridforum.org/sf/go/doc13939 Meeting minutes from Oct. 9th: - https://forge.gridforum.org/sf/go/doc13942 > AI-1009a: Review slide 6 again and clarify what the problem is > (Reference Model Design Team) > AI-1009b: Review the Reference Model 'Manage Job' in more > detail. Specifically look at it from the perspective of > an enterprise application (e.g., a 3-tier app) (Reference > Model Design Team) > AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 > - Perspective of submitter vs platform provider and the > hierarchical model connection Design team will bring revised slides to the call. 4) Glossary discussion (Jem Treadwell, 20 min) Jem's email: > Per discussion on the October 9th meeting, I've now posted a discussion > document for the Glossary. The primary objective is to converge the EGA > Reference Model glossary and the OGSA glossary, and the target for > completion is OGF19. > > The discussion document is posted in the gridforge Glossary folder at > http://tinyurl.com/yzwt4c, along with the current draft of the Glossary. > > I received some initial comments from Olegario Hernandez, who has been a > regular contributer to each version of the OGSA Glossary. These > comments are posted in tracker 5617 - there's a link to the tracker in > the discussion document. > > I believe we had agreed that we would discuss the terms initially by > e-mail and with discussions as needed bi-weekly on the regular Monday > OGSA calls. I propose that we begin with a discussion on next Monday's > call, as the last agenda item to minimize the pain :0) For anyone who > wants to get a head start, I propose to look at "enterprise" and related > terms first (and, from his comments, I think Olegario would second that > proposal!). 3) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 26 (Thu): EMS scenarios, Security Oct. 30 (Mon): DMTF work register, OGSA roadmap Nov. 2 (Thu): Information/data modeling Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 (Thu): F2F prep <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Oct. 9 call. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready (by Oct. 26) AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 26) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 25 call. AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 21 call. AI-0921c: Dave S (as Standards VP) to talk to the next Security ADs (Blair Dillaway and David Groep) about the Security Area task list. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next EMS call (Oct. 26): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document ---- Hiro Kishimoto

1 1

Teleconference minutes - 19 October 2006
by Andreas Savva 23 Oct '06

23 Oct '06

Attached and uploaded. https://forge.gridforum.org/sf/go/doc13960?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd

1 0

Proposal for re-organizing trackers
by Andreas Savva 23 Oct '06

23 Oct '06

I've been talking with Jem about re-organizing the trackers and we agreed on the following proposal. If you have any comments or suggestions please respond. Background: OGSA-WG maintains one tracker per document per version, for a current total of 12 document trackers. (The number of artifacts per tracker vary.) Half of these trackers are for already published documents: they are marked 'closed' and will not be used again. Since many of our documents are likely to be revised again we'll have to set up more trackers. For example, work is already starting on a third version of the Glossary, the Roadmap is expected to be updated periodically and so on. Proposal: To keep the total number of trackers down and keep the tracker summary view usable the proposal is to re-organize the trackers so that each document has at most 2 trackers associated with it: an archival tracker and a current tracker. The archival tracker will hold artifacts of *all* past versions of that document. Artifacts will be tagged with an appropriate "Document Version" value so that it is clear which version they relate to (e.g., version 1.0, 1.5, etc). The current tracker will hold all new artifacts, including any artifacts that were deferred in previous versions. In terms of process, new artifacts will be put in the current tracker. When a document is published all closed artifacts from the current tracker are tagged with the document version and moved to the archival tracker; all deferred artifacts remain on the current tracker and are set back to the open state. Current tracker summary view: https://forge.gridforum.org/sf/tracker/do/listTrackers/projects.ogsa-wg/tra… -- Andreas Savva Fujitsu Laboratories Ltd

3 4

Updated: OGSA Teleconference
by Andreas Savva 23 Oct '06

23 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061023T220000Z DTEND:20061024T000000Z TRANSP:OPAQUE SEQUENCE:2 UID:040000008200E00074C5B7101A82E00800000000908183F164ECC6010000000000000000100 0000076824268C7E4DB45977CBD7092D2808F DTSTAMP:20061023T025306Z DESCRIPTION:When: 2006年10月24日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1023\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (if available)\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F update (20 min)\n\n3) HPC cluster usecase for EGA reference model (Paul and Hiro\, 60 min)\n In order to clarify relationship between OGSA architecture\n and EGA reference model\, design team is trying to write-up\n HPC cluster usecase for EGA reference model assuming that\n OGSA is SOA and Web-service based instantiation of EGA\n reference model.\n\n Hiro's draft slides:\n - https://forge.gridforum.org/sf/go/doc13939\n Meeting minutes from Oct. 9th:\n - https://forge.gridforum.org/sf/go/doc13942\n\n> AI-1009a: Review slide 6 again and clarify what the problem is\n> (Reference Model Design Team)\n> AI-1009b: Review the Reference Model 'Manage Job' in more\n> detail. Specifically look at it from the perspective of\n> an enterprise application (e.g.\, a 3-tier app) (Reference\n> Model Design Team)\n> AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n> - Perspective of submitter vs platform provider and the\n> hierarchical model connection\n\n Design team will bring revised slides to the call.\n\n4) Glossary discussion (Jem Treadwell\, 20 min)\n\nJem's email:\n> Per discussion on the October 9th meeting\, I've now posted a discussion\n> document for the Glossary. The primary objective is to converge the EGA\n> Reference Model glossary and the OGSA glossary\, and the target for\n> completion is OGF19.\n> \n> The discussion document is posted in the gridforge Glossary folder at\n> http://tinyurl.com/yzwt4c\, along with the current draft of the Glossary.\n> \n> I received some initial comments from Olegario Hernandez\, who has been a\n> regular contributer to each version of the OGSA Glossary. These\n> comments are posted in tracker 5617 - there's a link to the tracker in\n> the discussion document. \n> \n> I believe we had agreed that we would discuss the terms initially by\n> e-mail and with discussions as needed bi-weekly on the regular Monday\n> OGSA calls. I propose that we begin with a discussion on next Monday's\n> call\, as the last agenda item to minimize the pain :0) For anyone who\n> wants to get a head start\, I propose to look at "enterprise" and related\n> terms first (and\, from his comments\, I think Olegario would second that\n> proposal!). \n\n3) Wrap up\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 26 (Thu): EMS scenarios\, Security\nOct. 30 (Mon): DMTF work register\, OGSA roadmap\nNov. 2 (Thu): Information/data modeling\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\nNov. 9 (Thu): F2F prep\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569\n\n > From Oct. 9 call.\n AI-1009a: Review slide 6 again and clarify what the problem is\n (Reference Model Design Team)\n AI-1009b: Review the Reference Model 'Manage Job' in more\n detail. Specifically look at it from the perspective of\n an enterprise application (e.g.\, a 3-tier app) (Reference\n Model Design Team)\n AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n - Perspective of submitter vs platform provider and the\n hierarchical model connection\n\n > From Oct. 5 call.\n AI-1005a: Alan Sill willing to take responsibility for pushing\n the process for getting a charter ready (by Oct. 26)\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 26)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 25 call.\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 21 call.\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security ADs (Blair Dillaway and David Groep) about the\n Security Area task list.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next EMS call (Oct. 26):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Fwd: [IDM] New NIST Publication: An Ontology of Identity Credentials
by Alan Sill 21 Oct '06

21 Oct '06

Useful for the dictionary / glossary effort? Alan Begin forwarded message: > From: Ann West <awest(a)EDUCAUSE.EDU> > Date: October 20, 2006 8:27:12 AM CDT > To: IDM(a)LISTSERV.EDUCAUSE.EDU > Subject: Re: [IDM] New NIST Publication: An Ontology of Identity > Credentials > Reply-To: Identity Management Constituent Group Discussion > list <IDM(a)LISTSERV.EDUCAUSE.EDU> > > Ken, > > Yes, we do compare notes with the federal documents where relevant. > > For instance, in the Enterprise Authentication Implementation Roadmap, > the concepts and terms in some cases cite the OMB M-0404 > E-Authentication Guidance for Federal Agencies. However, we also wrote > some of our own definitions to either scope a broader term for use in > the Roadmap context or explain a concept more simply or clearly. > http://www.nmi-edit.org/roadmap/draft-authn-roadmap-03/1- > concepts.html. > > In short, glossary definitions will be similar, but not the same. > > Best, > Ann > > > >> -----Original Message----- >> From: Ken Brumbaugh [mailto:Ken.Brumbaugh@CSU.MNSCU.EDU] >> Sent: Wednesday, October 18, 2006 2:54 PM >> To: IDM(a)LISTSERV.EDUCAUSE.EDU >> Subject: Re: [IDM] New NIST Publication: An Ontology of Identity >> Credentials >> >> 10/18/06 >> >> Ann >> >> Will you, or any one, be doing a terminology/definitions check >> between >> glossaries that NMI-Edit has, and what NIST is now disseminating? >> >> If this has not been done, it might be beneficial to the group to >> have >> this done by one party - and shared with others. >> >> Using a common glossary could be most advantageous to many - >> particularly those of us, who are now starting this long IdM/IAM > journey >> with our clientele. >> >> Thanks. >> >> >> >> Ken Brumbaugh, Ph.D. >> System Director, Identity Management & Directory Services >> Minnesota State Colleges & Universities >> Office Phone - 651-201-1429 >> Cell Phone - 651-269-9988 >> >>>>> awest(a)EDUCAUSE.EDU 10/18/2006 12:36 PM >>> >> All, >> >> If you are reviewing your identifiers and credentials, consider >> reading >> the new NIST draft "An Ontology of Identity Credentials - Part 1: >> Background Formulation" released on October 6. >> >> http://csrc.nist.gov/publications/drafts/sp800-103-draft.pdf >> >> Best, >> Ann >> >> ------------- >> Ann West >> NMI-EDIT Outreach Lead, EDUCAUSE >> Program Manager, Middleware and Security, Internet2 >> Michigan Technological University 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

4 3

Glossary discussion document posted
by Treadwell, Jem 19 Oct '06

19 Oct '06

Hi, Per discussion on the October 9th meeting, I've now posted a discussion document for the Glossary. The primary objective is to converge the EGA Reference Model glossary and the OGSA glossary, and the target for completion is OGF19. The discussion document is posted in the gridforge Glossary folder at http://tinyurl.com/yzwt4c, along with the current draft of the Glossary. I received some initial comments from Olegario Hernandez, who has been a regular contributer to each version of the OGSA Glossary. These comments are posted in tracker 5617 - there's a link to the tracker in the discussion document. I believe we had agreed that we would discuss the terms initially by e-mail and with discussions as needed bi-weekly on the regular Monday OGSA calls. I propose that we begin with a discussion on next Monday's call, as the last agenda item to minimize the pain :0) For anyone who wants to get a head start, I propose to look at "enterprise" and related terms first (and, from his comments, I think Olegario would second that proposal!). E-mail comments and suggestions are, of course, welcome. Thanks, - Jem ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

1 0

Editors call postponed to 25th.
by Christopher Jordan 18 Oct '06

18 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 We had previously discussed having a Roadmap editor's call today. Due to scheduling conflicts, I'd like to postpone this call to the 25th of October. I'll send meeting details soon. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iD8DBQFFNnevPCVtcXn6kg8RAoy1AKDmAZtVYmurstZfLgb78WZHv9WqqQCdGI4G jIIklhp2/eiZNURVy8YVY8w= =xiYz -----END PGP SIGNATURE-----

1 0

Proposed agenda for Oct. 19th call
by Hiro Kishimoto 18 Oct '06

18 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 19th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1019 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 16) - https://forge.gridforum.org/sf/go/doc13952 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F update (Hiro Kishimoto, 10 min) 3) OGSA AuthN WG BoF draft (Alan Sill, 30 min) > - Alan Sill willing to take responsibility for pushing the process > for getting a charter ready > - AI-1005a: Alan Sill to have draft Charter ready before next > security telecon (Dave to help and only as stand in for new area > director). > - Do we need more covereage if we have an active authorization and > authentication working groups > -- No, we need more covereage > -- AI-1005b: People to send Dave Snelling more information, ideas for > more security calls to complete coverage 4) Security Profile Update (Takuya Mori, 30 min) > AI-0928a: Takuya will issue a final call on BSP-Core on the list. > - Need to check status of WS-I documents > - Secure Channel Profile on next telecon 5) Information/data modeling (Ellen Stokes, 30 min) > - Discussion on if a requirements XML document could be constructed > with powerful comparative expressions and at same time avoids the > XPath expressions/joins on collecting input documents? Perhaps just > the relevant subset of a query in job. - Agreed to discuss more in > second hour on Next Call - Oct 19th 6) Wrap up AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling, EMS scenarios Oct. 30 (Mon): DMTF work register Nov. 2 (Thu): Security Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 (Thu): F2F prep <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569 > From Oct. 16 call. AI-1009d: Jem Will post tomorrow, comments received and will put into tracker. AI-1005a: Charter form created, ready for review. Hiro will send links to charters. Paper work for new working group needed - can use security design team folder in OGSA temporarily. Feedback: Use next OGF to start WG rather than form a BOF. Hiro will bring proposal to GFSG, since needs security Area Director approval & GFSG. > From Oct. 8 call. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready (by Oct. 19) AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 19) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 25 call. AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next EMS call (Oct. 26): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

2 1

Draft charter for OGSA-AuthN WG
by Alan Sill 18 Oct '06

18 Oct '06

Discussion among participants and potential participants has indicated a desire to proceed directly to a launch of the OGSA-AuthN working group rather than proceed through a BOF. Most people who would participate or be affected have up to now been involved in related efforts and would be able to come up to speed fairly quickly in this effort. Here are the elements of a charter, or potential charter, for this group that I have identified: 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 b) Review mature and maturing technologies likely to affect the above best practices for grid services 2) Provide an AuthN development roadmap to compare with the overall OGSA roadmap 3) Spawn any subgroups and/or suggest associated research groups that may be necessary for consistent development in this area. The charter can be developed from the above skeleton, and the basics agreed to before the first session at OGF-19 in North Carolina. It is explicitly a part of the charter for this group to work in a symmetrical manner with any OGSA-AuthZ work that may be needed for consistency in grid services. Comments welcome. Alan 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

2 2

Proposed agenda for Oct. 16th call
by Hiro Kishimoto 16 Oct '06

16 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 16th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: <1002> See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 2 & 9) - https://forge.gridforum.org/sf/go/doc13917 - https://forge.gridforum.org/sf/go/doc13942 Action Items status review (see the bottom of this email) Agenda bashing 2) Nov. F2F meeting update (Ellen Stokes and Fred Brisard, 20 min) Next interim F2F will be on Nov. 9 and 10 in Tampa, FL just before SC06. Review logistics, agenda, and attendees. - https://forge.gridforum.org/sf/go/wiki1620 3) New DMTF workregister review (Ellen Stokes and Tom Roney, 30 min) After GGF and EGA merge, OGF need to agree new workregister with DMTF sooner rather than later. Tom Roney, OGF liaison to DMTF, is working on new draft. - https://forge.gridforum.org/sf/go/doc13947 From Tom's email: > Please take a look with these notes in mind: > > - I added "Background" to the "Mission" heading > Our (GGF/EGA) mission statements have > been combined. Modify as you see fit. > I did remove references to "enterprise" > grids and "enterprise" grid computing, > referring now to (simply) grids and > grid computing. > > - Under the heading of "Alliance Scope" > Please take a look at the third paragraph > regarding the "Reference Model." Do we > leave this? I think so. > > - After Figure 2 > We should include a corresponding link between > the OGF's Semantic Grid Research Group and a > group within the DMTF. What would that group be, > and who would be the DMTF contact? > > - Under the "Milestones" heading > I have done little with this other than > to remove what has been accomplished wrt > the last register for the GGF. > > Do we still want the second bullet, regarding > mapping the work underway, etc.? I think this > is important, but we (I) did nothing to move it > forward, and it will take the effort of a good > many minds. > > Please add to and/or modify this list of goals. > > - Under the "Contacts" heading > I have updated the OGF side with respect > to the once-GGF contacts, noting that the > Security Area Directors are listed as > Olle Mulmo and Dane Skow. I do not know > if this is accurate, and do not see on the > OGF website where this can be found. Also, Ellen will bring OGSA-WG related update before the call. > AI-0915b: Ellen to check the status of the items on the > DMTF work register: report which have been done, and what > DMTF is doing for the rest. (by Oct. 13) > AI-0915c: Ellen to propose new text to update the DMTF register > (by Oct. 13) Obsolete GGF-DMTF workregister: - http://www.ogf.org/documents/liaison/GGF-DMTFWorkRegister.pdf Obsolete EGA-DMTF work resister - http://www.dmtf.org/about/register/EGA-DMTFWorkRegister.pdf 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 16 (Mon): DMTF Workregister Oct. 19 (Thu): Information/data modeling, Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling, EMS scenarios Oct. 30 (Mon): <TBD> Nov. 2 (Thu): Security Nov. 6 (Mon): EGA reference model, OGSA roadmap Nov. 9 (Thu): F2F prep <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Oct. 8 call. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready (by Oct. 19) AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 19) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. > From Sept. 25 call. AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Oct. 13 call: AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register Until next EMS call (Oct. 26): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

2 1

Updated: OGSA Teleconference
by Andreas Savva 16 Oct '06

16 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061016T220000Z DTEND:20061017T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E008000000008088EFBB64ECC6010000000000000000100 0000040E2FFAC2911984D9CA8E87DBC436C4A DTSTAMP:20061016T094843Z DESCRIPTION:When: 2006年10月17日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: <1002>\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Oct. 2 & 9)\n - https://forge.gridforum.org/sf/go/doc13917\n - https://forge.gridforum.org/sf/go/doc13942\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Nov. F2F meeting update (Ellen Stokes and Fred Brisard\, 20 min)\n Next interim F2F will be on Nov. 9 and 10 in Tampa\, FL\n just before SC06.\n\n Review logistics\, agenda\, and attendees.\n - https://forge.gridforum.org/sf/go/wiki1620\n\n3) New DMTF workregister review (Ellen Stokes and Tom Roney\, 30 min)\n After GGF and EGA merge\, OGF need to agree new workregister\n with DMTF sooner rather than later.\n Tom Roney\, OGF liaison to DMTF\, is working on new draft.\n - https://forge.gridforum.org/sf/go/doc13947\n\n From Tom's email:\n> Please take a look with these notes in mind:\n> \n> - I added "Background" to the "Mission" heading\n> Our (GGF/EGA) mission statements have\n> been combined. Modify as you see fit.\n> I did remove references to "enterprise"\n> grids and "enterprise" grid computing\,\n> referring now to (simply) grids and\n> grid computing.\n> \n> - Under the heading of "Alliance Scope"\n> Please take a look at the third paragraph\n> regarding the "Reference Model." Do we\n> leave this? I think so.\n> \n> - After Figure 2\n> We should include a corresponding link between\n> the OGF's Semantic Grid Research Group and a\n> group within the DMTF. What would that group be\,\n> and who would be the DMTF contact?\n> \n> - Under the "Milestones" heading\n> I have done little with this other than\n> to remove what has been accomplished wrt\n> the last register for the GGF.\n> \n> Do we still want the second bullet\, regarding\n> mapping the work underway\, etc.? I think this\n> is important\, but we (I) did nothing to move it\n> forward\, and it will take the effort of a good\n> many minds.\n> \n> Please add to and/or modify this list of goals.\n> \n> - Under the "Contacts" heading\n> I have updated the OGF side with respect\n> to the once-GGF contacts\, noting that the\n> Security Area Directors are listed as\n> Olle Mulmo and Dane Skow. I do not know\n> if this is accurate\, and do not see on the\n> OGF website where this can be found.\n\n Also\, Ellen will bring OGSA-WG related update before the call.\n\n > AI-0915b: Ellen to check the status of the items on the\n > DMTF work register: report which have been done\, and what\n > DMTF is doing for the rest. (by Oct. 13)\n > AI-0915c: Ellen to propose new text to update the DMTF register\n > (by Oct. 13)\n\n Obsolete GGF-DMTF workregister:\n - http://www.ogf.org/documents/liaison/GGF-DMTFWorkRegister.pdf\n Obsolete EGA-DMTF work resister\n - http://www.dmtf.org/about/register/EGA-DMTFWorkRegister.pdf\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 16 (Mon): DMTF Workregister\nOct. 19 (Thu): Information/data modeling\,\n Security\, secure channel profile review\nOct. 23 (Mon): EGA reference model\, OGSA roadmap\nOct. 26 (Thu): Information/data modeling\, EMS scenarios\nOct. 30 (Mon): <TBD>\nNov. 2 (Thu): Security\nNov. 6 (Mon): EGA reference model\, OGSA roadmap\nNov. 9 (Thu): F2F prep\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Oct. 8 call.\n AI-1009a: Review slide 6 again and clarify what the problem is\n (Reference Model Design Team)\n AI-1009b: Review the Reference Model 'Manage Job' in more\n detail. Specifically look at it from the perspective of\n an enterprise application (e.g.\, a 3-tier app) (Reference\n Model Design Team)\n AI-1009c: Hiro to ask Jay to provide his comments for Slide 6\n - Perspective of submitter vs platform provider and the\n hierarchical model connection\n AI-1009d: Jem will produce a topic discussion list for the\n converged glossary\n\n > From Oct. 5 call.\n AI-1005a: Alan Sill willing to take responsibility for pushing\n the process for getting a charter ready (by Oct. 19)\n AI-1005b: People to send Dave Snelling more information\, ideas\n for more security calls to complete coverage\n (Since this does not have any specific owners\, it will\n be closed Oct. 19)\n\n > From Sept. 28 call.\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n\n > From Sept. 25 call.\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil Oct. 13 call:\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest.\n AI-0915c: Ellen to propose new text to update the DMTF register\n\nUntil next EMS call (Oct. 26):\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security AD (when one is selected) about the Security Area\n task list.\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

clarification on the OGSA Job Management capability
by Sergio Andreozzi 14 Oct '06

14 Oct '06

Dear OGSA-WG, as part of the OMII-Europe project, I'm performing a decomposition of the functionalities provided by a number of Grid middlewares related to our project following the capabilities identified in the OGSA 1.5 document. A problem I'm dealing with is about the Job Management service. For instance, in the gLite middleware, there are two main categories of services providing job management capability: 1. the Computing Element, that is an abstraction of a batch system exposing an interface to let other services to submit and manage a job; in the near future this component will adopt the OGSA-BES interface, but at the moment it is present in different flavours (GT 2 GRAM, g-Lite CE and CREAM) 2. the Workload Management System (WMS), that is a meta-scheduler and exposes an interface to let other services to submit and manages a job (or collection of jobs or DAGs); the WMS not only does Job Management, but also Execution and Planning, and Candidate Set Generator. My doubt is the following: from the viewpoint of Job Management, are a meta-scheduler and a computing service semantically different or identical? If they are identical, is it expected that in a medium future, the BES interface could be extendend to support the number of job types handled by a meta-scheduler, hence the meta-scheduler will expose the same interface of a computing service? If they are not identical, what are the differences? Thanks in advance for your comments, Sergio Andreozzi -- Sergio Andreozzi INFN-CNAF, Tel: +39 051 609 2860 Viale Berti Pichat, 6/2 Fax: +39 051 609 2746 40126 Bologna (Italy) Web: http://www.cnaf.infn.it/~andreozzi

2 2

Teleconference minutes - 9 October 2006
by Andreas Savva 10 Oct '06

10 Oct '06

Attached. Gridforge https://forge.gridforum.org/sf/go/doc13942?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 9 October 2006 ==================================== * Participants Jay Unger (IBM) Jem Treadwell (HP) Paul Strong (eBay) Ellen Stokes (IBM) Dave Snelling (Fujitsu) Andreas Savva (Fujitsu) Fred Maciel (Hitachi) Hiro Kishimoto (Fujitsu) Chris Kantarjiev (Oracle) Chris Jordan (SDSC) Alan Clark () Mukund Buddhikot (SUN) Michael Behrens (R2AD, LLC) Minutes: Andreas Savva * Summary of new actions AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection AI-1009d: Jem will produce a topic discussion list for the converged glossary * October 5th minutes accepted with minor corrections - Correct Abdeslem Djaoui's name - Add Andreas Savva to participants - Correct AI misnumbering * Oct 2 minutes approval postponed - Many people were not aware that the Oct.2 minutes had already been posted. * EGA Reference Model ** HPC Cluster Use Case Explained by Hiro - [slide 2] Note that this description is more general than the scope of the *HPC Profile*---this is an HPC cluster use case - [slide 4] The "Abstract Application Definition" appears twice in the stack - There is no problem doing this from the view of the EGA reference model. (It is not necessary to have a 1-to-1 mapping of things on the stack.) - In this case the "HPC cluster" level is probably better called "virtualized platform". Agreed to make this correction. - [slide 5] Provisioning, etc, are noted as out-of-scope of the HPC use case. They do happen but they are done (typically manually) at very rare occasions---e.g., at installation or upgrading of environment---and might occur a long time before or after the actual HPC use case of submitting a job. - There is no actual model conflict here but that is perhaps due to the HPC work not focusing on these aspects even though there are a number of assumptions. (And the assumptions should be made explicit.) - One consequence of this analysis might be to start looking at some other use cases; and so leverage other work from the Reference Model. Staying only on the HPC use case might provide enough coverage. - The works otherwise seem complementary - "Managed Job" in the case of the EGA reference model is probably a much richer concept than in the HPC use case - A longer lived application vs one-off invocation - Interactive vs non-interactive; but this may be less true for HPC applications nowadays - If one can thinks in terms of aggregation of HPC jobs as higher level services then it would fit better into the EGA model - [slide 6] Raises the issue of difference in job vs application state model - Reviewed Paul's suggested alternate figure sent to the mailing list. Agreed it is a good way of looking at things: workload - job +- hpc cluster - node +- binary - This relationship occurs frequently. It is the same for database/database service/database software. (An instance of a database service is composed through managing the things it depends on.) - There is a danger here of trying to do a very elaborate model (like CIM). It is important to know where to draw the line and stop. - OGSA position so far is close to "stop once the service is identified"; the Reference Model on the other hand takes a few more steps towards CIM; but aims to have a broad rather than than a deep view - There is no assertion by the Reference Model that there is only one possible graph - Another difference is what the submitter of the job cares about (needed characteristics/attributes) vs what the environment/platform provider cares about (which includes the hierarchical model needed to instantiate things) - (With the reference model it is enough to focus on the current node; no need to try and dig deep in the hierarchy.) - Some preliminary work is being done in OGSA in the context of the EMS scenarios---the JSDL and CDL connection. - There is a need to discuss and refine the next version of this figure; and incorporate Jay's comments - [slide 5] Need more discussion on what "Submit Job" means - Also "Manage Job" in the Reference Model is much richer than what the HPC/BES model are doing - This is essentially the difference between (discrete) invocations of an HPC job and taking care of an enterprise application that once up has to be taken care of, resources provided appropriately to maintain the required service level, etc. AI-1009a: Review slide 6 again and clarify what the problem is (Reference Model Design Team) AI-1009b: Review the Reference Model 'Manage Job' in more detail. Specifically look at it from the perspective of an enterprise application (e.g., a 3-tier app) (Reference Model Design Team) AI-1009c: Hiro to ask Jay to provide his comments for Slide 6 - Perspective of submitter vs platform provider and the hierarchical model connection ** Glossary review Jem has produced an initial draft with EGA terms highlighted. Agreed that the target is a converged glossary by GGF19. (The HPC discussion is higher priority.) It is important to know where there are differences or discussion points. Agreed that the discussion should proceed by email and the occasional time slot on a teleconference. AI-1009d: Jem will produce a topic discussion list for the converged glossary * AI Review [Only items with updates are listed] AI-0928b: Closed (see next item) AI-0928c: Closed. Obsolete since we have agreed to provide normative text AI-0925b: Closed. Draft was posted to gridforge AI-0921b: Closed. Started writing charter. AI-0921d: Closed. AI-0914f: Closed. Picked location and launched zoomerang. AI-0803e and AI-0803f: No update. - Hiro volunteered to talk to the CDDLM-WG. * OGSa Roadmap Review Chris Jordan gave an overview of current state, followed by some discussion on the status of various documents. - There have been many contributed updates, in particular from Jem, Hiro and Andreas. - Still missing updates for some documents, especially HPC Profile and Naming. - With respect to the state of documents Dave S mentioned that the status of the WSRF and WSN specs has changed since the publication of Roadmap 1.0. - For the Roadmap however the various specification owners (that actually refer to WSRF or WSN) have to update their documents for the Roadmap tables to change. - Chris J is leaving the update of the tables for last. - Status of HPC documents - The HPC Use Cases have finished their public comment period on Sep.20. - Not sure about the HPC Profile - Naming documents: Not sure. The profile does seem close to completion. - Review progress at the next Roadmap call * Other business - Jem has updated the OGSA Wikipedia entry to bring it up to date with the publication of OGSA 1.5 and Basic Profile 1.0 - Thursday's call is cancelled

1 0

no call on Oct. 12
by Hiro Kishimoto 10 Oct '06

10 Oct '06

Hi all, We don't have a call on this Thursday (Oct. 12). Next call will be next Monday. Oct. 16 (Mon): DMTF Workregister Oct. 19 (Thu): Information/data modeling, Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling OGSA-WG and fellow WGs will have interim F2F meeting on Nov. 9 and 10 in Tampa FL just before SC06. If you have not yet answered by Zoomerang survey, please let us know your availability by Oct. 13 Friday. http://www.zoomerang.com/survey.zgi?p=WEB225QVWQBDKV For more information on this F2F, visit living agenda wiki page: https://forge.gridforum.org/sf/go/wiki1620 Thanks, -- Hiro Kishimoto

1 0

Proposed agenda for Oct. 9th call
by Hiro Kishimoto 09 Oct '06

09 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 9th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1009 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Oct. 5) - https://forge.gridforum.org/sf/go/doc13922?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) HPC profile usecase for EGA reference model (60 min) > AI-092625b: Jem to pull definitions together and produce a new > merged first draft. > - Send a mail to the ogsa list about this work > - Set Oct. 9 as the target for the first Glossary draft > - Mike Behrens also volunteered to help out on the Glossary Jem will write-up his first draft before the call. > - At GGF18 the proposal was to consider OGSA as a rendering of the > EGA reference model. Agreed that this seems a good starting > point. It should be tested by picking a candidate topic and see > if it is really the case. > - Hiro proposed the OGSA HPC Profile as a test case (a concrete > use case) > - The HPC Profile is more detailed when compared to the style of > the use cases in the EGA Reference Model. Therefore it would > help flesh out what is needed in the context of OGSA. Doing UML > would be good. > - It was noted that EGA graphs (DAGS) are specific to > instantiation > - Tentative agreement on the HPC Profile proposal but need more > information before making a decision. Hiro will write-up draft proposal before the call. 4) Roadmap document v1.1 discussion (Chris Jordon, 20 min) ChrisJ will report out the status of roadmap v1.1. He will ask if current direction is on the right track or not. The latest roadmap document: - https://forge.gridforum.org/sf/go/doc13733?nav=1 List of included documents and associated contacts: - https://forge.gridforum.org/sf/go/wiki1486?nav=1 Minutes from Oct. 4th roadmap call: - https://forge.gridforum.org/sf/go/doc13923?nav=1 3) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 12 (Thu): <No call?> Oct. 16 (Mon): DMTF Workregister Oct. 19 (Thu): Information/data modeling, Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling Oct. 30 (Mon): <TBD> <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Oct. 5 call. AI-1005a: Alan Sill willing to take responsibility for pushing the process for getting a charter ready AI-1005b: People to send Dave Snelling more information, ideas for more security calls to complete coverage (Since this does not have any specific owners, it will be closed Oct. 19) > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. AI-0928b: Takuya will get another opinion on TLS 1.1 and ciphersuites (probably ask Frank Siebenlist) AI-0928c: Andreas will propose new text for the reference to the NIST document to make it clearer that it is an informative statement > From Sept. 25 call. AI-0925b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 21 call. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Sept. 14 OGSA F2F AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until Oct. 13 call: AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register Until next EMS call (date TBD): AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

3 5

Nov. interim F2F meeting survay
by Hiro Kishimoto 07 Oct '06

07 Oct '06

Hi all, OGSA-WG and fellow WGs will have interim F2F meeting on Nov. 9 and 10 in Tampa FL just before SC06. Please let us know your availability and session proposals by answering Zoomerang survey before Oct. 13 Friday. http://www.zoomerang.com/survey.zgi?p=WEB225QVWQBDKV For more information on this F2F, visit living agenda wiki page: https://forge.gridforum.org/sf/go/wiki1620 Thanks, -- Hiro Kishimoto

1 0

OGSA-AuthN WG start
by Alan Sill 06 Oct '06

06 Oct '06

Hi Hiro and the group, At the EUGrid PMA meeting today in Karlsruhe, Germany ( see the URL http://eugridpma.org/agenda/fullAgenda.php?ida=a062 for details), there was wholehearted endorsement of the idea of starting an OGSA-AuthN working group and for organizing a BOF along these lines at OGF 19 to write the charter and begin the OGSA activities of this group. At this point, I would like to suggest that we formally pursue the steps to create this group. Best, 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

Roadmap call minutes, 10/4, uploaded
by Christopher Jordan 06 Oct '06

06 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the OGSA Roadmap editors call of October 4th to Gridforge. Hiro and Dona, please feel free to make additions or corrections if I missed anything. https://forge.gridforum.org/sf/go/doc13923?nav=1 The next OGSA call discussion of the Roadmap will be next monday, October 9th, and I'd like to propose that the next OGSA Roadmap Editors call be Wednesday, October 18th. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFJZniPCVtcXn6kg8RAm+IAJ9D3uCKvU6FpcPnCmX177UY4W05UQCggMMs uBSM8D7KOIGB9MXqlT5pNfs= =PszJ -----END PGP SIGNATURE-----

2 1

Fwd: [caops-wg] OGSA activity to cover authentication and identity provision roadmap
by Alan Sill 05 Oct '06

05 Oct '06

FYI -- this is typical of responses. Alan Begin forwarded message: > From: David Groep <davidg(a)nikhef.nl> > Date: October 5, 2006 6:54:42 AM CDT > To: Alan Sill <Alan.Sill(a)ttu.edu> > Cc: igtf-general(a)gridpma.org, Mailing List for CAOPS-WG <caops- > wg(a)ogf.org>, gsmv(a)webapp.lab.ac.uab.edu, gridshib-beta(a)globus.org > Subject: Re: [caops-wg] OGSA activity to cover authentication and > identity provision roadmap > > Dear Alan, all, > > First of all, I would like to support this proposal, as it could > indeed > provide the focal point for harmonisation amongst the various > activities in this area that have emerged both inside and those > (still) outside OGF. Over the past year I feel we have come quite > close > to a kind of "common understanding" of what the issues are, and > drafting > a collective roadmap is IMHO a very timely activity. > > Of course, I can happily offer a timeslot during the upcoming > EUGridPMA > meeting to discuss this (of course also completely open to the > world and > community at large: join this part of the meeting via VRVS in > the "Sky" virtual room, "Earth/Universe" community: www.vrvs.org) > If the current planning is not optimal (this Friday, Oct 6, > 11.00 AM CEST=UTC+2), it can also be delayed a few hours. > > As I see it, the BoF for this new WG could also address some issues > I feel we currently have with the CAOPS charter and position with > respect to other activities in OGF (both with CAOPS being seen as an > "operations" activity, but even more importantly the possible > conception > that CAOPS is only about the operation of "traditional" X.509 CAs). > In this respect, I would be highly interested in how others in CAOPS > see the relationship between CAOPS and such a new group. > Personally, I think also the IGTF as an operational policy > coordination > body, should have close relationships with both groups, especially > as they are expanding into new authentication profile models. > > There is, however, also an increasing overlap between the > activities in > AuthN and AuthZ. The new federations of organisationally-based > sources of authority supply attributes and assertions that are > relevant for both: some attributes relate to what we have > traditionally seen as authentication (unique names, their long-term > binding to entities, and the way to prove identity), but others > by the same source relate more to authorisation (roles, position in > the organisation &c). > In the long run there may be not that clear a division between the > two, especially when multiple sources of authority are involved in > a combined decision. But this combination of assertions, possibly > with different assurance levels, and with different levels from > different sources, will highlight the need to convey such assurance > levels, and their recognition in policy decisions, in a harmonised > formats and semantics. > Will the AuthN roadmap address include such issues - which I > think it certainly should - when these assertions relate to > long-term "AuthN" attributes? Even of the actual assertions are > more related to what we might now consider "AuthZ" (such as > organisational role/position)? But that's probably something for > the BoF to figure out (given sufficient participation from > the OGSA-AuthZ folks). > > Lastly, I think we should advertise this BoF and our intentions > widely, as there are very many related activities in this area, > also outside OGF. In particular (with a slight European bias) there > are the TERENA TF-EMC2 and TF-Mobility groups that to some extent > rely on or aim for coordination in this domain; there is the > eduGAIN activity (organised as part of the GEANT2 project); and > the EuroCAMP meetings on federation (the next one in two weeks in > Malaga, ES) are all highly relevant to this work. Many of > our combined groups will attend at least a few of these meetings, > and -- if we all agree OGSA-AuthN is a good idea -- should take the > opportunity to get all relevant people around the table at OGF19. > > > Best regards, > DavidG. > > > Alan Sill wrote: >> I'd like to suggest to the CAOps and Grid CA community that we >> attempt to pull together thoughts on grid identity authentication >> in terms of a roadmap and/or BOF among interested parties, >> focusing primarily on the AuthN side. This would be a complement >> to the OGSA- AuthZ activity, which we could clearly call OGSA-AuthN. >> I realize that we need another working group like, well, a whack >> on the head, but I have thought about this one a lot and I think >> that the OGSA process would bring a lot of rationalization to >> the activities and effort that we are pursuing more or less >> piecemeal in the search for a workable solution. Among things >> that we could gain by having such an effort, we could include: >> - Clear separation from OGSA-AuthZ while still allowing a strong >> channel for communication >> - Bringing together several different working groups who are all >> working on identity provision (as opposed to authorization) for grids >> - Providing for better communication between the OGSA roadmap and >> CAOps practices >> - Providing a context for working groups, such as the Bridge CA >> and Shibboleth activities, to communicate their findings >> - Placing OGSA-AuthN and OGSA-AuthZ on a similar footing >> To follow through on this, I would like to have a brief discussion >> in the IGTF portion of the upcoming EUGridPMA meeting, followed >> by a similar discussion at the TAGPMA Novemvber face-to-face, and >> of course encourage similar discussion at the APGridPMA meeting >> this fall. Any decision to follow this path should be discussed >> with the incoming area directors of the Security area within the >> Open Grid Forum, along with specific details about the charter. >> To make this happen, we could form a BOF to be held at the next >> OGF conference in North Carolina in January, along the lines of >> the recent "Shibboleth for Grids" one that we held at GGF 18, >> with an aim to take on this topic as a roadmap activity directly. >> Thought are extremely welcome and recruited. As a point of >> background information, I have been discussing this idea among >> the members of the overall OGSA-WG working group, and have found >> many useful suggestions and an open reception to this idea. The >> topic of a BOF as discussed above has been strongly encouraged. >> Best, >> Alan >> 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : >> ==================================================================== >> -- >> caops-wg mailing list >> caops-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/caops-wg > > > -- > David Groep > > ** National Institute for Nuclear and High Energy Physics, PDP/Grid > group ** > ** Room: H1.56 Phone: +31 20 5922179, PObox 41882, NL-1009DB > Amsterdam NL ** > > 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

Proposed agenda for Oct. 5th call
by Hiro Kishimoto 05 Oct '06

05 Oct '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 5th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1005 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Sept. 28) - https://forge.gridforum.org/sf/go/doc13912?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA security (David Snelling, 60 min) - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization 3) Secure Channel Security Profile status (Takuya Mori, 20 min) > Takuya will prepare a new version. Since there are a number of > unresolved issues the Secure Channel will not go to final call until > the issues raised during this review are closed. > > There is a security discussion scheduled for next Thursday (Oct > 5). Confirm status at that time. 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 9 (Mon): EGA reference model, OGSA roadmap Oct. 12 (Thu): <No call?> Oct. 16 (Mon): DMTF Workregister Oct. 19 (Thu): Information/data modeling, Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap Oct. 26 (Thu): Information/data modeling Oct. 30 (Mon): <TBD> <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Sept. 28 call. AI-0928a: Takuya will issue a final call on BSP-Core on the list. AI-0928b: Takuya will get another opinion on TLS 1.1 and ciphersuites (probably ask Frank Siebenlist) AI-0928c: Andreas will propose new text for the reference to the NIST document to make it clearer that it is an informative statement > From Sept. 25 call. AI-0925a: Hiro to setup wiki page with names of people who have expressed interest in the security team AI-0925b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 21 call. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items for Oct. 5th: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. (by Oct. 13) AI-0915c: Ellen to propose new text to update the DMTF register (by Oct. 13) AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Sept. 14 OGSA F2F AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. Postponed: Until next EMS call. AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. ---- Hiro Kishimoto

6 8

OGSA design teams and members
by Hiro Kishimoto 05 Oct '06

05 Oct '06

Hi all, I setup OGSA design team wiki page: design teams and members, not only for security design team but all. It is draft status. Please have a look. https://forge.gridforum.org/sf/go/wiki1618?nav=1 > AI-0925a: Hiro to setup wiki page with names of people who have > expressed interest in the security team If you find any mistake or you want to add your name, please update this page by yourself or send an email to me. I will ask each design team lead to fill in their "current scope" and "milestones and schedule." Thanks, -- Hiro Kishimoto

1 0

secure channel profile explanatory ciphersuite statements
by Andreas Savva 05 Oct '06

05 Oct '06

The Security Profile - Secure Channel (Sep 28 draft) has a set of statements, which elaborate on the compliance statements, along the lines of "Ciphersuites listed in Table 3 in TLS-Guideline [TLS Guidelines] meet criteria of R0XXX." We discussed these statements last Thursday and it was stated that such statements are not intended to be normative. I took an action to rewrite the text to make it clearer that these are not normative statements. The problem I have after looking at the text again (incl the compliance statements) and also looking at the WS-I BSP is that it does not help people wishing to implement the Secure Channel profile if these statements are not normative and if they do not describe concretely which suites should be used (or not). Saying 'do not use known insecure suites' or 'only use secure ones' are motherhood statements. In any case they are not really testable which is one point of compliance statements. Also the WS-I BSP has some discussion and normative statements in sec.3.2 about TLS/SSL ciphersuites and since the Secure Channel states that it "extends the WS-I Basic Security Profile 1.0" I became unsure about the relation of the various compliance statements in the Secure Channel and the statements in the WS-I BSP is. In short, sorry, can't do. I am not a security person... ;-) Maybe we should discuss this issue again on the next call this Thursday. (Dave? Alan? Takuya? Frank!) Andreas

3 3

Updated: OGSA Teleconference
by Andreas Savva 04 Oct '06

04 Oct '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061005T133000Z DTEND:20061005T153000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000C06829BECBE7C6010000000000000000100 000001D94CC1AEEC74D49AD628FD7F700343E DTSTAMP:20061004T090532Z DESCRIPTION:When: 2006年10月5日木曜日 22:30 to 2006年10月6日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Oct. 5th\nThursday from 8:30am - 10:30am (CDT).\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1005\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Sept. 28)\n - https://forge.gridforum.org/sf/go/doc13912?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) OGSA security (David Snelling\, 60 min)\n - What needs to be done to achieve simple interop\n generally and to bootstrap more\n - Profile to get authentication information from a\n secure channel for authentication\n - Profile for other methods to get authentication\n informatin for authorization\n\n3) Secure Channel Security Profile status (Takuya Mori\, 20 min)\n\n> Takuya will prepare a new version. Since there are a number of\n> unresolved issues the Secure Channel will not go to final call until\n> the issues raised during this review are closed.\n> \n> There is a security discussion scheduled for next Thursday (Oct\n> 5). Confirm status at that time.\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 9 (Mon): EGA reference model\, OGSA roadmap\nOct. 12 (Thu): <No call?>\nOct. 16 (Mon): DMTF Workregister\nOct. 19 (Thu): Information/data modeling\,\n Security\, secure channel profile review\nOct. 23 (Mon): EGA reference model\, OGSA roadmap\nOct. 26 (Thu): Information/data modeling\nOct. 30 (Mon): <TBD>\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Sept. 28 call.\n\n AI-0928a: Takuya will issue a final call on BSP-Core on the list.\n AI-0928b: Takuya will get another opinion on TLS 1.1 and\n ciphersuites (probably ask Frank Siebenlist)\n AI-0928c: Andreas will propose new text for the reference to the\n NIST document to make it clearer that it is an informative\n statement\n\n > From Sept. 25 call.\n AI-0925a: Hiro to setup wiki page with names of people who have\n expressed interest in the security team\n AI-0925b: Jem to pull definitions together and produce a new\n merged first draft.\n - Send a mail to the ogsa list about this work\n - Set Oct. 9 as the target for the first Glossary draft\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 21 call.\n AI-0921b: Security members to discuss the BoF proposal(s) further\n - For example\, one outcome could be some standards\n activity to mirror CAOPS activities and tie-in to OGSA\n AI-0921d: Dave S to collect additional material in order to identify\n security issues better.\n - (AI-0921e is an issue instance)\n AI-0921i: Dave S to provide an agenda for the next security call.\n - Draft agenda items for Oct. 5th:\n - What needs to be done to achieve simple interop\n generally and to bootstrap more\n - Profile to get authentication information from a\n secure channel for authentication\n - Profile for other methods to get authentication\n informatin for authorization\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest. (by Oct. 13)\n AI-0915c: Ellen to propose new text to update the DMTF register\n (by Oct. 13)\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Sept. 14 OGSA F2F\n AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the\n next F2F and inform the group vial the mailing list\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\nPostponed:\nUntil next EMS call.\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security AD (when one is selected) about the Security Area\n task list.\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC END:VEVENT END:VCALENDAR

1 0

OGSA Roadmap draft 4 on GridForge
by Christopher Jordan 04 Oct '06

04 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the most recent OGSA Roadmap draft to GridForge, and am passing the pen to Andreas Savva so that he can add the "OGSA-EMS Architecture Scenarios" section, and update the JSDL information, since I'm mostly still waiting on updates from document authors for most of my remaining changes. I've updated some of the document status information and done most of the formatting and textual changes required to conform to the new OGF document template. I've also added a draft Web Services context section from Mike Behrens, currently in "Appendix B". The document remains imperfect and all the graphs still need updating, but it's getting closer. https://forge.gridforum.org/sf/go/doc13733?nav=1 Andreas - Please upload the document to GridForge and let me know when you've completed your changes and are ready to pass me back the pen. Feel free to call in to the Editors discussion tomorrow afternoon if you have any comments or updates for the Roadmap document. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFIzDSPCVtcXn6kg8RAjlaAKCxit0Mu95fh3ONMyO74q//BOuy8ACghdks 1GKCvJ4k+BklmJbEiVQGTjQ= =3M4M -----END PGP SIGNATURE-----

2 1

XQuery
by Michel Drescher 02 Oct '06

02 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Folks, here's the example. Cheers, Michel - -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFIZpUk0lMZTNKw4QRAhCVAKCvVAMQQlbPbAQT6Rbh3TFjOZ2zQwCgqOZ7 lOFLThj9uYHgjYe7ZgubuGs= =CkQ3 -----END PGP SIGNATURE----- declare function local:filterByProcessorArchitecture( $proc as element(), $resources as element()+ ) as element()+ { if ( count($proc/Architecture) > 0 ) then for $resource in $resources where data($proc/Architecture) = data($resource//Architecture) return $resource else $resources }; declare function local:filterByOSType( $os as element(), $resources as element()+ ) as element()+ { if ( count($os/OSType) > 0 ) then for $resource in $resources where data($os/OSType) = data($resource//OSType) return $resource else $resources }; let $job := doc('./job_1.xml') (: load job 1 :) let $jreq := $job//Capabilities (:take the Capabilities :) let $prov := doc('./provisions.xml') (: load the hosts :) let $resources := $prov//Resource let $result := local:filterByProcessorArchitecture($jreq/Processor, $resources ) let $result2 := local:filterByOSType( $jreq/OS, $result ) return $result2

1 0

Regrets
by Maguire_Tom＠emc.com 02 Oct '06

02 Oct '06

0 *H÷ 010 +0 *H÷ $Content-Type: multipart/mixed; boundary="----=_NextPart_000_0075_01C6E644.4F15C830" X-MS-TNEF-Correlator: 50D422D665E6C601 This is a multi-part message in MIME format. ------=_NextPart_000_0075_01C6E644.4F15C830 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 ------=_NextPart_000_0075_01C6E644.4F15C830 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IjAVAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBAFQAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAADANAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAAyNQsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAE9SAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAC4wAgEJEAEAAABkEgAAYBIAAOEpAABM WkZ1byBLeAcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3RbCZgdABUAHbX0CgwBQ9wPUFc8W22IXsRggF4IeVIcYoAcT GbdoZWx2HIDlDrBhGzQzNxuvHL8dx1cX5B4yGKBWBJBkAHBhxwKDDwIVbTIzOCIUGj74IENFGb8a yw4AE5AlfvcYECafJ6V5CLEoTylbDhC5FW0xNhuRK48DgkcJ0dZrLQ8pPTYvHzYlUTBvfQOCVAhw Mg8pPSDxErBkdmkDNi+INyDxNW8DgijISGViCXB3KTbvKT3/JoE5HzokJo87lgcQAaAOsOs8fyku OT8PODQBQF8Dgn5CQnEOsEIvKTwXwEQ/NtcqIUWPO8NWCJB0JMAHgf5lQh9IPiVRISwmaAcTJ/r/ H/1JECohTt0rR1BVLOlRb/8vASEsMBhQVDG8VU80AVaO/zU2UFQ2ullPOOhWjTp3UFT/PA9dLz6I Xt5P3EGvYc9EId9WjUVHUFRG3WZuNwvCVp3vSmZgVUv/ak9mNSBOryZo/yR1J/FvhVJ/Kzhxpyzg b4X/Vl8wGHGmMbNvhVpfNRhxpv82sW+FZ39FOHGmRtRvhBfgf3tfSldxpm2aAoACkQjmO/UJbzCC D2Uu4YM6LuKEH/+FKIMkLuKDr4d/hz2Gv4Tv84M/FDAyOI0KjiGN347p/4MkjxKNf5FPkQ2Qj46/ koT+OQ8gldSXMY9TlzACghBQvHlsB5Af8CHgAABxAyEebBLBBRABQAPwZGN0LmwKsZoQQcBwAQFh dXtNAABgcwqwmnAhoJtybkx1bUzRmzB0bw1RauZ1EFAFEGdom2AFEAoBy5mgCgFpAZBwMAMwACCm bBDAIXFzMQMwYQEx/5+AC/ArUAdADbWZgZ1AnvT/npGf0xMnE+gI0AnAPsCh0xxucKIpo8QDMHNu Zf54IfAHsAWwAMACcxbgnzF/npENYD7QIEAgIKTxIdBtTmkSAKawCfAgRJsUIBpQCsBhCcCa4Ggg RncCIaXkEGAxAFAQYANgdycLMJ1AAYBzVz7AdGjeQhOQnUAKsKawbA3gQCB9q1Ryq8gNkKs2AYCt N2LlrTdyqzJjYgqwMACvIn8iIK+DAmALgAmRsFSYsHDuZasxBPAgAGyaIasAqqH9sLFzICAAIEzx qbE8MKxQf7MWCVCzNAyxs0OaoLM0ZL5ntBa1kLUWnwCzNHYDMP+Zb5p/m4+cn52vnr+fwryx/6Dd vAENtKHEFCKf8aMsv8f/wUSk9angpyylhE0gAaCY0P+l56Chpqi87b48uWAI0CUg/aTxYrmgCYAC IKZimKEhwJs+wJ/wM0Uwj6AgSLFB77QAC4B386YjNsVPxl/Hav/I4shvyXepILHQqkAJgMoP/zpg yz+fFwBRvf8bdAwBzf/3p0oQQMohcwIgUIEQQAWgbG1wFzLJDkUAwAMQU9+YsjpggTMW4AtgdAnw EGAzmLO3sHNkEFAHcGF4b8UgNADbMRFRawmAAQEwi6XzgiB2AlEge1XKcPkXIHdu2fXJQt1S3nMm YD40XiHJQ1pARUHJQjg0/DUxK1DJQuDA4LA1IclD70kQDvATkOGkNw8QAFDJQv4zKhDgwOI040Bn YFZByUL+NA3gDfDgNN9wAdAPEeUVzDc5RCDkYzg4yaDkRPsXwBfAOeREAcDJoEUw58VuOEAQt+Hn 4jPi0OZFOO/gwEVA35SXMDABwOp2LvD/5ZUN4OjB5KDg5AHQ4hHg1f/q4cmg4jQO8OdhKhHstGtw /6vQ35TuAA7wlyDslemBa2Df69UmcBfg5tDvpTnjQA7w/+DlSlDmsO4V41HnoOA0xSDYOTQ34XX0 cTgu8OZU+zAQE3A08lD1pcmQ4LD1le9AEI+gIOH3NDkYEPSw9+b/5CDJwODk+FDJweDV6tEXsP/u FeQgXiD0Bvkh8jHfBBfw//Ph/FfmQPHF4tCrwWdh/fT/8lD2MOLkb+AX4uA06CHq8Pv3BSZgN/Sg 4KDfBMmUAab/6QAABuCg4VHg1DjB42EAFf/useTA4jUAsDAgBUdeIP2B/98E4JATgOhVj6DmQOmA 4DT/F+DmQPSQ5ETm4eCQezEJNP8wIPJACdUX4eYw35QTgFZA/99wCFXJkMmQ5CDi9OYRC7H/4vQB UOCgn/ENtelxC1XisP/iEQ8WSlBWQOGEJnBFQO62/yZw8lLoZBggycCXIuRkF8D/ezDflAmwALDg oBOX+3HkRf/3ofPh5FQYIAmBEhUYIDAg/+F1DhD0sCOh5QUu8Ogx5QX/9sABdt9x8ZHlpuCS5lXo EP8JsASFDtLwAeZl//Au4hy1/zjQ6iDmZUAQ9gASFfBAWkD/9VAe5ueg1OHJQv/wHeH0oP8gZfbA RBAhFveB8EUlQGdg/+lw4DQFENTgCAAilemA5tD/DkUFEPSQj6AilevAJTHiNP8z8PYw6vDmVDjQ +dFiwSBz/+bQokA6cSf0IjHtRSjxG3H/5EREEF4gcQAnFeZAojDnpf8wIObQM/DhhHshEcHgNPbA /2/g9JDg1PbAI/EURSbB7gD/a3HnIx3S8QVWQBNRKgVaQP9rYAmw4jQGkXaQ+FAxpftR/+hV+TED cjMlDHDmIecU+FD/55BxEefTojDuAOrwNWUIAP/mwefEOmAMcPKFIzHlgee1/+SgK3E4VuKwMvYB UAtA93D/6RUesXViOrSp4Jcw6GXpAP/JkTbV6QBnYAvgPCWksEUw/+e1J6H5Nh6R+3HmVGRg8lD/ q9A9leZA6XABUOBE6vELQP/pFPwh6YDrFcnA5MDisOI0/xKRq9Dm9SehKIAnBSei9VD/QVXyQBfx QtUi8TgR4EQwcf9BN1ZAEELgROgQlyAAsOBE/+kA+SFEVf5xGjbmwPhACvH/4ETyUPhAHUUIAf/g 98X4Uf/2weDUTRKiQE4X6XD0BfhQ//bA9tHqhKngZ1HhhPBAWjH/AYUvEV+x6GTwQOpRLcWXMP8O EDmB6oX2wO5wThUcUSt2/wjxYsAIAOqE5DDuABRFQfH/+GAABTpRCwLqhCqBB1Hr5f+iMAFQdqHr 9PARJTFaNuCR/+OFPhNv0lsWJ4HoZKBx65H/56WgcShhDkW/ovVBXwf/8P+/suv0UlFrYmDF1ODh 8WC2/09hAYWksekA43aksAmwCZH/Y+fjQFLx6+Um »sT1R6+YLIv9eNuCRY4Hg5GeCDhDslaSw//SQ dqBeNangGrHvhvARC8D/4CVQwRKRDYWp4AvAT2Foxv9NMfV3xSAL4EK2qeDngf8B/26GH3EYxW7R 8/EMBang9LH/LxFoBT1BCLFxxnmB9JBxxv8+AeZFc7IXAF72c8E9cV1l/yPRj6BdVmrhIjHtVuDA C0D/IQVaozaR7KUjAW/34pKrwv95Jeog+cF6tyiAWuZVUWLx/+vVVVFK0XxGFwEgsX32CZD/eBgb cQxwfrbgsDFh7JYR8f8m0YBm56BXkYIH6OBw1uHx/wxwCbDuJhzxWhYE8fGS7ub//9EJkO7mayAI AO1WPIHz9/+IESiA7RCHtx6Ch7ZbkXQW/+jR32F8RvVQTcFhdTXx/+D/LcXv8emh7gZSUfJASYXv 8f8oQT2F7/HyUY+3RkHgoe+l/+Cw/NKRdioABnGRdikxWUb/40CDYXJ2ZUGAwu+l+sDz8f+MhmFg 9KBzRl7RkTGSNugQ//MRlKZNslBF8jH0wN9h8eb/9LBWNvIxNEHyh+eRZhHg5f92IqSwnNb1cVKF nSH7UeyG/8mQiQGdhwCB5rDyllbxZjf/9tHqUaGnDACksPQVAsF/8f+hphPxG6GkJmsg9KDvlQ4Q //nCWVVnsQJA5DXhMh3ho0b/mhE1Aag3Cafy8eSgpXHypv9EMfrGqwIngfKmg1FjBqWR/28Aomf0 kB6hnMbnoPdxnzb/56CmYaaG5CDxsWF1//BTAv/vlf/wKoEFRZHx5NBQwbLG/wOBgeaR4QUx81b+ MDLCtTb/C8HzRyMB/aG1NjaRZkbrwP/rgRpFxSB0wo1GuaF0sbeW/+SgCzG6B4JhW7YYkfhBsRb/ A5FGMfNlDUH+MLeWMrESwP++F1YxcAaTghKRwJYWQXMQ/8CWryGZdgmQW3HCF3ZxBdH/9CYs8e7G OBHnoKWm5WEIsf9clfrAflFbtuQwLNHHxxBx//YQ9BVwwQIhyXea4eZA0RMweG1sbtrA3tF9XHRw YdCRd3lhnLHMI2jHCYJhcNlAcmdsciHNhFpyzfd0pHHNhGLPM2d0dXTagHJhcNPR2ABjOnTTsHdZ kN3g0PBybOHUgHRuYmrTUNqQ3IAV3EBc3dB42mF0b3kB2pBcZXhwc2hyW9Hg0qF10KHcAHDSkGTH 2qDe0MugYmRi0qHW8ORhY9ygb3LUINHA1eBKbdOgYdyQXGjWQHpp0nJkZ82iadNQ11Bot9WDciHX QXbYGdbRadeh/6wBWiDYodmVRbLX4tbQzHDr2JPbY2rTcWHSUNSg1yAMdHnMQFyQdmlldw5r2dAg oN1Dc2NhbEvYUKjhcM+wcmTNIGVH1pDetdYwb3Rc1YBs8Hl0d27Z0Naw0dHgR/xodM+A0DDVgNKh y5DhkGXWkGrLwVx10NDQoGL/3lDXwONRy8HdodCQ4FDeQfvQ8MvQd+QTy8HTwM5w0JB50fBya9Xx 1rDVYOXRd+RycOKyc27M8NMQznC3WZDZ0NWwbNYQ3lBs0WD6Zt1gbNag0lDjAdEg5rDscHXnwOAA YewA3IDl1t1ZcnLf4QH24KB3y8HLsHp51fFz0qHOcNFg4cFvQ+hw0QFmZXQwyzJ34c5wZmZtdOhw 0KDMUPIgY7AzZswA7mDWMM+A595A5FDLkHVw0IPMIO6ge+AQ0OFk0RDQpdCQ4JF4/2Fw0kHiUMxQ 1rDQ0vGS53L/OAHwlNXA4cDQoO+w4BDR05ogyzJwy6DQ4Gx2zeD59RF1Y9ZQ9RLicNPA9aI73aHT QHSXkfUR1oBuZxP00fUgdHjicCAuff/LI/UmXJD1wtCh9i/3P/hP//WAWVD1INag0pD6H/sv/D9+ bF8A9SDkgPnf/q//tSkf+JxeMP1/Am//lWIgKP/LIQOf9VNrMAE/Bg8HHwgv//VxlXAJgvYPCu8L /wQNXWD/CY8PHxAvET/1cVrwDh8Tv/8UzxXVzBHe8MwQ0uDZ0PDz+fBRXHHL4PGBYXEcUdEx//Kx G8LmoMzw89XpscwgHRD/1oAeEu/QF3Dz8OzS0iDikN/i8NGQ2bDhkBxxbtCBIGK77SDM8DDRENPA 5IBo0cDIY3Mx0RBhZmFwIiD+c17x3lD/UWAy8PMhlCExvyJzItRZQSLS7WAkw2Pncvkkc25wJMkm ZPTRIWxaIP8iYiExI3taICjSJbAiMdnQPnNZcusWIZDNsCrpIA3+ChrCLJYatBt/HI8dlx8l/yBe J65NQSjP7UFNQSonItWvJGQlUl7x1WBw6tFmKq0h9NNia21rF7MgX1JNG0BsQezhU9mwff5U71DL ISfPInBzECkfOwLfKmFEQTU/Nk8sHl9AH0Ev/0H6Oc8h8TttNP89zz7fLVJ/Qx867zv/RY9Gnywm OZEgWzjQ0CBp8mAspVPTQGm31kBOYNDgaOIh52Bpy7CoLCBP7hBp1bAg7QDwIENUT0ifRB9FL0yP f0dPSF9Jb0p/S49U/zcbRXxNQ1dPWF9Zb1p/dOFz7+/gzFBbryw1Ml1fUs9T399bP1X/VwXoc8sy ZuigKrE/0QBjv2TPZd9m7zcbSFkAUEVSTElOSyBmIs+A7mFvOs+ATtNfAdMQbUBlbWMuY/3vUCJj r2t/bI9tnyrPK9P3xpN5ofTTZNLwIiDogtEQBmLZ0MsAIADQyeoAefm6zhGMggCAqgBLqQsCAHqA KgN6geB5jTZ6gW0AAGEAaQBsAHQAiG8AOnwjZwB1fGFgcgBlAF98o3wwQON9wXwwYwAufsF+MnqA //iQaTLooIFA0KBqb15vX3r/1gFgP3UfNwxwrzmh+JJyH/9zL3Q/hK9oH1c/gV9fb4ofI4svjDgr MSja8DUp8iCYYDktrmChgC0fLi//1WAvPzBPMV8oD47PNK+Q//+SDy0PlS8vLx3PHt8f75jf/yH0 I1wqebNwsDC/gHfAN9cn0kE4vJ72fQCrAB4AcAABAAAACAAAAFJlZ3JldHMAAgFxAAEAAAAWAAAA AcbmZdWWcDfzc6qHS9SyUeb584yn9AAAAwAmAAAAAAALAAIAAQAsIAsAAQ4AAGh1AgEKDgEAAAAu AAAAAAAAAEcAeBfHkKxKr+8LploFF7ABAPwVTdjvdXlKhysGywQ4l68AAAADrAUAAAAAAwAJWQMA AAADAN4/n04AAAIBfwABAAAAEQAAADUwRDQyMkQ2NjVFNkM2MDEAAAAAAwAGEA03zI4DAAcQTwAA AAMAEBAAAAAAAwAREAAAAAAeAAgQAQAAAFAAAABUT01UT01NQUdVSVJFU0VOSU9SVEVDSE5PTE9H SVNULE9GRklDRU9GQ1RPRU1DMk1BR1VJUkVUT01ARU1DQ09NKzEoODQ1KTcyOS00ODA2AAuJ ------=_NextPart_000_0075_01C6E644.4F15C830-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 061002210048Z0# *H÷ 1Y nèb*N9hk²ØÌ[0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ {cÛNZ^LÂš2ùý¢þŽ á69,@(!X,fú Ä8WÏa©ó§ß0<$øüjGgã¶ÁŒkðÊ%)6[ŒØö*«aôkÊ$ŠÔóÔèa3nÿunì3fI°¯Ô?Ö]œ{Ì:ÎØ f¹ÚTY[3æç®

1 0

ws-naming: Returning an alias-EPI in the referral-fault
by Frank Siebenlist 02 Oct '06

02 Oct '06

I'd like to share two use cases for the return of a alias-EPI a an alternative to returned referral resolver services: * Two EPIs are independently generated for the same resource. If we associate a resource with some bio-object, the it happens that two different researchers "name" the same object independently from each other. When this is discovered, one needs the option to consolidate the metadata and policy "underneath" one of those EPIs to lessen the burden of maintenance and to ensure consistency. A common solution is to assign a "master-EPI", and to let the other EPIs refer to that master-EPI when it receives resolution requests. * Moving metadata management to a different admin domain. When a global naming system and global resolution frameworks are used, like DNS, HandleSystem or LSID, then the EPI's URI will include information about the naming server, i.e. the "prefix". This prefix in the name is commonly mapped to a real, physical identifier service that is used to administer the metadata/resolution bindings and such a server will be part of a certain admin domain. When the owner/administrator/PI of the individual identifier binding moves/changes-jobs, she often wants to take the data-objects with her to the new admin domain as well as the ability to administer the identifier bindings. Unless that user "owns" a whole prefix, the administration of the identifier has to remain at the original naming server. This is often not an acceptable solution both for the naming server admin domain as well as the original identifier owner. A common solution is to create a new EPI with a prefix that is maintained in the new admin-domain, and to use that for all the bindings/resolution information, and to add to the original EPI a one-time referral to the new EPI. The semantics for the referral fault is something like: "The resolver service that was asked for the resolution was unable to provide the caller with the resolution information. However, the resolution service has alternative information returned which the caller may optionally use to try to resolve." It seems to me that returning a alias-EPI fits very well within the referral fault semantics. Furthermore, the processing of a returned alias-EPI seems completely equivalent to the processing of the original EPI with some checks for looping and such. Enjoy the F2F without me. Regards, Frank. -- Frank Siebenlist franks(a)mcs.anl.gov The Globus Alliance - Argonne National Laboratory

2 5

XQuery examples for Oct 2 OGSA call
by Ellen Stokes 30 Sep '06

30 Sep '06

XQuery examples for the Oct 2 OGSA call are in gridForge https://forge.gridforum.org/sf/docman/do/viewDocument/projects.ogsa-wg/docm… Ellen

2 1

OGSA Roadmap Editor call, 10/4
by Christopher Jordan 30 Sep '06

30 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 There will be an OGSA Roadmap document editors conference call this coming Wednesday, October 4th, at 3PM PDT, 6PM EDT. Anyone with comments on the current draft OGSA Roadmap document, or anyone who would like to provide information on documents which are currently included, or marked to be added, to the Roadmap v1.1, is welcome to join. We are fast approaching the date at which if you do not provide us with information, we will be forced to make it up or ritually shame you, so please provide any and all information regarding document status, descriptions, and schedules, either via email to myself or Dona Dickinson - <Dona.Dickinson(a)ngc.com>, as soon as possible, or by calling in to talk to us about it this wednesday. Call-in details: To Join Audio Conference Primary Dial-In: 1 (877) 218-2986 Alternate Dial-In: 1 (847) 619-6049 Enter Passcode: 9435289# Thank you. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFHfbGPCVtcXn6kg8RAofZAKC6f/wPo2SIEnAcXGbwAYPctrPDCACeMIF6 s4uAqNYtYWZWS8GL45SDgFw= =DyOC -----END PGP SIGNATURE-----

1 0

Updated: OGSA Teleconference
by Andreas Savva 29 Sep '06

29 Sep '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20061002T220000Z DTEND:20061003T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000303FF491EFE3C6010000000000000000100 00000EF60FA66A7A9C5439CB7E2B9FE00A18B DTSTAMP:20060929T092012Z DESCRIPTION:When: 2006年10月3日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Oct. 2nd\nMonday from 5pm to 7pm (CDT).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 1002\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Sept. 25)\n - https://forge.gridforum.org/sf/go/doc13903?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) Information/data modeling Xquery (Ellen\, 30 min)\n\nMinutes from GGF18:\n> generate 3 to 5 queries that might be issued\; would like to use as a\n > starter set for usefulness of XML document and to show how it would\n > look like in XQuery.\n\n3) Separation of service/info model (Tom\, 30 min)\n\nMinutes form Sept. 25:\n> - Another open issue is how does the Information Model work (in\n> context of DMTF) comes together with the EGA reference model\n> (dags).\n> - A possible viewpoint is that the EGA Reference Model is the\n> overarching model: \n> - With specific/concrete stuff mapping to CIM\n> - But some more abstract stuff do not map to CIM easily\n> - There is some more abstract work in the SMIS space and this\n> will end up at some point in DMTF schema\n> - So the DMTF might be an eventual consumer for some of this work\n> \n\n Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n4) Clarify OGSA request to include "Container Model" as BES Appendix\n\nOGSA-BES-WG *is* sole authority of BES-spec and OGSA-WG\nrespects that. We have had discussions in the past and an understanding\nthat this appendix would be included. I would like to discuss the issues\nand identify a mutually agreeable way forward.\n\nI'd like to encourage both OGSA and BES members to attend this part of\nthe call.\n\n\nEllen's email:\n> The intent of this appendix is to provide the container model as an \n> 'informational' appendix so it can be submitted to DMTF as concrete \n> proposal for inclusion in the DMTF CIM and a context for why a container \n> model is necessary.\n> \n> The inclusion of the model in the BES spec does not imply that OGSA must \n> implement this CIM container model to implement BES\; it is merely an \n> abstraction for a general container model where BES can provide context \n> for the need and implementation of a specific container model. If this \n> point doesn't come across in the appendix text\, I have no problem \n> modifying the text.\n\n5) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 5 (Thu): Security\, secure channel profile review\nOct. 9 (Mon): EGA reference model\, OGSA roadmap\nOct. 12 (Thu): <No call?>\nOct. 16 (Mon): Information/data modeling\nOct. 19 (Thu): Security\, secure channel profile review\nOct. 23 (Mon): EGA reference model\, OGSA roadmap\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Sept. 25 call.\n AI-0925a: Hiro to setup wiki page with names of people who have\n expressed interest in the security team\n AI-092625b: Jem to pull definitions together and produce a new\n merged first draft.\n - Send a mail to the ogsa list about this work\n - Set Oct. 9 as the target for the first Glossary draft\n AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to\n contribute to join the OGSA list and this convergence work. -\n Members may have changed but organizations have not\n AI-0925d: Paul Strong to send EGA Glossary MS-Word file to Jem\n Treadwell\n AI-0925e: Hiro to talk with Andrew Grimshaw and Mark Morgan and\n bring back a concrete proposal for the HPC Profile use\n case as a convergence candidate.\n AI-0925f: Hiro to talk with Ellen Stokes and add more items in DMTF\n register in the context of this convergence work\n AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M)\n on why the current separation of service/info model may\n not be quite right.\n\n > From Sept. 21 call.\n AI-0921b: Security members to discuss the BoF proposal(s) further\n - For example\, one outcome could be some standards\n activity to mirror CAOPS activities and tie-in to OGSA\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security AD (when one is selected) about the Security Area\n task list.\n AI-0921d: Dave S to collect additional material in order to identify\n security issues better.\n - (AI-0921e is an issue instance)\n AI-0921i: Dave S to provide an agenda for the next security call.\n - Draft agenda items for Oct. 5th:\n - What needs to be done to achieve simple interop\n generally and to bootstrap more\n - Profile to get authentication information from a\n secure channel for authentication\n - Profile for other methods to get authentication\n informatin for authorization\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest.\n AI-0915c: Ellen to propose new text to update the DMTF register\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Sept. 14 OGSA F2F\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the\n next F2F and inform the group vial the mailing list\n\n > From GGF18 EMS session (Sept. 13)\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n\n > From Sept. 7 call\n AI-0907b: Takuya will search for an external reliable source of\n strong (or deprecated) ciphers to reference.\n AI-0907c: Andreas will revise the explanatory text and send the new\n version to Takuya.\n AI-0907d: Takuya will update the documents and issue a final call\n on the list. (Probably during GGF18.)\n\n > From Aug. 31 call\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Oct. 2nd call
by Hiro Kishimoto 29 Sep '06

29 Sep '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Oct. 2nd Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 1002 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Sept. 25) - https://forge.gridforum.org/sf/go/doc13903?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) Information/data modeling Xquery (Ellen, 30 min) Minutes from GGF18: > generate 3 to 5 queries that might be issued; would like to use as a > starter set for usefulness of XML document and to show how it would > look like in XQuery. 3) Separation of service/info model (Tom, 30 min) Minutes form Sept. 25: > - Another open issue is how does the Information Model work (in > context of DMTF) comes together with the EGA reference model > (dags). > - A possible viewpoint is that the EGA Reference Model is the > overarching model: > - With specific/concrete stuff mapping to CIM > - But some more abstract stuff do not map to CIM easily > - There is some more abstract work in the SMIS space and this > will end up at some point in DMTF schema > - So the DMTF might be an eventual consumer for some of this work > Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. 4) Removal of container model from BES spec appendix (Ellen, 10 min) Ellen's email: > The intent of this appendix is to provide the container model as an > 'informational' appendix so it can be submitted to DMTF as concrete > proposal for inclusion in the DMTF CIM and a context for why a container > model is necessary. > > The inclusion of the model in the BES spec does not imply that OGSA must > implement this CIM container model to implement BES; it is merely an > abstraction for a general container model where BES can provide context > for the need and implementation of a specific container model. If this > point doesn't come across in the appendix text, I have no problem > modifying the text. 5) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 5 (Thu): Security, secure channel profile review Oct. 9 (Mon): EGA reference model, OGSA roadmap Oct. 12 (Thu): <No call?> Oct. 16 (Mon): Information/data modeling Oct. 19 (Thu): Security, secure channel profile review Oct. 23 (Mon): EGA reference model, OGSA roadmap <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Sept. 25 call. AI-0925a: Hiro to setup wiki page with names of people who have expressed interest in the security team AI-092625b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925d: Paul Strong to send EGA Glossary MS-Word file to Jem Treadwell AI-0925e: Hiro to talk with Andrew Grimshaw and Mark Morgan and bring back a concrete proposal for the HPC Profile use case as a convergence candidate. AI-0925f: Hiro to talk with Ellen Stokes and add more items in DMTF register in the context of this convergence work AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. > From Sept. 21 call. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items for Oct. 5th: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Sept. 14 OGSA F2F AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From GGF18 EMS session (Sept. 13) AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." > From Sept. 7 call AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) > From Aug. 31 call AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. ---- Hiro Kishimoto

1 1

IETF Transport Layer Security (TLS) status
by Alan Sill 28 Sep '06

28 Sep '06

As discussed in the call today, here is the current status of the TLS group as recorded on the IETF page: http://www.ietf.org/html.charters/tls-charter.html Goals and Milestones: Done Agreement on charter and issues in current draft. Done Final draft for Secure Transport Layer Protocol ('STLP') Done Working group 'Last Call' Done Submit to IESG for consideration as a Proposed Standard. Done First revised draft of TLS specification Done TSL 1.1 Specification Done First draft of TLS 1.2 specification, including CTR mode cipher suites Done First draft of specification for cipher suites with combined encryption/authentication modes Dec 2006 Submit specification of TLS 1.2 specification to IESG for publication as Proposed Standard Dec 2006 Submit specification of cipher suites with combined encryption/ authentication modes to IESG for publication, with at least one of these suites to be Proposed Standard 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

Proposed agenda for Sept. 25th call
by Hiro Kishimoto 28 Sep '06

28 Sep '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 25th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0925 See more explanation: - https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (if available) F2F meeting minutes approval (Sept. 15) - https://forge.gridforum.org/sf/go/doc13871?nav=1 - https://forge.gridforum.org/sf/go/doc13862?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA and EGA reference model (45 min) > - No specific OGF policy on unifying EGA and GGF work, but there is > an expectation that parties talk to each other > - Merging the glossaries? Yes and does not look too difficult > - Proposal: maintain the distinction between reference model; and > OGSA as (a service oriented) rendering of it; > - Is it true, or should it be made true? > - As an exercise, what is the specific use case to drive it; need > a reason--more than an abstract motivation. No reason just to be > consistent. > - EMS (or the more restricted HPC Profile) might be a good > starting point > - Would probably need more than one use case; would also have to > think broader than current thinking in OGSA. > - Transaction processing kind of environment as one motivation? > - Next step: Set up an initial group of people to start a discussion > within OGSA. Identify what should be done. > - Dave Snelling, Andrew Grimshaw, Tom Maguire > - Paul Strong, Alan Clark, Bob Thome GGF18 session material, minutes, and EGA document: - https://forge.gridforum.org/sf/go/doc13838?nav=1 (Glossary) - https://forge.gridforum.org/sf/go/doc13827?nav=1 (OGSA vs EGA) - https://forge.gridforum.org/sf/go/doc13839?nav=1 (minutes) - http://www.gridalliance.org/en/WorkGroups/index.asp (EGA doc) 3) OGSA roadmap v1.1 status update (Chris Jordon, 45 min) Chris will make the next revised draft available up on gridforge by this weekend for review and discussion on the 25th. 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Sept. 28 (Thu): TBD Oct. 2 (Mon): Information/data modeling Oct. 5 (Thu): Security Oct. 9 (Mon): EGA reference model, OGSA roadmap <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Sept. 14 OGSA F2F AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0914b (D Snelling, D Merrill): Set up an OGSA Security design team AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From GGF18 EMS session (Sept. 13) AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." > From GGF18 EGA session (Sept. 12) AI-0912a: Hiro to set up an initial group of people to start a discussion within OGSA. Identify what should be done. - Dave Snelling, Andrew Grimshaw, Tom Maguire - Paul Strong, Alan Clark, Bob Thome > From Sept. 7 call AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) > From Aug. 31 call AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. ---- Hiro Kishimoto

3 2

Regrets this morning
by Maguire_Tom＠emc.com 28 Sep '06

28 Sep '06

0 *H÷ 010 +0 *H÷ $Content-Type: multipart/mixed; boundary="----=_NextPart_000_00B1_01C6E2DC.8A7A2120" X-MS-TNEF-Correlator: E0B38811FEE2C601 This is a multi-part message in MIME format. ------=_NextPart_000_00B1_01C6E2DC.8A7A2120 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Internal meeting that I MUST attend. Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_00B1_01C6E2DC.8A7A2120 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IhsNAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgD0FQAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAA0KAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAABibAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAADt3AwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABADtmAgEJEAEAAADwEgAA7BIAADUrAABM WkZ12LLsDQcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3RbCZgdABUAHbX0CgwBQ9wPUFc8W22IXsRggF4IeVIcYoAcT GbdoZWx2HIDlDrBhGzQzOBuvHL8dx1cX5B4yGKBWBJBkAHBhdwKDDwIVbTIg4iIyGj4g/ENFGb8a yw4AE5AlfhgQ+yafJ6V5CLEoTylbDhAVbVwxNhuRK48DgkcJ0WvrLQ8pPTYvHzYlUTBvA4JuVAhw Mg8pPTcCABKwZHZpAzYviDc44TVvA4IoyEhlYglwdyk27yk9/yDxOR86JCaPO5YHEAGgDrDrPH8p Ljk/Dzg0AUBfA4J+QkJxDrBCLyk8F8BEPzbXKiFFjzvDVgiQdCTAB4H+ZUIfSD4lUSEsJmgHEyf6 /x/9SRAqIU7dK0dQVSzpUW//LwEhLDAYUFQxvFVPNAFWjv81NlBUNrpZTzjoVo06d1BU/zwPXS8+ iF7eT9xBr2HPRCHfVo1FR1BURt1mbjcLwlad70pmYFVL/2pPZkpQTq8maP8kdSfxb4VSfys4cacs 4G+F/1ZfMBhxpjGzb4VaXzUYcab/NrFvhWd/RThxpkbUb4QYIH97X0pXcaZtmgKAApEI5jv1CW8w gg9lLuGDOi7ihB//hSiDJC7ig6+Hf4c9hr+E7/ODPxQwMjiNCo4hjd+O6f+DJI8SjX+RT5ENkI+O v5KE/jkPIJXUlzGPU5cwAoIQULx5bAeQH/Ah4AAAcQMhHmwSwQUQAUAD8GRjdC5sCrGaEEHAcAEB YXV7TQAAYHMKsJpwIaCbcm5MdW1M0ZswdG8NUWrmdRBQBRBnaJtgBRAKAcuZoAoBaQGQcDADMAAg pmwQwCFxczEDMGEBMf+fgAvwK1AHQA21mYGdQJ70/56Rn9MTJxPoCNAJwD7AodMcbnCiKaPEAzBz bmX+eCHwB7AFsADAAnMW4J8xf56RDWA+0CBAICCk8SHQbU5pEgCmsAnwIESbFCAaUArAYQnAmuBo IEZ3AiGl5BBgMQBQEGADYHcnCzCdQAGAc1c+wHRo3kITkJ1ACrCmsGwN4CDwfatUcqvIDZCrNgGA rTdi/a03cqsxAmALgAmRrzSYsNxwZasxBPAgAGyaIasA+6qhr5FzICAAIEzxqbE8MP+sULH2CVCy FAyxsiOaoLIUfGRnsva0cLP2nwCyFHb/AzCZb5p/m4+cn52vnr+fwv+7kaDduuENtKHEFCKf8aMs /76nwCSk9angpyylhE0gAaD/mNCl56Chpqi7zb0cuEAI0PslIKTxYriACYACIKZimKE7IcA+wDg+ cGLAdXAgSN+wIbLgC4B386YjNsQvxT//xkrHwsdPyFepILCwqkAJgP/I7zpgyh+fFwBRvN8bdAwB 78zfp0oQQMkBcwIgUIEQQNkFoG1wFzLH7kUAwAMQvlOYsjpggTMW4AtgdAnwZxBgmLO2kHNkEFAH cGHeeMQANADaERFRawmAAQEWMKXzgiB2AlEge1XzyVAXIHdu2NXIItwy3VN9JmA0XiHd81pARUHI IzT8NTErUMgi36DfkDUh3fPvSRAO8BOQ4IQ3DxAAUMgi/XVwM9+g4RR1cGdgVkHIIv40DeAN8N8U 3lAB0A8R4/XsNzlEIONDOMigxADdU/sXwBfAOeMkAcDiQEUw5qV+OEAQtsHmwm/glyDlNDjv36BF QN50lzAwAcDpVi7w/+R1DeDnoeOA38QB0ODx37X/6cHiQOEUDvDmQSoR65RrcP+r0N507OAO8Jcg 63XoYWtg3+q1IOAX4Mig7oU5dXAO8P/fxUpQ5ZDs9eIx5oDfFMQA+Dk0N+BV81HIYEQR39P9F8E0 8TD0heJg35D0dUAQ/Y+gM+515RAYEPOQ9sbjAP/2cN/E9zD2cd+16bEXsOz1/+MAXiDy5vgB8RHd 5Bfw8sH/+zflIPCl4bCrwWdh/NTxMP/1EOHE4MAX4t8U5wHp0PXl/SZgN/OA34Dd5OJg5+D+5v/f gOAx37Q4weJB/vXtkeOg/+EV/5AwIANnXiD8Yd3k33D/E4DnNY+g5SBv4N8UF+DlIO/zcOMk5cHf cDLlNOJAMCD/ezAH9Rfh5RDedBOAVkDeUP8GdeJg4mDjAOHU5PEJ0eHU/wAw34Cf8QvV6FEJdeGQ 4PH/DTZ4UeR1IOBFQO2WIODxMv/nRBgg9nCXIuNEF8AH4N50/wfQ/5DfgBG3+lHjJfaB8sH/4zQY IAehEDUYIDAg4FUMMP/zkBfR4+Uu8OcR4+V+IABW/95R8HHkht9y5TXm8AfQAqX/DPLu4eVF/tAu 4hrVONDpAP/lRUAQFgAQNe8gWkD0MB0G/+aA08HIIv7QHAHzgB6FfiD/RBAfNvZh7yUlQGdg6FDf FP8DMNPABiAgtW/gyKAMZQMw//Nwj6AgtSVAI1HhFDPw9RD/6dDlNDjQ+LFiwR6TyKByoP86cSYU IFHsJScRGZHjJEQQ/14gcQAlNeUgojDmhTAgyKH/4FU1IPQw8TDfFH4g4MDzcP/ftH4gIhESZSTh 7OBrceYD/xvy7+VWQBFxKCVaQGtgB9D/4RQEsXaQ9zAvxfox5zX4Ef8BkjFFCpDlAeX09zDmcHER /+azojDs4OnQM4UGIOWh5qT/OmAKkPFlIVHkYeaV44Apkf82duGQMRYAMAlgOmDn9RzR/3mQ5pV2 oJch50Xn4OJg7OX/59FnYAoAOkWksEUw5pUlwf/4Fhyx+lHlNEAQ8TCr0Du1/+Ug6FAAMN8k6dEJ YOf0+wH/b+Dp9fZw46DhkOEUELGr0P/l1SXBJqAlJSXC9DA/dfEg/xYRQPUhETYxRMXIg98kLpH/ P1dWQA5i3yTm8Jcg/5DfJP/n4PgBQnX9URhW5aD3IAkR/98k8TD3IBtlBiH+wPal9zH/9aHftEvy cqBM9+hQ8uX3MP9+IPWx6WSp4GdR4GTvIFox/wBlLTFfsedE7yDpMSvllzD/DDA3oellfiDtUEz1 GnEplv8HEWLABiDpZOMQ7OASZUAR//dA/uU4cQki6WQooQVx6sX/ojAAMHah6tTu8SNRWRbfcf/i ZTwzeZDqtnxQJaHnRKBx/+px5oWgcSaBDGW+gvQhXef//tC+kurUUTFrYl+l08Dg0f9flk5BAGWk sefg4laksAfQ/wexYsd1cFHR6sUk0Ttx6sb/CUJd³Ft9xYmHfxGZiDDDrdf+ksPNwdqBdFangGNHu Zu7x/3hg3wVPoRCxC6Wp4HhgTkH/Z6ZMEfRXxAAKAEDWqeDmYf/94W1mHZEW5W2x8tEKJang//OR LTFm5TthBtFwpnmB83D/cKY8IeUlcpIVIF3WcqE7kf9cRSHxj6BcNmnBIFHsNt+g/wlgHyVZgzSx 64UhIW7X4XL/q8J4BekA+KF5lyagWcZUMf9h0eq1VDFJsXsmFSEe0XzW/8hwdvgZkQqQfZbfkC+B 63b/EBEk8X9G5oBWcYDn58Bvtv/g0QqQB9DtBhsRWPYDEfBy/+3G/rHIcO3GyIFyJo+g90D/8teG 8Sag6/CGlxyihpZacf9y9uex3kF7JvQwTKFgVTQR//7AK+Xu0eiB7OZRMfEgSGX/7tEmYTul7tHx MY6XRGHfgf/uhd+Q+7KQVupwBJGQVidR/1gmRiCCQXFWZCF/ou6F+aD/8tGLZmBA84ByJl2xkBGR Fv/m8PHxk4ZMkkYl8RHzoN5B//DG85BVFvERMmHxZ+ZxZPH/38V1AqSwm7b0UVFlnAH6Mf/rZuJg h+GcZ/9h5ZDxdlXR/2UX9bHpMaCHCiCksPL1AOH/ftGghhIRGcGjBmoA84Dudf8MMPiiWDVmkTog 4xXgEhwB/6ImmPEzIacXB8fx0eOApFH/8YZCUfmmqeIlofGGgjFh5v+kcW3goUfzcBzBm6bmgPZR /54W5oClQaVm4wDwkWBV/tD/UeLudf7QKKEDZZDR47BPof+xpgGhgMaQwQNR8jb9EDDi/7QWCeHy JyEh/IG0FjSxZSb/6qDqYRhlxABzoowmuIFzkf+2duOACVG454FBWpYWsfch/6/2AbFEUfJFMNEQ 4Lz3VRH/buaSYhCxvqYUYXHwvqauAf+YVshwWlHAJ3VRA/HzBisR/+2mNjHmgKSG5EEG0Vt1+aD/ fTFaluMQKvHF1w6R9PDy9V9voVvwBmWdwkOxOc/zeBhtbG7ZoN2xfVxwumHPcXd4QZuRyjNoB6Jj YFDYIHJnbHEBy5RyLcwHdKNRy5RizUNndTp02WByYFDSsdbgY3Sd0pB3WHDcwM8AcmzTYPB0bmJq 0fDZcNtg2yCKXNyweNlBdG952XCAXGV4cHNocs/wrdCxdc6x2uBw0KBk2YBj3bDJsGJkYtCx1dBh cmPbgG9y0jDP0NPwbaXRsGHbcFxo0/B60IK0ZGfLsmnRYNVgaNOT23EB1VF21inU4WnVsarh/1kA 1rHXpUPS1fLU4MqA1qN12XNq0YFh0GDSsNUwdAZ5ylBbcHZpZXdrh9fgHsDbU3NjYWzXIKWnwXDN wHJkyzBl1KAj3MXUQG90XNOQbHl4dHdu1+DUwM/h3ldo/nTNkM5A05DQscmg36DUoLJqydFcdc7g zrBi3GD/1dDhYcnR27HOoN5g3FHPAP3J4HfiI8nR0dDMgM6g0AA8cmvUAdTA03Dj4Xdy8nDgwnNu ywDRIMyAWHBb1+DTwGzUINxgbM9wZn3bcGzUsNBg4RHPMOTAcPZ15dDeEGHq4NqQ4+ZYUm5y3fFF 1t6wd8nRycB5vdQBc9CxzIDPcN/Rb+aAoc8RZmV0MMlCd8yAcGZmbXTmgM6wymAg+WKQM2bKEOxw 1EDNkNxQ8+JgyaB1cM6TyjDssN4gvc7xZM8gzrXOoN6heGBQ/9BR4GDKYNTAzuLvouWCNiF/7qTT 0N/QzrDtwN4gz+MgzclCcMmwzvBsdsvw8yH8dWPUYPMi4IDR0POy27Gd0VB0lnHzIdSQbmfy4Ynz MHR44IAgLn3JM//zNltw89LOsfQ/9U/2X/OQf1gw8zDUsNCg+C/5P/pPbL9d4PMw4pD37/y//cUp 9qyPXRD7jwB//aViICjJMf8Br/NjahD/TwQfBS8GP/OB/5RQB5L0Hwj/Cg8CHVxAB5//DS8OPw9P 84FZ0AwvEc8S3/8T5coh3QDKINDw1+DvA+5h/FxxyfDvkWBRGmHPQfDB/xnS5LDLAPHl58HKMBsg 1JD/HCLt4BWA8gDq4tAw4KDhAO/PoNfA36AagW7OkR5y6zBdywAwzyDR0OKQaM/QY2RzMc8gYWZg UCAwc/9d0dxg/WFfEu8DH6QfQSCD3yDkWCEg4utwItNj5YIig/xucCLZJHTy4R98WQAgcn8fQSGL WQAm4iPAIEHX4HN5RZkgSdLQymDlMMnwbW5l64DX4P2AdNSQzxBJwCBNVVNUINEB0FF/9pAlvybP J98o6iPA1JBy+Sj6DQoY0jD2GMQZjxqf/xunHTUebiwOZsEtL+tRZsG/Locg5SJ0I2Jd0dNwcOjh hmYovslCYmttaxXDSCBfTRlQbEHq8VP518B9VO1gK/8tA3HwLX+/P2IuwUJhOZ86rzB+X0R//0WP Rlo+LyABP805X0IvQz//MbJHfz9PQF9J70r/KTY98bUrIGHOMGnwcDEFU9FQbmnUUFLAzvBo4DHl cGlRycAsIE/sIGnTwCDh6xAgQ1RPTP9If0mP/1DvS69Mv03PTt9P71lfKOv4RU1DW69cv13PXt9z wd5z7fDKYGAPKUUyYb9XL79YP1+fWl9bZeaDyUJm5rB/KMHPEGgfaS9qP2tPKOtIAFlQRVJMSU5L zCAizZDscW86zZBTMwJf0SBtQGVtYy76Y+1gImgPb99w73H/Ly+/MDOyQIWQsjCE0PLjZNEANyAw 5pLPIGLX4MkQIAAA0Mnqefm6zhEAjIIAqgBLqQtUAgB+4AN+4eB97TYBfuFtAGEAaQBsQAB0AG8A OoCDZwQAdYDBcgBlAF8bgQOAkECCIYCQYwAu/4MhgpJ+4PagbZLmsIXQzrD/bs9iz2Pa1BFkn3l/ KNx1D/8+Afaidn93j3ifiQ9sf1ufH4W/Y8+Of4+PKRgrMSiR2QA1KSAWsDktrUD/oGAxDZG/ks+T 3JTPld8pGNwiVN0wVaDfASDlsOwg0/Bh5dEgYuuAdypQGXAv/hDUAM8Q2pEgzIBhdj9VkFTwKrFV kNSw5NBoLiAiIC0gUhxiIFf/3GDPYGFwKkClgJ+AmW+NL/+cP51PkF8xrzK803AznzSv/zW/LG+l bzkPpz+oT6lfqm//M48b3xzvHf+uHyAEIWwu2fvKkCOgNsMwfaA8RtBRPRwJtDZ9AMBAHgBwAAEA AAAVAAAAUmVncmV0cyB0aGlzIG1vcm5pbmcAAAAAAgFxAAEAAAAWAAAAAcbi/hFhlVX6VmTLQ+yR 5Ok8Yi32dgAAAwAmAAAAAAALAAIAAQA8LwsAAQ4AAGU+AgEKDgEAAAAuAAAAAAAAAEcAeBfHkKxK r+8LploFF7ABAPwVTdjvdXlKhysGywQ4l68AAAADrAUAAAAAAwAJWQMAAAADAN4/n04AAAIBfwAB AAAAEQAAAEUwQjM4ODExRkVFMkM2MDEAAAAAAwAGELsR/00DAAcQrwAAAAMAEBAAAAAAAwAREAAA AAAeAAgQAQAAAGUAAABJTlRFUk5BTE1FRVRJTkdUSEFUSU1VU1RBVFRFTkRUT01UT01NQUdVSVJF U0VOSU9SVEVDSE5PTE9HSVNULE9GRklDRU9GQ1RPRU1DMk1BR1VJUkVUT01ARU1DQ09NKzEoODQ1 AAAAANPw ------=_NextPart_000_00B1_01C6E2DC.8A7A2120-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 060928130027Z0# *H÷ 1»0"&íÊÜÕOÛ¢}ÁðÚ0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ F7äÕÖ1l©·µz F=¯¥ÄMuø«û0ÅýnO°§c"¢Žüý:2¶€=Ä*=¢sÕÛ8N±8pÖòòÎº÷Bã¯}»çÉšÉoîtàE9AÚ»f¯V@èöIÖî

1 0

Teleconference minutes - 25 September 2006
by Andreas Savva 28 Sep '06

28 Sep '06

Attached. https://forge.gridforum.org/sf/go/doc13903?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 25 September 2006 ======================================= * Participants Mike Behrens (R2AD, LLC) Mukund Buddhikot (SUN) Chris Jordan (SDSC) Hiro Kishimoto (Fujitsu) Tom Maguire (EMC) Mark Morgan (UVa) Andreas Savva (Fujitsu) Alan Sill (TTU) Paul Strong (eBay) Jem Treadwell (HP) Minutes: Andreas Savva * Summary of new Actions AI-0925a: Hiro to setup wiki page with names of people who have expressed interest in the security team AI-092625b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not AI-0925d: Paul Strong to send EGA Glossary MS-Word file to Jem Treadwell AI-0925e: Hiro to talk with Andrew Grimshaw and Mark Morgan and bring back a concrete proposal for the HPC Profile use case as a convergence candidate. AI-0925f: Hiro to talk with Ellen Stokes and add more items in DMTF register in the context of this convergence work AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right. * Minutes approval ** September 21 minutes approved with no changes ** F2F minutes for September 15 (two parts) approved with minor changes: - Fix Michael Behrens affiliation - Correct AI number overlap * AI review [Only items with updates/comments are listed below] - AI-0921b: Pending. (Really a sub-item of AI-0921c) - AI-0921c: Pending. New Security ADs not selected yet. - AI-0921e: Closed. Alan has sent information to the list - AI-0921f: Closed. Already discussed on the Interop call. - AI-0921g: Closed. - AI-0921i: Close once the agenda is fixed - AI-0914b: Closed. There was a call last week. - AI-0925a: Hiro to setup wiki page with names of people who have expressed interest in the security team - AI-0912a: Closed. Today's discussion. * EGA Reference Model Discussion ** Glossary - Jem gave an overview of his glossary presentation from GGF18; number of terms and overlaps (or non-overlap) - Explanatory (EGA) vs more formal/committee style (OGSA) definitions - Should also look for less obvious overlaps, beyond just same/different terms - Should probably define some new ones (e.g., Enterprise) - Possible editors for this work: Jem Treadwell & Paul Strong - Glossary convergence should be done in the context of other convergence work (i.e., Reference Model and OGSA) - The EGA reference model structure and verbosity of the Glossary is driven by the expected consumers of the documents. One reason that more text was pushed in the Glossary was to avoid excess overlap with definitions. - Might need to have taxonomony/ontology discussion to sort out things - Is a single Glossary possible? - Probably no problem doing it. - There is no way but to have a single Glossary - The OGSA Glossary is specific to the OGSA Architecture document---for scoping reasons. (In other words, it is not a general Grid or GGF Glossary.) - Occasionally there are 'battles' over common definitions of terms. Having an OGSA definition should not stop others from having their own definitions of terms. - Definitions of terms perceived to fall in this category are often prefixed with "In OGSA, " in the Glossary to make the context clear. - How to proceed? Wait for broader work to start? - No need to wait. Could start small, using email and then use the occasional call/F2F meeting to resolve remaining problems - In terms of process the OGSA list should be used AI-092625b: Jem to pull definitions together and produce a new merged first draft. - Send a mail to the ogsa list about this work - Set Oct. 9 as the target for the first Glossary draft - Mike Behrens also volunteered to help out on the Glossary - Is everyone from EGA on the OGSA list? Maybe. - Are the EGA lists still active? The EGA alias does work and people have been invited to join AI-0925c: Hiro to ask Alan Clark to ask EGA TC member who want to contribute to join the OGSA list and this convergence work. - Members may have changed but organizations have not - Is the EGA Glossary available as an MS-Word file? It would simplify the work for the first draft. (The pdf version is otherwise sufficient.) AI-0925d: Paul Strong to send EGA Glossary MS-Word file to Jem Treadwell - From a more general perspective, it would be nice to have the EGA documents available on the OGF site. - This was assigned by OGF to the OGF Editor (Greg Newby). He is now reading the EGA documents. ** Reference Model and OGSA convergence - At GGF18 the proposal was to consider OGSA as a rendering of the EGA reference model. Agreed that this seems a good starting point. It should be tested by picking a candidate topic and see if it is really the case. - Hiro proposed the OGSA HPC Profile as a test case (a concrete use case) - The HPC Profile is more detailed when compared to the style of the use cases in the EGA Reference Model. Therefore it would help flesh out what is needed in the context of OGSA. Doing UML would be good. - It was noted that EGA graphs (DAGS) are specific to instantiation - Tentative agreement on the HPC Profile proposal but need more information before making a decision. AI-0925e: Hiro to talk with Andrew Grimshaw and Mark Morgan and bring back a concrete proposal for the HPC Profile use case as a convergence candidate. - What are the deliverables? - If the use case approach works then the refinement could be put in the next version of Reference Model. - Should this work be in the same WG? Should a new OGF Reference Model WG be formed? - Forming a new WG is a possibility, especially since the reference model work is at a different level from other OGSA work - Initially this work can start in an OGSA design team. It could be spun out later when the scope is clearer. A decision could be made by the end of the year. - Does this mean that the result is a converged model? - Yes, the result would be a reference model that also covers the HPC space, in addition to the enterprise space. - Can we expect more use cases from EGR-RG? - Maybe but their use cases are more abstract - Paul Strong may bring more use cases - Part 2 of the Reference Model document includes use cases. Should these be in a separate document? Or should the work be done in a different WG? - Doing the use case work in the same WG is ok - Typically the use case document would be a separate document - Another open issue is how does the Information Model work (in context of DMTF) comes together with the EGA reference model (dags). - A possible viewpoint is that the EGA Reference Model is the overarching model: - With specific/concrete stuff mapping to CIM - But some more abstract stuff do not map to CIM easily - There is some more abstract work in the SMIS space and this will end up at some point in DMTF schema - So the DMTF might be an eventual consumer for some of this work AI-0925f: Hiro to talk with Ellen Stokes and add more items in DMTF register in the context of this convergence work AI-0925g: Tom will send a note to the list (to: Ellen S and Fred M) on why the current separation of service/info model may not be quite right.

1 0

Proposed agenda for Sept. 28th call
by Hiro Kishimoto 28 Sep '06

28 Sep '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 28th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 See more information: - https://forge.gridforum.org/sf/go/wiki1477?nav=1 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0928 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (if available) Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA roadmap v1.1 status update (Chris Jordon, 30 min) > From Chris Jordan's email: > I had some issues with Word destroying my latest draft of the > document, but I've uploaded a less-recent version with some schedule > and status updates. It is incomplete, but I'm mostly interested at > this point in feedback on how I'm currently handling documents which > have been released as GFDs and which don't have definite plans for > future versions yet. > > So if you'd like to discuss the roadmap document in todays call, > please take a look specifically at the OGSA Architecture and glossary > sections, along with other documents in a similar state, such as JSDL > 1.0. Not all documents have updated status in this version, but I > left track changes on so you can see what I have updated in this > version. > > Latest roadmap draft: > > https://forge.gridforum.org/sf/go/doc13733?nav=1 Chris will fix broken draft and upload it to gridforge before the call. 3) Security Profile final review (Takuya, 60 min) Takuya will revise two security profiles before the call. 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Oct. 2 (Mon): Information/data modeling Oct. 5 (Thu): Security Oct. 9 (Mon): EGA reference model, OGSA roadmap Oct. 12 (Thu): <TBD> <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Sept. 21 call. AI-0921a: Andreas to ask Greg to setup a tracker for change requests to the OGF template document. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921f: Dave S to ask Richard C to put the security topic on the agenda of the first Interoperability call and to also ask that the teleconference announcements be sent to the OGSA list AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items for Oct. 5th: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization > From Sept. 15 OGSA F2F AI-0915a: (A Savva, S McGough): Set up a telephone conference to collect workflow (BPEL) experience AI-0915b: Ellen to check the status of the items on the DMTF work register: report which have been done, and what DMTF is doing for the rest. AI-0915c: Ellen to propose new text to update the DMTF register AI-0915d: Tom will post BP base faults issue to tracker AI-0915e: Hiro to talk with OGF Editor to start an errata process > From Sept. 14 OGSA F2F AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0914b (D Snelling, D Merrill): Set up an OGSA Security design team AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From GGF18 EMS session (Sept. 13) AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal on "ActivityExecutionCandidate." > From Sept. 7 call AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) > From Aug. 31 call AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Due Oct. 9) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. ---- Hiro Kishimoto

2 2

Updated: OGSA Teleconference
by Andreas Savva 26 Sep '06

26 Sep '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060928T133000Z DTEND:20060928T153000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000D0BC3D1562E1C6010000000000000000100 00000CCA41384C861944CADC9A96A1D9895A9 DTSTAMP:20060926T025215Z DESCRIPTION:When: 2006年9月28日木曜日 22:30 to 2006年9月29日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Sept. 28th\nThursday from 8:30am - 10:30am (CDT).\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0928\n See more explanation:\n https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (if available)\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) OGSA roadmap v1.1 status update (Chris Jordon\, 30 min)\n\n > From Chris Jordan's email:\n> I had some issues with Word destroying my latest draft of the\n> document\, but I've uploaded a less-recent version with some schedule\n> and status updates. It is incomplete\, but I'm mostly interested at\n> this point in feedback on how I'm currently handling documents which\n> have been released as GFDs and which don't have definite plans for\n> future versions yet.\n> \n> So if you'd like to discuss the roadmap document in todays call\,\n> please take a look specifically at the OGSA Architecture and glossary\n> sections\, along with other documents in a similar state\, such as JSDL\n> 1.0. Not all documents have updated status in this version\, but I\n> left track changes on so you can see what I have updated in this\n> version.\n> \n> Latest roadmap draft:\n> \n> https://forge.gridforum.org/sf/go/doc13733?nav=1\n\n Chris will fix broken draft and upload it to gridforge\n before the call.\n\n3) Security Profile final review (Takuya\, 60 min)\n Takuya will revise two security profiles before the call.\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nOct. 2 (Mon): Information/data modeling\nOct. 5 (Thu): Security\nOct. 9 (Mon): EGA reference model\, OGSA roadmap\nOct. 12 (Thu): <TBD>\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Sept. 21 call.\n AI-0921a: Andreas to ask Greg to setup a tracker for change requests\n to the OGF template document.\n AI-0921b: Security members to discuss the BoF proposal(s) further\n - For example\, one outcome could be some standards\n activity to mirror CAOPS activities and tie-in to OGSA\n AI-0921c: Dave S (as Standards VP) to talk to the next\n Security AD (when one is selected) about the Security Area\n task list.\n AI-0921d: Dave S to collect additional material in order to identify\n security issues better.\n - (AI-0921e is an issue instance)\n AI-0921f: Dave S to ask Richard C to put the security topic\n on the agenda of the first Interoperability call and to\n also ask that the teleconference announcements be sent to\n the OGSA list\n AI-0921i: Dave S to provide an agenda for the next security call.\n - Draft agenda items for Oct. 5th:\n - What needs to be done to achieve simple interop\n generally and to bootstrap more\n - Profile to get authentication information from a\n secure channel for authentication\n - Profile for other methods to get authentication\n informatin for authorization\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest.\n AI-0915c: Ellen to propose new text to update the DMTF register\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Sept. 14 OGSA F2F\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0914b (D Snelling\, D Merrill): Set up an OGSA Security design\n team\n AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the\n next F2F and inform the group vial the mailing list\n\n > From GGF18 EMS session (Sept. 13)\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n\n > From Sept. 7 call\n AI-0907b: Takuya will search for an external reliable source of\n strong (or deprecated) ciphers to reference.\n AI-0907c: Andreas will revise the explanatory text and send the new\n version to Takuya.\n AI-0907d: Takuya will update the documents and issue a final call\n on the list. (Probably during GGF18.)\n\n > From Aug. 31 call\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

New roadmap draft uploaded
by Christopher Jordan 25 Sep '06

25 Sep '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I had some issues with Word destroying my latest draft of the document, but I've uploaded a less-recent version with some schedule and status updates. It is incomplete, but I'm mostly interested at this point in feedback on how I'm currently handling documents which have been released as GFDs and which don't have definite plans for future versions yet. So if you'd like to discuss the roadmap document in todays call, please take a look specifically at the OGSA Architecture and glossary sections, along with other documents in a similar state, such as JSDL 1.0. Not all documents have updated status in this version, but I left track changes on so you can see what I have updated in this version. Latest roadmap draft: https://forge.gridforum.org/sf/go/doc13733?nav=1 Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "If we had a keen vision and feeling of all ordinary human life, it would be like hearing the grass grow and the squirrel's heart beat, and we should die of that roar which lies on the other side of silence." - George Eliot -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFGEKyPCVtcXn6kg8RAlY5AJwLGPrQyFfYH156n0ZiJCAV1olEkwCgoFW4 5PdnGHcZNdOWcAu5kiXyqJs= =Xt4T -----END PGP SIGNATURE-----

1 0

Updated: OGSA Teleconference
by Andreas Savva 25 Sep '06

25 Sep '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060925T220000Z DTEND:20060926T000000Z TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000B0454EF8A6E0C6010000000000000000100 00000B8C9D493D752DC4C97538F297AF5D824 DTSTAMP:20060925T060027Z DESCRIPTION:When: 2006年9月26日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n\nThe following is a proposed agenda for OGSA-WG telecon on Sept. 25th\nMonday from 5pm to 7pm (CDT).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n See more information:\n - https://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0925\n See more explanation:\n - https://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (if available)\n F2F meeting minutes approval (Sept. 15)\n - https://forge.gridforum.org/sf/go/doc13871?nav=1\n - https://forge.gridforum.org/sf/go/doc13862?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) OGSA and EGA reference model (45 min)\n> - No specific OGF policy on unifying EGA and GGF work\, but there is\n> an expectation that parties talk to each other\n> - Merging the glossaries? Yes and does not look too difficult\n> - Proposal: maintain the distinction between reference model\; and\n> OGSA as (a service oriented) rendering of it\;\n> - Is it true\, or should it be made true?\n> - As an exercise\, what is the specific use case to drive it\; need\n> a reason--more than an abstract motivation. No reason just to be\n> consistent.\n> - EMS (or the more restricted HPC Profile) might be a good\n> starting point\n> - Would probably need more than one use case\; would also have to\n> think broader than current thinking in OGSA.\n> - Transaction processing kind of environment as one motivation?\n> - Next step: Set up an initial group of people to start a discussion\n> within OGSA. Identify what should be done.\n> - Dave Snelling\, Andrew Grimshaw\, Tom Maguire\n> - Paul Strong\, Alan Clark\, Bob Thome\n\n GGF18 session material\, minutes\, and EGA document:\n - https://forge.gridforum.org/sf/go/doc13838?nav=1 (Glossary)\n - https://forge.gridforum.org/sf/go/doc13827?nav=1 (OGSA vs EGA)\n - https://forge.gridforum.org/sf/go/doc13839?nav=1 (minutes)\n - http://www.gridalliance.org/en/WorkGroups/index.asp (EGA doc)\n\n3) OGSA roadmap v1.1 status update (Chris Jordon\, 45 min)\n Chris will make the next revised draft available up on\n gridforge by this weekend for review and discussion on\n the 25th.\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nSept. 28 (Thu): TBD\nOct. 2 (Mon): Information/data modeling\nOct. 5 (Thu): Security\nOct. 9 (Mon): EGA reference model\, OGSA roadmap\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Sept. 15 OGSA F2F\n AI-0915a: (A Savva\, S McGough): Set up a telephone conference to\n collect workflow (BPEL) experience\n AI-0915b: Ellen to check the status of the items on the\n DMTF work register: report which have been done\, and what\n DMTF is doing for the rest.\n AI-0915c: Ellen to propose new text to update the DMTF register\n AI-0915d: Tom will post BP base faults issue to tracker\n AI-0915e: Hiro to talk with OGF Editor to start an errata process\n\n > From Sept. 14 OGSA F2F\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0914b (D Snelling\, D Merrill): Set up an OGSA Security design\n team\n AI-0914f (Fred Brisard and Hiro Kishimoto): Fix the location of the\n next F2F and inform the group vial the mailing list\n\n > From GGF18 EMS session (Sept. 13)\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal on\n "ActivityExecutionCandidate."\n\n > From GGF18 EGA session (Sept. 12)\n AI-0912a: Hiro to set up an initial group of people to start a\n discussion within OGSA. Identify what should be done.\n - Dave Snelling\, Andrew Grimshaw\, Tom Maguire\n - Paul Strong\, Alan Clark\, Bob Thome\n\n > From Sept. 7 call\n AI-0907b: Takuya will search for an external reliable source of\n strong (or deprecated) ciphers to reference.\n AI-0907c: Andreas will revise the explanatory text and send the new\n version to Takuya.\n AI-0907d: Takuya will update the documents and issue a final call\n on the list. (Probably during GGF18.)\n\n > From Aug. 31 call\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Due Oct. 9)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

contact
by Jamal Macdonald 24 Sep '06

24 Sep '06

1 0

Teleconference minutes - 21 September 2006
by Andreas Savva 23 Sep '06

23 Sep '06

Minutes attached. This was mostly an action review and Security call. http://forge.gridforum.org/sf/go/doc13879?nav=1 -- Andreas Savva OGSA Teleconference - 21 September 2006 ======================================= * Participants Jay Unger (IBM) Jem Treadwell (HP) Dave Snelling (Fujitsu) Alan Sill (TTU) Frank Siebenlist (ANL) Andreas Savva (Fujitsu) Mark Morgan (UVa) Duane Merrill (UVa) Tom Maguire (EMC) An Ly (CA) Hiro Kishimoto (Fujitsu) Chris Jordan (SDSC) Andrew Grimshaw (UVa) Donal Fellows (UoM) Abdeslem Djaoui (RL) Fred Brisard (CA) Mike Berhens (R2AD, LLC) Minutes: Andreas Savva * Summary of Actions AI-0921a: Andreas to ask Greg to setup a tracker for change requests to the OGF template document. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921e: Alan S to provide material on the issues relating to path validation. AI-0921f: Dave S to ask Richard C to put the security topic on the agenda of the first Interoperability call and to also ask that the teleconference announcements be sent to the OGSA list AI-0921g: Hiro to add Alan Sill to the OGSA-WG list AI-0921h: Hiro to allocate a slot to review security work progress at a future call. Perhaps Oct 5. AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization * September 7 teleconference minutes approved with no changes * Review of Action Items - AI-0912a: Hiro will be arranging the first call next Monday. (Close after Monday call.) - AI-0913a: Andreas to put issue in the EMS Scenarios tracker and close this action - AI-0913b: Pending. - AI-0913c: Andreas to put issue in the EMS Scenarios tracker and close this action - AI-0913d: Closed. - Done at GGF18. - AI-0913e: Andreas to put issue in the EMS Scenarios tracker and close this action - AI-0913f: Andreas to put issue in the EMS Scenarios tracker and close this action - AI-0913g: Pending. - AI-0914a: Pending. - Review all EMS Scenarios actions at the next document review. (No need to review every call.) - The next EMS Scenarios review call is not set yet. Andreas and Hiro will discuss it offline. - AI-0914b: Pending. - Discussion on the mission of the Security design team is part of this call. - AI-0914c: See AI-0914d. - AI-0914d: Closed. - Andrew has started working on new text for the Appendix. This AI belongs to the BES WG. - AI-0914e: Closed. - Andrew has initiated this activity. Richard Ciapala (MS) has taken over this activity. - AI-0914f: Pending - Proposal is Florida (Tampa or Orlando) the week before SC06. - Fred Brisard is inquiring about hotels in Tampa. He expects to have results (3-4 proposals) by next week. - Hiro will do the zoomerang after that - AI-0915a: Pending. - This was specific to experiences of people implementing BPEL and JSDL. - AI-0907a: Obsolete; Closed. - AI-0907b: Pending. - This has to be done before the Security profiles can go to final call. - AI-0907c: Pending. - AI-0907d: Pending on AI-0907b and AI-0907c - AI-0907e: Closed. - Already added to template. AI-0921a: Andreas to ask Greg to setup a tracker for change requests to the OGF template document. - AI-0907f: Closed. - The BaseFaults issues were discussed at the last F2F. - The minutes of this session were uploaded after the agenda of this call. There are an additional 4 actions (2 on BF). - AI-0831c: Closed. - Put in EMS Scenarios tracker. - AI-0831d: Closed - Put in EMS Scenarios tracker. - AI-0831e: Pending. - AI-0831f: Pending. - AI-0831g: Closed. - Andreas set up EMS Scenarios tracker. - AI-0831h: Closed - Mark sent the document out before GGF18. - AI-0828a: Closed. - Initial discussion clarified that this action is about annotating EPRs - Frank has looked into it. The recently released WS-Metadata Exchange specification shows (examples of) how this annotation can be done. The approach should be applicable here. - Initially this issue was specifically about adding porttype information but WS-MetadataExchange shows how any kind of information may be embedded. - (Dave S) There is non-normative text in the WS-Addressing Core specification (sec. 2.2, under endpoint Metadata extensibility) that refers to examples on how to include wsldLocation information. This is sufficient and there is no need to use the WS-MetadataExchange spec. - There were questions about the status of the WS-MetadataExchange specification. It is not in a standards body yet. It is covered by the recent MS open licence announcement. - Is this issue covered by the WSRF BP? Yes. - AI-0817a: Pending. - This was not not discussed at GGF18 or at the F2F. - There has not been much progress - Jay will talk with Dave Berry on how to proceed - Hiro will schedule this topic on a future call in 1-2 weeks time. - AI-0810a: Closed - Subsumed by AI-0913g - AI-0803e: Pending - AI-0803f: Pending - EGR-WG (Ravi) will contact Geoffrey Fox and invite him to contribute use cases. - Pending - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. - Pending - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) - Done at the F2F. Closed. * GGF18 and F2F meeting discussion - Event went quite smoothly. - A good set of specs are coming to completion; felt like many things are finally getting done. There are lots of implementations (of BES, etc) including from MS. The interoperability activity was started and looking forward to the results. - There was no chance to cover some issues, like the relationship between OGSA Security work and other (OGF) security work. But this is on the agenda of this call. ** Minutes approval - Information Model Minutes (two) (Fred M)--approved with no changes - EGA Reference Model (one) (Andreas)--approved with no changes - EMS Scenarios (one) (Hiro)--approved with no changes - F2F minutes, Thursday (Michel D)--approved with no changes - F2F minutes, Friday 1. (Michel D)--approved with no changes 2. (Andreas)--approval postponed for next week because there was insufficient time to review them before the call. - All the material is believed to have been uploaded. Let the chairs/secretary know if anything is missing. * Security Profile review postponed * OGSA security Led by Dave Snelling. OGSA security work has produced two security profiles (Core and Secure Channel). Both are close to publication. One question is what should be the next work items of the design team. The HPC Profile interoperability work is probably facing an immediate problem since there is no profiled way to pass the required identity credentials for job submission. There is a gap in authentication---the OGSA security profiles only go as far as defining a secure channel. Therefore a short-term work proposal is to identify what the next minimal use cases are and to produce profiles to address them. The result could be a profile on how to do authentication. (There is no OGSA-AuthN group.) From a broader perspective there are a number of security groups (FI-RG, OGSA-AuthZ-WG, TC-RG) and a lot of good work has been done already. But it is not clear what the connections are. Alan Sill said that the CAOPS-WG has also been very active. CAOPS has been somewhat incorrectly categorized as operations; it does in fact also do design work and should have a connection to OGSA. (There are some worries that the practice of academic users may be getting decoupled from broader OGSA work.) The group was spawned by the Grid PMAs--which also formed IGTF. IGTF's purpose is authentication in a federated infrastructure. The CAOPS-WG was created to cover specific needs of educational organizations--bridging between organizations. It is not clear how this work links to the commercial world. (Commercial CAs are in the business of issuing server certs; EDUs for identity.) A main driver has been the federal government---driving use by requiring (path validation) by legislative means. - Peter Alterman @NIH Federal Bridge: runs commercial solution Is a lot of the work still around plain x.509 certificates? No, VOMS uses extended attribute certificates. - A higher level view is that x.509 certificates with SAML assertions seem to satisfy most requirements - It is not clear how industry views attribute extensions One issue is to identify what is needed for web (grid) services. A lot of existing (or pursued) approaches (CAS, Kerberos, etc) in other bodies are done without reference to specific Web services requirements. A number of different approaches for authentication were mentioned: - vanila x.509 - x.509 extensions - EPI based identity (UVA) - 'pure' SAML (identity is just another assertion) What is the current OGSA level? - Use of x509 certificates to establish a secure channel between client/server. There is mutual authentication between client and server. If a single CA is used for tests is it enough? And could it be extended later to support bridging? - The weak point is atribute extension and path validation; otherwise it works for the small case. - For the (small) base case it is sufficient to have copies of the base root certificates and be able to check whole chain (including checking all additions; so it is simpler not to allow additions). This setup is enough for basic interop but it is really functionality that has been available for the past 10 years. - Bridging is actually a lot more complicated. Another possibility for future work is to define a standardized path validation i/f that hides the operations behind, which are quite complex. - But this may be longer term work. It goes beyond current interoperability work. - Alan mentioned a number of people that might be worth including in such a discussion. - Frank proposed doing a BoF for such a path validation i/f and also proposed Alan Sill as a good person to lead it. For the Interoperability workshop one could arrange for an IGTF accredited CA; install it on both sides. (It has the advantage of also plugging in the federal infrastructure.) - It is not clear if such a setup would be acceptable to all participants. - It is not clear whether the use of the OGSA security profiles is going to be acceptable either. - Interoperability calls are being planned and this issue should be taken up there. - Richard Ciapala (richci 'at' microsoft.com) is organizing the interoperability work/calls. AI-0921b: Security members to discuss the BoF proposal(s) further - For example, one outcome could be some standards activity to mirror CAOPS activities and tie-in to OGSA AI-0921c: Dave S (as Standards VP) to talk to the next Security AD (when one is selected) about the Security Area task list. AI-0921d: Dave S to collect additional material in order to identify security issues better. - (AI-0921e is an issue instance) AI-0921e: Alan S to provide material on the issues relating to path validation. AI-0921f: Dave S to ask Richard C to put the security topic on the agenda of the first Interoperability call and to also ask that the teleconference announcements be sent to the OGSA list AI-0921g: Hiro to add Alan Sill to the OGSA-WG list AI-0921h: Hiro to allocate a slot to review security work progress at a future call. Perhaps Oct 5. AI-0921i: Dave S to provide an agenda for the next security call. - Draft agenda items: - What needs to be done to achieve simple interop generally and to bootstrap more - Profile to get authentication information from a secure channel for authentication - Profile for other methods to get authentication informatin for authorization

1 0

Links for material on path validation and on the IGTF, etc.
by Alan Sill 22 Sep '06

22 Sep '06

Per action items from meeting of 21 Sep. 2006: A link for information on the International Grid Trust Federation (IGTF) and its activities with respect to the large-scale grids in science and academics is below: http://www.gridpma.org/ Information in general on path validation is available at http://tools.ietf.org/html/rfc3379 I will look for and try to supplement the above with information specific to path validation and related issues for the use of Bridge CAs and similar structures in grids as soon as possible. Note that The Americas Grid PMA (TAG PMA) has formed a working group on the above issue including members from the other PMAs, and that is currently in process. There is also extensive activity, especially in the Internet2, Educause and related sectors with respect to the use of Shibboleth with grids, including related PKI and X.509-embedding issues, see http://grid.ncsa.uiuc.edu/events/ggf18-shib-bof/ Best, Alan 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

Proposed agenda for Sept. 21st call
by Hiro Kishimoto 22 Sep '06

22 Sep '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 21st. Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0921 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Sept. 7) https://forge.gridforum.org/sf/go/doc13796?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) GGF18 and F2F meeting debriefing (20 min) Feedback and impression on GGF18 sessions and F2F. Minutes approval https://forge.gridforum.org/sf/docman/do/listDocuments/projects.ogsa-wg/doc… If you have not yet upload your materials, please do so before the call. 3) OGSA security (David Snelling, 80 min) 3-1) Formalities 3-2) Existing Technologies Summary X.509 X.509, with proxy extension SAML Specific SAML profiles of interest. XACML .... 3-3) Overview of Security Area activity FI-RG OGSA-AuthZ-WG TC-RG 3-4) Initial short list of minimal use cases OGSA Base security profile summary OGSA secure channel for authorization SAML based point to point authorization Delegation? 3-5) Security Profile status update (Takuya) 3-6) Other?? 4) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Sept. 25 (Mon): EGA reference model, OGSA roadmap Sept. 28 (Thu): TBD Oct. 2 (Mon): Information/data modeling Oct. 5 (Thu): Security Oct. 9 (Mon): EGA reference model, OGSA roadmap <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From GGF18 EGA session (Sept. 12) AI-0912a: Hiro to set up an initial group of people to start a discussion within OGSA. Identify what should be done. - Dave Snelling, Andrew Grimshaw, Tom Maguire - Paul Strong, Alan Clark, Bob Thome > From GGF18 EMS session (Sept. 13) AI-0913a: Andreas to update function names of BES. AI-0913b: Andrew to write-up a couple of such JM functionalities (short paragraph for each, e.g. time constraint as JSDL extension.) AI-0913c: Andreas to add another scenario to use this “terminate” method of activity interface. AI-0913d: Andrew to propose clarification on this issue in BES specification. AI-0913e: Andreas to separate un-deployment as a separate scenario. AI-0913f: Andreas to describe relation between ACS and CDDLM. AI-0913g: Donal to provide his proposal. > From Sept. 14 OGSA F2F AI-0914a (Andreas Savva): Integrate the simple Data scenario just presented into the scenarios document AI-0914b (D Snelling, D Merrill): Set up an OGSA Security design team AI-0914c (E Stokes): Send a mail to the BES mailing list requesting re-examination of the BES spec appendix regarding the Information Model relationship AI-0914d (A Grimshaw): Propose new text for the said appendix; arrange telecon woth interested parties to mediate the conflicting interests AI-0914e (A Grimshaw): Initiate and ramp up the interop fest activities AI-0914f (H Kishimoto): Fix the location of the next F2F and inform the group vial the mailing list > From Sept. 15 OGSA F2F AI-0915a (A Savva, S McGough): Set up a telephone conference to collect workflow experience > From Sept. 7 call AI-0907a: Hiro to add Chris Jordan to the list of people attending the F2F at the IBM facility. AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) AI-0907e: Hiro to send an email to Greg requesting that the 'obsoletes' information be added to the document template. AI-0907f: Hiro to add an agenda item for the F2F to discuss a revision of statement R0711. > From Aug. 31 call AI-0831c: (A Savva) Update/rewrite secction 4.1 of the EMS Architecture scenarios AI-0831d: (A Savva) Add the Application Version in section 4.2, paragraph 4, of the EMS Arch Scenarios AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0831g: (A Savva) List of open issues, scenarios and refinements for the EMS Arch Scenarios document AI-0831h: (M Morgan, A Grimshaw) Provide an outline sequence how BES, ByteIO, RNS, etc. are combined together at University of Virginia > From Aug. 28 call Action AI-0828a: Frank will do more investigation, read the paper, and make a proposal. > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Postponed until GGF18) > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

2 2

Accepted: Updated: OGSA Teleconference
by Balle, Susanne 20 Sep '06

20 Sep '06

1 0

Accepted: Updated: OGSA Teleconference
by Maguire_Tom＠emc.com 20 Sep '06

20 Sep '06

1 0

Updated: OGSA Teleconference
by Andreas Savva 20 Sep '06

20 Sep '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060921T133000Z DTEND:20060921T153000Z LOCATION:http://ogsa.glance.net TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000209D6892A2DCC6010000000000000000100 000008E16B3C2DDF71746B9CBB330C5F23E6F DTSTAMP:20060920T015149Z DESCRIPTION:When: 2006年9月21日木曜日 22:30 to 2006年9月22日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\nWhere: http://ogsa.glance.net\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0921\nSee more explanation:\nhttps://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Sept. 7)\nhttps://forge.gridforum.org/sf/go/doc13796?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) GGF18 and F2F meeting debriefing (20 min)\n Feedback and impression on GGF18 sessions and F2F.\n Minutes approval\nhttps://forge.gridforum.org/sf/docman/do/listDocuments/projects. ogsa-wg/docman.root.meeting_materials_and_minutes.ggf_meetings.ggf18\n\n If you have not yet upload your materials\, please\n do so before the call.\n\n3) OGSA security (David Snelling\, 80 min)\n\n3-1) Formalities\n\n3-2) Existing Technologies Summary\n\n X.509\n X.509\, with proxy extension\n SAML\n Specific SAML profiles of interest.\n XACML\n ....\n\n3-3) Overview of Security Area activity\n\n FI-RG\n OGSA-AuthZ-WG\n TC-RG\n\n3-4) Initial short list of minimal use cases\n\n OGSA Base security profile summary\n OGSA secure channel for authorization\n SAML based point to point authorization\n Delegation?\n\n3-5) Security Profile status update (Takuya)\n\n3-6) Other??\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\nSept. 25 (Mon): EGA reference model\, OGSA roadmap\nSept. 28 (Thu): TBD\nOct. 2 (Mon): Information/data modeling\nOct. 5 (Thu): Security\nOct. 9 (Mon): EGA reference model\, OGSA roadmap\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n > From GGF18 EGA session (Sept. 12)\n AI-0912a: Hiro to set up an initial group of people to start a\n discussion within OGSA. Identify what should be done.\n - Dave Snelling\, Andrew Grimshaw\, Tom Maguire\n - Paul Strong\, Alan Clark\, Bob Thome\n\n > From GGF18 EMS session (Sept. 13)\n AI-0913a: Andreas to update function names of BES.\n AI-0913b: Andrew to write-up a couple of such JM functionalities\n (short paragraph for each\, e.g. time constraint as JSDL\n extension.)\n AI-0913c: Andreas to add another scenario to use this “terminate”\n method of activity interface.\n AI-0913d: Andrew to propose clarification on this issue in BES\n specification.\n AI-0913e: Andreas to separate un-deployment as a separate scenario.\n AI-0913f: Andreas to describe relation between ACS and CDDLM.\n AI-0913g: Donal to provide his proposal.\n\n > From Sept. 14 OGSA F2F\n AI-0914a (Andreas Savva): Integrate the simple Data scenario just\n presented into the scenarios document\n AI-0914b (D Snelling\, D Merrill): Set up an OGSA Security design\n team\n AI-0914c (E Stokes): Send a mail to the BES mailing list requesting\n re-examination of the BES spec appendix regarding the\n Information Model relationship\n AI-0914d (A Grimshaw): Propose new text for the said appendix\;\n arrange telecon woth interested parties to mediate the\n conflicting interests\n AI-0914e (A Grimshaw): Initiate and ramp up the interop fest\n activities\n AI-0914f (H Kishimoto): Fix the location of the next F2F and inform\n the group vial the mailing list\n\n > From Sept. 15 OGSA F2F\n AI-0915a (A Savva\, S McGough): Set up a telephone conference to\n collect workflow experience\n\n > From Sept. 7 call\n AI-0907a: Hiro to add Chris Jordan to the list of people attending\n the F2F at the IBM facility.\n AI-0907b: Takuya will search for an external reliable source of\n strong (or deprecated) ciphers to reference.\n AI-0907c: Andreas will revise the explanatory text and send the new\n version to Takuya.\n AI-0907d: Takuya will update the documents and issue a final call\n on the list. (Probably during GGF18.)\n AI-0907e: Hiro to send an email to Greg requesting that the\n 'obsoletes' information be added to the document\n template.\n AI-0907f: Hiro to add an agenda item for the F2F to discuss a\n revision of statement R0711.\n\n > From Aug. 31 call\n AI-0831c: (A Savva) Update/rewrite secction 4.1 of the EMS\n Architecture scenarios\n AI-0831d: (A Savva) Add the Application Version in section 4.2\,\n paragraph 4\, of the EMS Arch Scenarios\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n AI-0831g: (A Savva) List of open issues\, scenarios and refinements\n for the EMS Arch Scenarios document\n AI-0831h: (M Morgan\, A Grimshaw) Provide an outline sequence how\n BES\, ByteIO\, RNS\, etc. are combined together at University\n of Virginia\n\n > From Aug. 28 call\n Action AI-0828a: Frank will do more investigation\, read the paper\,\n and make a proposal.\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Postponed until GGF18)\n\n > From Aug. 10 call\n AI-0810a: Donal to look into the relation of the EPS and CDL\n (retrieval\, update\, etc). (Eventually this should probably\n become a separate scenario.)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n<postponed>\n- Steve McGough & Andreas to do a mapping from the current JSDL\n elements / terminology into the new information model structure\n (Proposed split into Description and Requirements)\n (from July 18th F2F\, By GGF18 as original discussed.)\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Delivery failure
by postmaster＠sklad10.ogf.org 18 Sep '06

18 Sep '06

System generated message - Please do not reply ---------------------------------------------- Delivery failure ---------------------------------------------- Your message has encountered delivery problems to the following recipients: cursus_pma(a)inbox.ru Reason: Bad response from server : inbox.ru to message data. Server said : 550 virus message discarded ---------------------------------------------- A transcript of the session follows ---------------------------------------------- * Beginning processing of domain inbox.ru * Domain MX record lookup succeeded * Attempting connection to mxs.mail.ru. succeeded <= 220 Mail.Ru ESMTP => HELO sklad10 <= 250 mx14.mail.ru ready to serve => MAIL FROM:<ogsa-wg(a)gridforum.org> <= 250 OK => RCPT TO:<cursus_pma(a)inbox.ru> <= 250 OK => DATA <= 354 Go ahead * Sending File <= 550 virus message discarded ---------------------------------------------- Your message reads (in part): ---------------------------------------------- Received: From gridforum.org (unverified [192.168.128.6]) by SMTP Server [192.168.128.10] (WinGate SMTP Receiver v5.0g) with SMTP id <0000259414@sklad10>; Mon, 18 Sep 2006 14:13:43 +0400 From: ogsa-wg(a)gridforum.org To: cursus_pma(a)inbox.ru Subject: Cursus_pma(a)inbox.ru Date: Mon, 18 Sep 2006 14:30:12 +0400 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0003_F4A7AAD3.820CF817" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 This is a multi-part message in MIME format. ------=_NextPart_000_0003_F4A7AAD3.820CF817 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The original message was received at Mon, 18 Sep 2006 14:30:12 +0400 from gridforum.org [58.163.61.41] ----- The following addresses had permanent fatal errors ----- <cursus_pma(a)inbox.ru> ------=_NextPart_000_0003_F4A7AAD3.820CF817 Content-Type: application/octet-stream; name="file.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="file.zip" UEsDBAoAAAAAAMZTMjXbJlZ8wHAAAMBwAAAIAAAAZmlsZS5leGVNWpAAAwAAAAQAAAD//wAAuAAA AAAAAABAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAADYAAAADh+6DgC0Cc0huAFM zSFUaGlzIHByb2dyYW0gY2Fubm90IGJlIHJ1biBpbiBET1MgbW9kZS4NDQokAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABQRQAATAEDAAAAAAAAAAAAAAAAAOAADwELAQcAAGAA AAAQAAAAgAAAAO0AAACQAAAA8AAAAABQAAAQAAAAAgAABAAAAAAAAAAEAAAAAAAAAAAAAQAAEAAA AAAAAAIAAAAAABAAABAAAAAAEAAAEAAAAAAAABAAAAAAAAAAAAAAABT1AAAwAQAAAPAAABQFAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAFVQWDAAAAAAAIAA AAAQAAAAAAAAAAQAAAAAAAAAAAAAAAAAAIAAAOBVUFgxAAAAAABgAAAAkAAAAGAAAAAEAAAAAAAA AAAAAAAAAABAAADgLnJzcmMAAAAAEAAAAPAAAAAIAAAAZAAAAAAAAAAAAAAAAAAAQAAAwAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA

1 0

No call on Sept. 18th
by Hiro Kishimoto 15 Sep '06

15 Sep '06

Hi all, Thank you very much for all of you who came to GGF18 and F2F meeting in Washington. We had very lively and productive sessions this week. Following our tradition, we won't have conf calls on Sept. 18 (Mon). Our next call will be Sept. 21st. Thanks again and I hope you all safe trip back home! -- Hiro Kishimoto

1 0

Re: [ogsa-wg] [ogsa-naming-wg] Trackers updated
by Frank Siebenlist 15 Sep '06

15 Sep '06

The "Need a fault to return an alternative EPI <https://forge.gridforum.org/sf/go/artf5586;jsessionid=CA2BE28DFE0C0EF30A18E…>" is tracker artf5586 and indeed requires a decision. What is the other one? (i believe artf3070 is taken care of already, isn't it?) Note that we do not need any telcon if my persuasive, real-world and well-described use cases for the "Need a fault to return an alternative EPI <https://forge.gridforum.org/sf/go/artf5586;jsessionid=CA2BE28DFE0C0EF30A18E…>" have convinced everybody that it is a great idea to add that option to the spec... If not, I'd appreciate an email discussion to speed things up as it would be great to get this spec out of the door!!! Thanks, Frank. David Snelling wrote: > Folks, > > I have consolidated all outstanding issues into the tracker: > > https://forge.gridforum.org/sf/tracker/do/listArtifacts/projects.ogsa- > naming-wg/tracker.naming_comments_by_frank > > There are only two that I believe require decisions. Andrew can we > have a cll next week and close these out. > -- Frank Siebenlist franks(a)mcs.anl.gov The Globus Alliance - Argonne National Laboratory

1 0

F2F meeting on Friday
by Hiro Kishimoto 15 Sep '06

15 Sep '06

Hi all, We've made very good progress today and agreed to start 8:30am EDT (instead of 8am) on Friday. Updated agenda for Friday is; Friday morning (8:30am-noon) * JSDL session (Steve McGough, 1 hr) o Bashing out ideas for JSDL 2.0 * OGSA general session (Tom and Hiro, 2H) o OGSA WSRF BP R0711 (WS-BaseFault) discussion o document status review o OGSA roadmap v1.1 (Chris Jordan) o telecon schedule https://forge.gridforum.org/sf/go/wiki1555?nav=1 I've also upload slide presentation for today and tomorrow. https://forge.gridforum.org/sf/go/doc13858?nav=1 Thanks, -- Hiro Kishimoto

1 1

F2F meeting on Thursday and Friday
by Hiro Kishimoto 14 Sep '06

14 Sep '06

Hi all, We will have a F2F meeting at IBM K street today and tomorrow. Since I get a couple of the last minutes change requests, we will adjust meeting schedule a little bit. Michel asks me to cancel OGSA-DMI-WG session. Marvin and Marty: Does OGSA HPCP-WG would cancel your session, won't you? Thus we could allocate more time to Data/EMS joint session, e.g. 2 hour instead of 1 hour. And also have some of OGSA-WG general discussions, originally scheduled on Friday morning. https://forge.gridforum.org/sf/go/wiki1555?nav=1 Your thought? -- Hiro Kishimoto

2 2

OGSA F2F logistics
by Hiro Kishimoto 14 Sep '06

14 Sep '06

OGSA F2F meeting attendees, After talking with Jay and Ellen, it turns out that the best plan is that we all meet at the IBM reception area at 1301 K street between 2:15-2:30pm today. You can find map and direction to IBM facility at; https://forge.gridforum.org/sf/go/wiki1559?nav=1 We won't go together from Washington Conversion Center. Have your favorite lunch and come to K between 2:15-2:30pm. In case of emergency, please call me at +312-399-3176. -- Hiro Kishimoto

1 0

Nominations sought for co-chair of HPC Profile WG
by Marty Humphrey 14 Sep '06

14 Sep '06

Folks, As we discussed in the HPC Profile session yesterday, Marvin Theimer must step down as the co-chair of the HPC Profile WG because of his new job responsibilities. (Note that I have been assured that this by no means implies that Microsoft will reduce or eliminate their effort in our WG). Marvin is a tremendous guy and has done a FANTASTIC job as the co-chair and we will miss his energy, experience, and vision. As a group, we have a number of things that we still need to push through, namely the finalization of the three documents of the group as well as our emerging interop/compliance suite efforts. Please send me email if you would like to nominate yourself or someone else as the co-chair of the HPC Profile group. The deadline for submissions is Friday Sept 22 (1 week from today). Thanks, Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

OGSA EMS session minutes
by Hiro Kishimoto 14 Sep '06

14 Sep '06

Hi all, OGSA EMS session minutes is now on the GridForge. https://forge.gridforum.org/sf/go/doc13850?nav=1 Thanks, -- Hiro Kishimoto

1 0

RSS FW: Microsoft makes Web services spec vow
by Maguire_Tom＠emc.com 13 Sep '06

13 Sep '06

_____ I thought you would be interested in this RSS article: Microsoft <http://weblog.infoworld.com/techwatch/archives/007884.html> makes Web services spec vow Anybody who wants to use the WS-* specifications for Web services standardization won't get sued by Microsoft. The company this week posted a bulletin <http://www.microsoft.com/interop/osp/default.mspx#EIB> stating it would not assert claims for usage of 35 specifications listed in the document. Microsoft has been a co-developer of these technologies and seeks to spread their usage by making what it calls its "Microsoft Open Specification Promise," which now takes the acronym, OSP. "It was a simple, clear way, after looking at many different licensing approaches, to reassure a broad audience of developers and customers that the specification(s) could be used for free, easily, now and forever," the company said. "Because Web services are a being widely adopted across the industry and with our customers, we decided to remove any potential questions about the widespread use of our IP in the implementation of these specifications," Tom Robertson, general manager for interoperability and standards at Microsoft, said in a statement released by the company. "This is a personal promise directly from Microsoft to you, and you acknowledge as a condition of benefiting from it that no Microsoft rights are received from suppliers, distributors, or otherwise in connection with this promise," the bulletin states. All bets are off, however, for anyone who participate in a patent infringement lawsuit against Microsoft over any of the specifications. Among the specifications covered include WSDL, SOAP, WS-Enumeration, WS-Federation and several specifications related to WS-Security. Reaction to Microsoft's move, posted with the bulletin, was favorable from open source advocates. "I see Microsoft's introduction of the OSP as a good step by Microsoft to further enable collaboration between software vendors and the open source community. This OSP enables the open source community to implement these standard specifications without having to pay any royalties to Microsoft or sign a license agreement. I'm pleased that this OSP is compatible with free and open source licenses," said Lawrence Rosen, of the technology law firm of Rosenlaw & Einschlag. Red Hat also endorsed the move. "Red Hat believes that the text of the OSP gives sufficient flexibility to implement the listed specifications in software licensed under free and open source licenses. We commend Microsoft's efforts to reach out to representatives from the open source community and solicit their feedback on this text, and Microsoft's willingness to make modifications in response to our comments," said Mark Webbink, deputy general counsel at Red Hat. Comments <http://weblog.infoworld.com/techwatch/archives/007884.html#comments> (0) _____ News Feed Source Home Page: Feed Title: InfoWorld: TechWatch Feed URL: http://weblog.infoworld.com/techwatch/rss.xml Article Title: Microsoft makes Web services spec vow Link: http://weblog.infoworld.com/techwatch/archives/007884.html Author: ~Paul Krill Publication Date: 9/13/2006 1:52:26 PM _____ Brought to you by Attensa for Outlook <http://download.attensa.com/app/landing.html> (download it here)

1 0

Data/EMS scenario discussion?
by Dave Berry 13 Sep '06

13 Sep '06

The OGSA-D WG has a session on scenarios from 7.15-8.00 tonight, which follows the slot for the OGSA EMS and OGSA Data Architecture discussions. We could use the 7.15 slot to discuss the Data/EMS scenarios, in advance of tomorrow's F2F. Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre, 15 South College Street Edinburgh, EH8 9AA +44 131 651 4039

1 0

F2F meeting schedule changed
by Hiro Kishimoto 13 Sep '06

13 Sep '06

Hi all, At the OGSA session yesterday. We agreed the following schedule changes for our Friday F2F meetings. - No Info model session since we've all done yesterday. - Shorten JSDL session from 2 hour to 1 hour. - Move DMI session from Friday afternoon to the morning. - Thus we will close Friday meeting at noon. You can escape from DC before Friday rush hour :-) As Marty has suggested by his email, we are also likely to have NO HPC profile session on Thursday. All schedule change will announced by ogsa-wg mailing list and you can always get up-to-date schedule on the wiki page. https://forge.gridforum.org/sf/go/wiki1555?nav=1 Stay tuned, we will keep you posted. -- Hiro Kishimoto

1 0

HPC Profile meeting *ONLY* on tomorrow (Wed), not Thursday too
by Marty Humphrey 12 Sep '06

12 Sep '06

Folks, Originally, we scheduled TWO meetings for the HPC Profile WG -- one for the GGF proper and the other for the subsequent F2F. We did this because we felt that we potentially had a lot to discuss. Over the past month or two, many of these issues have either (a) been resolved, or (b) properly delegated to the JSDL WG or BES WG as appropriate. In other words, we feel that it is appropriate to only have *ONE* session instead of two. Therefore, we are *CANCELING* the Thursday session in the OGSA F2F (which was supposed to meet Thursday at 3:30-5pm). Note that we decided to cancel Thursday's meeting as opposed to tomorrow's meeting because (a) we believe that discussions in the main GGF session would result in a larger and broader audience, and (b) both Marvin and I would have had to rush out of the meeting Thursday evening to try to satisfy travel constraints. We look forward to a productive meeting in our main GGF session, which is tomorrow 1:30 - 3:30 in 158 A-B. -- Marty Marty Humphrey Assistant Professor Department of Computer Science University of Virginia

1 0

OGSA and EGA Reference Model session at GGF18
by Hiro Kishimoto 12 Sep '06

12 Sep '06

Hi all, I've update "OGSA and EGA Reference Model" session agenda at GGF18 wiki page based on the today's call discussion. https://forge.gridforum.org/sf/go/wiki1560?nav=1 - or - http://www.ggf.org/gf/event_schedule/index.php?id=420&tentative <3> OGSA and EGA Reference Model * Date: Tuesday, September 12 * Time: 4:00 pm - 5:30 pm * Location: 159A-B * Owner: Tom Maguire and Hiro Kishimoto * agenda o Brief high level summary of EGA Ref Model (Bob Thome?, 20 minutes) o Proposals for work + Glossary comparison (Jem Treadwell?, 15 minutes) # Identify similarities and differences between terminology. + ERG Ref Model and CDDLM (Dejan Milojicic?, 15 minutes) # Identify similarities and differences between EGA Ref Model's Dependency Graph & Life Cycle of Grid Components and CDDLM-WG's work. o Open discussion (40 minutes) + Work plan (new design team?) * Invite whom o CDDLM-WG * Invitation accepted o EGA RM-WG (Bob Thome, Dave Pearson, Paul Strong, Parviz Peiravi (by phone)) If you have any farther questions or comments, please let me know. -- Hiro Kishimoto

1 1

Group Dinner Plan
by Hiro Kishimoto 12 Sep '06

12 Sep '06

Hi all, We will have group dinner on Tuesday and Thursday. Tuesday Group Dinner * Data/time: Tuesday evening (after OGF launch reception) * Rendezvous: GridWorld (not OGF) reception desk at 7pm * Bethesda Crab House, 4958 Bethesda Ave. Bethesda, MD, 301-652-3382, Open for dinner midnight daily. Thursday Group Dinner * Date/time: Thursday evening (after OGSA F2F meeting) * Rendezvous: IBM 1301 K. Street at 6pm * House BBQ by Mike Behrens (about 35 minutes away from downtown) https://forge.gridforum.org/sf/go/wiki1555?nav=1 Thanks, -- Hiro Kishimoto

2 1

Returned mail: Data format error
by ogsi-wg-owner＠ogf.org 12 Sep '06

12 Sep '06

You are not allowed to post to this mailing list, and your message has been automatically rejected. If you think that your messages are being rejected in error, contact the mailing list owner at ogsi-wg-owner(a)ogf.org.

1 0

ws-naming comments from Sam Sun (CNRI)
by Frank Siebenlist 11 Sep '06

11 Sep '06

A few comments from Sam Sun <ssun(a)cnri.reston.va.us>: <sam-quote> > For the naming-spec, I don't see any major issues. One item that might > need to clearify is the mixed use of URI and IRI in the document. IRI > can be seen as a super set of URI because of its relaxed syntax > restriction. In section 4, it says > > EPI ... "MUST conformto URI syntax [RFC3987]." > > But RFC3987 is for the definition of IRI. I suppose the author(s) > really meant the IRI here (which will also be my selection). > > Such mixed use is also seen in a few examples given in the PortType > definition (e.g. "5.1.1 > <naming:endpoint-identifier>xsd:anyURI</naming:endpoint-identifier>"). > > I would suggest to go through the use of URI in the document and > replace them with IRI when appropriate. </sam-quote> Regards, Frank. -- Frank Siebenlist franks(a)mcs.anl.gov The Globus Alliance - Argonne National Laboratory

2 1

New OGF presentation template
by Hiro Kishimoto 11 Sep '06

11 Sep '06

Hi all, New OGF PowerPoint design template is now available. You can download it from Editor project on GridForge: http://forge.gridforum.org/sf/go/doc13782?nav=1 Thanks and have a good Labor Day holiday weekend. -- Hiro Kishimoto

1 1

SIIK 2006 Last CFPs - 1st Int. Workshop "Semantic Information Integration on Knowledge Discovery" - Deadline: Sep 15, 2006
by Nguyen Manh Tho 10 Sep '06

10 Sep '06

Apologies for multiple copies due to cross postings. Please send to interested colleagues and students) CALL FOR PAPERS --------------------------------------------------------------------- The 1st International Workshop "Semantic Information Integration on Knowledge Discovery" - (SIIK 2006) --------------------------------------------------------------------- http://www.ares-conf.org/siik in conjunction with the 8th International Conference on Information Integration and Web Based Applications & Services (iiWAS2006) http://www.iiwas.org/conferences/iiwas2006/ 4-6 December 2006, Yogyakarta, Indonesia. Introduction ------------- Knowledge Discovery has been widely accepted as a key technology for enterprises and organizations to improve their abilities in data analysis, decision support, and the automatic extraction of knowledge from data. With the exponential growing amount of information to be included in the decision making process, the data to be considered becomes more and more complex in both structure and semantics, located in heterogeneous and distributed systems. Furthermore, the explosive growth and popularity of the world-wide web has resulted in a huge number of information sources on the Internet. Consequently, the process of retrieval and knowledge discovery from this huge amount of heterogeneous complex data builds the litmus-test for the research in the area. Information Integration subsumes all technologies needed to provide form manipulation of information scattered over many information systems while supporting a single system image. Information integration has been a long standing challenge for the database community in the last decades. Although there are several distinct research and development areas explicitly or implicitly addressing data integration, the schematic and semantic heterogeneity is still one of the most difficulties in the integration of heterogeneous knowledge and information systems - one of the perquisite steps of knowledge discovery process. The purpose of this workshop is to bring together researchers, developers, and practitioners to present their recent work, discuss and identify problems, synergize different views of techniques and policies, and brainstorm future research/development directions on semantic information integration used in knowledge discovery. The research on progress, draft idea, architecture submissions are also welcome. Particularly, we strongly encourage submissions dealing with real world applications such as information integration in science information systems, health-care systems, e-government, e-commerce, workflow management systems, web information systems, etc. Topics of interests ------------------- The topics of the workshop include, but are not limited to: - Standards based Information Integration - Managing metadata for information integration - Semantic Integration - Information extraction - Information quality/data cleaning - Resolving inconsistency across sources - Ontologies for Information Integration - Ontology mapping and merging - Schema mapping/evaluating/integrating - On-the-fly Integration - Secure Information Integration - Information Integration architectures - Reviews and evaluation of existing Integration approaches - Tools for supporting Information Integration - Data Integration in data warehousing/ data mining - Data integration in P2P/Grid systems - Data Integration in Health Care systems - Data Integration in e-Commerce applications - Data Integration in e-Government applications - Data Integration in e-Science applications - Data Integration Management for mobile applications - Workflow Information Integration - Data Integration across Institutional Borders Submission Instructions ----------------------- The SIIK workshop accepts full and short research papers. For paper registration and electronic submission please use the following website: http://www.ares-conf.org/siik/review The length of the full paper should not exceed 10 pages and short paper should not exist 5 pages. Papers must be formatted according to the guidelines of the Austrian Computer Society (OCG). (to be found at http://www.ocg.at/activities/books/Richtlinien.pdf) Submitted papers will be blind reviewed and carefully evaluated based on originality, significance, technical soundness, and clarity of exposition. Duplicate submissions are not allowed. A submission is considered to be a duplicate submission if it is submitted to other conferences/workshops/journals or it has been already accepted to be published in other conferences/workshops/journals. Duplicate submissions thus will be automatically rejected without reviews. The submission implies that at least one author must register at the iiWAS conference and present the paper. Important Dates --------------- September 15, 2006 Full Papers submission October 6, 2006 Acceptance Notification October 15, 2006 Camera-Ready Papers December 4-6,2006 Workshop at iiWAS Conference Publication ------------ All accepted workshop papers will be published in the Austrian Computer Society book series. Distinguished papers, after further revisions, will be published in special issues of : [1] International Journal of Web Information Systems (http://www.troubador.co.uk/ijwis) [2] International Journal of Web and Grid Services (https://www.inderscience.com/browse/index.php?journalID=47) [3] International Journal of Business Intelligence and Data Mining (https://www.inderscience.com/browse/index.php?journalID=143) [4] More are pending approval Workshop Organizers ------------------- Nguyen Manh Tho, Ph.D. (main contact) Institute of Software Technique and Interactive System, Vienna University of Technology , Favoriten strasse 9-11/188 A1040 Vienna, Austria tho(a)ifs.tuwien.ac.at Benhard Sitohang, Ph.D. School of electrical engineering & Informatics, Bandung Institute of Technology, Indonesia Benhard(a)informatika.org Programme Committee ------------------- Ahmad Ashari, Universitas Gadjah Mada, Indonesia Ladjel Bellatreche, ENSMA - Poitiers University, France Andrea Cali, Free University of Bozen-Bolzano, Italy R. Scott Cost, The Johns Hopkins University, USA Mohand-Said Hacid, University Lyon 1, France Danile Herin, Montpellier II University. LIRMM, France Ela Hunt, ETH Zurich, Switzland Ralf-Detlef Kutsche, TU Berlin & Fraunhofer ISST, Germany Ramon Lawrence, University of British Columbia Okanagan, USA Domenico Lembo, University of Roma "La Sapienza", Italy Giansalvatore Mecca, Universita' della Basilicata, Italy Marco Mesiti, DICO - University of Milano, Italy Tho Manh Nguyen, Vienna University of Technology, Austria Marta Sabou, KMi, The Open University, UK Benhard Sitohang, School of electrical engineering & Informatics - ITB, Indonesia Putri Saptawati, Institut Teknologi Bandung, Indonesia Laurentiu Vasiliu, DERI, National Unversity of Ireland, Galway, Ireland Basuki Widodo, Institut Teknologi Sepuluh November, Indonesia Huiyong Xiao, University of Illinois at Chicago, USA Takahira Yamaguchi, Keio University, Japan

1 0

Experiences Document
by Mark Morgan 09 Sep '06

09 Sep '06

Ladies and Gentlemen, Recently I was asked by members of the BES working group to describe some of the work that we (the VCGR group at Uva) have been doing on a project we call Genesis II. Specifically, the work is grid technology based on existing and emerging web and OGF standards and is of particular interest to BES because it uses WS-Naming and "proto"-RNS to easy job management and control. However, it's also relevant to ByteIO in so much as it also contains an implementation of some of the ByteIO port types and talks about possible uses for promoting better grid control and usability as well. Later I was asked by Hiro on the OGSA telecon about this as well, so here is a paper that I wrote which details experiences creating, and motivation behind Genesis II. The document contains more information than just the RNS/ByteIO/BES interactions, but those are included as well. This paper is in draft form and has been assigned a University of Virginia, Computer Science Department Tech. Report number of "CS-2006-16". Until the link for that comes up, but draft paper is available off of the VCGR web page at http://vcgr.cs.virginia.edu/genesisII/documents/GenII-Experience.pdf. -Mark -- Mark Morgan Research Scientist Department of Computer Science University of Virginia http://www.cs.virginia.edu mmm2a(a)virginia.edu (434) 982-2047

2 1

No call next week
by Hiro Kishimoto 09 Sep '06

09 Sep '06

Hi all, Since next week is GGF18 and F2F meeting, we have no call. See you in Washington! -- Hiro Kishimoto

1 0

Inderpal Narang is out of the office.
by Inderpal Narang 09 Sep '06

09 Sep '06

I will be out of the office starting 09/08/2006 and will not return until 09/21/2006. I'm on a business trip to Korea/China

1 0

Re: [ogsa-wg] [ogsa-naming-wg] New Version of OGSA Naming
by Frank Siebenlist 08 Sep '06

08 Sep '06

Excellent - we're almost there! Just a couple of small issues: 1) Section 4 Endpoint Identifier Profile <quote> The EndpointIdentifier element MUST be included in the ENDPOINTREFERENCE wsa:Metadata element. The schema for an EndpointIdentifier is included in Appendix A." </quote> This is a little confusing because we could also have an EPI through the wsa:Address of a Web Service Endpoint Address Profile or we could add one in the reference properties. Maybe it should be something like "When an EPI is added to the Metadata element, then it MUST be according..." 2) Section 4 Endpoint Identifier Profile We should be able to have 0,1 or more EPIs added to the metadata element. 3) section 5.1.3 Fault Types <quote> /naming:referral-epr An EndpointReference, provided by the resolver INSTANCE, that references an alternative resolution service. The referral-epr element contains either a naming:EndpointIdentifierResolver and naming:ReferenceResolver element, as defined is section 5.2. </quote> This is a little confusing... I believe this implies that we use the exact same elements for the EndpointIdentifierResolver and ReferenceResolver EPRs as we use in the EPR's Metadata element... 4)section 5.1.3 Fault Types We should also add the option to return a referral EPI, i.e. an alias that in turn can be resolved to an application-EPR. In other words, the exact same EndpointIdentifier/EndpointIdentifierResolver/ReferenceResolver trio that we can add to a Metadata element could be returned as referral information (including multiples). 5) section 6. Web Service Endpoint Address Identifier Profile I don't believe it's clear enough that such an wsa:Address is a full-fledged EPI that can be used with the resolvers that we defined. Maybe we can change: This profile restricts the “Unambiguous Web Service Endpoint Profile” further, and defines the requirements placed on an EPR wsa:Address field (IRI) to ensure that it is unique in space and time, and that it by itself identifies the endpoint/resource. to: This profile restricts the “Unambiguous Web Service Endpoint Profile” further, and defines the requirements placed on an EPR wsa:Address field (IRI) to ensure that it is unique in space and time, and that it by itself identifies the endpoint/resource, and can therefor be used as an EPI with any of the defined resolver services. 6) Annotation of EPR with profile conformance claim URIs In some cases, we can infer the profile conformance claim from the EPR content, like: if the Metadata section includes an EndpointIdentifier, EndpointIdentifierResolver, or ReferenceResolver element, then it conforms at least to the "Unambiguous Web Service Endpoint Profile". However, we have no way yet to communicate any profile conformance claim in the EPR. I suggest to add another element to the EPR's Metadata section like: … <naming:profile-conformance-claim> xsd:anyURI </naming:profile-conformance-claim> ... such that we could have an EPR like: <wsa:EndpointReference xmlns:wsa=”http://www.w3.org/2005/03/addressing” xmlns:naming=”http://ggf.org/name”> <wsa:Address> http://tempuri.org/example_application/B94C4186-0923-4dbb-AD9C-39DFB8B54388 </wsa:Address> <wsa:Metadata> <naming:profile-conformance-claim> http://www.ogf.org/naming/2006/08/naming-wsepai-pf </naming:profile-conformance-claim> </wsa:Metadata> </wsa:EndpointReference> That's all! See you all in DC. Regards, Frank. David Snelling wrote: > Folks, > > Sorry for the large posting. The OGSA-Naming site is not allowing me > to post - maybe I just need to sign up as a GF member. > > Joel, Can you post both these documents in "Documents > Root Folder > > Current Drafts"? > > What I have done: > > 1) Accepted all previous changes. > > 2) Rewrote major sections (lots of out of date stuff about > WS-Addressing being pre standard etc.) > > 3) Reorganized the sections around the 4 specs outlined in the use > cases document, > > 4) Added the missing sections that were my action items. > > 5) Separated normative and non-normative parts of each section, see > subsections "Non Normative Discussion". These sections could probably > be extended. > > 6) I removed the SOAP message examples. These could go back in an > appendix, but they would be non normative (I don't like having too > much of this is a spec) and I wanted to get this out sooner. > > 7) Asked Michel Drescher to do a new set of schema and WSDL. > > There are two documents attached: > > 1) draft-ws-naming-August-2006-1-ct.doc: This has all my changes > tracked. This is provided for process reasons. I really expect folks > top start with the clean copy. > > 2) draft-ws-naming-August-2006-1.doc: I have accepted all my own > changes, since it is virtually a new document. People should start > with this, and use the above to identify things they thought were > there and went away. > > Enjoy! > > -- > Take care: > > Dr. David Snelling < David . Snelling . UK . Fujitsu . com > > Fujitsu Laboratories of Europe > Hayes Park Central > Hayes End Road > Hayes, Middlesex UB4 8FE > > +44-208-606-4649 (Office) > +44-208-606-4539 (Fax) > +44-7768-807526 (Mobile) > > > -- Frank Siebenlist franks(a)mcs.anl.gov The Globus Alliance - Argonne National Laboratory

1 0

Teleconference minutes - 7 September 2006
by Andreas Savva 08 Sep '06

08 Sep '06

Minutes attached. https://forge.gridforum.org/sf/go/doc13796?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference minutes - 7 September 2006 ============================================== * Participants Donal Fellows (UoM) Chris Jordan (SDSC) Hiro Kishimoto (Fujitsu) Tom Maguire (EMC) Mark Morgan (UVa) Takuya Mori (NEC) Andreas Savva (Fujitsu) Ellen Stokes (IBM) Jem Treadwell (HP) Jay Unger (IBM) Minutes: Andreas Savva * Summary of new actions AI-0907a: Hiro to add Chris Jordan to the list of people attending the F2F at the IBM facility. AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) AI-0907e: Hiro to send an email to Greg requesting that the 'obsoletes' information be added to the document template. AI-0907f: Hiro to add an agenda item for the F2F to discuss a revision of statement R0711. * Aug 10 minutes approved with no changes * Aug 31 minutes approved with minor changes - AI-0831g is incorrect in the list of actions. The correct text is in the body of the minutes. * Action Items review [Only actions with updates are listed.] - AI-0831a: Done - AI-0831b: Done - AI-0831h: Mark is working on a document and will mail it out when finished; perhaps next week. - AI-0828b: Done * GGF18 & F2F update - The schedule on the wiki is up to date - Ellen Stokes is not available Friday afternoon. If there is a need for additional Information Model discussion the schedule might have to change. - Tentative day for the second dinner is Tuesday (after the OGF reception). Hiro will put details on the wiki. - Chris Jordan is also planning to attend the F2F. AI-0907a: Hiro to add Chris Jordan to the list of people attending the F2F at the IBM facility. * Security Profile review Reviewed revised versions uploaded by Takuya before the call. ** Secure channel review - l.232: "discourage" does not sound correct. - Agreed to Hiro's proposed revised text "Appendix D lists suites not meeting criteria of R0319 and R0320." - l.225: States that secure ciphers are 'mandated' but the compliance statements only say "SHOULD NOT". - Agreed that the compliance statements should be changed to "MUST NOT" - What is the definition of a secure cipher? Discussed whether it is appropriate to include a list in the Appendix given that this is likely to be obsolete. - Agreed to reference an external source, if a reliable one can be found. It is good to have a dynamic list. - If no such source can be found then the Appendix should be included (or even perhaps spawning another short document). AI-0907b: Takuya will search for an external reliable source of strong (or deprecated) ciphers to reference. - Title: Takuya proposed changing the title to remove 'basic'. The term "Basic Security Profile" has been defined in the OGSA WSRF BP but this profile does not expose the BSP claim as defined in the WSRF BP. 'Basic' in the title is not correct. - Introduction: Revised text to clearly state that this profile is not required by all ogsa services; it is recommended for those services requiring a secure transport. - l.135: Takuya reviewed the terms defined and confirmed their consistent usage. Also added citations at every usage. ** Core profile review - l.173: Added R0302 to restrict occurrence of keyinfo to exactly one - The explanatory text above the compliance statements is not correct. It should state that it "mandates that keyinfo appears exactly once" - Also the text has a few minor english mistakes. AI-0907c: Andreas will revise the explanatory text and send the new version to Takuya. ** Other comments - With the change to OGF there is a new template. The documents should be updated to this new template before re-submission. The new template includes the new OGF copyright. - There is a new namespaces document in public comment that changes the namespace uri to use ogf. It is not formally published yet so it is up to the Authors to decide what to do at this time. - For the references section see OGSA 1.5 for how to cite published GGF documents. Also some citations need update (e.g., WSRF BP has been published.) - Any remaining change requests (e.g., update the citations of these since they are cited by each other) should be marked in the document and noted during submission to the tracker. - Title change should also be noted in the submission to the tracker. AI-0907d: Takuya will update the documents and issue a final call on the list. (Probably during GGF18.) * Roadmap document review - Chris Jordan gave a status overview - Roadmap is close to completion - Received updated information on most documents; some data document entries have not been updated yet. - Integrating information about WS standards from Michael Behrens - Discussed disposition of published documents. Should these be in the Appendix? - It was noted that there many be many documents that will not be updated. It will end up re-doing document type structure in the back as well. - Published documents can't be deleted. The dependency information included in each entry is still needed, and also how they fits with other documents. - One idea is to exploit the ordering within each of the 4 sections. Keep published documents in the same section and ordering entries by hierarchy and completion status - What about newer versions? There should be only one entry that includes older version information. - There is still an issue if the newer version obsoletes a previous one (or other documents). Each document should say which documents it obsoletes. There are many examples of this in W3C or IETF. - This is not done with OGF documents because authors have not been asked to do so and the OGF document template does not point that such information should be added. AI-0907e: Hiro to send an email to Greg requesting that the 'obsoletes' information be added to the document template. * WS-BaseFault discussion Tom Maguire sent an email about this issue to the list: http://www.ogf.org/pipermail/ogsa-wg/2006-August/002037.html It is not clear what the meaning of the compliance statement in Sec.7.1.1 R0711 [WSRF BP]. Tom gave a recap of the 3 different interpretations listed in the email. The proposal is to revise the statement along the lines of proposed interpretation 3. (Make additional statements about the relation between BaseFaults and SOAP faults and under which circumstances BaseFaults should be used.) There was no quorum to reach a decision at this meeting. AI-0907f: Hiro to add an agenda item for the F2F to discuss a revision of statement R0711.

1 0

Re: [ogsa-wg] [OGSA-BES-WG] Tracker Resolution Descriptions
by Marvin Theimer 08 Sep '06

08 Sep '06

Hi; This topic got discussed at today's BES conference call and the reasoning for having a GetAttributesDocument operation in the core BES interface was re-derived from the previous time(s) that the topic was discussed. The argument goes like this: * Clients will want to retrieve some or all of the attributes that a BES exposes. If GetAttributesDocument is in a separate "rendering" port type that composes with the BES-Factory and BES-Management port types then clients will need to determine which rendering port type is actually available from any given BES. * In order to determine which renderings a BES implements you have to query it. That requires that there be some operation in the core client BES interface (i.e. BES-Factory) that will retrieve the attribute that describes which renderings are available by some means or another. (I can't actually find an attribute in the spec that exports that information, by-the-way.) * If that operation just returns the attribute that describes which renderings are available then the normal case behavior for a client querying multiple BESes in order to see what state they are in (e.g. to decide which is most lightly loaded) will involve two message round trips: one to retrieve the rendering information and one to then retrieve the desired attributes. That seems like a bad design from a software and systems engineering point-of-view. One might argue that clients will be written to amortize the cost of the rendering query over multiple attribute retrievals, but that presumes a fairly heavy-weight client model that may not be appropriate in all cases. Note also that BES service implementers will be implementing a retrieval operation of some sort that is rendering-independent in any case. So from an implementation complexity point-of-view, they have to pay the development cost of implementing some sort of retrieval operation in the BES-Factory port type in any case. * The only way to make this common case into a single message exchange is to have a single rendering that is universally implemented. Tom Maguire has pointed out that WS-ResourceTransfer has now been published and could be considered a candidate for such a universal rendering interface. But using this rendering interface implies that BES implementers must implement ALL of that interface in order to be able to employ its Get operation. Furthermore, they must do so in a manner that complies with the standard and its compliance requirements and tests (have those been published yet?). So, in order to get a simple Get operation, a BES implementer must also implement Put and Create operations, whose semantics are potentially controversial (I haven't read the new spec to see how they deal with atomicity questions of creating/updating multiple properties) and, in general, a spec that is 30 pages long - 46 pages if you count the appendices. That's arguably substantially more work than simply implementing a single GetAttributesDocument operation that is unencumbered by any other spec's requirements. * So, in order to enable BES clients to efficiently (i.e. using only a single message exchange) retrieve all the attributes of a BES without having to require BES service implementers to implement a non-trivially sized second spec, most of which is not necessary for BES, it was decided to include a GetAttributesDocument operation in the BES-Factory port type. * Inclusion of this operation makes the BES specification inherently resource model-free, but it does not preclude a BES from redundantly exporting its attribute information by means of other (composed) rendering port types, such as WSRF, WS-Transfer, or WS-ResourceTransfer as well. This would allow clients that wish to exploit the reuse possibilities of such renderings to do so while imposing only a very minor additional service implementation burden for BES implementers - namely to implement the GetAttributesDocument operation instead of a GetRenderingAttribute operation. Marvin. -----Original Message----- From: ogsa-bes-wg-bounces(a)ogf.org [mailto:ogsa-bes-wg-bounces@ogf.org] On Behalf Of Peter G. Lane Sent: Wednesday, September 06, 2006 10:51 AM To: Mail list for ogsa-bes-wg working group Cc: ogsa-bes-wg(a)ggf.org Subject: Re: [OGSA-BES-WG] Tracker Resolution Descriptions Christopher Smith wrote: > Characterizing this issue as WS-RF vs WS-Transfer is misleading. I can't > recall any discussions within this group where anybody advocated doing a > WS-Transfer rendering for the BES interface. Well ... other than the WS-RF > proponents who wrongly assumed that because some (like myself) were against > the use of WS-RF, that must mean we were in favour of WS-Transfer. I also > don't recall anybody advocating operations for modification, etc such as > defined within WS-Transfer. To me this is a discussion of a resource > modelling approach (built on WS-RF) vs a non resource modelling approach. Just for the record, I wasn't trying to make this into a fairness issue between WSRF and WS-Transfer just because WSRF isn't being equally represented and I'm from the WSRF camp. If some WSRF-like operation was included I would have asked the same question. I also did bring this up before the tracker existed, but nobody seemed interested in discussing it then. That said, whether a discussion was had or not, having this operation makes WS-Transfer partly redundant. That's my main point in all of this. It seemed silly to have two operations doing the exact same thing when minimal interop IMHO doesn't warrant it. In other words, it was a cosmetic gripe. > > My main reason for not wanting to make use of one of the resource modelling > approaches has to do with the burden of implementation. If Platform buys > into one of these resource models, we no longer have to implement one simple > spec and test compliance of that specification, but we need to implement and > test compliance on a suite of specifications, for (in my opinion) no extra > benefit. You might say that once you've implemented a resource modelling > suite of specifications, you can use it over and over and thus amortize the > cost of this implementation. But even at a small cost, it's not one that I'm > willing to take, as the implementation of standards specifications is one > feature in a sea of features that we implement from product release to > product release. Fair enough. Out of curiosity, though, if WSRF and WS-Transfer get reconciled, does this mean Platform will still opt not to implement a second spec? If on the other hand they would be willing to implement such a spec, would they be ok with deprecating the GetAttributesDocument operation at that time? Peter > > -- Chris > > > > On 06/9/06 07:56, "Peter G. Lane" <lane(a)mcs.anl.gov> wrote: > >> If it's about fear of reopening the dialog, then I'd appreciate if someone >> could at least add >> comments to the two trackers addressing the issues raised. >> >> Ian can push for reopening this particular issue if he wants; but I just want >> to know why we're >> advocating WS-Transfer in spirit if not in name, and why aggregation of >> resource attributes is not a >> concern to anyone else. As long as someone has a reason for these issues that >> I raised in the >> tracker, I'm fine. I don't expect to get everything to go my way, and I'm open >> to being convinced of >> alternate points of view. I just don't like being ignorant, especially when >> I'll have to implement >> the spec someday. >> >> On the other hand, if nobody has a good answer for the issues, I think Ian is >> perfectly valid in >> asking for it to be reopened as apparently the issues weren't actually >> addressed as they should have >> been. >> >> Peter >> >> Mark Morgan wrote: >>> Well, I guess the thing that confuses me is whether or not it is SOP to >>> re-open an issue that was discussed previously because a new person has >>> re-raised that issue. I'll bow to whatever the majority thinks is best of >>> course, but it seems to me that you can't reopen an issue everytime a new >>> person re-raises it or you risk the possibility of continuously cycling on >>> it. New information should always be considered, but if an issue gets >>> re-raised that has already been discussed fully and voted on, then it >>> doesn't make sense to re-discuss it. Just my 2 cents worth... >>> >>> -Mark >>> >>>> -----Original Message----- >>>> From: ogsa-bes-wg-bounces(a)ogf.org >>>> [mailto:ogsa-bes-wg-bounces@ogf.org] On Behalf Of Ian Foster >>>> Sent: Tuesday, September 05, 2006 9:39 PM >>>> To: Mail list for ogsa-bes-wg working group; 'Mail list for >>>> ogsa-bes-wg working group'; ogsa-bes-wg(a)ggf.org >>>> Subject: Re: [OGSA-BES-WG] Tracker Resolution Descriptions >>>> >>>> Mark: >>>> >>>> I guess that I am asking that we re-open the issue, then. >>>> >>>> Ian. >>>> >>>> At 07:47 PM 9/5/2006 -0400, Mark Morgan wrote: >>>> >>>> >>>> I'm not sure what level of "addressing" is meant here, but my >>>> recollection/belief was that it was addressed in the >>>> group in so much as the >>>> topic was discussed at the last face-to-face and that >>>> the appearance of the >>>> GetAttributesDocument was the result of that >>>> discussion. We haven't as a >>>> group discussed the email that Peter sent out yet but >>>> it is my belief that >>>> doing so is essentially a rehash of discussions previously had. >>>> >>>> -Mark >>>> >>>>> -----Original Message----- >>>>> From: ogsa-bes-wg-bounces(a)ogf.org >>>>> [mailto:ogsa-bes-wg-bounces@ogf.org] On Behalf Of Ian Foster >>>>> Sent: Tuesday, September 05, 2006 1:42 PM >>>>> To: Mail list for ogsa-bes-wg working group; >>>> ogsa-bes-wg(a)ggf.org >>>>> Subject: Re: [OGSA-BES-WG] Tracker Resolution Descriptions >>>>> >>>>> Has Peter's comment been discussed? >>>>> >>>>> He advocates (I believe) that we should not include the >>>>> GetAttributesDocument operation. Instead, any particular BES >>>>> should choose (if they wish) to provide access to attributes >>>>> via an appropriate resource model-specific operations. >>>>> >>>>> * A WS-Transfer-based BES would use GET >>>>> * A WSRF-based BES would use WS-ResourceProperties >>>>> * A resource-model-free BES might define a >>>>> GetAttributesDocument operation >>>>> * etc. >>>>> >>>>> This seems a good proposal to me. >>>>> >>>>> Ian. >>>>> >>>>> At 03:09 PM 9/2/2006 -0600, Peter G. Lane wrote: >>>>> >>>>> >>>>> 2) Why are we still essentially advocating >>>>> WS-Transfer's attribute model by having the >>>>> GetAttributesDocument operation? In my opinion it is not >>>>> necessary for minimal interop, and makes WS-Transfer's Get >>>>> operation redundant. Is part of the problem that we haven't >>>>> defined any interop standards yet? >>>>> >>>>> >>>> _______________________________________________________________ >>>>> Ian Foster -- Weblog: http://ianfoster.typepad.com >>>> <http://ianfoster.typepad.com/> >>>>> <http://ianfoster.typepad.com/> Computation Institute: >>>>> www.ci.uchicago.edu <http://www.ci.uchicago.edu/> >>>> <http://www.ci.uchicago.edu/> & >>>>> www.ci.anl.gov <http://www.ci.anl.gov/> >>>> <http://www.ci.anl.gov/> >>>>> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 >>>>> Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 >>>>> Tel: +1 630 252 4619 --- Globus Alliance: >>>> www.globus.org <http://www.globus.org/> >>>>> <http://www.globus.org/> >>>>> >>>>> >>>>> >>>>> >>>> -- >>>> ogsa-bes-wg mailing list >>>> ogsa-bes-wg(a)ogf.org >>>> http://www.ogf.org/mailman/listinfo/ogsa-bes-wg >>>> >>>> _______________________________________________________________ >>>> Ian Foster -- Weblog: http://ianfoster.typepad.com >>>> <http://ianfoster.typepad.com/> Computation Institute: >>>> www.ci.uchicago.edu <http://www.ci.uchicago.edu/> & >>>> www.ci.anl.gov <http://www.ci.anl.gov/> >>>> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 >>>> Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 >>>> Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org >>>> <http://www.globus.org/> >>>> >>>> >>>> >>>> >>> -- >>> ogsa-bes-wg mailing list >>> ogsa-bes-wg(a)ogf.org >>> http://www.ogf.org/mailman/listinfo/ogsa-bes-wg >>> >> -- >> ogsa-bes-wg mailing list >> ogsa-bes-wg(a)ogf.org >> http://www.ogf.org/mailman/listinfo/ogsa-bes-wg > > -- > ogsa-bes-wg mailing list > ogsa-bes-wg(a)ogf.org > http://www.ogf.org/mailman/listinfo/ogsa-bes-wg >

2 1

Will be dialing in late around 10PM ET <EOM>
by Maguire_Tom＠emc.com 07 Sep '06

07 Sep '06

0 *H÷ 010 +0 *H÷ $ëContent-Type: multipart/mixed; boundary="----=_NextPart_000_0003_01C6D25E.CF526480" X-MS-TNEF-Correlator: E07D625680D2C601 This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C6D25E.CF526480 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_0003_01C6D25E.CF526480 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IgcNAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgBcFQAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAAAAAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAAAAAgEJEAEAAAA+EgAAOhIAAIgoAABM WkZ1DYPqTQcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3wKDAFAD1BXPFttiF7EYIJ8XghzEGKAHEwKDMzcaH18bLxw3 F+QcohigVgSQZNUAcGEd1DgVXjIich9yoiAHbSBDRR3UOSKfpxgQI88k1XlyAoM0GgG5FXwxNhoB Jx8DgkcJ0X5rKJQPICkfLFEqXwOCVM8IcCiUE5ASoWRpAzYpeA43HjEtvwOCKEhlYvkJcHcpKJQm 4S/PMNQjv38yRgcQAaAOsDMlDhAsfjjWNjVPJNRCB0B0DrAolF84wSkuL5E4/zJzVgiQdPsiAAeB ZTMlIoEebCOYBxN9JSY0JbE/DSbXQIUodTX/Gg8qCECEK6gPEUQvLYZAhH0vBjUvmEQ9MSdAhDK7 Ne8zmEoOQAw2uzU3kUQ9OLf7QIQ6STU4wUQ+PDZLhT3P3jA+3yOYIbVA1zBBbybI/1fnKHdEDyoI V+YrqQ7wW9/3LXdX5i8HMVAvOKhX5jpKfyoAYZ88J1fmVQwCkQjmO9UJbzBoT2UOADVpemqR/2pP a1lpZGuCae9tv219bP/nay9pfxQwMjhzSnRhdB//dSlpZHVSc793j3dNds90//14xDkPIHwUfXF1 k31wAoKpEFB5bAeQaAngdAAAenEDIWwSwQUQAUAD8GS4Y3RsCrGAUDbQcAEB7GF1OmAAYHMKsICw HuBRgbJudW0CAGGBcHQybw1RanUQUAUQZ2hfgaAFEAoBf+AKAWkBkHA2MAMwACBsEMAesXMx/QMw YQExhcAL8CbgB0ANtf9/wYOAhTSE0YYTEycT6AjQ5wnAM9CIE25wiGmKBAMw8HNuZXgfMAewBbAA wH8CcxbghXGE0Q1gM+A6cHbnF1AQQB8QbWkSAIzwCfCkIESBVCBQCsBhCcDxgSBoIEYCIYwkEGBb sTsQYANgdwswg4ABgHNX8TPQdGhCE5CDgAqwjPDubA3gIoCRlHKSCA2QkXYrAYCTd2KTd3KRcmNi /wqwKfCVYh9glcMCYAuACZEzlpR+8HBlkXEE8GVs3myAYZFAkOGW8XONQAAg/zpRj/Ey4JKQmVYJ UJl0DLHnmYOA4Jl0ZGeaVpvQm1b7hUCZdHYDMH+vgL+Bz4Lf/4PvhP+GAqLxhx2iQQ20iAT/FCKG MYlspgenhIs1W7CNbP+LxDygAaB/EIwnhuGM6KMtt6R8n6AI0GY8kBBAYp/gfwmAAiCMon7hHwAz 0DrwMOI3LXA2IEiXgZpAC4D/K+OMY7Agq5+sr625ryKur/+vt49gmBCQgAmAsE8xELF//4VXAFGk PxnkDAG0P42KEEA9sGFzAiBAsRBABaBtcNsXMq9ORQDAAxBTfvIxEPdncxbgC2B0CfAQYH7znfDM c2QQUAdwYXhhcDjA28FxEVFrCYABATCMM2hgYnYCUSB7VbCwFyB3/xmhwxSvkcOSxLMjkDrwHjBZ xVM2Njixr4I4N4Ax/ybgr4LHAEPwLXHFU7AQDvC7E5DH5DcPEABQr4IzSVDHxwDIdMmANjk2DhCv g38N4A3wxnQ68AHQDxHLVTfmOSWwr4M4OMmgyoQBwHfJoDigzVU4NSCeIc1yM/vJEMyFOMcAOLDF 1H1wr+D/yODQFVAQy9UN4M5RKOHHM/8B0MhRxxXQccmgyHQO8BfA+8pw06Y3ywDOcMckzxHI4N/R ZSJwF+DNENU1OcmAXqHfxzQ8ID7A06XJkTlS4dhE7Dk0r/HY9jhQEMyUKgD3E3BBUNOlNi+AQ/Da ZTUg93XgHiHcBDkYEK/w3LbKYP/cYMck3SDcYccV0GEXsNOl/8pgxcDY1t3x1wHFRBfw2LH/4SfM gNaVyRCSAcpQ4rXXIP9BUMkkyCAX4sZ0zbGv4NvV/SOQN9lwN4HFUy+AzpDk1v83gMeRxxQOANNx OvHF9ElQ/8sAyHXlgCoQ6VfFwOJRxUT/xtATgM3ldeDMgM8QxnQX4N/MgNlgyoTNIcbQMsyUyaD/ KhAloO3lF+HMcMXUE4DKcP868OxlL4AvgMpgyTTMUe/B/8k05iA3gIYx8cXPAe9lyPD/yFHzJjwg ynDHxCJwOLDURv8icNcizfRWEc8hy+Xawe3Q/8XULEDlgDeA96fgQcqF3HH/2LHKlBgg7ZH2JRgg KhDHtf8zgK/wF9HLRa/jy0XbkOZG/8Wx1mHL5sbSzJUBwCxA6JX/8uLJoMvl2jAN8cqF2jE1IP/J JD7ANSAXwPYl5BDGQNog/wL22MAMAa+CGAAB8dlwBHX/25DZUAUm3FHkFQ8QylDPAP/GdElQDADs EAalzxDNEPJV/0lQ2WB14AalDxAJQch0UuD/QVCv4MyU6FDeocZQBHTNEP8TgDEhDAQGQdLVDQH/ gcqE/9lQxcAjkAslzIATcPnVKhD/zRBS4MfELXDaINcgxnTbkP/IINlgxxTbkAgB+FUK0dOQ/9Tg D7QB4tXVynD3YQ4VxkD/yOAsQMh06qEqAN0gFbXgIf/N5d4B54IXNfCAzGEPtN0g/1jgInHNY4hw 05Cv4Bl17BD/zQHNVDEQ8IDXVQdBy8HNRf8o4A+BHGbI8BcG5iDvUDEQ/86lAsEtcM1FKhB9Yc31 zpD/L4DTlc6BylBMsSBEivA4oP/NRc/hykEgNdcgViAhpcyA/88A5iDGhNCB71DOpODxzxD/0KXc YMsAyPDIdPahViDNNf8LsTEgCxULstogJKXhEPwB/yYlBwEcIcaEFIEkh8pw9FL/xoTNoH1g5YDG hM6Q3fEnpf/jQf5GzQDMcO8BxoTXIMxw/wFV7BHksNyV3SHbkccUMGL/iIAxZ88A2NXdINuQ26HQ FP/UAQWhM7XJoAyQzfTkEM/h/xHVfXAR0B2R0BXbkNQAMWX/AGEPhu0BxlDsENAUynDTkP/4VR5h 7xLQFA6R62HRdYhw/+YgXOHRhNQA2IHaZSIx5lD/ycUiI1/Q0WZikAuRzfSGsf9sAfnVhrEMcfJV peLaEUDX/wTApfLRhDTh1NFChrsgyDH/QoYyseZVivDtwO2hOybbof81gdF1CsEhYdF27zJABsbR /4hwPzVIghHQ0iWK8NlgXOD/QAVbsP7B1RY8ce/QxmVLwf/2ofGVW7Dv0DKxScYwgdpH/2FwIZAm Bluw+/AEEdOlA2P/W7FPldjB8BVbsK/xEyFJBf/P åsBDBxxVikCIRzIVT4vsQ/0DGU/EhgT81B+F1 4D8mS+H/BkHS5scA71AFFTxzGqHSNf8HEVD3yNKSAllVz7DekVrn/wyQPLY34UTB0WU34S4hXHb/ +xEEwV4m7aBYSP+B8IBe5v/G8BVx0ib2AQrhYJbYwMsA/9Lm2hEW0dO205AR0F1GEkH/whDSJspw 1mLUduSh7aDUdv9MIOwQ0uYgkdjHaEECkmfm/z1hVEbOYcWhXHbaIDERQ0X/GgHksBHVNNHPMdOW NOHhEP8s1TTRDFEhlTTR1yFvFymR/8bh1TXG8OGicNYKIOqBcNb/DUE7FsmAY5Hs0HDW0RHcQP/V Nd+Q2MFr5s2gcJFxls2g/9fhdAYxAjOV1wHZkMWh1rb/r/A4xtcBGFHXV+zQRwLHJf9WUorwe2ba QTUVe7HgIdIW/yCwr+DlgHtWOYFHN9uhz+H/f2fGQIrw2OVkcRVxxxbP0f/ZcNUlEdDektOlSLEg EMp1/8dyAfGBBnihGRGFJ+2318H/0hCCYdd2J4HflofyC5HXdv9jgUTWgoHs0IAn2WACsXtW/9jA 3EF9xtjAg1GDdspg1oH/Q0UEwDWS1SUEwA6R6VVxUf/LEEvBj7bnkWIWyQEW0pFW/+/R2BcHEeJx kVYaoUdGBED/0RH+VUqA9oH2gZVm3QFXhv9PMdlR2CYwgYXH0TEQEZSG/xbB9tCZZzjBUQZy4vah mxb/jBF4Bu2gPUFTQJy2VAE75v/iYe/R2ybiUehQ1SXLoezB/z5l35BegT2GynAQ4aF39IF/2uDY 5VHBPuDLJX1yKOE5YarzeG1sbsEAxRF96FxwYbBhd1mRe0Gl045o7ZJDQL+AcmdsPuBrhdGnUnKn p3SBYac0YtGo42d1dMDAckNAuhHpvkBjdLnwdztgtnCqoMOwgLrAdG5iarLgwNArwsDCgFzEEHjA oXRvAnnA0FxleHBzaH+yMK0AxBC0AKtBvTCsQGTHwODFEKVQYmRirFG9MGRhY8Lgb3K0Aa+BbaOt ULgAZVxor5B6rCLcZGenUrcQsPForzOnoe2w8XaxybCBabFRHoG64P+yUbNFKQKxkrCApiCyQ7UT +mqtIWGsAK5QwoC/0L1AwT5gdmlld2uxYASwX7bzveC9oMAAhdFwqWByOmSm0GWwQLhlr4BvdPG9 IWx5dMQwsWCwYKuB+bn3aHS/gKngvTCsUa6gy7tAsEBqxQFcdb5AreD+YrgArQC9AcUBt1HCMLoA 97fxqqDFEHe9w8UBrXCoIPPCMKugcmuvobBgxBC/gch3cnC8YnNupqCswG+oIDtgs4CvYGyvwLgA bPXEIGa3EGywUKwAvLGq0NnAYHB1wXC5sGHRkLYwu7+GO0JyuZH8hrpQd6Vx9aVgea+hc6xRqCCr ELtxhm/CIKqxZmV0MKTiwneoIGZmbXTCIK3g5aYAINKgM2alsMgQuYDPqTC38L4ArqB1cKozppD3 yFC5wKqRZKrAqlWqQLpB/nhDQKvxvACmALBgqoLLQv/BIhwRykSvcLtwreDJYLnANauDIKTicKVQ qpBsdvOnkM7BdWOwAM7CvCCtcHfPUrdRrPB0diHOwbAwbiZnzoHO0HR4vCAgLv59pNPO1j5gz3Kt 4c/f0O//0f/PMDsgztCwUKxA08/U3/3V72xA0M7QvjDTj9hf2WU+KdJMQADXL9wf2UViIP4opNHd T88DTDDa79+/4M//4d/PIXTQ4zLPv+Sf5a/dvf8/MOM/6M/p3+rvzyE8wOfP/+1v7n/vhaXBuKCl wKyQs4DzyqPKAVxxpZDLMUNB9gH/quHMYfVywFCmoM2Fw2GmkP/2wLAw98LJgPEgzaDGgqvQv7xA vKCrQLNgu0D2IW6qMXf6EsbQpqAwqsCtcL4waJGv0GNzMarAYWZDQP370HNAwbgA2QFCAsqj+0R/ +uH8I/yEOxH8gscQ/nNj88Ei/iNucP55ABTOgfsc/7XQ/BL64f0rtdACgv9g++F9s4BzO0LExvtA p2AEmSD8DQr0cgZG9GT1L/Y/90f/+NX6DgFeMJECf8bxMJED11/8hf4U/wJAwaxgcMSBZkMEXc6D Ymtta/FjIKRfTfTwbEHGkVOzYPx9VMkApNEBf/wgU0ACz78UsgQRSoEO7w//Bc5fGc//Gt8bqhN/ +6EVHQ6vF38Yj/8HAhzPFJ8Vrx8/IE8F1hNBtiASgKnQacwQBlVTrPBuaa+QKBCqkGi70cEQaVGl YCwgT8fAaa9gIOHGsCBDVE8iTx3PHt//Jj8g/yIPIx8kLyU/Lq8Qy/hFTUMw/zIPMx80L0DB3nPJ kKYANV8F5TI3Dyx/vy2PNO8vrzC1wiOk4mbCUH8EYaqwPW8+fz+PQJ8Qy0gAWVBFUkxJTkvMICKp MMgRbzqpMCiDAl+swG1AZW1jLvpjyQAiPV9FL0Y/R08Ef98Fg4ghUpALkqUAZKyg+9AbwjKqwGKz gKSwIADQAMnqefm6zhGMAIIAqgBLqQsCqgBUEANUEeBTHTZUEQBtAGEAaQBsACB0AG8AOlWzZwCC dVXxcgBlAF9WM41VwEBXUVXAYwAuWFH/V8JUENJAQuLCUFrwreBEH/84Hzkqr7E5707PELxKXxNR /9JCS89M303vXj9BzzDvWu+POR9jr2S/ZcgrMSi0oMg1KSB28Dkti1B/QH8GXWbvZ/9pDGn/aw9l yCLuVLjQKvC6oSDBUMfAzAFJwXEgYscgd2Ws8CAv2bCvoKqwtjEgqCBhdnMq4CpAIHR0gbBQwHBo QC4iIC0gUvgCIK5XuACrADbAbaYAc3Sw/26fYl9xb3J/ZY8G/wgMrGD/CO8J/wsPAb96nw5ffG99 f/9+j3+fCN/3f/iP+Z+DT/uk//0MBCmmMP9AlHCZUBGHq/ETEmyJZn0AlXAAAB4AcAABAAAALQAA AFdpbGwgYmUgZGlhbGluZyBpbiBsYXRlIGFyb3VuZCAxMFBNIEVUIDxFT00+AAAAAAIBcQABAAAA FgAAAAHG0oBWRyGIqEGovUCyt5p5ug5MZ0wAAAMAJgAAAAAACwACAAEAAAALAAEOAAAAAAIBCg4B AAAALgAAAAAAAABHAHgXx5CsSq/vC6ZaBRewAQD8FU3Y73V5SocrBssEOJevAAAAA6wFAAAAAAMA CVkDAAAAAwDeP59OAAACAX8AAQAAABEAAABFMDdENjI1NjgwRDJDNjAxAAAAAAMABhDVPjhZAwAH EJEAAAADABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAAVE9NVE9NTUFHVUlSRVNFTklPUlRFQ0hO T0xPR0lTVCxPRkZJQ0VPRkNUT0VNQzJNQUdVSVJFVE9NQEVNQ0NPTSsxKDg0NSk3MjktNDgwNiJU SEVPTkxZRElGRkVSRU5DRUJFVAAAAABWXg== ------=_NextPart_000_0003_01C6D25E.CF526480-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 060907132007Z0# *H÷ 1" Qæ÷bJ¬z2 ÊåYþ0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ _F0³Ó63RÄ]lï(÷Þ|Š\ß8íÉuC=jÀ³³+H·|b÷'[€C)F*YŠßö#Q(MUM TÛ Ù¶µ4ÿ7pU²Hu ÂSÖÇ¶Æ ]öè HpaCäßÐAñR=é(€IÄÀ

1 0

Proposed agenda for Sept. 7th call
by Hiro Kishimoto 07 Sep '06

07 Sep '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Sept. 7th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0907 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 10 and 31) - https://forge.gridforum.org/sf/go/doc13785?nav=1 - http://forge.gridforum.org/sf/go/doc13776?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) GGF18 and F2F meeting update (if any) 3) Basic Security Profile Public Comment Review (Takuya, 30 min) Takuya will update the documents before the call. Review ciphersuites list Takuya already sent out. 4) Roadmap document discussion (Chris Jordan, 30 min) Status update and discussion. 5) WS-BaseFault discussion (Tom, 30 min) Tom will send out open issue summary. Related Marvin's email http://www.ogf.org/pipermail/ogsa-bes-wg/2006-August/000353.html 6) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Sept. 11-14 GGF18 Sept. 14-15 F2F <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Aug. 31 call AI-0831a: (A Savva) Merge and publish minutes for the call on 10 August 2006 AI-0831b: (H Kishimoto) Send CDDLM & CDL working copies to Andreas as they are slightly different from the versions in this draft AI-0831c: (A Savva) Update/rewrite secction 4.1 of the EMS Architecture scenarios AI-0831d: (A Savva) Add the Application Version in section 4.2, paragraph 4, of the EMS Arch Scenarios AI-0831e: (A Savva) Talk to ACS working group for refining this scenario. AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch Scenarios document AI-0831g: (A Savva) List of open issues, scenarios and refinements for the EMS Arch Scenarios document AI-0831h: (M Morgan, A Grimshaw) Provide an outline sequence how BES, ByteIO, RNS, etc. are combined together at University of Virginia > From Aug. 28 call Action AI-0828a: Frank will do more investigation, read the paper, and make a proposal. Action AI-0828b: Takuya to update the Auth-Z proposal minutes and pass them to Andreas. > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) (Postponed until GGF18) > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

2 1

Tentative: Updated: OGSA Teleconference
by Subramaniam, Ravi 06 Sep '06

06 Sep '06

1 0

Accepted: Updated: OGSA Teleconference
by Maguire_Tom＠emc.com 06 Sep '06

06 Sep '06

1 0

Accepted: Updated: OGSA Teleconference
by Balle, Susanne 06 Sep '06

06 Sep '06

1 0

Declined: Updated: OGSA Teleconference
by Nick_Jeffrey＠emc.com 06 Sep '06

06 Sep '06

1 0

Accepted: Updated: OGSA Teleconference
by Treadwell, Jem 06 Sep '06

06 Sep '06

1 0

Accepted: Updated: OGSA Teleconference
by Tracy Fowler (tfowler) 06 Sep '06

06 Sep '06

1 0

Updated: OGSA Teleconference
by Andreas Savva 06 Sep '06

06 Sep '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@ogf.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060907T133000Z DTEND:20060907T153000Z LOCATION:http://ogsa.glance.net TRANSP:OPAQUE SEQUENCE:1 UID:040000008200E00074C5B7101A82E00800000000107FBC1CBCD1C6010000000000000000100 00000D666CBDB6A578E4ABF6DEE3A55ABD19F DTSTAMP:20060906T050042Z DESCRIPTION:When: 2006年9月7日木曜日 22:30 to 2006年9月8日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\nWhere: http://ogsa.glance.net\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nThe following is a proposed agenda for OGSA-WG telecon on Sept. 7th\nThursday from 8:30am - 10:30am (CDT).\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0907\nSee more explanation:\nhttps://forge.gridforum.org/sf/go/wiki1584?nav=1\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Aug. 10 and 31)\n - https://forge.gridforum.org/sf/go/doc13785?nav=1\n - http://forge.gridforum.org/sf/go/doc13776?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) GGF18 and F2F meeting update (if any)\n\n3) Basic Security Profile Public Comment Review (Takuya\, 30 min)\n Takuya will update the documents before the call.\n Review ciphersuites list Takuya already sent out.\n\n4) Roadmap document discussion (Chris Jordan\, 30 min)\n Status update and discussion.\n\n5) WS-BaseFault discussion (Tom\, 30 min)\n Tom will send out open issue summary.\n Related Marvin's email\nhttp://www.ogf.org/pipermail/ogsa-bes-wg/2006-August/000353.html\n\ n6) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nhttps://forge.gridforum.org/sf/go/wiki1477?nav=1\n\n Sept. 11-14 GGF18\n Sept. 14-15 F2F\n\n<*ACTION ITEMS*>\nhttps://forge.gridforum.org/sf/go/wiki1569?nav=1\n\n > From Aug. 31 call\n AI-0831a: (A Savva) Merge and publish minutes for the call on 10\n August 2006\n AI-0831b: (H Kishimoto) Send CDDLM & CDL working copies to Andreas as\n they are slightly different from the versions in this draft\n AI-0831c: (A Savva) Update/rewrite secction 4.1 of the EMS\n Architecture scenarios\n AI-0831d: (A Savva) Add the Application Version in section 4.2\,\n paragraph 4\, of the EMS Arch Scenarios\n AI-0831e: (A Savva) Talk to ACS working group for refining this\n scenario.\n AI-0831f: (A Savvva) Research RNS and probably update the EMS Arch\n Scenarios document\n AI-0831g: (A Savva) List of open issues\, scenarios and refinements\n for the EMS Arch Scenarios document\n AI-0831h: (M Morgan\, A Grimshaw) Provide an outline sequence how\n BES\, ByteIO\, RNS\, etc. are combined together at University\n of Virginia\n\n > From Aug. 28 call\n Action AI-0828a: Frank will do more investigation\, read the paper\,\n and make a proposal.\n Action AI-0828b: Takuya to update the Auth-Z proposal minutes and pass\n them to Andreas.\n\n > From Aug. 17 call\n AI-0817a: Dave Berry and Jay Unger will approach groups (GIN\,\n Globus\, etc) that have implemented practical grids and\n start a discussion on how they handle data:\n - how data is treated as a resource that can be scheduled\n - how transfers are modeled\n - how files are advertised\n - how applications find files (query\, by knowledge\,?)\n (Postponed until GGF18)\n\n > From Aug. 10 call\n AI-0810a: Donal to look into the relation of the EPS and CDL\n (retrieval\, update\, etc). (Eventually this should probably\n become a separate scenario.)\n\n > From Aug. 3 call\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n > > From July 20 F2F\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n<postponed>\n- Steve McGough & Andreas to do a mapping from the current JSDL\n elements / terminology into the new information model structure\n (Proposed split into Description and Requirements)\n (from July 18th F2F\, By GGF18 as original discussed.)\n\n</pre>\n\n\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC END:VEVENT END:VCALENDAR

1 0

OGSA documents are now published as GFDs
by Hiro Kishimoto 05 Sep '06

05 Sep '06

Hi all, Our three documents are now formally published and down-loadable. GFD.72: OGSA(tm) WSRF Basic Profile 1.0 GFD.80: The Open Grid Services Architecture, Version 1.5 GFD.81: Open Grid Services Architecture Glossary of Terms Version 1.5 http://www.ggf.org/gf/docs/?final Thanks Greg, Joel, and authors. -- Hiro Kishimoto

1 0

Teleconference minutes - 22 June 2006
by Andreas Savva 05 Sep '06

05 Sep '06

Attached. Main topics: - BSP public comment review - Information modeling discussion Gridforge: https://forge.gridforum.org/sf/go/doc13624?nav=1 -- Andreas Savva OGSA Teleconference - 22 June 2006 ================================== * Participants Michel Drescher (Fujitsu) Hiro Kishimoto (Fujitsu) Takuya Mori (NEC) Darren Pulsipher (EMC) Andreas Savva (Fujitsu) Dave Snelling (Fujitsu) Marvin Theimer (Microsoft) Jem Treadwell (HP) Pete Ziu (Northrop Grumman) Minutes: Andreas Savva * June 12 minutes approved with no changes * June 15 minutes approved with no changes * Action items review - Andreas will categorize OGSA 1.5 issues and send the list to Dave Snelling. - Done, waiting for response. - Review at next "OGSA 1.5" call. - Andreas and Hiro to talk offline about how to start sending ical invitations. - Done. - Andreas will send an email to the list explaining where the calendar is and what invitations will be sent out. - Jun will correct the CDL XML examples written by Hiro. - No update. - Hiro will probably move the review teleconference to another day. - EMS team (Steven, Andreas, Donal) to review data staging scenario (section 5 of https://forge.gridforum.org/sf/go/doc13591?nav=1 ) (postpone until June 22) - Andreas has read it. - Bring to people's attention again at the next EMS call. - Add sequence diagrams to the scenarios: (postpone until June 22) -- Andreas will do the "Install application" scenario (3.1) -- Mike will do the "Install application using ACS" scenario (3.3) -- Other volunteers welcome. (Andreas will ask Donal for the EPS scenario) - Andreas has started doing the sequence diagrams in RSM - Darren volunteered to help out - Review again at the next EMS call - Andreas will merge draft scenarios and sequence diagrams to the "EMS Architecture Scenarios" document (postpone until June 22) - Review again at the next EMS call. * Roadmap (postponed) * Authorization (postponed) * BSP Public Comments Reviewed public comments and Takuya's proposed replies 1. Add text explaining that the Secure Channel profile is not required by all ogsa services. The introduction is probably a good place for this. 2. [Basic-Security-Profile] usage. The term is defined in the document. Takuya to check whether such special terms are used consistently and that they stand out. Refer to the WSRF BP for a similar example. 3. Ciphersuites: Agreed that it important to list acceptable ciphers. - As a first step Takuya will list up available ones (from the WS-I BSP); select the ones that are in common use; and then select the ones that are considered sufficiently safe. - Review the list at the next BSP teleconf 4. Multiple keys in keyinfo field? - Takuya to talk to Von in order to understand the use case for multiple keys; and will propose a resolution at the next BSP teleconf. The next BSP review is set for the June 29 teleconference. * Information Model rendering discussion Started with the question of whether a rendering discussion is the right discussion to have. Concluded that talking only about the rendering overlooks more important issues: what the intermediate model should be and how it should be derived. One question is whether it is possible to define tags with semantics sufficiently pinned down to offer users the guarantee that a correct choice will be made when placing a job. For example, what does the system guarantee the user when a job requesting a box with "OS=Linux" (possibly of a specific version). There is enough variance to match with a box that advertises itself in this way but will not be able to run the job for other reasons (configuration etc). And vice versa other boxes that could potentially run the job may be missed. There was some discussion on various lists (BES, JSDL) already about the feasibility of defining equivalence classes but it is unlikely that anything like that can be done in the near term. The best that can be done is to define such terms while leaving some of the details unsaid (in the manner of JSDL). There is a tension between trying to describe something precisely while allowing the necessary looseness. Another issue is how to define the set of terms that people will actually want to use. There are many successful systems that are based mainly on user defined tags (or, equivalently, pre-configured queues that guarantee some kind of resource configuration) that are mainly site specific. It may not be possible to define these tags normatively however. So one key decision for the intermediate model is whether it should be driven by site-specific/defined information; or whether it should be driven from precise definitions like CIM. - There has been success for both sides (noting that Condor successes are often linked to also providing concrete specifications) - Informal definitions might not work across sites and this is a big issue for interoperability. - One community driven way forward would be to set up a framework to define combinations of capabilities; but this is likely to take a long time. GGF has published work with JSDL 1.0. The model is known to have deficiencies but captures a small set of common resource descriptions. The terms & concepts are a distillation of terms already in use at a number of sites running Globus, Unicore, (and to some extent Condor). - There is a compliance issue. For example, what does it really mean to say that a system is JSDL 1.0 compliant? What should the users expectation be and can the vendor deliver accordingly? - CIM has some experience in this area. It precisely enumerates known features (but there is no notion of (algorithmic) equivalence classes). Tentative consensus that both approaches are needed. It is important to be careful not to promise more than can be done with JSDL style resource descriptions. And that keeping these fuzzy to some extent does that. Also that user defined tags are needed. Since JSDL already allows the inclusion of user defined tags (xsd:any) the next question is whether there is a need to also define a framework for users to define their tags or to leave this completely open. Tentative consensus that defining a (or some) generic element with associated well defined matching semantics to allow users to add their own tags is a good idea. Marvin is working on a proposal for such an element and will post it to the relevant list(s). - Jay is also probably thinking along these lines so some offline discussion between Jay and Marvin might be good. - The proposal should be sent mainly to the OGSA Information Modeling team since they are the drivers of this work. And also to JSDL and BES; the other stakeholders in this process.

2 1

<wsa:metadata>
by Maguire_Tom＠emc.com 04 Sep '06

04 Sep '06

0 *H÷ 010 +0 *H÷ $+Content-Type: multipart/mixed; boundary="----=_NextPart_000_0173_01C6CACF.FCB8AC40" X-MS-TNEF-Correlator: 60B8C583F1CAC601 This is a multi-part message in MIME format. ------=_NextPart_000_0173_01C6CACF.FCB8AC40 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit www.iona.com/hyplan/vinoski/pdfs/IEEE-WS-Addressing_Metadata.pdf Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_0173_01C6CACF.FCB8AC40 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IgcWAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgDgFAAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAASAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAAEgAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAASAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAASAAgEJEAEAAADiEQAA3hEAAP4nAABM WkZ1MzScEAcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3RbCZgdABUAHY30CgwBQ9wPUFc8W22IXsRggF4IdtOcYoAcT AoMzOBsPHB8dJ1cX5B2SGKBWBJBkAHBh7QKDMhggFV4yHxIgYho08Qe4IENFGb8jMxrxI733GBAk zyXVeQixJn8jUROQuRVtMTYa8SkfA4JHCdH+ayqfIzMo4SwuDyAtTwNzPlQIcC7/IzMOEBKhZGkz AzYseDc3MZ8l1ChIZGViCXB3KTM/IzM2/zSvNbYkvzdGBxABoA6wOC93IyQ2MSwtODmRO28DgkL/ GgEOsD0/IzMfISwuK/E//7U3c1YIkHQi8AeBZT0v/yMjGAAfPiSYBxMmIUdlGv//KMhJhSpwR2Ur 8R9cLQhJhP8uo0dlKOFNXjGGSYQzAUdl/zSYTV02J0mEN7ZHZTmYU07/SQw8tkdlNjFNXT+3SYRB RP9HZR8vRBhUxUXJAoMxcEff/ySYIqVJ1jFwSn8oyGFXTJX/MXBNLy0IYVZPODFwT/8xaP9hVlIG MXBZjz+oYVZbmTFwv1xvRBhhVl58ApEI5jsJb/owcb9lUoFy6lKCc8902P9y1FKCc193L3btdm90 n3Lv/xQwbeB8un3RfY9+mXLUfsK/fS+A/4C9gD9+b4I0OQ8gP4WEhuF/A4bgAoIQUHlsVQeQaAng dAAAcQMhbA8SwQUQAUAD8GRjdGyXCrGJwDzQcAEBYXUaED0AYHMKsIogH9CLIm51Jm1GoYrgdG8N UWp18xBQBRBnaIsQBRAKAYlQZQoBaQGQcDADMAAgbNMQwB+hczEDMGEBMY8w/wvwKOAHQA21iTGM 8I6kjkF/j4MTJxPoCNAJwDnQkYNuDnCR2ZN0AzBzbmV4/yAgB7AFsADAAnMW4I7hjkF3DWA54EFw dhdQEEAgAG1OaRIAlmAJ8CBEisQgGlAKwGEJwIqQaCBGdwIhlZQQYDEAUBBgA2B3JwswjPABgHNX OdB0aN5CE5CM8AqwlmBsDeBt8H2bBHKbeA2QmuYBgJznYv2c53Ka4QJgC4AJkZ7kiGCMcGWa4QTw ZWxsidH3mrCaUZ9Bc5awACAaAZlh/zfgnAChpglQocQMsaHTilD5ocRkZ6KmpCCjpo6wocT+dgMw iR+KL4s/jE+NX45v/49yq0GQjaqRDbSRdBQiaBH/ktyuV6/UlKWZkJbclTQaMP8BoIiAlZeQUZZY q32szKfw9wjQI1CUoWKoMAmAAiCWEneIUR/wOdAzYkEYAJBQSN+f0aKQC4BPc5XTNrPftO//tfq3 crb/uAeY0KBgmfAJgP+4nzYQuc+OxwBRrI8a1AwB77yPlvoQQLixcwIgSbEQQNkFoG1wFzK3nkUA wAMQvlOIYjYQcOMW4AtgdAnwZxBgiGOmQHNkEFAHcGHeeLOwOZDJwRFRawmAAQEWMJWjcdB2AlEg e1XzuQAXIHduyIW30svizQPPJJA5gDYwzaM2Nj+xt9L6ODSAMSjgt9LPUEpgMXHfzaPOgA7wE5DQ NDcPEABQH7fTTRDPUNDE0dA2OTb3DhC30iegMA3wzsQ5gAHQIw8R06U3OTnS5Dg4v9Hw0tQBwNHw P6DVpTg7INumcdXCM2JQ1NU4z1A/sPvOJIbgMAHA2FZSkNQlDeD/1qEnoc+DAdDQoc9l2MHR8N/Q xA7wF8DSwNv2N9NQ1sD/z3TXYWrg2bUfEBfg1WDdhf450dAO8M91RCBC8Nv10eF2OVYB4JQ5PoDQ BeGROO9SkNTkLQATcDTfcOLFK+DvSmDitTsgbeAz3XXUwBgQ/+HQ5QbSsOSwz3TlcOSxz2X/2LEX sNv10rDOEOEm5kHfUf/NlBfw1NDe5WJQm3HSoOpF/99w41DRdNBwF+LOxNYB2ND75CUkkDc+gDSB zaMr4Nbg/+xmNIDP4c9kWWHR8ex13JH/01DQxe0QLRDw584Q6eHNlP/PIBOA1jVt4NTQ12DOxBfg 39TQ4bDS1NVxzyAy1OTR8P8tEN9g9XUX4dTAziQTgNLA/zmA8/W4JPfG11C4ENGE7bD/NIBoEflV 11H29dFA0KH6tv9EINLA0BQfED+w3JYfEN9y/9ZEGCDksIbS0vQXwPVgziT/9VDtEDSA/zfokdLV 5MHhAf/S5BggLRDQBTBA4dAX0dOV/+Pg7dY5gM8i1OXXUdHw1DX/4oE7INF0QvA7IBfA/bXroP/O kOJwBsbhEAwBt9K4UTsg/z6BCFTj4OGgCPbkoeulDxD/0qDXUM7ETRDkwfnlTRDhsP9t4Ap1DxAM UdDEVgDjUNjQ/9TkWXDm8c6gCETVYBOANiH/DxQKEdslEBE+gA0wCETSsP/V8Q411NCR4AFlLRDV YFYA/9AUMXDicN9wzsTj4NBw4bD/z2Tj4POgs7DOJNLABcHeJf/SwP7xESXOkGrg9VDQxPIx/y0A 5XASxOSw7xIYxc3w1LH/EsTlcPRgHxHVs5Hg2+DY0P8bBfOg1VHVpDYQzfDfpQsR/9QR1ZUnoBKR HfbRQO0Q1kX/41Ac0db1BpExcNWVLRCG0f/WRdbgK+Db5dbR0qBP4SHU/5RgP6DVldgx0pEhxd9w m4D/IzXU0NdQ7bDO1NjR9uDW9P/pQddg2PXksNNQ0UDQxP4x/5uA1YUOwTYgDiXVYBJxG6X/P7BW ACYX0sD74s7U1fCG0P/tEM7U1uDmQSk16tHsMNAU/9VQ1MD2kc7U33DUwBll86H/7EDk5eVx4+HP ZDBykfAxd//XUOEl5XDj4OPx2GTcUQlx/zPF0fA2INZE66DYMRTlhuD/FOAfIdhl4+DcUDF1BPES lv8f8fai2GQRofLx2cWR4O2w/2ZR2dQ/oO3g0hUjs2lA2bb/P6AOodZEkCEPgfnlrjLiYf89x8eA rkLZ1DTx3SE/dsNw/9CBP3Yywe3llGDj8TWR2cX/DdEi8dnG9sJB1s8hkeA89f9EohTg2nWUYOGw ZlBB1ZmQ/wQR3WbcUNvgzqZH4f4x+SX/mZC4EDLBReZSkBShR4YCwP8H4dv1BzOZkUrl4RH3pZmQ /+HRNNFFJdgAE9HPZWwAI6H/1NXa0eSxPOZIAQoR2zbPUP/24Ajl3FAK4UxH0SKbclI1/9gA5uFT xw+g6WXQobgQ33D/T6bt4NbAUgcRAc3wQdUNMP/k 9kPVQ2nb9kQ3xV9bhENNQ/9s24mHh0OE10IHN 8PVQ3Ab/BZE6dmrgbBDzoNs2IiHhF/9d4QZiXYY7IU+X1sDN8U+m/+JwMSFANRuR7EAU5TTh14H/ 2+Y08d9gLOU04d9xIyUnYf/lcUnm34HkEUHV0dANMPIR/2WmEFE5ptHQWtH0YGWm2WH/5JDdhW8Q 4RFhhtXwZWFmZv/V8OAxaNYxEjOl31Hh4M3x/98G4dDVUGwXGeHfp/RgQyL/z3VKYfbgPPX+0TXB OoXSEP/Y0O0QcCZnoUNX4/HYMXNn/86QlGDhNVuxF8HPZg3x5LD/2/VE0YKQ0sXPwgXBdQZtcf8a oXhX9UfgEdMwSEDPZukx/ysxesgOod/GWsFBxgjg3TD/9uBzZuGwBoFwJuEQ5JFxxv/SsN7RQDXH gBGh8OVmIdNg/0fhgUbvIVlWCBD3YeBnCuH/6gGC5hwxQ2YIENlhLmWzsP/+Ef4RhiblUVE2SoHh oeB2/zCRePfZgRMhhUbOENKgedb/ymBuYUxW9sH7MGzW9TA7Af9OkOFGFBHcph2x4RAPpU6R/wLR /mVOkOJhiGf8wY+B4TVfTRE8oNN1cXJdQTmVo3iYbWxuyVDNYX1cpzDduLF3UnFwEZQjaPUiquD9 x9BypDA8oHkBlaKcEJYG17FgAdGVk2KXM2epYMkQ/nKqkanwxpCnAK2AptG+wMenAKKRoNBuYmqo ILCQa5vwytBczGB4yPGpcHnFsJBcsUBwc2i6gJtQ38xgp/GikKhAmpBkyTCzAHmToGJkoyDMYKhB oEBmN7KAvFGd0W2boMBQZVz6aLKAeppypCCVoqrAn0HuaJ2DlfGfQXagGZ7RqhD/qsAgEcMwoKGh lT5yn+Ke0PeUcKCTo2Nqm3GuAK9wmnEHyCC4sDwgdmlld2v/qsAIgKVDxjCoYK7RlMGXsHRyZJUg ZcBQprWd0G/jqkCccGx5dMyAqsCesPOZ0ahHaHTH0JgwnHCaofec8KmQwFBqzVG8QMaQwmD/xACc 8JognPDNUaWhyoCoUPemQZmAswB3rBPNUbqAr0DzyoCZ8HJrnfGesMxgrdH4d3JwqrKxIJTwmxCW cL858KHQnbC+oKuBvrFmpWA+bLIxyeCrEJkgrrBwdXevwKgAxBBppICt1jnScven4fgWqKB3zVG3 orxQyaBvzGCWcL7AqcFvsHCZAWYoZXQwy3J3lnBmZlxtdLBwwmDFoCDa8DP+ZpQAx/Cn0MfQpkCs UJzwfHVwmIOkcLagxsCY4WTvwkOY0sqAqJF4mICaQapQ/8WgqLCY0rmSr3IdobiUyzB/qcDCYLew xsCZ08wQy4FwM50AmOBsdpXgvRF1Y/+eUL0SqnDA8L2ipaHJIWrxM70RnoBuZ7zRvSB0ePmqcCAu yJS9JjwgvcKcMf++L78/wE+9gDmwvSCwsJ8w98Ifwy/EP2w9wL0grIDB3/vGr8e1KcCcQdDFf8pv x5X4YiAowKHLn71TSFDJP//OD88f0C+9cUeA0YK+D9Lv/9P/zA088NGP1x/YL9k/vXH/DjDWH9u/ 3M/d1ZQRp6CUEM+a4KHQuPO4UVxxk+C5gf9AMeRRmTG6sePCrqCU8LvV/7GxpHDlEJ6A5hK30N9w u/D/tNKaIKqQqvCZkKGwqZDkcd5umIHoYrUglPAwuPCbwEWsgGi1UGNzMbjwYfZmmIDqIHM9saxw x1E+8v+48+mU6THqc+rUOaHq0rVgzezDY69y7HNucOzJ7mT/vNHpbKQg6mLpMet7pCDw0vftsOox odBz99rpkJeQ99lEIHf0oC5pb68gLrJjt1AvaKUA6tEvpVAbnWGlkC/lkOpwL0lFwfbALVdTLUGa YLpg5nNDoMdgX021cJ6QmvD/9RD2YcCh78/w3/Hv8v/0CPwNCuLC/abitON/5I/ll//nJehe+L4a 4fnftUEa4fs3X+rV7GTtUj2xmrBwstFmQ/u9vNNia21r37MgU/fQ40BsQbThU6Gwff5Ut1D4r/mz TpD6LwwS+3HvKSEGTwdf/S5fES8SPxMK/wrf6fEMfQYPDt8P7/5iFC+/C/8NDxafF6/0JgqhIAng 7Zggabpg/bVTm0D04LagWlSY4GiqIa9gad+wLFQgT7YQaZ2wILUAIPhDVE8ZrxUvFj8dnxhfPxlv Gn8bjxyfJg8IK0VNvkMoXylvKn8rjz2xc7fg95RQLL/0NTIubyPfJO8sT+8nDygVsHO1omawoPvB mQAfNM813zbvN/8IK0hZUABFUkxJTksgIrOXgLZhbzqXgB/jX5sQoG1AZW1j9SIiNL//PI89nz6v +9/z02FgfaCJIG+80/gisHO48GKh0JMAIAAA0Mnqefm6zgARjIIAqgBLqagLAgBLcANLceBKfQI2 S3FtAGEAaQCAbAB0AG8AOk0TCGcAdU1RcgBlADZfTZNNIEBOsU0gYwD+Lk+xTyJLcMCQOkKwoJjA /5wwO38vfzCKngExT0YvCBz/Qb8KscCSQy9EP0VPVZ85Lz8oT1JPMH9bD1wf9AgrMSIoovA1KSBr wDkt/36Ac0D9vV5PX19gbGFfYm+59AgiVKcgIlCo8SCvoCe2ELpRr8EgYrVwd2W9m0AgyACd8JkA pIEglnDMYXYiQCGgIHRr4bCwAa7AaC4iIC0gUrnmUiBXrHCZUC4gbZRQ/nP08GX/Wb9oz2nfXO/+ X///bJqwAE8BXwJv+R9x/wW//3PPdN9173b/AD/lz+bf5++/eq/p9Otc+4mUgO2QNo3wn0jkCTKa QQnMgMZ9AIzQAAAeAHAAAQAAAA8AAAA8d3NhOm1ldGFkYXRhPgAAAgFxAAEAAAAWAAAAAcbK8YOf AEY4N6qlT1utCsux8EVm7gAAAwAmAAAAAAALAAIAAQAEgAsAAQ4AAASAAgEKDgEAAAAuAAAAAAAA AEcAeBfHkKxKr+8LploFF7ABAPwVTdjvdXlKhysGywQ4l68AAAADrAUAAAAAAwAJWQMAAAADAN4/ n04AAAIBfwABAAAAEQAAADYwQjhDNTgzRjFDQUM2MDEAAAAAAwAGEKnHlkIDAAcQzQAAAAMAEBAA AAAAAwAREAAAAAAeAAgQAQAAAGUAAABXV1dJT05BQ09NL0hZUExBTi9WSU5PU0tJL1BERlMvSUVF RS1XUy1BRERSRVNTSU5HTUVUQURBVEFQREZUT01UT01NQUdVSVJFU0VOSU9SVEVDSE5PTE9HSVNU LE9GRklDRU9GAAAAANKU ------=_NextPart_000_0173_01C6CACF.FCB8AC40-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 060828223007Z0# *H÷ 1 °5¡HH~eþ¹À¹5³hn0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ Xë Z<)`º"Ò¥TYË:Ï(ah<Â®Ð<x*íöU%á¹MV}šÅŠÒöÕGýŸ%§ç)hã`áú'<³4Büó:pÅÌøÃ72¢»¹\?'rpbí`·â«¡&à®Q{/0wï5

2 2

[wg-all] Mailing List Changes
by Andre Merzky 03 Sep '06

03 Sep '06

Sorry for duplicates ------------------------------------------------------------ As of yesterday, all GGF/OGF mailing lists are migrated to the ogf domain. They are now managed by mailman, the web interface is available at http://www.ogf.org/mailman/listinfo With that migration, all list can be now reached via <list>@ogf.org The old @ggf.org addresses will be available for some time, but are bound to disappear eventually - please start using the ogf addresses! A number of lists have changed their names: ggf-it --> ogf-it ggf-office --> ogf-office ggf-proc-wg --> ogf-proc-wg ggf-sponsors --> ogf-sponsors ggf-tutorials --> ogf-tutorials ggf-compute --> ogf-compute ggflistowners --> ogflistowners ggfstudentmembers --> ogfstudentmembers Postings to the old list names get forwarded to the new ones. With the migration we have also been able to fix the archives - you may have noticed that list archiving stopped sometime in mid June. Well, now its working again, and all mails from June to now have been added to the archive. The list archives can be found at: http://www.ogf.org/archives/<list> If you are an list administrator, and would like to receive the list admin password, please contact postmaster(a)ogf.org. In general, however, we tried to map the old majordomo settings to the mailman settings, in terms of privacy etc, so no or little changes should be required from your side. The spam avoidance policy has been changed to some extent, and is somewhat stricter than before. Please let us know if you experience any trouble with that. On all questions in respect to mailing lists, or mails in general, please contact postmaster(a)ogf.org. Best regards, Andre. -- "So much time, so little to do..." -- Garfield -- wg-all mailing list wg-all(a)ogf.org http://www.ogf.org/mailman/listinfo/wg-all

1 0

[wg-all] Mailing List Changes
by Andre Merzky 03 Sep '06

03 Sep '06

As of yesterday, all GGF/OGF mailing lists are migrated to the ogf domain. They are now managed by mailman, the web interface is available at http://www.ogf.org/mailman/listinfo With that migration, all list can be now reached via <list>@ogf.org The old @ggf.org addresses will be available for some time, but are bound to disappear eventually - please start using the ogf addresses! A number of lists have changed their names: ggf-it --> ogf-it ggf-office --> ogf-office ggf-proc-wg --> ogf-proc-wg ggf-sponsors --> ogf-sponsors ggf-tutorials --> ogf-tutorials ggf-compute --> ogf-compute ggflistowners --> ogflistowners ggfstudentmembers --> ogfstudentmembers Postings to the old list names get forwarded to the new ones. With the migration we have also been able to fix the archives - you may have noticed that list archiving stopped sometime in mid June. Well, now its working again, and all mails from June to now have been added to the archive. The list archives can be found at: http://www.ogf.org/archives/<list> If you are an list administrator, and would like to receive the list admin password, please contact postmaster(a)ogf.org. In general, however, we tried to map the old majordomo settings to the mailman settings, in terms of privacy etc, so no or little changes should be required from your side. The spam avoidance policy has been changed to some extent, and is somewhat stricter than before. Please let us know if you experience any trouble with that. On all questions in respect to mailing lists, or mails in general, please contact postmaster(a)ogf.org. Best regards, Andre. -- "So much time, so little to do..." -- Garfield -- wg-all mailing list wg-all(a)ogf.org http://www.ogf.org/mailman/listinfo/wg-all

1 0

Re: [OGSA-WG] No call on Sept. 4th.
by ogsa-wg-bounces＠ogf.org 02 Sep '06

02 Sep '06

I am currently out of office to attend DEXA/DaWaK 2006 in Krakow, Poland until September 10. During this time, I can rarely access my email thus your message may be answered with delay. Best regards, Nguyen Manh Tho

1 0

No call on Sept. 4th.
by Hiro Kishimoto 02 Sep '06

02 Sep '06

Hi all, Since Sept. 4th is US holiday (Labor Day), we have no call on upcoming Monday. Next call is Sept. 7th for Roadmap, Basic Security Profile, and WS-BaseFault discussions. Have a great Labor Day weekend, -- Hiro Kishimoto

1 0

Phne conference minutes 31 August 2006
by Michel Drescher 31 Aug '06

31 Aug '06

... are posted to Gridforge at http://forge.gridforum.org/sf/go/doc13776?nav=1 Cheers, Michel -- Michel <dot> Drescher <at> uk <dot> fujitsu <dot> com Fujitsu Laboratories of Europe +44 20 8606 4834

1 0

EMS Scenarios: suggested changes w.r.t. v10
by Donal K. Fellows 31 Aug '06

31 Aug '06

Hi Andreas! I've been going through the EMS Scenarios document and I've got some changes I'd like to suggest in the section on the deployment scenarios: * In 4.1, the updates to the Info Service should come not from the Job Manager but rather the BES and the Deployment Service (or rather the BLAST System). After all, it is those services that can be expected to know whether BLAST is present and in use. Otherwise, the IS would appear to be only ever accessed from the JM and would, as such, be an integral part of it instead of its own independent service. In particular, the destruction of the BLAST System should force the update of the IS so that entities other than the JM can initiate the operation (e.g., the system administrator) without forcing the IS to be inconsistent. (Inconsistency is likely enough anyway!) * In 4.2, the JSDL ApplicationVersion should be used as well as the AppName as part of the input data for the LookupArchives operation. * In 4.2, the scenario diagram should show the interaction between the ACS and DS, even if no specific operation names are assigned. This would make the scenario clearer. It would be nice if there was a way remove the requirement for JM to rewrite the JSDL document after deployment but before submission. Perhaps by delegating this to the BES itself? Like this, it would be much easier for me to write the Discovery-and-Deployment scenario (which I am working on, honest!) Donal.

1 0

Joint Data/EMS Scenario 1
by Dave Berry 31 Aug '06

31 Aug '06

As promised, we discussed a joint data/EMS scenario at the OGSA-D F2F this week. The attached word file is what we came up with as a basis for discussion. More complex scenarios should be possible but we are starting with the simple case. Best wishes, Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre, 15 South College Street Edinburgh, EH8 9AA Tel: +44 131 651 4039

2 1

Roadmap call canceled today
by Christopher Jordan 30 Aug '06

30 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The roadmap call previously scheduled for today at 3PM PDT will be canceled, due to scheduling conflicts. My apologies for not sending out a note earlier. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Why is there so much silence here?" - Sholay -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE9cpEPCVtcXn6kg8RAtMcAKDmyWrbZX7xC3/5wO/yD2LLgx6EDwCffTo2 XBsfcbaeAg63kCj7t1HPCMs= =xyAk -----END PGP SIGNATURE-----

1 0

Minutes from the August 28 telecon
by Treadwell, Jem 30 Aug '06

30 Aug '06

Hi, the minutes from Monday's call are attached, and posted at http://tinyurl.com/rmt8l. Three new action items have been added to the action list on the wiki, for Hiro, Takuya & Frank. - Jem ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

1 0

Re: [ogsa-wg] OGSA F2F meeting agenda on Sept. 14 & 15
by Hiro Kishimoto 30 Aug '06

30 Aug '06

Hi Donal, >> Does Friday 8-9am work for you? > That's fine. It's just Friday afternoon that is tricky. Given we got 2-hour slot on Thursday afternoon, do you want to move RSS session from Friday morning to Thursday afternoon (4-5pm)? >> We will discuss F2F schedule at the call Today. > > Sorry I missed it but I was dealing with family matters. OGSA-WG will have another F2F schedule update at this Thursday call. Thanks, ---- Hiro Kishimoto

2 1

Group Dinner in Washigton D.C.
by Hiro Kishimoto 30 Aug '06

30 Aug '06

Hi all, Mike Behrens is extremely generous to invite us to BBQ party at his house (many thanks Mike!). His house is about 35 minutes away from downtown via metro or 25 minutes to drive. In addition to Mike's generous offer, Hiro and Jay are planing to have Maryland blue crab dinner at famous Peter Pan Inn on the other day. (http://pages.frederickcounty.com/dining/cracked.htm) For landfood lovers: They also have Beef & Poultry menues. Please let me know your preference by answering the Zoomerang Survey at your earliest convenience. Your comments and questions are also very welcome. http://www.zoomerang.com/survey.zgi?p=WEB225M5LKZWT7 Thanks, -- Hiro Kishimoto

1 0

Proposed agenda for Aug. 31st call
by Hiro Kishimoto 30 Aug '06

30 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 31st Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0831 See more explanation: https://forge.gridforum.org/sf/go/wiki1584?nav=1 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (if available) Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA F2F meeting agenda update (20 min) F2F agenda on Sep. 14 (Thur) and 15 (Fri) https://forge.gridforum.org/sf/go/wiki1555?nav=1 3) EMS scenarios (Andreas and Steven, 30 min) EMS architecture scenario document review - https://forge.gridforum.org/sf/go/doc12749?nav=1 4) EMS & Data joint scenario (30 min) > Agreed that a good first candidate scenario is simple job execution > with data staging. In particular the combination of JSDL, BES, Data > transfer service (DMI based?). > > AI-0817b: Stephen Davey will do a cut down parameter sweep scenario > focusing on the JSDL+BES+Data Transfer/Staging service > > The aim is to discuss it at least within Data at the Data F2F (Aug > 28-30 @Edinburgh) and with EMS at GGF18. Since many Data members > will be leaving on Thursday it would be good to arrange some time > early on Thursday (OGSA F2F). 5) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

1 0

RE: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg
by Maguire_Tom＠emc.com 30 Aug '06

30 Aug '06

Apologies for the cross post but some of this discussion is relevant to the OGSA-WG I would agree that WS-BaseFaults are not required for BES. In WS-ResourceProperties the use of BaseFaults is optional (SHOULD). The OGSA Basic Profile for WSRF has mandatory (MUST) use of BaseFaults for WS-Resources. 7.1.1 BaseFault Structure R0711 A MESSAGE for a fault from a WS-Resource MUST conform to the structure specified in Web Services Base Faults Section 2, "Base Fault Type." As I re-read this section it is not nearly clear enough about the scope of 'WS-Resource'ness. I could interpret this requirement several ways: * ALL faults from a WS-Resource MUST be extensions of BaseFaults * ALL faults from a WS-Resource based portType MUST be extensions of BaseFaults * ALL faults from a WS-Resource base portType that match the semantics of existing BaseFaults MUST use the BaseFault extension type that is defined for that portType (basically what this does is turn the SHOULD in WSRF specs for faults into MUSTs) Clearly, point 1 is a non-starter; no implementation will be able to guarantee that all faults are extension of BaseFaults. Point 2 is also extremely difficult as there are significant numbers of interceptors between the consumer and the provider implementation all of which are likely to not fault with WS-BaseFaults. Which leads us to point 3, I think this is the only reasonable interpretation of the requirement; that faults that are defined in WSRF specs MUST be used (as opposed to the SHOULD requirement in WSRF). Perhaps we should clarify this requirement in the Basic Profile. w.r.t the subject at hand I think that any consumer will need to deal both SOAP faults and BaseFaults and as such I don't see much of a need to fuss about the fault definitions in BES. I do however, agree with Ian that there is value in having a common base type for faults. Tom _______________________________________________ Tom Maguire +1(845) 729-4806 _____ From: owner-ogsa-bes-wg(a)ggf.org [mailto:owner-ogsa-bes-wg@ggf.org] On Behalf Of Ian Foster Sent: Friday, August 18, 2006 11:27 AM To: Marvin Theimer; ogsa-bes-wg(a)ggf.org Subject: RE: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg Marvin: David's proposal, which is realized in the current draft, is that we define BES to just have "GetStatus" and "GetProperties" operations (as well as CreateActivity etc.). We can then compose WS-Transfer operations or WSRF operations, if desired, in a particular BES implementation. This seems to me to be a really nice solution to the "problem" that we thought we had, in that it avoids the need for multiple renderings. The one tricky issue is the rendering of faults. In the current BES document, we use WS-BaseFaults. You report that the Microsoft WS team has problems with that. I don't think we should let this be a show stopper, as I don't think it is essential that we use WS-BaseFaults in BES. At the same time, WS-BaseFaults was introduced for a reason. Thus I'd like to propose that we proceed as follows: a) We set up a phone call with the Microsoft WS team and the WS-BaseFaults guys to talk this over, in case it turns out that we can in fact all agree that WS-BaseFaults is useful. b) In the (likely) case that the Microsoft WS team still doesn't want to see WS-BaseFaults included, we check with the BES team that it is ok to use a different fault model for the BES core vs. the specs that might be composed with the BES core, such as WSRF. Thoughts? Ian. At 05:17 PM 8/16/2006 -0700, Marvin Theimer wrote: Hi; Another comment/question on Dave Snellings proposal: I dont really understand how it avoids distinct renderings since it is still the case that we have at least 3 different WSDLs, one per rendering option: * WSRF version that employs WS-ResourceProperties, etc. * WS-Transfer version that employs WS-Transfer, etc. * Resource model-free version that employs an explicit QueryStatus operation (and potentially additional QueryFoo operations). It is certainly the case that there is a coreset of operations that is common to all 3 interface choices and we should certainly write the spec that way. But dont we still end up with 3 different rendering versions? Marvin. _____ From: Ian Foster [mailto:foster@mcs.anl.gov] Sent: Friday, August 04, 2006 2:20 PM To: Marvin Theimer; ogsa-bes-wg(a)ggf.org Subject: Re: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg Marvin: I've claimed the pen on the document, but have been finding it hard to find time to make a lot of progress. I will try to do some work on it tomorrow morning. That said, I want to mention an important development that Dave Snelling may or may not have mentioned on calls. Dave argues that we can avoid the need for distinct renderings by defining our interfaces carefully. The basic idea, as I understand it, is that: a) the "core interface" has the basic operations for creating jobs, modifying their status, etc., and an operation for grabbing all of the factory state; b) then, if desired, a WSRF service (for example) can also implement the WS-ResourceProperties, WS-ResourceLifetime, WS-BaseNotification, operations; c) while a WS-Resource service would implement the WS-Resource equivalents of those. So we exploit the power of interface composition to avoid the need for separate bindings. The only problematic issue, as I understand it, is that of faults. The question is how we render faults. The WSRF binding must (by the spec) use WS-BaseFaults. If we can all agree to use that, then we are ok. If not, then we still have problems. Ian. At 01:29 PM 8/4/2006 -0700, Marvin Theimer wrote: x-ms-exchange-organization-recipient-p2-type: To Content-Type: text/plain; charset="us-ascii" Hi; The HPC Profile (HPCP) work depends critically on BES. The recent face-to-face meeting at Argonne made substantial progress in terms of reshaping the proposed BES specification in a way that would make it suitable for supporting the HPCP on top of it. Are there plans to generate a new revision of the BES specification draft in the near future? As soon as the revised version comes into existence we'll be able to seriously start doing the actual HPCP work (which will take place on the hpcp-ogsa-wg mailing list and in weekly telecom calls that will be starting shortly). Since the HPCP WG is effectively gated on this revised spec, having a draft of a revised spec sometime in the next week or so would be really helpful. I would be willing to help rewrite the BES spec if that would be useful to the BES WG. Marvin. _______________________________________________________________ Ian Foster, Director, Computation Institute Argonne National Laboratory & University of Chicago Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619. Web: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> . Globus Alliance: www.globus.org <http://www.globus.org/> . _______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com <http://ianfoster.typepad.com/> Computation Institute: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> & www.ci.anl.gov <http://www.ci.anl.gov/> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org <http://www.globus.org/>

2 2

OGSA F2F meeting agenda on Sept. 14 & 15
by Hiro Kishimoto 29 Aug '06

29 Aug '06

Hi all, GGF18 and back-to-back OGSA meeting are just around the corner and we need to finalize meeting agenda very soon. The following is current proposal and if you have any request or comment, please let me know ASAP. We will review and finalize meeting agenda at the upcoming Thursday call. Also, if you plan to come (or dial-in) but your name is not on the attendee list, please let me know. You should be on the list to enter facility. https://forge.gridforum.org/sf/go/wiki1555?nav=1 Thursday afternoon (2:30-6pm) * A joint EMS/Data session (Dave and Andreas, 1-2hr depending on people's availability) o Since many Data members will be leaving on Thursday it would be good to arrange some time early on Thursday. * Info Model (Ellen and Fred, 2H or half day) o agenda is overflow from work that will not get done during the 2 GGF sessions o first draft of base model objects for HPC/BES/JSDL o probably XQuery examples. Friday morning (8am-noon) * OGSA general session (Tom and Hiro, 2H) o OGSA direction and priority o document status review o winter F2F schedule o telecon schedule * JSDL session (Steve McGough, 1-2 hr) o Bashing out ideas for JSDL 2.0 Friday afternoon (1-4pm) * OGSA-DMI Update (Michel Drescher, 1hr) o This session is to update the OGSA-WG and all interested parties on the status of the OGSA-DMI work. It is expected that a first draft of the functional interface is drafted at GGF18. * OGSA-RSS (Donal Fellows, ??) o discuss the EPS and its relation to the rest of the EMS arch -- Hiro Kishimoto

3 8

Proposed agenda for Aug. 28th call
by Hiro Kishimoto 28 Aug '06

28 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 28th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0828 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 21st) - https://forge.gridforum.org/sf/go/doc13750?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA F2F meeting agenda update (20 min) F2F agenda on Sep. 14 (Thur) and 15 (Fri) https://forge.gridforum.org/sf/go/wiki1555?nav=1 3) OGSA authorization call-out proposal review (Frank, 20 min) > - Frank is now consulting with people in GGF (David Chadwick, Von > Welch) on whether his approach can be defined within the AuthZ > group. If there is no agreement then he will accept the XACML > group's decision. David's "Functional Components of Grid Service Provider Authorisation Service Middleware" document - https://forge.gridforum.org/sf/go/doc13724?nav=1 4) Basic Security Profile PC review (Takuya, 30 min) Review Takuya's proposal. 5) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Aug. 31 (Thu): EMS scenarios (Andreas and Steven) EMS & Data joint scenario (Allen, Dave Barry, Steven, and Andreas) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Aug. 21 call AI-0821a: Hiro to talk to Jun and CDDLM group about EGA & CDDLM comparison proposal. AI-0821b: Hiro to talk to Jem about EGA & OGSA glossary comparison > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

2 1

draft minutes for OGSA-Authz call-out proposal review (Aug 11)
by Hiro Kishimoto 28 Aug '06

28 Aug '06

OGSA Teleconference - 11 August 2006 ==================================== * This is first half of Aug. 11 call * * Participants Andrew Grimshaw (UVa) Jay Unger (IBM) Frank Seibenlist (ANL) Steven Newhouse (OMII) Takuya Mori (NEC) Marvin Theimer (Microsoft) Jem Treadwell (HP) Duane Merrill (UVa) David Chadwick (U of Kent) Andreas Savva (Fujitsu) Donal Fellows (Uom) Minutes: Takuya Mori * OGSA authorization call-out proposal review (Frank, 20 min) Reference: "Functional Components of Grid Service Provider Authorisation Service Middleware" https://forge.gridforum.org/sf/go/doc13724?nav=1 David presented a draft document, "Functional Components of Grid Service Provider Authorisation Service Middleware", which was sent to the OGSA-AuthZ and OGSA-WG list on Aug 9. (The document was based on discussions between Von, Frank and David.) David introduced functional components, Policy Enforcement Point (PEP), Credential Validation Service (CVS) and PDP (Policy Decision Point) and showed four types of interactions between the components (See Fig.1 to Fig.4 in the document). David proposed to define two protocols, one for CVS and the other for PDP. The followings are the points of his proposal. - CVS is used to validate credentials and to issue valid attributes of Access Requestors. - CVS is passed authenticated name and credentials. - CVS determines if the credential is trust worthy and returns valid attributes. - An administrator manages two types of rules, auhtz decision rules and rules to resolve trust relationships - CVS makes use of XACML policy query interface, but it is not necessarily be an XACML policy engine behind the interface. - CVS is needed to separate authentication and authorization. Various questions and answers arouse during the presentation and some major points made clear in the discussion were: - The two protocols are intended to support all the configuration shown in the figures - Revisions of the two "OGSI" profiles are also in the scope of current activities of the OGSA-AuthZ-WG. - Defining attributes values (terms and semantics) is not in the scope of current activities of the OGSA-AuthZ-WG, but in its future scope. The discussion were suspended until Aug 28 due to the running out of the meeting time. The followings are some interactions during the discussion. * The scope of the work (1) Q: Does the two protocols cover all the configurations shown in the figures? The protocols shown in the figures look different. A: Yes, the both protocols can cover all the configuration. The current OGSA-Authz profiles can handle this kind of interactions. Q: The current profiles are not "OGSA" profiles. These are "OGSI" profiles. A: The difference between "OGSI" and "OGSA" is small for OGSA-Authz profiles. Revisions of these two profiles are also on the table. * How to define service I/F of applications Q: As an application desginer, do I need to choose appropriate one? * long interactions were taken place which Takuya couldn't perfectly follow, but if Takuya understood well, the answer from the authz wg is: * A: Interafces of applications will not be affected. It is the middleware which speaks the protocols. Authorization is taken place behind the infrastructure. * The scope of the work (2) Q: The architecture for authorization has not clearly been defined. What the OGSA-AuthZ-WG are going to define? Do we need to define all the comopnents? Various terms and semantics also needs to be defined for attributes and policies. These also should be standardized. A: The OGSA-AuthZ-WG did the similar things in the past, the credential formats and terms over the SAML Attribute Assertion and the X.509 Attribute Certs. Q: It covers a different interop level - only attribute name or type level - not the values. A: The OGSA-AuthZ-WG focuses only on the interface level. David doesn't have a need to define values. (at this moment?) The WG needs to define them later in the future. -- Hiro Kishimoto

1 0

Telecon minutes for Thursday Aug 24
by Treadwell, Jem 24 Aug '06

24 Aug '06

Hi, we didn't have the necessary people on the call for today's scheduled CDDLM discussion, so we didn't have a real meeting. But I've uploaded the minutes, and as they're extremely short I've embedded them below. - Jem OGSA Teleconference - 24 August 2006 ==================================== * Participants Hiro Kishimoto (Fujitsu) Jay Unger (IBM) Mark Morgan (UVa) Andrew Grimshaw (UVa) Jem Treadwell (HP) Michel Drescher (Fujitsu) Minutes: Jem Treadwell * As there were insufficient people for the scheduled business, no formal meeting was held. Hiro will reschedule the planned agenda items. ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

1 0

FW: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg
by Maguire_Tom＠emc.com 22 Aug '06

22 Aug '06

For some reason this did not make it to the OGSA-WG mailing list. In particular I think this points out the need for a bit more clarity in the Basic Profile. Tom _______________________________________________ Tom Maguire +1(845) 729-4806 _____ From: Maguire, Tom Sent: Monday, August 21, 2006 3:44 PM To: Maguire_Tom(a)emc.com; foster(a)mcs.anl.gov; theimer(a)microsoft.com; ogsa-bes-wg(a)ggf.org; ogsa-wg(a)ggf.org Subject: RE: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg As an aside I am not quite sure how BaseFaults breaks tooling. The BaseFault element is carried as an extensibility item in the s11:detail or s12:Detail elements. Isn't that what these items were designed for?? Tom _______________________________________________ Tom Maguire +1(845) 729-4806 _____ From: owner-ogsa-bes-wg(a)ggf.org [mailto:owner-ogsa-bes-wg@ggf.org] On Behalf Of Maguire_Tom(a)emc.com Sent: Monday, August 21, 2006 3:30 PM To: foster(a)mcs.anl.gov; theimer(a)microsoft.com; ogsa-bes-wg(a)ggf.org; ogsa-wg(a)ggf.org Subject: RE: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg Apologies for the cross post but some of this discussion is relevant to the OGSA-WG I would agree that WS-BaseFaults are not required for BES. In WS-ResourceProperties the use of BaseFaults is optional (SHOULD). The OGSA Basic Profile for WSRF has mandatory (MUST) use of BaseFaults for WS-Resources. 7.1.1 BaseFault Structure R0711 A MESSAGE for a fault from a WS-Resource MUST conform to the structure specified in Web Services Base Faults Section 2, "Base Fault Type." As I re-read this section it is not nearly clear enough about the scope of 'WS-Resource'ness. I could interpret this requirement several ways: * ALL faults from a WS-Resource MUST be extensions of BaseFaults * ALL faults from a WS-Resource based portType MUST be extensions of BaseFaults * ALL faults from a WS-Resource base portType that match the semantics of existing BaseFaults MUST use the BaseFault extension type that is defined for that portType (basically what this does is turn the SHOULD in WSRF specs for faults into MUSTs) Clearly, point 1 is a non-starter; no implementation will be able to guarantee that all faults are extension of BaseFaults. Point 2 is also extremely difficult as there are significant numbers of interceptors between the consumer and the provider implementation all of which are likely to not fault with WS-BaseFaults. Which leads us to point 3, I think this is the only reasonable interpretation of the requirement; that faults that are defined in WSRF specs MUST be used (as opposed to the SHOULD requirement in WSRF). Perhaps we should clarify this requirement in the Basic Profile. w.r.t the subject at hand I think that any consumer will need to deal both SOAP faults and BaseFaults and as such I don't see much of a need to fuss about the fault definitions in BES. I do however, agree with Ian that there is value in having a common base type for faults. Tom _______________________________________________ Tom Maguire +1(845) 729-4806 _____ From: owner-ogsa-bes-wg(a)ggf.org [mailto:owner-ogsa-bes-wg@ggf.org] On Behalf Of Ian Foster Sent: Friday, August 18, 2006 11:27 AM To: Marvin Theimer; ogsa-bes-wg(a)ggf.org Subject: RE: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg Marvin: David's proposal, which is realized in the current draft, is that we define BES to just have "GetStatus" and "GetProperties" operations (as well as CreateActivity etc.). We can then compose WS-Transfer operations or WSRF operations, if desired, in a particular BES implementation. This seems to me to be a really nice solution to the "problem" that we thought we had, in that it avoids the need for multiple renderings. The one tricky issue is the rendering of faults. In the current BES document, we use WS-BaseFaults. You report that the Microsoft WS team has problems with that. I don't think we should let this be a show stopper, as I don't think it is essential that we use WS-BaseFaults in BES. At the same time, WS-BaseFaults was introduced for a reason. Thus I'd like to propose that we proceed as follows: a) We set up a phone call with the Microsoft WS team and the WS-BaseFaults guys to talk this over, in case it turns out that we can in fact all agree that WS-BaseFaults is useful. b) In the (likely) case that the Microsoft WS team still doesn't want to see WS-BaseFaults included, we check with the BES team that it is ok to use a different fault model for the BES core vs. the specs that might be composed with the BES core, such as WSRF. Thoughts? Ian. At 05:17 PM 8/16/2006 -0700, Marvin Theimer wrote: Hi; Another comment/question on Dave Snellings proposal: I dont really understand how it avoids distinct renderings since it is still the case that we have at least 3 different WSDLs, one per rendering option: * WSRF version that employs WS-ResourceProperties, etc. * WS-Transfer version that employs WS-Transfer, etc. * Resource model-free version that employs an explicit QueryStatus operation (and potentially additional QueryFoo operations). It is certainly the case that there is a coreset of operations that is common to all 3 interface choices and we should certainly write the spec that way. But dont we still end up with 3 different rendering versions? Marvin. _____ From: Ian Foster [mailto:foster@mcs.anl.gov] Sent: Friday, August 04, 2006 2:20 PM To: Marvin Theimer; ogsa-bes-wg(a)ggf.org Subject: Re: [ogsa-bes-wg] Create a revised BES spec draft that reflects the decisions of the July F2F mtg Marvin: I've claimed the pen on the document, but have been finding it hard to find time to make a lot of progress. I will try to do some work on it tomorrow morning. That said, I want to mention an important development that Dave Snelling may or may not have mentioned on calls. Dave argues that we can avoid the need for distinct renderings by defining our interfaces carefully. The basic idea, as I understand it, is that: a) the "core interface" has the basic operations for creating jobs, modifying their status, etc., and an operation for grabbing all of the factory state; b) then, if desired, a WSRF service (for example) can also implement the WS-ResourceProperties, WS-ResourceLifetime, WS-BaseNotification, operations; c) while a WS-Resource service would implement the WS-Resource equivalents of those. So we exploit the power of interface composition to avoid the need for separate bindings. The only problematic issue, as I understand it, is that of faults. The question is how we render faults. The WSRF binding must (by the spec) use WS-BaseFaults. If we can all agree to use that, then we are ok. If not, then we still have problems. Ian. At 01:29 PM 8/4/2006 -0700, Marvin Theimer wrote: x-ms-exchange-organization-recipient-p2-type: To Content-Type: text/plain; charset="us-ascii" Hi; The HPC Profile (HPCP) work depends critically on BES. The recent face-to-face meeting at Argonne made substantial progress in terms of reshaping the proposed BES specification in a way that would make it suitable for supporting the HPCP on top of it. Are there plans to generate a new revision of the BES specification draft in the near future? As soon as the revised version comes into existence we'll be able to seriously start doing the actual HPCP work (which will take place on the hpcp-ogsa-wg mailing list and in weekly telecom calls that will be starting shortly). Since the HPCP WG is effectively gated on this revised spec, having a draft of a revised spec sometime in the next week or so would be really helpful. I would be willing to help rewrite the BES spec if that would be useful to the BES WG. Marvin. _______________________________________________________________ Ian Foster, Director, Computation Institute Argonne National Laboratory & University of Chicago Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619. Web: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> . Globus Alliance: www.globus.org <http://www.globus.org/> . _______________________________________________________________ Ian Foster -- Weblog: http://ianfoster.typepad.com <http://ianfoster.typepad.com/> Computation Institute: www.ci.uchicago.edu <http://www.ci.uchicago.edu/> & www.ci.anl.gov <http://www.ci.anl.gov/> Argonne: MCS/221, 9700 S. Cass Ave, Argonne, IL 60439 Chicago: Rm 405, 5640 S. Ellis Ave, Chicago, IL 60637 Tel: +1 630 252 4619 --- Globus Alliance: www.globus.org <http://www.globus.org/>

1 0

Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 22 Aug '06

22 Aug '06

Hi Hiro, I agree with you that we need to make sure this is not a lot of work. Actually I was thinking that this would be recorded in the meeting minutes and them cut an pasted into a wiki or doc. This also like you indicate may be an extra effort on part of minutes keepers. I wish I could send out an example but the best example of minutes I have seen here is what Jim Hughes (HP) would keep for the Globus consortium. He had a neat scheme etc for recordiing AI and resolutions and other aspects of a meeting and from what I understood he had adapted this from some well known method. He would do this almost as a course of the meeting but in our case we could achieve something similar where we pause in the meeting to allow the note taker to record resolutions would help. Anyway, I am not suggesting we add more work so unless we can incorporate it into our current activity we could drop this for now. Ravi Ravi Subramaniam -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Friday, August 18, 2006 08:14 PM Pacific Standard Time To: Subramaniam, Ravi Cc: Andreas Savva; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Hi Ravi, "Summary resolutions compiled in one location" is very good idea. However, I worry about who is in charge. Our note taker(s) is doing very good job but I cannot ask him to do additional works. As an co-chair, I have started "telecon log" wiki page which has recorded discussed topics at each call instead of proposed agenda. Thus you can easily locate related minutes. https://forge.gridforum.org/sf/go/wiki1482?nav=1 Actually we need volunteers to maintain suggested resolution summary pages. Thanks, ---- Hiro Kishimoto Subramaniam, Ravi wrote: > Hi Andreas, > > I think intent and means are clashing in our discussion. I feel that we need to capture decisions and consensus that we reached at meetings. The items are spread into minutes (though not always recorded as a resolution) and other discussions including email. > > I think these also have two levels like action items. One level is recording the essence in a few lines (whether the topic is on of the domains or procedural like format ting) like we do with AIs and the other is an elaboration where necessary or possible like a document or in case of an AI the work product of that item. It is very likely that a collection of resolution/decisions/observations would lead to a single document elaboration and a resolution may not have any other elaboration. Maybe the disconnect is that I think you are referring to the latter level and I am indicating the need for the former level. (I think both levels are important and have their value propositions) > > Having the 'summary resolutions' compiled in one location (organised by domain if necessary) allows us to see where we have conflicts and, if as new members join or in course of discussion, we are revisiting earlier resolutions (we may change resolutions but we know that we are changing a previous one and not reinventing). Where we need more clarity on the earlier resolution we may refer to the 'Architectural notes' or other such related document. > > My experiential perception is that we have revisted a topic many > times and have reached the same conclusions. This is subjective (and I may be able to dig up a couple of recent examples). > > My one cent! > > Ravi > > > Ravi Subramaniam > > -----Original Message----- > From: Andreas Savva [mailto:andreas.savva@jp.fujitsu.com] > Sent: Friday, August 18, 2006 01:39 AM Pacific Standard Time > To: Subramaniam, Ravi > Cc: Hiro Kishimoto; OGSA-WG ML > Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) > > Ravi, > > I still feel that what you are asking is too fine-grain and would not > work in the long run. What is really needed is to document what the > approach is on important topics. > > Taking the 'font' example below it would not be very useful on a general > list of resolutions if that list also included stuff on information > modeling, execution management, data access, security, etc. Instead if > someone thinks a topic is important and they want to maintain a short > (or long) document explaining what the group consensus is, and *keep it > up-to-date* I would be all for it. > > I'll just point out that I did set up an "Architecture Notes" forum some > time back and we still only have one note there. But it's a very good > note and I later used it to write up one subsection in OGSA 1.5. > > Andreas > > Subramaniam, Ravi wrote: >> Thanks. I am ok with Andreas' rationale too. >> >> Just a quick clarification though: The "resolution" I was referring to >> was not the resolution of the action item but noting any resolutions >> that were made/taken in the meeting, for example, if we decided that >> "All documents will be in 12 point font". It would be good to record >> such resolutions taken (or maybe there is a better word than >> 'resolution'). These will likely be around for a while and so the 'year' >> may be required here :-). >> >> Ravi >> > >

3 2

Proposed agenda for Aug. 24th call
by Hiro Kishimoto 22 Aug '06

22 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on <DATE> Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0824 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 21st) https://forge.gridforum.org/sf/go/doc13750?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA F2F meeting agenda discussion (20 min) Establish F2F agenda on Sep. 14 (Thur) and 15 (Fri) https://forge.gridforum.org/sf/go/wiki1555?nav=1 3) CDDLM joint discussion #1 (40 min) Follow-up discussion on August 3rd. (3-1) >> PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in >> CDL documents > > - Jun thinks that this is not a good idea because ID must be unique > in the document and CDL inheritance may break this guarantee by > creating duplicate IDs in the resulting document. CDL has a > mechanism based on non-unique ids. > > AI-0803e: Jun will provide an example of the CDL mechanism and why > using ID/IDREF is not a good idea. (3-2) >> PROPOSAL 2: Eliminate the EnvironmentVariable concept from the >> PosixComponent (CDL plugin) >> >> * Proposal 2 is specific to the OGSA EMS scenarios document. > > Agreed that this is a reasonable resolution for resolving the > problem with the PosixComponent and is sufficient for the EMS > Scenarios document. > > AI-0803f: Jun will update the CDL document to remove the Environment > variables (3-3) > - A normative definition of PosixComponent > - At the moment there is no such definition; there are only some > examples. > - Agreed that a normative definition is necessary and that it is > not part of CDL version 1.0. Also it is probably too late to > leave it for CDL version 2.0---since it is not scheduled yet. > - Tentative agreement that this should be a work item for > CDDLM-WG between these two document release > - Dejan and Jun with discuss this in the CDDLM-WG and seek > approval as a work item after CDL 1.0. 4) CDDLM joint discussion #2 (20 min) OGSA-WG and EGA Reference Model WG started to identify similarities and differences between current works. EGA Ref Model's Dependency Graph and Life Cycle of Grid Components looks very relevant to CDDLM-WG's work. http://www.gridalliance.org/en/WorkGroups/ReferenceModel.asp OGSA-WG will have a GGF18 session on Tuesday 4-5:30pm for this discussion. https://forge.gridforum.org/sf/go/wiki1560?nav=1 5) Wrap up (10 min) AOB <*NEXT CALL*> https://forge.gridforum.org/sf/go/wiki1477?nav=1 Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) EMS & Data joint scenario (Allen, Dave Barry, Steven, and Andreas) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) <*ACTION ITEMS*> https://forge.gridforum.org/sf/go/wiki1569?nav=1 > From Aug. 21 call AI-0821a: Hiro to talk to Jun and CDDLM group about EGA & CDDLM comparison proposal. AI-0821b: Hiro to talk to Jem about EGA & OGSA glossary comparison > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

1 0

Teleconference minutes - 21 August 2006
by Maguire_Tom＠emc.com 21 Aug '06

21 Aug '06

0 *H÷ 010 +0 *H÷ $Content-Type: multipart/mixed; boundary="----=_NextPart_000_002B_01C6C556.45071830" X-MS-TNEF-Correlator: C0E20DCC77C5C601 This is a multi-part message in MIME format. ------=_NextPart_000_002B_01C6C556.45071830 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit https://forge.gridforum.org/sf/go/doc13750?nav=1 Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_002B_01C6C556.45071830 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+Ig4XAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgAQFAAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAAAAAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAAAAAAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAAAAAAwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABAAAAAgEJEAEAAAD8EAAA+BAAABgmAABM WkZ1xkT3dgcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3wKDAFAD1BXPFttiF7EYIP8XghzEGKAHEwKDGCAaHxsvrxw3 F+QcohigVgSQZABw4mECgzIzOBVeInMfcqIgB20gQ0UiJTkir6cYECPfJOV5ciIkNBoBuRV8MTYa ASc/A4JHCdF+ayi1DyApTyyRKo8DglTPCHAotROQEqFkaQM2KagMNzct3yTkKEhlYvkJcHcpKLUn ATAfMSQjz38ylgcQAaAOsDN2DhAsvjjWNjWvJORCB0B0DrAotV85MSleL+E5bzLDVgiQdPsiAAeB ZTN2IpEebCOoBxN9JTc0JdE/nSb3QRUoljX/Gg8qOEEUK9kPEUTfLcZBFH0vRzUv6ETtMXdBFDMM Ne8z+EreQJw3HDU4AUTtOSf7QRQ6ujU5MUTuPLZMVT5O/zygP28jqCG1JTY8oEIPJuj7WOcolTYp EkTvWH0r2Fyg/0ePLahY5i9GXKBRHzkYWOb/OrlcoFP/PJhY5lYMApEI5uo7CW8waU9lUPFqelDy /2tfbGhqZFDyau9uv259bf/nbC9qfxQwMjh0SnVhdR//dilqZHZSdL94j3hNd891//15xDkPIH0U fnF2k35wAoKpEFB5bAeQaAngdAAAenEDIWwSwQUQAUAD8GS4Y3RsCrGBUDcwcAEB7GF1OtAAYHMK sIGwHuBRgrJudW0CAGGCcHQybw1RanUQUAUQZ2hfgqAFEAoBgOAKAWkBkHA2MAMwACBsEMAesXMx /QMwYQExhsAL8CcAB0ANtf+AwYSAhjSF0YcTEycT6AjQ5wnANDCJE25wiWmLBAMw8HNuZXgfMAew BbAAwH8CcxbghnGF0Q1gNEA64HbnF1AQQB8QbWkSAI3wCfCkIESCVCBQCsBhCcBxgiBoIEYCIY0k EGAxdwBQEGADYHcLMISAAYBz4lc0MHRoQhOQhIAKsN2N8GwN4CKQkpRykwgNkFeSdgGAlHdilHdy knJj/mIKsCoglmIfYJbDAmALgGcJkZeUf/BwZZJxBPBlvGxsgWGSQJHhl/FzjkD/ACA6wZDxMzCT kJpWCVCadM8MsZqDgeCadGRnm1ac0PecVoZAmnR2AzCAr4G/gs//g9+E74X/hwKj8Ygdo0ENtP+J BBQihzGKbKcHqISMNZEg/45sjMQ9IAGggBCNJ4fhjei/pC2lfKCgCNAiYIwxYqDgPwmAAiCNon/h HwA0MDI25X5wN1ygIEiYgZtAC4D7LBONYzasj62frqqwIq+v/7C3kGCZEJGACYCxTzFgsn//hlcA UaU/GeQMAbU/jooQQD2xYXMCIEFBEEAFoG1w2xcysE5FAMADEFN/8jFg92hzFuALYHQJ8BBgf/Oe 8MxzZBBQB3BheKxgOTDbwnERUWsJgAEBMI0zaWBidgJRIHtVsbAXIHf/GaHEFLCRxJLFsyJwO3Ax gPWwgjg38DEnALCCx2BEoL8tsbCDsMAO8BOQyEQ3DxD7AFCwgjNKIMdgyNTJ4LDQ7jYOELCCKRAw DfA5MMsDzy2wF/DIJMvxNzkl0LCC7wHAygA5EM0FODWAnyHNIvYzyXDM5TjHYDkgxtR+cP4wAcDP tlEAzDUN4M4BKRH/x5MB0Mixx3XQIcoAyNQO8PcXwMrQ01Y3y2DOIMeEIoD3F+DVUNTlOcngDvDH hTygNz9Q01XJ8TlT4dc0OTT3sQDRFdhAOFEAzPQqMC/Q70Sg2VU1gHbgM9TVzNAYEP+xANrmysDa kMeE21Dakcd1/9ARF7DTVcrAxsDXxtwh1fH/xkSRIJMQsNDfZdYQQfDJhO/IgBfiy5QicDfYYDfx sIP/L9DOQOGGN/DH8cd0DgDTIX87cbCESiDLYMjVsNTGRDf/KjHlRrEA1JDZRdGhE4DNlV8X4Mzg 2FDK5MoANccwMv/M9MoAKkAlwOnVF+HM0MbU/xOAytA7cMuU68Cw8OuxyZT/4hA38Icx7PTWMdrF IoA5IP/T9iKA1hLNpCkQF8DpwMbU/yyA5oA38PCX3nHK5RggKkD/yBXr8eInO3DHMsz0P1BRAP81 gMmEP1A1gBfA79XgwN5Q/9kQ9ebXsAwBsIIYAPTh2GD/92ViYetFGADageDFDxCw0P/OsMuUSiDa oe2FSiDYUHbg//mVDxD7ccjUU+BB8NAwzPT/5EDc0dww92TVUBOAMXH+NP/5MdKF/zHYYA4B93PK wM1R//1VzOATcNewxbMqQNVQU+D/yCRfkenAM+ECtO+ArGDG1P/K0PThzVAEJfBRAEXeULDw/yyA yNTnUSow21AB5NqQ43L/ByXGoMzBAeTbUOjAIoHNE/+TENkQ1YXmgP9x1kX6Mcwh/8rk4hDrQDFg zlX1sS2wC5X/KkB+Yc2lzkAv0NNFzjGw0P9NkQ30i/A5EAuVz5HKoQ3l/9YQkxAPVczgzrDiEMbk 0DH/60DOVN8hzsDQVdqQy2DJUP/I1NqQkwGsYBPlxsAxcM8F/yXAF9HG1QUxEjfK0LEA7MX/7sDo wNwwFVXf8eFQyCTuwP/M0OrxxuTWEMzQB8XvgNtQ/+UQz7UOUNnBx3Qb0omAHNf/zrDXxeDAsMBi Yh50ygAxcP/NpH5wM+DYYB8VsMAKsRzV/87AiYABxQwR6wLPxADB6BH/0SWJcOIQKkHRNDkQN/DK Jf8P0y2w0RY5EP3BzaSHsf6h/+2FpuLZASen97Cm8tE0zsD/y3EkZtrAyeDiRYvw2dHgwP8m1vzx DxHRJusiKubHMYlw/ybVLbIz4NHVi/DYUF3gKuX/kSDz8dTG07DTQNww19V20f8xEi4168AeIS72 UQADATCW/wtQ9wHTVfZTkSEz9dex7AX/kSDYcR9xLjXuwC9h2VW8IP/akSbGMRH5MdKWx2DrQPgF /9OwsME1V8kykwI6dc9g3MH/PAf+wN9FyLHrwNYQN+YAIf8KoCrlRJEGIdHW77H9ET9G/9ewy2DS lgOxU+DR1vWR74D/0pYOQde3Q7H1gkNWJQE31//OIMahN+bZEByBQNUWseFg/wNFH4HO4dNGH5FZ 4OaASDb/1hEPRROB21Ey9tYh2fEq5f/J4ABAsPFLdv9xI4bJ4M4g/zRRS3bQwdpw1OVZ0QVB1OX/ zVBLMUw2zVDW0U6mysDGkv/VprEA7sBR5whB1kfowCwy/8eFM3HrQCbV8DEjUdHVJSD/0DDmgFUm TkHGwNlVJSDeUP+L8NfVA0AGEsd2/RHakNNV/y3hduDK1cfS9OFZNlJxCQH/XIfpp9axLuBjoMd2 3xEXUf9e+P3B1mbZEOI2x2D+wOjA/1hX2FD1oVUm17DacVbGysD/1XFA1fewAMHlRUvxy3Aw8f9l duOBQMbRAOvB1wewwczg/ybV0QAJ0Sx20QDQwRnFrGD/8oDHMDvmSoDbMTl2M5HYQf/XFhvxXSfD ELEAfnBpdlNS/zVm6yEy8Mng1yXPYNGx19f/1hDT9wtR17D+xcgBFqF+cf/ZdMrQcuHX1TYhJoDL hVZyhUMROY0zeG1sbsIA2cYRfVyf4LFhdzqxVRHddrNo6YKjkMCAcpzgJoB/XTF4MpOgeJaXYPJx eCNi7XnDZ6IQwcByo0GioL9Af5+wpjCfgZGAn7CbQZmAbrxiaqDQftCN8MOAXMUQVnjBoaIgeXzQ XIxwcP+AMLMwfeDFEKChm0Cg8H0gzmSQgKuwdjBiZJvQxRC7oPGY8GarMLUBgGFtfjDRlWBlXGir MHp9ApzQd3gyo3CB0WiAE3iBgdF2/4KpgWGiwKNwDDG74IMxhCW/KFKCcoFgdwCDI4Xzan4BH6aw kaB9AZhyJgB2aWX8d2uXwSrgh+KY4KEQp4F3d1F6QJ3iZZVgiUWAYG/joMCg8Gx5dMUwo3CBQP98 YYrXouDAgKIQoPB9MXYg/6LgolGXkbTwv0C7ELWQdiD/oNB2IJeUnvCK4IjRn7CrsH+RkYrRl5Gz MJ2BdiCakGvfgIGBQMUQkGGgIHCNQqnQf6PQoiCn8qNwmPKOEbdhZj2H8Gyq4cKQmQCgEXBwdnWS UKDCaaawkGYjsnL3inHltqngd5eRsFK1AMJQf8UQp/C3cKICkwB7kadwdAowxCJ3p/BmZm10l5MA uxC+UCDSUDNmdpC/wKCKYMCAiNCO4I3wdaPg77Qyn+GpsXtxZKVze2KjUv+p8KOQfNGM4L5QgUB7 Ypwi/6fyC0GbJKB0mkC/cHxjxMBnxDGhkHthbHZ4cJ+hdf5jgOCfoqPAszCgMogxwdG/UMGfoYEQ p1CfYZ+wdKoA+GEgLsFEn7YmAKBSuxH/oL+hz6LfoBAjkJ+wquB9IPekr6W/ps9slgCfsLnApG/7 qT+qRSmjLCrgqA+s/6ol+GIgKHWxri+f48Mgq8//sJ+xr7K/oAHU0LQSoJ+1f/+2j66dJtC0H7mv ur+7z6AB/yyAuK++T79fwGV2oYowdqDPfXCEYJuDmuFccXZwnBH/QNHG4XvBnUHGUpPAd4CeZf+U QYcAx6CBEMiimmDCAJ6A/5difLCNII2AfCCEQIzwxwHebpqRyvKXsHeAMJuAflBFvUBol+BjczGb gGH2ZpqQzLBzJ5GPAKnhKNL/m4PMJMvBzQPNZCOBzWKX8M3PU2OSAs8DbnDPWdD0/59hy/yGsMzy y8HOC4aw02L30EDMwYRgc+V6zCB6IOV5iiCM8HR+IDovL4BhmGdlLpICgGJtLtfBwi+fAC9nby99 AVChxfewP5Gwdj0xdbHSX8/Tb9R/1Y/WmA0KxVLfNv/FRMYPxx/IJ8m1yu7aTlUR/9tvl9FVEdzH zWXO9M/iJ5E1fUBwlWFm3U2fY2JrRG1rwkMgX03F0GzKQZdxU4RAfVSZ4No//9tD8rDbv+2i3QEV Qeff6O/93r5f8r/zz/Sa7G/Mge4N/+ef8G/xf9/y9b/tj+6f+C+3+T/exuwxIOtwerBpnPB130VT fNBpgNABAHtwaIuMsZHwacJALCBPmKAKaYOQIJeQIENUT//7P/a/98//L/nv+v/8D/0fx/4vB5/p u0VNQwnvCv/3DA8NHyeRc5pwduAOT97V/jIP/wVvBn8N3wifCaWTA/2YMmaTMN1Re5AWXxdvGH8D GY/pu0hZUEVSTGBJTksgInoQmPFvFjp6EAFzX5eAbUBl0G1jLmOZ4CIWTx4f7x8vID/db9ZjM13R LGDSEr2YUGSaIMywkxKbgGKEYAF1kCAA0MnqefkAus4RjIIAqgCgS6kLAgAtEAMtEQrgLB02LRFt AGEAAGkAbAB0AG8AIjous2cAdS7xcgDYZQBfLzMuwEAwUS7A+GMALjFRMMItEKMgG9L/kzAz8H7A HQ8RDxIagJES3/8nv+msI0/sQaMiJL8lzybf/zc/Gr8J3zPvEg88rz2/PsiIKzEohYA1KSBRkPw5 LWKwWSDfTT/vQP9CDOdC/0QPPsgiVImwA+CLgZ4gkjCYoJzhklEgYpgA9HdlfNAgqpCAgHuQhxGe IJIA2fAD0AMwIHRNgQOTQJFQaC4iIC0gclLI4iBXjwB74A+wbf124HNNsEefO19Kb0t/Po//3+/g /H1A4d/i7+P/2q9Tn//nT1VvVn9Xj1if4c/IX8lv/8p/XE/MhM3s3Rl3ENAglbA+MyvQ6oZ80etc YmZ9AAFucB4AcAABAAAAKAAAAFRlbGVjb25mZXJlbmNlIG1pbnV0ZXMgLSAyMSBBdWd1c3QgMjAw NgACAXEAAQAAABYAAAABxsV3y8DCEYPv4lhKO4lfWReqHE6yAAADACYAAAAAAAsAAgABAAAACwAB DgAAAAACAQoOAQAAAC4AAAAAAAAARwB4F8eQrEqv7wumWgUXsAEA/BVN2O91eUqHKwbLBDiXrwAA AAOsBQAAAAADAAlZAwAAAAMA3j+fTgAAAgF/AAEAAAARAAAAQzBFMjBEQ0M3N0M1QzYwMQAAAAAD AAYQJfv2pgMABxC/AAAAAwAQEAAAAAADABEQAAAAAB4ACBABAAAAZQAAAEhUVFBTOi8vRk9SR0VH UklERk9SVU1PUkcvU0YvR08vRE9DMTM3NTA/TkFWPTFUT01UT01NQUdVSVJFU0VOSU9SVEVDSE5P TE9HSVNULE9GRklDRU9GQ1RPRU1DMk1BR1VJUkUAAAAAbeA= ------=_NextPart_000_002B_01C6C556.45071830-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 060821231614Z0# *H÷ 1Kž{å¯ËÑÒêíÛÌ»ÊAê±Šé0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ aìtµÀÔv¢S×6fÇ7g¡hÅ ÙflNhÄ §Òu¡®Kí!M Ñï±3~èÐÑþ¬»øJ¯ežü¶'ŒaKÉpþ}êãËÚZÉJ>ùŸm}÷<hö2Ë¶~JXmSÊ+'&nè€{n

1 0

Proposed agenda for Aug. 21st call
by Hiro Kishimoto 21 Aug '06

21 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 21st Monday from 5pm to 7pm (CDT). Sorry for the last minutes posting. The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0821 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 17th and 19th if available) - https://forge.gridforum.org/sf/go/doc13745?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA F2F meeting agenda discussion (20 min) Establish F2F agenda on Sep. 14 (Thur) and 15 (Fri) https://forge.gridforum.org/sf/go/wiki1555?nav=1 > Since many Data members > will be leaving on Thursday it would be good to arrange some time > early on Thursday (OGSA F2F). > - Confirmed that a number of people from EMS on the call (Donal, > Andreas) will be at the F2F. > > AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot > on Thursday. It is important to know early next week---by > the Monday (8/21) call. 3) OGSA and EGA reference architecture (60 min) Preliminary discussion for GGF18 session. Bob Thome, EGA reference model WG co-chair, will join the call. EGA Reference Model and Use Cases v1.5 http://www.gridalliance.org/en/WorkGroups/ReferenceModel.asp 4) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) EMS & Data joint scenario (Allen, Dave Barry, Steven, and Andreas) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> > From Aug. 17 call AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call. > From Aug. 10 call AI-0810a: Donal to look into the relation of the EPS and CDL (retrieval, update, etc). (Eventually this should probably become a separate scenario.) > From Aug. 3 call AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, By GGF18 as original discussed.) ---- Hiro Kishimoto

1 0

Teleconference minutes - 17 August 2006
by Andreas Savva 20 Aug '06

20 Aug '06

Attached. https://forge.gridforum.org/sf/go/doc13745?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 17 August 2006 ==================================== * Participants Jay Unger (IBM) Jem Treadwell (HP) Ellen Stokes (IBM) Andreas Savva (Fujitsu) Darren Pulsipher (EMC) Allen Luniewski (IBM) Chris Jordan (SDSC) Donal Fellows (Uom) Michel Drescher (Fujitsu) Stephen Davey (NESC) Dave Berry (NESC) Minutes: Andreas Savva * Summary of Actions AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call. * Aug 10 minutes - not available * Aug 14 minutes - approved with no changes * July F2F minutes - Roadmap - approved with no changes * Review of Actions AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. - Agreed to schedule this for Aug.31, preferably in the second part of the call. - Data will provide updates (if any) from their F2F at the end of August. AI-0803c: Ellen to book the IBM facility on Thursday afternoon - Done. - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - Done - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) - By GGF18 as original discussed. * OGSA Information Model and Data Ellen gave an overview of the Information Model work. - Slide 6 shows a middle abstract model. But it might be the case that different abstract model might be necessary for different purposes. One example in Data is where the information for discovery may be different than that for scheduling. - Implementation could be a (set of) XML document(s) or a database. And XQuery is supported by DBs as alternative to ODBC etc - Slide 11 shows a symmetric model. Expressing and matching between resource requirements and job capabilities may involve policy---there are many standards that may be applicable but the group has not worked through them yet. - For Data there are a number of open questions around the idea of different models for discovery vs scheduling. What are the interesting properties for Data scheduling? What information is needed for modeling and at what level of abstraction? - Agreed that there needs to be an effort to tackle the scheduling issue between EMS and Data - Data has so far mostly focused on access rather than scheduling. For example, issues with data availability on the network, or performance characteristics are not modeled - What are the necessary abstractions for these? (fast data, available, ...?) - There are a number of groups that should be consulted to get a better idea of current practice (GIN,Globus,etc). The impression is that the state of the art is - a metadata catalog---what is available - a replica catalog---abstract filename to physical location - choice of what to use is up to application AI-0817a: Dave Berry and Jay Unger will approach groups (GIN, Globus, etc) that have implemented practical grids and start a discussion on how they handle data: - how data is treated as a resource that can be scheduled - how transfers are modeled - how files are advertised - how applications find files (query, by knowledge,?) - The Data group is also thinking about a file metadata definition (something like the information retrievable from a POSIX stat()) - CIM has existing work on files and Ellen can help out * Common Data/EMS Scenarios Data has a set of scenarios describing services that interact with EMS. For example, the parameter sweep scenario. EMS also has some expectations, for example that a data staging description from a JSDL document will be correctly processed by some data transfer service---even though that service may not be described further. So it would be useful to have a set of common scenarions describing basic common activities, making sure that the overlap is checked and the interaction between Data and EMS services is done consistently. Agreed that a good first candidate scenario is simple job execution with data staging. In particular the combination of JSDL, BES, Data transfer service (DMI based?). AI-0817b: Stephen Davey will do a cut down parameter sweep scenario focusing on the JSDL+BES+Data Transfer/Staging service The aim is to discuss it at least within Data at the Data F2F (Aug 28-30 @Edinburgh) and with EMS at GGF18. Since many Data members will be leaving on Thursday it would be good to arrange some time early on Thursday (OGSA F2F). - Confirmed that a number of people from EMS on the call (Donal, Andreas) will be at the F2F. AI-0817c: Andreas will talk with Hiro about getting a 1-2 hour slot on Thursday. It is important to know early next week---by the Monday (8/21) call.

2 1

Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 19 Aug '06

19 Aug '06

Hi Andreas, I think intent and means are clashing in our discussion. I feel that we need to capture decisions and consensus that we reached at meetings. The items are spread into minutes (though not always recorded as a resolution) and other discussions including email. I think these also have two levels like action items. One level is recording the essence in a few lines (whether the topic is on of the domains or procedural like formatting) like we do with AIs and the other is an elaboration where necessary or possible like a document or in case of an AI the work product of that item. It is very likely that a collection of resolution/decisions/observations would lead to a single document elaboration and a resolution may not have any other elaboration. Maybe the disconnect is that I think you are referring to the latter level and I am indicating the need for the former level. (I think both levels are important and have their value propositions) Having the 'summary resolutions' compiled in one location (organised by domain if necessary) allows us to see where we have conflicts and, if as new members join or in course of discussion, we are revisiting earlier resolutions (we may change resolutions but we know that we are changing a previous one and not reinventing). Where we need more clarity on the earlier resolution we may refer to the 'Architectural notes' or other such related document. My experiential perception is that we have revisted a topic many times and have reached the same conclusions. This is subjective (and I may be able to dig up a couple of recent examples). My one cent! Ravi Ravi Subramaniam -----Original Message----- From: Andreas Savva [mailto:andreas.savva@jp.fujitsu.com] Sent: Friday, August 18, 2006 01:39 AM Pacific Standard Time To: Subramaniam, Ravi Cc: Hiro Kishimoto; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Ravi, I still feel that what you are asking is too fine-grain and would not work in the long run. What is really needed is to document what the approach is on important topics. Taking the 'font' example below it would not be very useful on a general list of resolutions if that list also included stuff on information modeling, execution management, data access, security, etc. Instead if someone thinks a topic is important and they want to maintain a short (or long) document explaining what the group consensus is, and *keep it up-to-date* I would be all for it. I'll just point out that I did set up an "Architecture Notes" forum some time back and we still only have one note there. But it's a very good note and I later used it to write up one subsection in OGSA 1.5. Andreas Subramaniam, Ravi wrote: > Thanks. I am ok with Andreas' rationale too. > > Just a quick clarification though: The "resolution" I was referring to > was not the resolution of the action item but noting any resolutions > that were made/taken in the meeting, for example, if we decided that > "All documents will be in 12 point font". It would be good to record > such resolutions taken (or maybe there is a better word than > 'resolution'). These will likely be around for a while and so the 'year' > may be required here :-). > > Ravi > -- Andreas Savva Fujitsu Laboratories Ltd

2 1

RE: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 19 Aug '06

19 Aug '06

Thanks. I am ok with Andreas' rationale too. Just a quick clarification though: The "resolution" I was referring to was not the resolution of the action item but noting any resolutions that were made/taken in the meeting, for example, if we decided that "All documents will be in 12 point font". It would be good to record such resolutions taken (or maybe there is a better word than 'resolution'). These will likely be around for a while and so the 'year' may be required here :-). Ravi -----Original Message----- From: Hiro Kishimoto [mailto:hiro.kishimoto@jp.fujitsu.com] Sent: Thursday, August 17, 2006 11:42 PM To: Andreas Savva Cc: Subramaniam, Ravi; OGSA-WG ML Subject: Re: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Hi Andreas and Ravi, Andreas's suggestions work for me. Thanks, ---- Hiro Kishimoto Andreas Savva wrote: > Hi Ravi, > > I used 'a-z' at the end instead of a number for contrast. Also I have > yet to see a meeting produce more than 26 actions but if we ever manage > to do it we could always append another letter at the end. :-) > > I thought about putting in the year but chose not to because an action > continuing for that long is either obsolete or it is a project. In > either case it shouldn't stay on this list! In other words, this list in > intended for short, one-off actions that don't need much tracking but > which we don't want to forget between meetings. > > If the result of an action is to start a document then the action is > closed and we track issues relating to that document more formally in > that document's tracker. It's not the intention here to re-invent trackers. > > Until now this list lived at the bottom of the minutes and stuff got > deleted once closed, with some explanation in the minutes. I think we > could have a heading (I like RS :-) but 'Done' would also be good) at > the end of the wiki page and move closed/resolved items under it with a > link to the relevant minutes; much like what Hiro does with the > teleconference schedule wiki page. > > Andreas > > Subramaniam, Ravi wrote: >> Hi Andreas, >> >> A small suggestion, if I may - would it make sense to augment the AI >> numbering from AI-mmdd'a-z' to AI-yymmdd-'number'. I think we need to >> think in terms of clarity since we can have AIs that span years >> especially near the end of the year. Also a - z means 26; could we not >> have more? :-). >> >> Since this trend has been started, could you also introduce RS (not Ravi >> Subramaniam :-) or RT for 'resolutions or resolution taken'. >> >> Ravi >> >> -----Original Message----- >> From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of >> Andreas Savva >> Sent: Tuesday, August 15, 2006 11:31 PM >> To: 'OGSA-WG ML' >> Subject: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference >> (August 17)) >> >> Donal's email motivated me to put the existing action list on the wiki. >> (This might make it easier to refer to and for other people--besides >> Hiro--to maintain.) >> >> https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Ac >> tionItems >> or >> http://tinyurl.com/pzqs2 >> >> (This wiki page is not intended to replace trackers! Trackers record >> issues on documents.) >> >>> I seem to recall that there was an action item (on me) from the August >>> 10 telecon relating to review and updating of the EMS scenario >> document. >>> It's important that we don't lose track of these things... >>> >>> Donal. >>> >

3 2

RE: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17))
by Subramaniam, Ravi 18 Aug '06

18 Aug '06

Hi Andreas, A small suggestion, if I may - would it make sense to augment the AI numbering from AI-mmdd'a-z' to AI-yymmdd-'number'. I think we need to think in terms of clarity since we can have AIs that span years especially near the end of the year. Also a - z means 26; could we not have more? :-). Since this trend has been started, could you also introduce RS (not Ravi Subramaniam :-) or RT for 'resolutions or resolution taken'. Ravi -----Original Message----- From: owner-ogsa-wg(a)ggf.org [mailto:owner-ogsa-wg@ggf.org] On Behalf Of Andreas Savva Sent: Tuesday, August 15, 2006 11:31 PM To: 'OGSA-WG ML' Subject: Action item list on wiki (was Re: [ogsa-wg] OGSA Teleconference (August 17)) Donal's email motivated me to put the existing action list on the wiki. (This might make it easier to refer to and for other people--besides Hiro--to maintain.) https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/Ac tionItems or http://tinyurl.com/pzqs2 (This wiki page is not intended to replace trackers! Trackers record issues on documents.) > > I seem to recall that there was an action item (on me) from the August > 10 telecon relating to review and updating of the EMS scenario document. > It's important that we don't lose track of these things... > > Donal. > -- Andreas Savva Fujitsu Laboratories Ltd

3 2

Aug 16 Roadmap call minutes uploaded
by Christopher Jordan 17 Aug '06

17 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the August 16th OGSA Roadmap Editors call to GridForge, in the telecon minutes folder: https://forge.gridforum.org/sf/go/doc13744?nav=1 The next meeting will be August 30th. Enjoy. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE5La9PCVtcXn6kg8RAm7TAJ4mO5bX29ZeGzIxwluYJFjid3L3zgCfVPw2 VrJP7f27HBU9RZoqaA1y6n0= =f2xs -----END PGP SIGNATURE-----

1 0

OGSA Teleconference (August 17)
by Andreas Savva 17 Aug '06

17 Aug '06

Following is the proposed agenda for OGSA-WG teleconference on Aug. 17th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0817 More explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (15 min) Note taker assignment Roll call Telecon minutes approval (Aug. 10th) (If available) Telecon minutes approval (Aug. 14th) http://forge.gridforum.org/sf/go/doc13739?nav=1 OGSA-15 F2F minutes (Roadmap) http://forge.gridforum.org/sf/go/doc13734?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA Information Model & Data Model discussion (50 min) (Ellen and Fred) Overview of Information Model decisions from OGSA-15 F2F (July). Material to be used in the call: - OGSA Information Model & Data Model: https://forge.gridforum.org/sf/go/doc13738?nav=1 - Information Modeling in OGSA Architecture Paper https://forge.gridforum.org/sf/go/doc13726?nav=1 3) Common EMS and Data scenarios discussion (50 min) (Dave/Allen and Steven/Andreas) > There is a pretty clear need for EMS to be tied into Data. The key > to making this happen is to have one or more scenarios that both > EMS and Data agree to and are taking actions to ensure that their > respective work satisfies those scenarios. > > EMS and Data [should] discuss scenarios and come to agreement on a > plan to first create one or more joint scenarios and, two, to > coordinate activities to ensure that our mutual work satisfies > those scenarios in a compatible manner. 4) Wrap up (5 min) AOB <*NEXT CALL*> Aug. 21 (Mon): Joint EGA call Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sep. 4 (Mon): No call (Labor Day) Sep. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17)

3 5

Roadmap Editors' call, 8/16
by Christopher Jordan 16 Aug '06

16 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please join us for the next OGSA Roadmap document conference call, Wednesday, August 16th, 3PM PDT/6PM EDT/ 7AM, 8/17 Tokyo time. To Join Audio Conference Primary Dial-In: 1 (877) 213-2541 Alternate Dial-In: 1 (630) 424-7813 Passcode: 9737458# Meeting Agenda: 1. Preliminary business Agenda bashing Previous minutes approval 2. Review of changes to section 1 by Chris Jordan 3. Report from Dona on document status updates received 4. Discussion of use of Wiki page for textual document description drafts, discussion of maintenance of textual document description responsibilities 5. Revisitation of the question of how to deal with published documents 6. Review of schedule for Roadmap release, cut-off dates for status updates 7. AOB - I'm sure I had one or two other things to discuss, but it's late, so I reserve the right to remember them tomorrow. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE4uLQPCVtcXn6kg8RArngAKDO3ngNXsEA43v04t/zZs1RPQ/QIQCg5CwT lWYFcidpfhFa9E6f6aZlz28= =+g/r -----END PGP SIGNATURE-----

1 0

Teleconference minutes - 14 August 2006
by Andreas Savva 16 Aug '06

16 Aug '06

Minutes attached. This was a Roadmap call. https://forge.gridforum.org/sf/go/doc13739?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 14 August 2006 ==================================== * Participants Mike Behrens (R2AD, LLC) Chris Jordan (SDSC) Andreas Savva (Fujitsu) Ellen Stokes (IBM) Jem Treadwell (HP) Minutes: Andreas Savva * No minutes approved - August 10 minutes not available * Next call - Information Modeling and Common EMS/Data scenarios are the main topics. - Ellen will review decisions and if there are questions will also give more details about other options considered. - Ellen will upload material to gridforge today. - Andreas will include links to Ellen's material in the agenda. - Chris will forward the agenda to the GFS list and also remind Dave Berry about the common scenarios discussion * OGSA Roadmap review - Chris has uploaded an edited version of the Roadmap document. Edits mainly to bring it up to date and to make it less dependent on developments relating to other specifications. - Also added information modeling documents; deleted obsolete entries, etc; - Consensus that these are good edits. - Is the Information Modeling document intended to be normative or not? - If it is intended to summarize what is described normatively in other documents then it should be non-normative. - Ellen's main concern is with making sure it can be implemented and can also be used by other bodies. In that sense a normative document may be better. - Agreed to revisit the issue of document type in a larger group; it is not critical at this point. - It is not necessary to capitalize "Service Oriented Architecture" - Is it important to change "Global Grid Forum" to "Open Grid Forum"? - Agreed to leave it for later; guidelines on what to do (e.g., copyright notices should say available soon). - Delete "Informational Profile" section? - Agreed to leave as is since this is a category defined in the Profile Definition. - Chapter 7 - Liaisons - needs updating - Review and confirm assignments; is all the work listed here still current? - Ellen will provide some updated material to Chris. - Update EGA connection; what happens to the EGA TCs and what is the relation of that work with OGSA? - There is call scheduled with some members of the EGA TC (reference model) next week and this question could be raised there. - SCRM description also needs update. The best person to talk is Hiro. - Chapter 8: Also need to contact the open source projects again and confirm that the paragraphs describing their activities are accurate. - Mike will contact Keisuke Fukui and update the ACS entry. - Why is the WSRF BP listed in the Appendix on the wiki? - It was one of Hiro's suggestions but it is not clear (nobody could recall) what the main motivation for this was. It was not just that the document was published already. - How should already published documents with ongoing revisions be treated? - One idea is to include the published version in the table of each document section together with the work-in-progress. - The official schedule for the Roadmap 1.1 was to submit it for public comment by GGF18. It will likely slip, but the plan is still to submit it to the Editor in September. - There is a bi-weekly call (Wednesdays). Interested people are welcome to join. - How are referenced specification updates handled? Should individual contributors use the spreadsheet? - The spreadsheet is still used. Andrew Wang is working on moving it to a relational db. - Individuals should send updates to Dona / Chris who will update the spreadsheet

2 2

Re: [ogsa-wg] OGSA Exec summary ...
by Hiro Kishimoto 16 Aug '06

16 Aug '06

Thanks Raj, Yes, "allocation" should be added to the list of functions/services including "reservation and deployment." Good catch! However, based on the recent architecture development, OGSA-WG has moved these services under "Execution Management Services" and made "Resource management" as general management framework. See my keynote slides: http://www.ggf.org/GGF17/materials/316/OGSA%20keynote%2020060510.ppt Now I am sure this exec summary needs major update. We will review Ravi's version in the very near future. Thanks, ---- Hiro Kishimoto Rajkumar Buyya wrote: > Hi Hiro: > > Regarding statements in your document: > --------- > • > Resource Management enables the monitoring, reservation, deployment, and > configuration of grid resources according to quality of service > requirements. Grids allow organizations to pool their departmental IT > resources and make them available for efficient and dynamic use across > the organization. > --------- > > "Resource allocation" need to be part of esource Management services. > > How about changing the above statements to following: > --------- > •Resource Management enables the monitoring, allocation, reservation, > deployment, and configuration of grid resources according to quality of > service requirements. Grids allow organizations to pool their > departmental IT resources and make them available for efficient and > dynamic use to meet demands from competing applications across the > organization. > --------- > > Thanks > raj > > Hiro Kishimoto wrote: >> Hi Ravi, >> >> The attached document is "OGSA introduction" we've used for SC04. >> I cannot find the final version but this is very close to the final. >> >> Since it is outdated, you need to update based on our recent >> major development. But I think it is good starting point. >> >> I would very much appreciate if you could bring yours back to >> OGSA-WG in the near future. >> >> Hope it helps, >> ---- >> Hiro Kishimoto >> >> Subramaniam, Ravi wrote: >>> Hi, >>> >>> >>> >>> Do we (or any kind soul willing to share) have an exec/mgmt summary of >>> the OGSA and OGSA architecture (yeah, seems redundant but am using OGSA >>> in the trademarked brand sense) - 2/3 pages? I am thinking of putting >>> one together for some conversations I need to have but in the essence of >>> "laziness" (efficiency/reuse in euphemistic terms) wanted to see if >>> there existed an exemplar that I could use. I am looking for an editable >>> version that I could tailor to my specific purpose (with the fond hope >>> that it is so well written that I could use it "right out of the box"). >>> >>> >>> >>> Thanks! >>> >>> >>> >>> Ravi >>> > >

1 0

Re: [ogsa-wg] OGSA Exec summary ...
by Hiro Kishimoto 16 Aug '06

16 Aug '06

Raj's email bounced. -------- Original Message -------- Subject: Re: [ogsa-wg] OGSA Exec summary ... Date: Fri, 11 Aug 2006 13:30:30 +1000 From: Rajkumar Buyya <raj(a)csse.unimelb.edu.au> Organization: The University of Melbourne, Australia To: Hiro Kishimoto <hiro.kishimoto(a)jp.fujitsu.com> CC: Subramaniam, Ravi <ravi.subramaniam(a)intel.com>, ogsa-wg <ogsa-wg(a)ggf.org> Hi Hiro: Regarding statements in your document: --------- • Resource Management enables the monitoring, reservation, deployment, and configuration of grid resources according to quality of service requirements. Grids allow organizations to pool their departmental IT resources and make them available for efficient and dynamic use across the organization. --------- "Resource allocation" need to be part of esource Management services. How about changing the above statements to following: --------- •Resource Management enables the monitoring, allocation, reservation, deployment, and configuration of grid resources according to quality of service requirements. Grids allow organizations to pool their departmental IT resources and make them available for efficient and dynamic use to meet demands from competing applications across the organization. --------- Thanks raj Hiro Kishimoto wrote: > Hi Ravi, > > The attached document is "OGSA introduction" we've used for SC04. > I cannot find the final version but this is very close to the final. > > Since it is outdated, you need to update based on our recent > major development. But I think it is good starting point. > > I would very much appreciate if you could bring yours back to > OGSA-WG in the near future. > > Hope it helps, > ---- > Hiro Kishimoto > > Subramaniam, Ravi wrote: >> Hi, >> >> >> >> Do we (or any kind soul willing to share) have an exec/mgmt summary of >> the OGSA and OGSA architecture (yeah, seems redundant but am using OGSA >> in the trademarked brand sense) - 2/3 pages? I am thinking of putting >> one together for some conversations I need to have but in the essence of >> "laziness" (efficiency/reuse in euphemistic terms) wanted to see if >> there existed an exemplar that I could use. I am looking for an editable >> version that I could tailor to my specific purpose (with the fond hope >> that it is so well written that I could use it "right out of the box"). >> >> >> >> Thanks! >> >> >> >> Ravi >> -- Hiro Kishimoto

1 0

Initial document drafts for HPC Profile
by Christopher Smith 14 Aug '06

14 Aug '06

Hi all, I've uploaded the following documents to gridforge: - HPC Profile Application Extension - JSDL extension for describing executables, etc. (https://forge.gridforum.org/sf/go/doc13735?nav=1) - HPC Basic Profile - the skeleton of the profile document with the section for JSDL profiling filled in (for debate :-) ). https://forge.gridforum.org/sf/go/doc13736?nav=1 Please send any comments to the list to get the discussion going, and we'll use the trackers to record any issues that need to be addressed. By the way ... in future I will only use the ogsa-hpcp-wg(a)ggf.org mailing list for discussion of these documents, so please subscribe if you haven't already. Please follow up to ogsa-hpcp-wg. -- Chris

1 0

OGSA F2F Roadmap minutes (finally) uploaded
by Christopher Jordan 14 Aug '06

14 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I finally got around to putting together my minimal notes on the roadmap session at last months F2F session, and have uploaded them to GridForge: https://forge.gridforum.org/sf/go/doc13734?nav=1 They are not long, so we should be able to approve them today. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE4KzOPCVtcXn6kg8RAp7PAJ9lfbRMgl/fjYWj4bthTWj/aBn9ngCglq4S 5h3Uh6FIEtGdFx/+U7UMnV0= =epHj -----END PGP SIGNATURE-----

1 0

Agenda for Monday, August 14th (5pm to 7pm (CDT))
by Andreas Savva 14 Aug '06

14 Aug '06

The following is the proposed agenda for the OGSA-WG teleconference on Aug. 14th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) Complete dial-in information: http://tinyurl.com/eg48j PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0814 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (10 min) Note taker assignment Roll call Telecon minutes approval (Aug. 10th), if available Action Items status review (see bottom of this email) Agenda bashing 2) OGSA Roadmap (Chris, 40 min) > A slightly edited version of the OGSA Roadmap v1.1 has been uploaded > to GridForge, at: > > https://forge.gridforum.org/sf/go/doc13733?nav=1 > > At this point, all I've done is added a comment or two and done some > rewriting of the introductory section. Please feel free to download > and read it if you'd like to discuss or savage my changes on > tomorrows call. 5) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 17 (Thu): Info/data model (Ellen and Fred), EMS and data joint scenarios (Allen and Steven) Aug. 21 (Mon): Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sept. 4 (Mon): No call (Labor Day) Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> [Not sure if there were updates on the Aug.10th call.] > > From Aug. 3 call AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) -- Andreas Savva Fujitsu Laboratories Ltd

2 1

Edited version of Roadmap 1.1. draft uploaded
by Christopher Jordan 13 Aug '06

13 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 A slightly edited version of the OGSA Roadmap v1.1 has been uploaded to GridForge, at: https://forge.gridforum.org/sf/go/doc13733?nav=1 At this point, all I've done is added a comment or two and done some rewriting of the introductory section. Please feel free to download and read it if you'd like to discuss or savage my changes on tomorrows call. Thanks. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE31GtPCVtcXn6kg8RAnHUAKCgrMqqazZJ9R7BvHL/jF/n5T89XgCfeyvS 3MSX63OiWKZzA0Lh/B1/r3U= =ISJl -----END PGP SIGNATURE-----

1 0

OGSA Exec summary ...
by Subramaniam, Ravi 11 Aug '06

11 Aug '06

Hi, Do we (or any kind soul willing to share) have an exec/mgmt summary of the OGSA and OGSA architecture (yeah, seems redundant but am using OGSA in the trademarked brand sense) - 2/3 pages? I am thinking of putting one together for some conversations I need to have but in the essence of "laziness" (efficiency/reuse in euphemistic terms) wanted to see if there existed an exemplar that I could use. I am looking for an editable version that I could tailor to my specific purpose (with the fond hope that it is so well written that I could use it "right out of the box"). Thanks! Ravi

2 1

Proposed agenda for Aug. 10th call
by Hiro Kishimoto 10 Aug '06

10 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 10th Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0810 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 3rd) - https://forge.gridforum.org/sf/go/doc13718?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) OGSA authorization call-out proposal review (Frank, 20 min) > - Frank is now consulting with people in GGF (David Chadwick, Von > Welch) on whether his approach can be defined within the AuthZ > group. If there is no agreement then he will accept the XACML > group's decision. 3) Basic Security Profile PC review (Takuya, 30 min) Takuya brings text proposal for the following PCs. >> Reviewed public comments and Takuya's proposed replies >> 1. Add text explaining that the Secure Channel profile is not >> required by all ogsa services. The introduction is probably a >> good place for this. >> 2. [Basic-Security-Profile] usage. The term is defined in the >> document. Takuya to check whether such special terms are used >> consistently and that they stand out. Refer to the WSRF BP for a >> similar example. >> 3. Ciphersuites: Agreed that it important to list acceptable >> ciphers. >> - As a first step Takuya will list up available ones (from the >> WS-I BSP); select the ones that are in common use; and then >> select the ones that are considered sufficiently safe. >> - Review the list at the next BSP teleconf >> 4. Multiple keys in keyinfo field? >> - Takuya to talk to Von in order to understand the use case for >> multiple keys; and will propose a resolution at the next BSP >> teleconf. 4) EMS scenarios (Andreas and Steven, 30 minutes) Andreas will send out revised version before the call. 5) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 14 (Mon): Roadmap (Chris) Aug. 17 (Thu): Info/data model (Ellen and Fred), EMS and data joint scenarios (Allen and Steven) Aug. 21 (Mon): Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sept. 4 (Mon): No call (Labor Day) Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> > From Aug. 3 call AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) -- Hiro Kishimoto

4 4

Customer briefing tomorrow (8/10) AM
by Maguire_Tom＠emc.com 10 Aug '06

10 Aug '06

0 *H÷ 010 +0 *H÷ $KContent-Type: multipart/mixed; boundary="----=_NextPart_000_006B_01C6BBF6.809FC0E0" X-MS-TNEF-Correlator: 00CDAC0718BCC601 This is a multi-part message in MIME format. ------=_NextPart_000_006B_01C6BBF6.809FC0E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit I am in a customer briefing in NYC tomorrow AM and will not be able to attend the call. Sorry. Tom _______________________________________________ Tom Maguire Senior Technologist, Office of CTO EMC2 maguire_tom(a)emc.com +1(845) 729-4806 "The only difference between a rut and grave is the depth." - Ralph Waldo Emerson ------=_NextPart_000_006B_01C6BBF6.809FC0E0 Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="winmail.dat" eJ8+IgIAAQaQCAAEAAAAAAABAAEAAQeQBgAIAAAA5AQAAAAAAADoAAEIgAcAGAAAAElQTS5NaWNy b3NvZnQgTWFpbC5Ob3RlADEIAQOQBgAAFAAAHwAAAAsAHw4BABIAAgH4DwEAAAAQAAAAGTFs0enA QU+TG+xdGMv50gIB+g8BAAAAEAAAAEcAeBfHkKxKr+8LploFF7ADAP4PBQAAAAMADTT9PwUAAwAP NP0/BQACARQ0AQAAABAAAABUlKHAKX8QG6WHCAArKiUXHgD6PwEAAAANAAAATWFndWlyZSwgVG9t AAAAAAsABIAIIAYAAAAAAMAAAAAAAABGAAAAAAaFAAAAAA0KAwARgAggBgAAAAAAwAAAAAAAAEYA AAAAAYUAAAAAAABAABOACCAGAAAAAADAAAAAAAAARgAAAABghQAAAAjW6CkAAAALABCACCAGAAAA AADAAAAAAAAARgAAAAADhQAAAABibAsABoAIIAYAAAAAAMAAAAAAAABGAAAAAA6FAAAAADt3AwAD gAggBgAAAAAAwAAAAAAAAEYAAAAAEIUAAAAAAAADAGqACCAGAAAAAADAAAAAAAAARgAAAAAYhQAA AAAAAAsAcIAIIAYAAAAAAMAAAAAAAABGAAAAAIKFAAABADtmAgEJEAEAAADsEAAA6BAAAAomAABM WkZ17I6eEwcABgEBC2BuZzEwMmY1AGQAcmNwDdAOADIdDGBjDUQBNAExc3Rz4mgFcGJjaBA1CQAQ x2ZoDrAQ1mJpAUMNpDPyMxLmZmUTYgH3AqQDY0cCABDACsBzZXQC0XAocnEyAAAqCqFuby0WICAN 8BdxNhNwMDWcMDQX8QHQF+A0fQdt3RbCZgdABUAHY30CgwBQ9wPUFc8W22IXsRggF4IdtOcYoAcT AoMzNxsPHB8dJ1cX5B2SGKBWBJBkAHBhxwKDGCAVXjIzOCBEGjTxB7ggQ0UZvyMyGvEjrfcYECS/ JcV5CLEmbyNQE5C5FW0xNhrxKP8DgkcJ0f5rKn8jMijBK/4PIC0fA3M+VAhwLs8jMg4QEqFkaTsD NixINx8hMX8DgihIZGViCXB3KTL/IzI2/zRfNWYkrzb2BxABoA6wN993IyMfISv9ODkxOw8DgkL/ GgEOsDzfIzI60Sv+K8E/j7U3I1YIkHQi8AeBZTzP/wKSGAAfPiSIBxMmEUbkGv//KKhI9SpQRuQr wR9cLNhI9P8uc0bkKMFMrjFGSPQywUbk/zRITK0110j0N2ZG5Dk4Un7/SHw8VkbkHy8/OEj0QNRG 5P860UyuQ7ZT9UVJJzVHTySI/yKlSUYngEnfKKhgV0v1J4D/TH8s2GBWTogngE8/MShgVv9RRieA WJ8/OGBWWqkngFtvX0OYYFZdfAKRCOY7CW8w9XC/ZQ4ANXHqcwFyv3PJ/3HUc/JyX3Yvde11b3Of ce/5FDAyOHu6fNF8j32ZcdR/fcJ8L3//f71/P31vgTQ5fw8ghISF4X4DheACghBQeapsB5BoCeB0 AABxAyEebBLBBRABQAPwZGN0LmwKsYjAPHBwAQFhdXsaEABgcwqwiSAf0Ioibkx1bUYhieB0bw1R auZ1EFAFEGdoihAFEAoBy4hQCgFpAZBwMAMwACCmbBDAH6FzMQMwYQEx/44wC/AowAdADbWIMYvw jaT/jUGOgxMnE+gI0AnAOXCQgxxucJDZknQDMHNuZf54ICAHsAWwAMACcxbgjeHvjUENYDmAQQB2 F1AQQCAAnG1pEgCVYAnwIESJxDQgUArAYQnAiZBoIH5GAiGUlBBgYVEQYANgdycLMIvwAYBzVzlw dGjeQhOQi/AKsJVgbA3gOtB9mgRymngNkJnmAYCb52L9m+dymeECYAuACZGd5IdgjHBlmeEE8GVs bIjR95mwmVGeQXOVsAAgGgGYYf83kJsAoKYJUKDEDLGg04lQ+aDEZGehpqMgoqaNsKDE/nYDMIgf iS+KP4tPjF+Nb/+OcqpBj42pkQ20kHQUIo6h/5HcrVeu1JOlYVCV3JQ0GjD/AaCHgJSXj1GVWKp9 q8ym8O0I0GZEEBBAYqcwCYACIF+VEodRH/A5cA3gNw3wM32OAEie0aGQC4BOw5TTNv+y37PvtPq2 crX/tweX0J9g/5jwCYC3nzXAuM+NxwBRq4+/GtQMAbuPlfoQQLexcwIgZ0khEEAFoG1wFzK2nkX7 AMADEFOHYjXAb+MW4AtgnnQJ8BBgh2OlQHNkEFB5B3BheLKwOTDIwRFRa1sJgAEBMJSjcNB2AlEg zHtVuAAXIHdux4W20vvK4swDODQwZxG208zxMTG5ttIyMizgJIDN5TcPEHsAULbSM0xgZxDOhM+Q Nvw5Ng4QttJegQ3wOTDQs48xMBfwzdTRoTc5OcwD7wHAt2Bs4dLEODrApXHS0vYzzyDSlThnED9A afC20v+F4LcgzvDVdVHA0eW3FdbW/35QJ4G20wHQzmHNJdXRt2D/zoQO8BfA0IDZxSSQF+DbAN/N NUOgQnDZxc+hOVUh3CTuOT4QzcXdIThRwNKkLNB/K7BJwN5FOsB+UB8R3yQ5/xgQ3WDf1tBw34DN NOBA34H/zSXVwRew2cXQcNVQ3LbhEb9kINKkzyCacdBg5FU52PC+Oc80zjAX4tFEJIA3PhD/NDHN 8yuw0/DmdjQwzaHNJH8OANmROSHN89ph0RDOhTf/LNHqN9VQF/DkRczgE4DTRT8X4NKQ3UDQlLdg W1A0Mv/SpLdgLODkMO4FF+HSgNVk/jPSYROA0UTm8TQwjqHwZPdJwObhz0Q4P0DaZiSQ5YD/ScDT VCeAF8Dt8NVk7eDqsP80MPQH42HQlRggLODNxTkg/96w5yZCcFHAOsDPNEJwOsD/F8DzReWw40De APiW3KAMAf+20hgA95E+Efok3rDdMPrG/99x5bUPENBg1GDRRExg35H/8PVMYN1AflD8RQ8Q/iHO hP9VIOWgtyDSpFiA4cHhIPoU/9sAE4A10QDk++HY9QHhPhD/DgH6I9Bw0wEABdKQE3DcoP/MAyzg 2wBVIM3U3rDOMN1A/80k3rDy8LKw1WTQgPeR0wD/BtXzwQL140DO8O3gzoTrgf8s0OBABJTfgOhi BJTgQOzw/ySR0sOagN4A2zXqsAIhDvD/1BUXwP7x0rTloAxh1AX4Yf8xMA2FLOCF0dNV0/ArsNm1 /9Ph0GBPIQ/kk2A/MA2F1UH/0FEP1eWAmoARRdKQ1GDnAP/MlNXh73DUBOQR1HDWBd+A/9EQzwDO hN+AmnGysBXV1VD/NdDUteQwIdEVxQfhFCfQgP/dYPA18jETQc3U8jDSgO8h/8yU5YDSgAp18vDg QOoA1WX/EEDesc0kHQKQ8B4H1GDctf/lsLdgNdDTVIXgMAA+ENCU/4Xg3rDaIB4F1HCQ8AR1DgH/ 7zLVdANx7EHW1ZDg5wAs4f+21D8wNDDP1RHDMTDWxj8w/wBx01SPIQFR8PWtMt3xKBf/+mCtQrbU 1HDRIdeG37DPkP/nNZNg3sHlsCdG/6ERAdbW/+9SK1bM4ZDgJ0UuIgXw14X/k2DdQGVQK1VhUDkg G2Eupf/koO/gP0ExJRbh8DVhUO/g/x9RL2ZRwAWxMQYNQPmx2cX/+QNhUTRl3KHjQC6l3WEf4f8u pfIwL9HeRcJw34EnNjGB//vh2QZnEO9w+rXaIPyxNcf/zuKacjrl1RDhsTx3AXDkNf/OYe/g5YA4 VgLRDJArVQLw/99g7eDYRvMh/8E/ttyg0RD/2QYGYVUg2Eb4QfLw2QYQMf/cp0Qh+DJDxiVxOEfT 0AyQ/yzm7fAQMQ1A2pW3IU8gzSX/0yHSkNm2IAHkMOqwSKbzAf8RNRVx4EEzZt7R3uErVc+Q/wLw 62FL5gIhI/bPkNPQNMH/S+bWcWnh2qTTAEuhTKbTAP/bwU8W0HDY4U1273Aw0VGH/9sADKZnEOzw LKLNNTPh73D/J0XzoSPB14UlkLcg6rBUxv9OsdVQ 3kUF8AjCzSb/wd+A/9tG+mB+UNCFzYL3kdzF 0aH/GHFUxmhA7dfboWzR6LUwsv/JUdtH1RAAcdtW3gDnJjpx/9UxXAfcoN9hVmbQcNshQUX/+mAD ceo1TGHocUE2zxDv4P8BIWRG0GDSkCdFzxALwSzm/88Q1nEa9bKw9fDM4DxWSvD/4CE55jQB3THc Bh0hW/fJYP/dYIXgZqZS8jXW71E8MM+Q/9wV1RDYIdzH5YDaZw1B3KD/AXXNsRiRheHeZNCAcBHc xV82kSbw0TVWEkOBOZSjeJhtbG7IUMxhfVymMN23sXc7IVSxc+No7bJ8AP3G0HKjMCbwXAF1YpsQ dcbXsGD14XVTYnbzZ6hgyBD+cqmRqPDFkKYArICl0Zjwx6YAoZGf0G5iaqcggfBrlWDJ0FzLYHjH 8ahwefWB8FyT4HCHoLmAexDLYO+m8aGQp0B6UGSX8LIAc2C8YmSiIMtgp0GfQGaxgBu7UX2RbYeg nNBlXGh9sYB6ejKjIHViqcB/AWj3fUN1sX8Bdn/ZfpGpEKnA/w4hwjCAYYFVKMJ/on6QdDD7gFOD I2p7Ma0AmRB6MZ7CwSZwdmlld2ueEStQf4USnzCO0K3RdIF3cKQyZTec0IZ1fZBvpxCnQGx5/nTL gKnAfnB5kYgHqTDG0P+oYKdAemFzUKkwqKGd4btA/8WQpwC74HNQjsF8gp4RpUD/iBCGAaYAsgCZ AYgBneG5gPej0XNQoeBrfbF+cMtgjZH9pnBwinKTwKogqHCuQqnA159Ci0G9sWaFIGyWccjgY59Q pmFwcHWPgKcSaX+tAI2WJCKY4Iew1yawMHf/neG2ortQyKDLYK5AmPCoUqeQMHjBrcB0MMpyd65A cGZmbXSQMKcAxKAg+djAM2ZzwMbwfZDG0IYA+4wQc1B1qjC6gqYxsAF4of5kq8N4kqmisEB3wHoB ihD/xKB+cHiSmVKuQg0xmFSmxH+XcMXAeZPLEMqBp+B4kWzmdnWgnNF1Y34QnNKgcP+5gJ1ihWHI IVBhnNGnkK2gi5yRp+B0sFBhIC7HlP+c5iZwnYLBYZ3vnv+gD51AfyQAp+CxMHpQod+i76P/bL+t YJzgqpChn6Zvp3UpoFyPK1ClP6ovp1ViIChy4f+rX50TyXCo/63Prt+v750x/zEAsUKdz7Kvs7+r zSdAsU//tt+377j/nTHSoLXfu3+8j/+9lXPRh2Bz0MfwgZCYs5gR/FxxzHGLoEFBxBF48Zpx/8OC kPB0sJuVkXGEMMTQfkD/xdKXkL8wm7CUknngilCKsO95UIFwiiDEMW6XwcgilOBNdLAwzIGagGNo lRBjZHMxmLBhZnfAyeBz/ygBjDCnESlCmLPJVMjxyjPfypQj8cqSlSDMg2OPMswz/G5wzInOJJyR ySyD4Moif8jxyzuD4NCSzXDJ8YGQc4HW6SBJIGFtIMMR/afAY8eBlxCWUYdQkECQMMOrAcMRTllD INQxfgCxlGEgQU3TcIVwIHjwzY+wIHpwlPBiZdNwi5Df1zCUsNNweAHWYXSG4NPwoY/hLiAgU9XB eaBA/89v0H/Rj9KazXB+QNXQ0rn8DQrCgt5WwnTDP8RPxVf/xuXIHtlu8bHaj5UB8bHb51/Klcwk zRIoAXpwcJKRZkPSbpViYmtta79zIKRfTcMAbEGUoVOBcPx9VJcQ2V/aY/Yg2t/swt/cIRcx5v/o D93eX/Hf8u//87rrj8mx7S3mv++P8J/fEn/03+yv7b/3T/hf0ubrUSBb6pB34GmaIN5lU3sAabd+ AAAgeKBoieGPIGm/cKgsIE+V0Gl9cCCUwPAgQ1RP+l/13/bv/k9/+Q/6H/sv/D/9Twa/0ptFfE1D CQ8KHwsvDD8oAXPvl6B0EA1v3fUyDx8EjwWf3wz/B78IxZAzlWJmkGDScT+U8BV/Fo8Xnxiv0ptI WQBQRVJMSU5LIGYid0CWIW86d0AAk1+B1DFAZW1jLmOXEP4iFW8dPx5PH1/cj92TUtH3SsBWUJyT ZJdQyeCQQpiwBmKBkHLAIADQyeoAefm6zhGMggCAqgBLqQsCACwwKgMsMeArPTYsMW0AAGEAaQBs AHQAiG8AOi3TZwB1LhFgcgBlAF8uUy3gQOMvcS3gYwAuMHEv4iww/6BQGvKQYBnAiuAcLxAvETr/ fcER/ybf0owib+thoFIj3/8k7yX/Nl8Z3wj/Mw8RLzvPIzzfPegrMSiCsDUpkiBRMDktYLAwNt5t Pz8PQB9BLEIfQy896CJU9dhRb4ixII9gldCaEY+B+9cRiCBlewDT0X2wlPDWUvmPMGF21zACUNgz kHCOgIBoLiIgLSBSxhK8IFeMMHkQDtDUUXNM0P9Gvzp/SY9Knz2v3w/gHHpw/+D/4g/jH9nPUr/m b1SPVZ//Vq9Xv+DvxY/Gn8evW2/JtP/LHNw6kxBukG6AKvDpptgCE+qLYYZ9AG2QHgBwAAEAAAAl AAAAQ3VzdG9tZXIgYnJpZWZpbmcgdG9tb3Jyb3cgKDgvMTApIEFNAAAAAAIBcQABAAAAFgAAAAHG vBgHi9vc9slzV0HqsS9T1eyDb64AAAMAJgAAAAAACwACAAEAPC8LAAEOAABlPgIBCg4BAAAALgAA AAAAAABHAHgXx5CsSq/vC6ZaBRewAQD8FU3Y73V5SocrBssEOJevAAAAA6wFAAAAAAMACVkDAAAA AwDeP59OAAACAX8AAQAAABEAAAAwMENEQUMwNzE4QkNDNjAxAAAAAAMABhDM4+T9AwAHENoAAAAD ABAQAAAAAAMAERAAAAAAHgAIEAEAAABlAAAASUFNSU5BQ1VTVE9NRVJCUklFRklOR0lOTllDVE9N T1JST1dBTUFORFdJTExOT1RCRUFCTEVUT0FUVEVORFRIRUNBTExTT1JSWVRPTVRPTU1BR1VJUkVT RU5JT1JURUNITk9MTwAAAACR2g== ------=_NextPart_000_006B_01C6BBF6.809FC0E0-- Ê0=0ŠÍºVðßäŒTþ"¬³rªU0 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 960129000000Z 280801235959Z0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority00 *H÷ 0å¿m£Va-HqögÞ¹ë· ú8%¯Fåsš $] Ìen°ÐV¡sßŽX9knÁöÕšš?ª1¬°4×4g ÍâNEVixÚÜG)»6Éc\Åà×-{¡·2°{0º*/1ªî£gÚÛ0 *H÷ L?žÆhßîC3]éŠËMz3ÿô6Ø"6hl|BÌó.Ä?°OÿvùâŒJéÍ ÷Å)ñ"]ž±Ý#£{%F0yøêKÂÈã·ô@<Ã_SèHäŽ{¡5°{%ºžÓ«?84óÑq0b0Ë ÚÁ?« tzŽÎ.30 *H÷ 0_10 UUS10U VeriSign, Inc.1705U.Class 1 Public Primary Certification Authority0 980512000000Z 080512235959Z0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated00 *H÷ 0»ZD»Uýz-Ox6ž J²oT¿Œèw*¹ðh»Ù1ApzK¹HV-ÇáB«À¢«D\ªBðé/ûÂ;»ŸÉ' ]¶°6B3µnTOJ¿Úùè¶ãÌÆj$ãüàeº§±~ïÉÛ7jÈJÈ ä£°00U0ÿ0GU @0>0<`HøE0-0++www.verisign.com/repository/RPA01U*0(0& $ " http://crl.verisign.com/pca1.crl0U0 `HøB0 *H÷ }oEK8 žÞéSd!ŒäL+þ@¬Ø 9j¡2!,«YþÒb}U8°7sÜôfcbœáSpRçšØRé[-ªáÞÏ¬1TÔÈØ#šï+2},È|š.wòDÑe MtµîÓst.;5rç@1Ó²Ä«çVŸãû00 aI±thÆãøSÈ¬1ÌÀ .0 *H÷ 0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not Validated0 060419000000Z 070419235959Z010U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. by Ref.,LIAB.LTD(c)9810UPersona Not Validated1402U+Digital ID Class 1 - Microsoft Full Service10UThomas Maguire1"0 *H÷ maguire_tom@emc.com00 *H÷ 0«ŒåO!² cuû!ç_ãÚFÒWðçínøíy>ÏŒ³$"ÎñÜeq¶Úß©Çï«t úK?@K¬þ[REæâËH¶#»ÇS1w\¯lúèŸa7Š)ì_eÎËê66$±s²ùxT¿4×íËª/ç£µ0²0 U00DU =0;09`HøE0*0(+https://www.verisign.com/rpa0U 0U%0++03U,0*0( & $"http://crl.verisign.com/class1.crl0 *H÷ <¢A·ë¡ø'¿ÎáÜßTî$ñ<Ü{nDa6gWÛÈØ¿€«ÉšO³Eq!ÛÃnw) Žæ5ÜÊ£Á×eF¹Dö¬«úÄ()ÌLç£4œä×Å²AÿÅ,^56¥¢Ò°®oI÷ñ¿AÿæÅ1>0:0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 + ²0 *H÷ 1 *H÷ 0 *H÷ 1 060810005802Z0# *H÷ 1j 6LSm£Eeàü}QXzßYì0g *H÷ 1Z0X0 *H÷ 0*H÷ 0 *H÷ @0+0 *H÷ (0+0 *H÷ 0ò +71ä0á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0ô*H÷ 1ä á0Ì10U VeriSign, Inc.10UVeriSign Trust Network1F0DU=www.verisign.com/repository/RPA Incorp. By Ref.,LIAB.LTD(c)981H0FU?VeriSign Class 1 CA Individual Subscriber-Persona Not ValidatedaI±thÆãøSÈ¬1ÌÀ .0 *H÷ WXŽólè1¥»€vUF;êüýj¬dýÜpÃîâa¢0Â:Î&]øÒnuçE*ð_ÚÃÌ}ÜOo±Ú,ur¿#ÜZšÃ²ÊSöÿÔË_1Áñ¢ºtj $iÀjiß7Å^êÓiX]M sXï

1 0

Updated: OGSA Teleconference
by Andreas Savva 09 Aug '06

09 Aug '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@gridforum.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060810T133000Z DTEND:20060810T153000Z TRANSP:OPAQUE SEQUENCE:3 UID:040000008200E00074C5B7101A82E0080000000010B6D95163B5C6010000000000000000100 00000525E76CA4D52FB4C89D8B8E1FAB31B6C DTSTAMP:20060809T015409Z DESCRIPTION:When: 2006年8月10日木曜日 22:30 to 2006年8月11日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0810\nSee more explanation:\nhttp://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/m sg00077.html\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (Aug. 3rd)\n - https://forge.gridforum.org/sf/go/doc13718?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) OGSA authorization call-out proposal review (Frank\, 20 min)\n> - Frank is now consulting with people in GGF (David Chadwick\, Von\n> Welch) on whether his approach can be defined within the AuthZ\n> group. If there is no agreement then he will accept the XACML\n> group's decision.\n\n3) Basic Security Profile PC review (Takuya\, 30 min)\n Takuya brings text proposal for the following PCs.\n\n>> Reviewed public comments and Takuya's proposed replies\n>> 1. Add text explaining that the Secure Channel profile is not\n>> required by all ogsa services. The introduction is probably a\n>> good place for this.\n>> 2. [Basic-Security-Profile] usage. The term is defined in the\n>> document. Takuya to check whether such special terms are used\n>> consistently and that they stand out. Refer to the WSRF BP for a\n>> similar example.\n>> 3. Ciphersuites: Agreed that it important to list acceptable\n>> ciphers.\n>> - As a first step Takuya will list up available ones (from the\n>> WS-I BSP)\; select the ones that are in common use\; and then\n>> select the ones that are considered sufficiently safe.\n>> - Review the list at the next BSP teleconf\n>> 4. Multiple keys in keyinfo field?\n>> - Takuya to talk to Von in order to understand the use case for\n>> multiple keys\; and will propose a resolution at the next BSP\n>> teleconf.\n\n4) EMS scenarios (Andreas and Steven\, 30 minutes)\n Andreas will send out revised version before the call.\n\n5) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nAug. 14 (Mon): Roadmap (Chris)\nAug. 17 (Thu): Info/data model (Ellen and Fred)\,\n EMS and data joint scenarios (Allen and Steven)\nAug. 21 (Mon):\nAug. 24 (Thu): CDDLM joint (Jun\, Dejan\, and Hiro)\nAug. 28 (Mon): Security (Takuya and Frank)\nAug. 31 (Thu): EMS scenarios (Andreas and Steven)\nSept. 4 (Mon): No call (Labor Day)\nSept. 7 (Thu): Roadmap (Chris)\, GGF18 prep (Tom and Hiro)\n\nTelecon schedule:\nhttps://forge.gridforum.org/projects/ogsa-wg/document/telecon_s chedule/\n\n<*ACTION ITEMS*>\n\n> From Aug. 3 call\n AI-0803a: Hiro to look into an option for a second EMS/Data call\n on Sep 7. Tentative\; needs confirmation with likely\n participants.\n AI-0803c: Ellen to book the IBM facility on Thursday afternoon\n AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods:\n Thursday afternoon\, Friday morning and afternoon.\n AI-0803e: Jun will provide an example of the CDL mechanism and why\n using ID/IDREF is not a good idea.\n AI-0803f: Jun will update the CDL document to remove the Environment\n variables\n\n> From July 20 F2F\n- Andreas and Hiro to revise the EMS scenario document (i.e. examples)\n so that proposal 2 is fulfilled\n + Andreas will merge Hiro's updates into the next draft\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n<postponed>\n- Steve McGough & Andreas to do a mapping from the current JSDL\n elements / terminology into the new information model structure\n (Proposed split into Description and Requirements)\n (from July 18th F2F\, postpone until Aug. 17)\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC BEGIN:VALARM TRIGGER:-PT15M ACTION:DISPLAY DESCRIPTION:Reminder END:VALARM END:VEVENT END:VCALENDAR

1 0

Re: [OGSA-AUTHZ] [ogsa-wg] Proposed agenda for Aug. 10th call
by Hiro Kishimoto 08 Aug '06

08 Aug '06

Alan's email bounced. -------- Original Message -------- Date: Tue, 08 Aug 2006 11:42:19 -0500 From: Alan Sill <alansill(a)fnal.gov> Subject: Re: [OGSA-AUTHZ] [ogsa-wg] Proposed agenda for Aug. 10th call Apologies for this call... I am interested in the topics being discussed in items 2) and 3), but have another call conference scheduled at the same time. Hope to see all of you at GGF 18. Alan On Aug 8, 2006, at 8:36 AM, Hiro Kishimoto wrote: > Hi all, > > The following is a proposed agenda for OGSA-WG telecon on Aug. 10th > Thursday from 8:30am - 10:30am (CDT). > > Dial-in numbers for Thursday: > Free: +1-888-452-0308 > Intl/Toll: +1-484-644-0505 > PIN: 71815 > > Screen share service will be provided. > URL: http://ogsa.glance.net > Session key: 0810 > See more explanation: > http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/ > msg00077.html > > 1) Early discussion (20 min) > Note taker assignment > Roll call > Telecon minutes approval (Aug. 3rd) > - https://forge.gridforum.org/sf/go/doc13718?nav=1 > Action Items status review (see the bottom of this email) > Agenda bashing > > 2) OGSA authorization call-out proposal review (Frank, 20 min) >> - Frank is now consulting with people in GGF (David Chadwick, Von >> Welch) on whether his approach can be defined within the AuthZ >> group. If there is no agreement then he will accept the XACML >> group's decision. > > 3) Basic Security Profile PC review (Takuya, 30 min) > Takuya brings text proposal for the following PCs. > >>> Reviewed public comments and Takuya's proposed replies >>> 1. Add text explaining that the Secure Channel profile is not >>> required by all ogsa services. The introduction is probably a >>> good place for this. >>> 2. [Basic-Security-Profile] usage. The term is defined in the >>> document. Takuya to check whether such special terms are used >>> consistently and that they stand out. Refer to the WSRF BP >>> for a >>> similar example. >>> 3. Ciphersuites: Agreed that it important to list acceptable >>> ciphers. >>> - As a first step Takuya will list up available ones (from the >>> WS-I BSP); select the ones that are in common use; and then >>> select the ones that are considered sufficiently safe. >>> - Review the list at the next BSP teleconf >>> 4. Multiple keys in keyinfo field? >>> - Takuya to talk to Von in order to understand the use case for >>> multiple keys; and will propose a resolution at the next BSP >>> teleconf. > > 4) EMS scenarios (Andreas and Steven, 30 minutes) > Andreas will send out revised version before the call. > > 5) Wrap up (10 min) > AOB > > <*NEXT CALL*> > Aug. 14 (Mon): Roadmap (Chris) > Aug. 17 (Thu): Info/data model (Ellen and Fred), > EMS and data joint scenarios (Allen and Steven) > Aug. 21 (Mon): > Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) > Aug. 28 (Mon): Security (Takuya and Frank) > Aug. 31 (Thu): EMS scenarios (Andreas and Steven) > Sept. 4 (Mon): No call (Labor Day) > Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) > > Telecon schedule: > https://forge.gridforum.org/projects/ogsa-wg/document/ > telecon_schedule/ > > <*ACTION ITEMS*> > >> From Aug. 3 call > AI-0803a: Hiro to look into an option for a second EMS/Data call > on Sep 7. Tentative; needs confirmation with likely > participants. > AI-0803c: Ellen to book the IBM facility on Thursday afternoon > AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: > Thursday afternoon, Friday morning and afternoon. > AI-0803e: Jun will provide an example of the CDL mechanism and why > using ID/IDREF is not a good idea. > AI-0803f: Jun will update the CDL document to remove the Environment > variables > >> From July 20 F2F > - Andreas and Hiro to revise the EMS scenario document (i.e. examples) > so that proposal 2 is fulfilled > + Andreas will merge Hiro's updates into the next draft > - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to > contribute use cases. > - Andreas to go through the minutes and formulate a reply mail to > Geoffrey on each artifact covered in these minutes. > > <postponed> > - Steve McGough & Andreas to do a mapping from the current JSDL > elements / terminology into the new information model structure > (Proposed split into Description and Requirements) > (from July 18th F2F, postpone until Aug. 17) > -- > Hiro Kishimoto > 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(a)ttu.edu ph. 806-742-4350 fax 806-742-4358 : ====================================================================

1 0

GGF18 sessions
by Hiro Kishimoto 08 Aug '06

08 Aug '06

Hi all, Given that OGSA-WG got 4 slots at GGF18 and Joel has resolved clash with OGSA-BES's session, I create wiki page for OGSA-WG sessions. Session owners: Please update them as you like in the wiki spirit of "don't comment, just do!" If necessary, I will also update official GGF18 schedule accordingly. Thanks, -- Hiro Kishimoto

2 4

Action Items from OGSA-WG F2F
by Hiro Kishimoto 07 Aug '06

07 Aug '06

Hi Michel and Bill, The following is your Action Items from OGSA and fellow WG F2F meeting. Please take them from here. - Michel to brain dump on difference between hold, suspend, can-cel. - Michel to talk to Dave on BES design pattern. + Both of these are OGSA-DMI and should be left to that WG. Delete from this list. Thanks, -- Hiro Kishimoto

2 1

OGSA F2F meeting at GGF18 survey
by Hiro Kishimoto 06 Aug '06

06 Aug '06

Hi all, OGSA-WG and fellow WGs will have F2F meeting just after GGF18, Sept. 14 (Thur) PM and Sept. 15 (Fri) AM/PM in Washington DC. Please let us know your availability and session proposals you would lead at the meeting. Zoomerang survey has been launched for this F2F. Please take a couple of minutes to answer soon (at latest by Aug. 14 Monday): http://www.zoomerang.com/survey.zgi?p=WEB225JZL9QE28 For more information on this F2F, see living wiki agenda on-line: https://forge.gridforum.org/sf/wiki/do/viewPage/projects.ogsa-wg/wiki/GGF18… Thanks, -- Hiro Kishimoto

1 0

Action Items from OGSA-WG F2F
by Hiro Kishimoto 06 Aug '06

06 Aug '06

Hi Andrew, Darren, and Steven, The following is your Action Items from OGSA and fellow WG F2F meeting. Please take them from here. - BES-WG chairs to ask the data group to define the filesystems as their work product Thanks, -- Hiro Kishimoto

1 0

Proposed agenda for Aug. 7th call
by Hiro Kishimoto 05 Aug '06

05 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 7th Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0807 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (Aug. 3rd) - https://forge.gridforum.org/sf/go/doc13718?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) Basic Security Profile PC review (30 min) Takuya brings text proposal for the following PCs. >> Reviewed public comments and Takuya's proposed replies >> 1. Add text explaining that the Secure Channel profile is not >> required by all ogsa services. The introduction is probably a >> good place for this. >> 2. [Basic-Security-Profile] usage. The term is defined in the >> document. Takuya to check whether such special terms are used >> consistently and that they stand out. Refer to the WSRF BP for a >> similar example. >> 3. Ciphersuites: Agreed that it important to list acceptable >> ciphers. >> - As a first step Takuya will list up available ones (from the >> WS-I BSP); select the ones that are in common use; and then >> select the ones that are considered sufficiently safe. >> - Review the list at the next BSP teleconf >> 4. Multiple keys in keyinfo field? >> - Takuya to talk to Von in order to understand the use case for >> multiple keys; and will propose a resolution at the next BSP >> teleconf. Frank is now in Amsterdam and ask me to move his authz-callout discussion to Thursday Aug. 10th. 3) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 10 (Thu): EMS scenarios (Andreas and Steven) Security (Frank) Aug. 14 (Mon): Roadmap (Chris) Aug. 17 (Thu): Info/data model (Ellen and Fred), EMS and data joint scenarios (Allen and Steven) Aug. 21 (Mon): Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sept. 4 (Mon): No call (Labor Day) Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) Telecon schedule: https://forge.gridforum.org/projects/ogsa-wg/document/telecon_schedule/ <*ACTION ITEMS*> > From Aug. 3 call AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) -- Hiro Kishimoto

1 1

Roadmap Editors call minutes, 8-2-06, uploaded
by Christopher Jordan 05 Aug '06

05 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the OGSA Roadmap editors call from August 2nd to GridForge, accessible at: https://forge.gridforum.org/sf/go/doc13717?nav=1 Thanks to Dona Dickinson for taking the minutes for this call. Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFE0qzwPCVtcXn6kg8RAiWGAJ9E6tHJ7/QptQRIjVCuajhVrgxsxwCdFMbX oLP9g3uVNoKfGSvUpQtNtU4= =8qOB -----END PGP SIGNATURE-----

2 1

Now that BES has been revised it's time to start defining an HPC Profile
by Marvin Theimer 04 Aug '06

04 Aug '06

Hi; Up till now the focus of HPC Profile work has effectively been to engage with the BES and JSDL working groups to try to effect changes that would be useful to the HPC Profile specification effort. As a consequence the email traffic and discussions have taken place on the BES and JSDL mailing list and teleconference calls. At the July face-to-face meeting in Argonne we made a lot of progress towards redefining BES in a manner that would nicely support an HPC Profile specification. We also discussed what kinds of restrictions would be appropriate to JSDL for the HPC Profile as well as the possibility of creating a "basic HPC execution" extension profile that could be used instead of the Posix extension in order to support non-Posix (e.g. Windows) execution systems. Given all this, it's now time to start working on a concrete HPC Profile specification. That means that you'll start seeing traffic on the HPC Profile mailing list (ogsa-hpcp-wg) and that we will start holding weekly telecon calls to make forward progress. I'm sending this email to several mailing lists in order to alert everyone to the fact that the ogsa-hpcp-wg mailing list is going to start seeing traffic and will become the locus of the discussion for the HPC Profile work. So if you're interested in participating - or just lurking and watching - please do start monitoring (and contributing to) the ogsa-hpcp-wg mailing list. One of the first things I'll be doing on the mailing list is nailing down a date and time for a recurring telecon call. Also, we've created a place on gridforge for HPC Profile-related documents: https://forge.gridforum.org/projects/ogsa-hpcp-wg/ That's where we will be putting all the documents related to the HPC Profile, including straw-man proposals. Indeed, if you have a straw-man proposal that you'd like to submit concerning any or all aspects of the HPC Profile then please feel free to post your document(s) to gridforge and alert people to them via email to the mailing list. Thanks, Marvin.

1 0

Teleconference minutes - 3 August 2006
by Andreas Savva 04 Aug '06

04 Aug '06

Attached. https://forge.gridforum.org/sf/go/doc13718?nav=1 -- Andreas Savva OGSA Teleconference - 3 August 2006 =================================== * Participants Jem Treadwell (HP) Jun Tatemura (NEC) Ellen Stokes (IBM) Dave Snelling (Fujitsu) Andreas Savva (Fujitsu) Joel Replogle (OGF) Darren Pulsipher (EMC) Dejan Milojicic (HP) Tom Maguire (EMC) Hiro Kishimoto (Fujitsu) Michel Drescher (Fujitsu) Minutes: Andreas Savva * Summary of actions AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. AI-0803b: Michel to revise and upload Joint CDDLM minutes (Done) AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. AI-0803f: Jun will update the CDL document to remove the Environment variables * July 31 minutes approved with no changes * Review of action items [Only items with updates are listed below. '+' marks added text.] - Ellen to send an email to Chris Jordan with the information needed to add these two documents to the OGSA Roadmap + Information sent. Done. - Hiro schedule a joint call with OGSA-Data to explain the Information model work before GGF18. - This could be one agenda item on the joing EMS/Data call already being schedule. + Joint call between EMS/DATA & Info Model is scheduled for August 17. Done. AI-0803a: Hiro to look into an option for a second EMS/Data call on Sep 7. Tentative; needs confirmation with likely participants. - Jun to feed back proposals 1a and 1b to the CDDLM Working Group, i.e. pass back the minutes to the WG. Ask Michel in case of any questions related to these proposals. + Discussed during this call. Closed - BES-WG chairs to ask the data group to define the filesystems as their work product + Hiro sent actions to WG chairs. Confirm that this is so and close. + Put on the agenda of the joint EMS/Data call. * July 2006 F2F minutes approval ** 20060718-pm-2 (GFS) - approved with no changes ** 20060719pm-2 (Joint Mgmt Committee) - approved with no changes. - Confirmed that there are no concrete actions on OGSA-WG at this time. ** 20060720-am-1 (Joint CDDLM) - approved with changes - Change XPath to XQuery - Modily statement on "removing environment variables from CDDLM" to removing from Posix component. (Proposal 2 correctly states this.) AI-0803b: Michel to revise and upload Joint CDDLM minutes (Done) ** 20060720-am-2 (EMS Scenarios) - approved with no changes ** 20060720-am-3 (G.Fox comments) - approved with no changes ** Roadmap minutes are not available (postponed) * GGF18 update ** B2B F2F GGF18 is probably finishing at 1pm on Thursday. Agreed to try and start the interim meeting from Thursday afternoon since many people are likely to want to leave early on Friday. Tentative start time: 2:30pm on Thursday AI-0803c: Ellen to book the IBM facility on Thursday afternoon AI-0803d: Hiro to divide GGF18 B2B F2F survey into three periods: Thursday afternoon, Friday morning and afternoon. ** GGF18 sessions - BES clashes with EMS session. Asked Joel to try and resolve it by moving one to a different slot. There are many dependencies, however. * Joint CDDLM discussion Discussed proposals from the F2F minutes (reproduced below and marked with '>') > PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document > and the CDL components - Clarified that this should be XQuery not XPath. - Agreed that it would be nice to do but it is probably a feature for the next version of CDL. It is one topic to discuss at GG18 as part of the future direction of the CDDLM-WG (See also AI-0803b) > PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in > CDL documents - Jun thinks that this is not a good idea because ID must be unique in the document and CDL inheritance may break this guarantee by creating duplicate IDs in the resulting document. CDL has a mechanism based on non-unique ids. AI-0803e: Jun will provide an example of the CDL mechanism and why using ID/IDREF is not a good idea. > * Proposals 1a and 1b are recommendations for the further > development of CDDLM Restated that both these proposals are for post-version 1.0 of CDL. > > PROPOSAL 2: Eliminate the EnvironmentVariable concept from the > PosixComponent (CDL plugin) > > * Proposal 2 is specific to the OGSA EMS scenarios document. Agreed that this is a reasonable resolution for resolving the problem with the PosixComponent and is sufficient for the EMS Scenarios document. AI-0803f: Jun will update the CDL document to remove the Environment variables (See also AI-0803b) - A normative definition of PosixComponent - At the moment there is no such definition; there are only some examples. - Agreed that a normative definition is necessary and that it is not part of CDL version 1.0. Also it is probably too late to leave it for CDL version 2.0---since it is not scheduled yet. - Tentative agreement that this should be a work item for CDDLM-WG between these two document release - Dejan and Jun with discuss this in the CDDLM-WG and seek approval as a work item after CDL 1.0.

1 0

Resignation
by Manuel Pereira 03 Aug '06

03 Aug '06

Dear Colleagues, It is with genuine sincerity that I express my gratitude for the many kind and gracious friends that I have had the opportunity to work with over the course of the past several years. I have thoroughly enjoyed participating in GGF as well as the creativity, friendly atmosphere, and stimulating activities availed by IBM. I am writing to you to inform you that I am resigning from IBM and the technical/scientific industry, including GGF and my leadership involvement. Though seemingly abrupt, this decision has been under consideration for over a year. The sole reason for my departure is in response to an inexplicable and ever increasing draw and loving desire to serve in full-time Christian ministry. I am pursuing higher education and training in one of the finest seminaries available while serving as a pastor of a regional Bible church. I leave IBM and all of my related participating activities in excellent standing and repute. I would love to share more with you, however out of respect for the diverse community of GGF, I want to invite anyone who is interested in more details or would simply like to discuss the matter to please contact me at: manuel(a)trinitybiblechurch.org. Best regards, Manuel Pereira ------------------------------------------------------ IBM Almaden Research Center 1-408-927-1935 [Tieline: 457] mpereira(a)us.ibm.com ------------------------------------------------------

1 0

Action Items from OGSA-WG F2F
by Hiro Kishimoto 02 Aug '06

02 Aug '06

Hi Andrew, Darren, Steven, Marvin, and Marty The following is your Action Items from OGSA and fellow WG F2F meeting. Please take them from here. - Marvin to do first draft of BES parallel state - draft schema - worked examples for identified specialized states Andrew and Dave S have volunteered to review the document Thanks, -- Hiro Kishimoto

1 0

Action Items from OGSA-WG F2F
by Hiro Kishimoto 02 Aug '06

02 Aug '06

Hi Andrew and Manuel, The following is your Action Items from OGSA and fellow WG F2F meeting. Please take them from here. - Frank Siebenlist, David Snelling Inline the "informational document" (written by D. Snelling & F. Siebenlist) into the normative specification document - Mark Morgan Add the formal element declaration of the ReferenceResolver (and the new element and its type) to the normative document. - Andrew Grimshaw Clarify the document purpose (as being a specification rather a profile) and align with the OGSA formal formatting. - David Snelling, Frank Siebenlist The "Web Service Endpoint Address Identifier Profile" needs to be added to the formal WS-Naming specification. - unassigned (tentatively: Frank, David) Write up the ResolverReferral solution that has been discussed at GGF17 and feed back into the WS-Naming group Thanks, -- Hiro Kishimoto

1 0

Updated: OGSA Teleconference
by Andreas Savva 02 Aug '06

02 Aug '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@gridforum.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060803T133000Z DTEND:20060803T153000Z TRANSP:OPAQUE SEQUENCE:3 UID:040000008200E00074C5B7101A82E0080000000000997D7960B5C6010000000000000000100 000001E68E842CF51A14191E3B4C9913315BE DTSTAMP:20060802T084426Z DESCRIPTION:When: 2006年8月3日木曜日 22:30 to 2006年8月4日金曜日 0:30 (GMT+09:00) 大阪、札幌、東京.\n\n*~*~*~*~*~*~*~*~*~*\n\n<pre>\n\nDial-in numbers for Thursday:\n Free: +1-888-452-0308\n Intl/Toll: +1-484-644-0505\n PIN: 71815\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0803\nSee more explanation:\nhttp://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/m sg00077.html\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (July 31)\n - https://forge.gridforum.org/sf/go/doc13712?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) July F2F meeting approval (Hiro and Andreas\, 20 min)\n Materials and minutes are available at meeting folder\nhttps://forge.gridforum.org/sf/docman/do/listDocuments/projects.og sa-wg/docman.root.meeting_materials_and_minutes.interim_meetings.2006_summe r_interim\n\n Approve minutes 20060720-am-{1\,2\,3} and of\n the Joint Mgmt committee meeting.\n\n3) CDDLM joint discussion (Jun\, Dejan\, and Hiro\, 60 min)\n minutes from OGSA F2F meeting on July 20.\n> PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document \n> and the CDL components\n> PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in\n> CDL documents\n> \n> * Proposals 1a and 1b are recommendations for the further development of CDDLM\n> \n> PROPOSAL 2: Eliminate the EnvironmentVariable concept from the PosixComponent\n> (CDL plugin)\n> \n> * Proposal 2 is specific to the OGSA EMS scenarios document.\n\n See attached minutes.\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nAug. 7 (Mon): Security (Takuya and Frank)\nAug. 10 (Thu): EMS scenarios (Andreas and Steven)\nAug. 14 (Mon): Roadmap (Chris)\nAug. 17 (Thu): Info/data model (Ellen and Fred)\,\n EMS and data joint scenarios (Allen and Steven)\nAug. 21 (Mon):\nAug. 24 (Thu): CDDLM joint (Jun\, Dejan\, and Hiro)\nAug. 28 (Mon): Security (Takuya and Frank)\nAug. 31 (Thu): EMS scenarios (Andreas and Steven)\nSept. 4 (Mon): No call (Labor Day)\nSept. 7 (Thu): Roadmap (Chris)\, GGF18 prep (Tom and Hiro)\n\n<*ACTION ITEMS*>\n\n > From July 31 call\n- Ellen to send an email to Chris Jordan with the information\n needed to add these two documents to the OGSA Roadmap\n- Hiro Schedule a joint call with OGSA-Data to explain the\n Information model work before GGF18.\n + This could be one agenda item on the joing EMS/Data call\n already being schedule.\n\n > From July 20 F2F\n- Andreas and Hiro to revise the EMS scenario document (i.e. examples)\n so that proposal 2 is fulfilled\n + Andreas will merge Hiro's updates into the next draft\n- Jun to feed back proposals 1a and 1b to the CDDLM Working Group\,\n i.e. pass back the minutes to the WG. Ask Michel in case of any\n questions related to these proposals.\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n > From July 17 F2F\n- BES-WG chairs to ask the data group to define the\n filesystems as their work product\n\n<postponed>\n- Steve McGough & Andreas to do a mapping from the current JSDL\n elements / terminology into the new information model structure\n (Proposed split into Description and Requirements)\n (from July 18th F2F\, postpone until Aug. 17)\n\n</pre>\n SUMMARY:Updated: OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC END:VEVENT END:VCALENDAR

1 0

Proposed agenda for Aug. 3rd call
by Hiro Kishimoto 02 Aug '06

02 Aug '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on Aug. 3rd Thursday from 8:30am - 10:30am (CDT). Dial-in numbers for Thursday: Free: +1-888-452-0308 Intl/Toll: +1-484-644-0505 PIN: 71815 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0803 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (July 31) - https://forge.gridforum.org/sf/go/doc13712?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) July F2F meeting approval (Hiro and Andreas, 20 min) Materials and minutes are available at meeting folder https://forge.gridforum.org/sf/docman/do/listDocuments/projects.ogsa-wg/doc… Approve minutes 20060720-am-{1,2,3} and of the Joint Mgmt committee meeting. 3) CDDLM joint discussion (Jun, Dejan, and Hiro, 60 min) minutes from OGSA F2F meeting on July 20. > PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document > and the CDL components > PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in > CDL documents > > * Proposals 1a and 1b are recommendations for the further development of CDDLM > > PROPOSAL 2: Eliminate the EnvironmentVariable concept from the PosixComponent > (CDL plugin) > > * Proposal 2 is specific to the OGSA EMS scenarios document. See attached minutes. 4) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 7 (Mon): Security (Takuya and Frank) Aug. 10 (Thu): EMS scenarios (Andreas and Steven) Aug. 14 (Mon): Roadmap (Chris) Aug. 17 (Thu): Info/data model (Ellen and Fred), EMS and data joint scenarios (Allen and Steven) Aug. 21 (Mon): Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sept. 4 (Mon): No call (Labor Day) Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) <*ACTION ITEMS*> > From July 31 call - Ellen to send an email to Chris Jordan with the information needed to add these two documents to the OGSA Roadmap - Hiro Schedule a joint call with OGSA-Data to explain the Information model work before GGF18. + This could be one agenda item on the joing EMS/Data call already being schedule. > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - Jun to feed back proposals 1a and 1b to the CDDLM Working Group, i.e. pass back the minutes to the WG. Ask Michel in case of any questions related to these proposals. - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. > From July 17 F2F - BES-WG chairs to ask the data group to define the filesystems as their work product <postponed> - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) (from July 18th F2F, postpone until Aug. 17) -- Hiro Kishimoto ** Participants ** David Snelling, Fujitsu Hiro Kishimooto, Fujitsu Andreas Savva, Fujitsu Michel Drescher, Fujitsu Jay Unger, IBM Jun Tatemura, NEC (via phone) * Jun walks the group through the document "Designing a POSIX component in CDL" written by Jun and with latest edits from Hiro. * Hiro asks Jun to correct his edits while walking through the document. - The newly added elements "cmp:CodeBase" and "bcp:ArchiveType" are effectively the same as "bcp:Binary". * An example in the document is provided how to use these elemeents. * Andreas asks whether the "cdl:ArchiveTye" element is a global element, or an anonmous sub-element of "cdl:PosixApplication". * bcp:PosixApplication is a base type. It is extended to e.g. define the BLAST appplication ddescription for a CDDLM system. * [example XML document] Andreas asks whether the name of a declared file system can be a child element instead of being part of the element name itself. - Yes, this is possible, as given in a proposal later in this document. * Andreas asks whether there is a way to define that the value of an element comes from another element in that CDL document, or whether that is out of scope of CDDLM. - It is not defined by either CDL language spec or component model spec. It should be part of the BasicPosixComponent spec. * Hiro proposes to remove the Environment Variable concept from CDDLM. - Because components can give predefined information that otherwise would have to be encoded in Environment Variables. - The Environment Variables concept os too general to transport such semantically special information like cdl:Hostname (where the applicaiton is to be deployed to). * The group discusses the Environment Variable cconcept, particularly the possibility that, through CDL, the values of certain environment variables can be retrieved from the target deployment system. The group shows consensus that the CDL document needs to carry enviroment variables that must be set on the target system so that the configured application can run. * The group discusses the relationships between "cdl:FileSystem" declarations and the definition of "lazy environment variables". In particular, the group is wondering about the exact mechanismms how the operation that provides the provisioning of the requested FileSystem feeds back the moint point of that file system into the appropriate environment variable PROPOSAL 1a: Use XPath 2.0 as an interface between the CDL document and the CDL components PROPOSAL 1b: Use xsd:ID/xsd:IDREF to allow relations between elements in CDL documents * Proposals 1a and 1b are recommendations for the further development of CDDLM PROPOSAL 2: Eliminate the EnvironmentVariable concept from the PosixComponent (CDL plugin) * Proposal 2 is specific to the OGSA EMS scenarios document. ** Action Items ** 1) Revise the scenario document (i.e. examples) so that proposal 2 is fulfilled (Andreas, Hiro) 2) Feed back proposals 1a and 1b to the CDDLM Working Group, i.e. pass back the minutes to the WG. Ask Michel in case of any questions related to these proposals. (Jun)

1 0

OGSA F2F RNS/GFS minutes uploaded
by Christopher Jordan 01 Aug '06

01 Aug '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I've uploaded the minutes of the F2F RNS/GFS session to GridForge. Hiro and Andreas, please feel free to edit them or e-mail me to add anything I may have missed, as I was simultaneously presenting and trying to listen, so it's easily conceivable that I didn't get it all. The minutes are available at: https://forge.gridforum.org/sf/go/doc13713?nav=1 Thanks, Chris Jordan Data Reliability Manager San Diego Supercomputer Center ctjordan(a)sdsc.edu 858.534.8347 "Mother, I feel so far away from everything." - The Enigma of Kaspar Hauser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (Darwin) iD8DBQFEztzEPCVtcXn6kg8RAvrzAJ0Tp5zVjWNGcpvgnPi+7T0ToCNATACfcvzt bfdri5KJYE7XxfGB9yZZsgs= =KYhV -----END PGP SIGNATURE-----

1 0

Teleconference minutes - 31 July 2006
by Andreas Savva 01 Aug '06

01 Aug '06

Minutes attached. https://forge.gridforum.org/sf/go/doc13712?nav=1 -- Andreas Savva Fujitsu Laboratories Ltd OGSA Teleconference - 31 July 2006 ================================== * Participants Chris Jordan (SDSC) Hiro Kishimoto (Fujitsu) Fred Maciel (Hitachi) Andreas Savva (Fujitsu) Ellen Stokes (IBM) Jem Treadwell (HP) Jay Unger (IBM) Ken Wood (Hitachi) Minutes: Andreas Savva * July 13 minutes approved with no changes * Summary of new actions ACTION: Ellen to send an email to Chris Jordan with the information needed to add these two documents to the OGSA Roadmap ACTION: Chris jordan to upload GFS and Roadmap minutes ACTION: Schedule a joint call with OGSA-Data to explain the Information model work before GGF18. - This could be one agenda item on the joing EMS/Data call already being schedule. - Ellen is unavailable from Aug 18 to Sep 4. * Action items review [Only items with updates are shown below] - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled + Andreas will merge Hiro's updates into the next draft - Michel to brain dump on difference between hold, suspend, cancel. - Michel to talk to Dave on BES design pattern. + Both of these are OGSA-DMI and should be left to that WG. Delete from this list. - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) + This is for the September OGF but some discussion/review on a call before the meeting might be good. Leave it on the list but there is no need to review progress on each call. Check again at the next Information Model call. + Agreed to move the Information Model discussion from Aug'14 to Aug'17 so that a prospective participant from Italy can join. - Frank Siebenlist, David Snelling Inline the "informational document" (written by D. Snelling & F. Siebenlist) into the normative specification document - Mark Morgan Add the formal element declaration of the ReferenceResolver (and the new element and its type) to the normative document. - Andrew Grimshaw Clarify the document purpose (as being a specification rather a profile) and align with the OGSA formal formatting. - David Snelling, Frank Siebenlist The "Web Service Endpoint Address Identifier Profile" needs to be added to the formal WS-Naming specification. - unassigned (tentatively: Frank, David) Write up the ResolverReferral solution that has been discussed at GGF17 and feed back into the WS-Naming group + These five actions are for OGSA-Naming and should be left to that WG. Delete from this list. - Marvin to do first draft of BES parallel state - draft schema - worked examples for identified specialized states Andrew and Dave S have volunteered to review the document + This action is for the HPC-Profile/BES-WG and should be deleted from this list. - BES-WG chairs to ask the data group to define the filesystems as their work product + This is BES & Data action and fits in a more general discussion between EMS & Data. Include it on an agenda of a joint EMS/Data call. * July F2F minutes review ** Discussed ways of making the meeting materials more approachable. - Agreed as proposed by Andreas that in the future the Agenda/Meeting overview should be done in the Wiki and that it should be updated with links to the minutes and presentations of each session. Also a short conclusion to each session should be put in this meeting wiki page - The meeting folder do not need to be organized differently. ** Minutes of 20060717-am_1 (Info Model) - approved with no changes ** Minutes of 20060718-am_1 (Info Model) - approved with no changes - Discussed deliverables of the Info Model design team. - Agreed to stay with the current two document structure of a guidelines (Fred) and position/architecture (Ellen) document. - There are a number of actions on various groups (BES mainly, but also HPCP and JSDL) to provide input and these should be added to the expected material for GGF18. ACTION: Ellen to send an email to Chris Jordan with the information needed to add these two documents to the OGSA Roadmap ** Minutes of 20060717-am_2 (Data) - approved with no changes ** Minutes of 20060717-pm (BES) - approved with no changes ** Minutes of 20060718-am_2 (BES) - approved with no changes ** Minutes of 20060718-am_bes2 (BES) - approved with no changes ** Minutes of 20060717-pm-2 (HPCP) - approved with no changes ** Minutes of 20060718-pm_1 (Naming) - approved with no changes ** Minutes of 20060718-pm_3 (Ad hoc JSDL) - approved with no changes ** Minutes of 20060719-am_1 (DMI) - approved with no changes ** Minutes of 20060719-am_2 (GGF18) - approved with no changes ** Postponed approval of remaining minutes 20060720-am-{1,2,3} and of the Joint Mgmt committee meeting. ACTION: Chris jordan to upload GFS and Roadmap minutes * Information model Discussion of Information Model postponed. As discussed(?) during the F2F a joint call with Data should be arranged. ACTION: Schedule a joint call with OGSA-Data to explain the Information model work before GGF18. - This could be one agenda item on the joing EMS/Data call already being schedule. - Ellen is unavailable from Aug 18 to Sep 4.

1 0

regrets
by Maguire_Tom＠emc.com 31 Jul '06

31 Jul '06

Flight delays have me in the air during the call Tom +1 (845) 729-4806 Blackberry Connect for Palm

1 0

Proposed agenda for July 31st call
by Hiro Kishimoto 31 Jul '06

31 Jul '06

Hi all, The following is a proposed agenda for OGSA-WG telecon on July 31st Monday from 5pm to 7pm (CDT). The dial-in number for Monday; US: +1 718 3541071 (New York) or +1 408 9616509 (San Jose) UK: +44 (0)207 3655269 (London) Japan: +81 (0)3 3570 8225 (Tokyo) PIN: 4371991 Screen share service will be provided. URL: http://ogsa.glance.net Session key: 0731 See more explanation: http://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/msg00077.html 1) Early discussion (20 min) Note taker assignment Roll call Telecon minutes approval (July 13) - https://forge.gridforum.org/sf/go/doc13654?nav=1 Action Items status review (see the bottom of this email) Agenda bashing 2) July F2F meeting approval (Hiro and Andreas, 30 min) Materials and minutes are available at meeting folder https://forge.gridforum.org/sf/docman/do/listDocuments/projects.ogsa-wg/doc… Chris Jordan and Joel: Please upload minutes from GFS, roadmap, and Joint Management Committee 3) info/data resource model discussion (Ellen and Fred, 60 min) Following discussion on info/data model from F2F GFS info/data model feedback (Chris Jordan) 4) Wrap up (10 min) AOB <*NEXT CALL*> Aug. 3 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 7 (Mon): Security (Takuya and Frank) Aug. 10 (Thu): EMS scenarios (Andreas and Steven) Aug. 14 (Mon): Info/data model (Ellen and Fred), Roadmap (Chris) Aug. 17 (Thu): Aug. 21 (Mon): Aug. 24 (Thu): CDDLM joint (Jun, Dejan, and Hiro) Aug. 28 (Mon): Security (Takuya and Frank) Aug. 31 (Thu): EMS scenarios (Andreas and Steven) Sept. 4 (Mon): No call (Labor Day) Sept. 7 (Thu): Roadmap (Chris), GGF18 prep (Tom and Hiro) <*ACTION ITEMS*> > From July 20 F2F - Andreas and Hiro to revise the EMS scenario document (i.e. examples) so that proposal 2 is fulfilled - Jun to feed back proposals 1a and 1b to the CDDLM Working Group, i.e. pass back the minutes to the WG. Ask Michel in case of any questions related to these proposals. - EGR-WG (Ravi) will contact Geoffrey Fox and invites him to contribute use cases. - Andreas to go through the minutes and formulate a reply mail to Geoffrey on each artifact covered in these minutes. > From July 19 F2F - Michel to brain dump on difference between hold, suspend, cancel. - Michel to talk to Dave on BES design pattern. - Hiro to lunch zoomerang survey for GGF18 B2B F2F meeting about availability and personal info need for entrance (Name, address, affiliation, nationality) > From July 18 F2F - Steve McGough & Andreas to do a mapping from the current JSDL elements / terminology into the new information model structure (Proposed split into Description and Requirements) - Frank Siebenlist, David Snelling Inline the "informational document" (written by D. Snelling & F. Siebenlist) into the normative specification document - Mark Morgan Add the formal element declaration of the ReferenceResolver (and the new element and its type) to the normative document. - Andrew Grimshaw Clarify the document purpose (as being a specification rather a profile) and align with the OGSA formal formatting. - David Snelling, Frank Siebenlist The "Web Service Endpoint Address Identifier Profile" needs to be added to the formal WS-Naming specification. - unassigned (tentatively: Frank, David) Write up the ResolverReferral solution that has been discussed at GGF17 and feed back into the WS-Naming group - Marvin to do first draft of BES parallel state - draft schema - worked examples for identified specialized states Andrew and Dave S have volunteered to review the document > From July 17 F2F - BES-WG chairs to ask the data group to define the filesystems as their work product -- Hiro Kishimoto

2 1

OGSA Teleconference
by Andreas Savva 31 Jul '06

31 Jul '06

BEGIN:VCALENDAR PRODID:-//Microsoft Corporation//Outlook 11.0 MIMEDIR//EN VERSION:2.0 METHOD:REQUEST BEGIN:VEVENT ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE:MAILTO:ogsa-wg@gridforum.org ORGANIZER:MAILTO:andreas.savva@jp.fujitsu.com DTSTART:20060731T220000Z DTEND:20060801T000000Z LOCATION:http://ogsa.glance.net TRANSP:OPAQUE SEQUENCE:0 UID:040000008200E00074C5B7101A82E0080000000020B5CF668BB4C6010000000000000000100 00000465344717779FD4AB08A341DC17A35EA DTSTAMP:20060731T012344Z DESCRIPTION:When: 2006年8月1日火曜日 7:00-9:00 (GMT+09:00) 大阪、札幌、東京.\nWhere: http://ogsa.glance.net\n\n*~*~*~*~*~*~*~*~*~*\n\n\n------------\nFrom: owner-ogsa-wg(a)ggf.org on behalf of Hiro Kishimoto [hiro.kishimoto(a)jp.fujitsu.com]\nSent: 2006年7月30日日曜日 14:22\nTo: OGSA WG\; Joel Replogle\nSubject: [ogsa-wg] Proposed agenda for July 31st call\n\nHi all\,\n\nThe following is a proposed agenda for OGSA-WG telecon on July 31st\nMonday from 5pm to 7pm (CDT).\n\nThe dial-in number for Monday\;\n US: +1 718 3541071 (New York) or\n +1 408 9616509 (San Jose)\n UK: +44 (0)207 3655269 (London)\n Japan: +81 (0)3 3570 8225 (Tokyo)\n PIN: 4371991\n\nScreen share service will be provided.\n URL: http://ogsa.glance.net\n Session key: 0731\nSee more explanation:\nhttp://www-unix.gridforum.org/mail_archive/ogsa-wg/2004/06/m sg00077.html\n\n1) Early discussion (20 min)\n Note taker assignment\n Roll call\n Telecon minutes approval (July 13)\n - https://forge.gridforum.org/sf/go/doc13654?nav=1\n Action Items status review (see the bottom of this email)\n Agenda bashing\n\n2) July F2F meeting approval (Hiro and Andreas\, 30 min)\n Materials and minutes are available at meeting folder\nhttps://forge.gridforum.org/sf/docman/do/listDocuments/projects.og sa-wg/docman.root.meeting_materials_and_minutes.interim_meetings.2006_summe r_interim\n\n Chris Jordan and Joel: Please upload minutes from GFS\,\n roadmap\, and Joint Management Committee\n\n3) info/data resource model discussion (Ellen and Fred\, 60 min)\n Following discussion on info/data model from F2F\n GFS info/data model feedback (Chris Jordan)\n\n4) Wrap up (10 min)\n AOB\n\n<*NEXT CALL*>\nAug. 3 (Thu): CDDLM joint (Jun\, Dejan\, and Hiro)\nAug. 7 (Mon): Security (Takuya and Frank)\nAug. 10 (Thu): EMS scenarios (Andreas and Steven)\nAug. 14 (Mon): Info/data model (Ellen and Fred)\, Roadmap (Chris)\nAug. 17 (Thu):\nAug. 21 (Mon):\nAug. 24 (Thu): CDDLM joint (Jun\, Dejan\, and Hiro)\nAug. 28 (Mon): Security (Takuya and Frank)\nAug. 31 (Thu): EMS scenarios (Andreas and Steven)\nSept. 4 (Mon): No call (Labor Day)\nSept. 7 (Thu): Roadmap (Chris)\, GGF18 prep (Tom and Hiro)\n\n<*ACTION ITEMS*>\n\n> From July 20 F2F\n- Andreas and Hiro to revise the EMS scenario document (i.e. examples)\n so that proposal 2 is fulfilled\n- Jun to feed back proposals 1a and 1b to the CDDLM Working Group\,\n i.e. pass back the minutes to the WG. Ask Michel in case of any\n questions related to these proposals.\n- EGR-WG (Ravi) will contact Geoffrey Fox and invites him to\n contribute use cases.\n- Andreas to go through the minutes and formulate a reply mail to\n Geoffrey on each artifact covered in these minutes.\n\n> From July 19 F2F\n- Michel to brain dump on difference between hold\, suspend\, cancel.\n- Michel to talk to Dave on BES design pattern.\n- Hiro to lunch zoomerang survey for GGF18 B2B F2F meeting\n about availability and personal info need for entrance\n (Name\, address\, affiliation\, nationality)\n\n> From July 18 F2F\n- Steve McGough & Andreas to do a mapping from the current JSDL\n elements / terminology into the new information model structure\n (Proposed split into Description and Requirements)\n- Frank Siebenlist\, David Snelling\n Inline the "informational document" (written by D. Snelling & F. \nSiebenlist)\n into the normative specification document\n- Mark Morgan\n Add the formal element declaration of the ReferenceResolver (and the \nnew\n element and its type) to the normative document.\n- Andrew Grimshaw\n Clarify the document purpose (as being a specification rather a \nprofile) and\n align with the OGSA formal formatting.\n- David Snelling\, Frank Siebenlist\n The "Web Service Endpoint Address Identifier Profile" needs to be \nadded to\n the formal WS-Naming specification.\n- unassigned (tentatively: Frank\, David)\n Write up the ResolverReferral solution that has been discussed at GGF17\n and feed back into the WS-Naming group\n- Marvin to do first draft of BES parallel state\n - draft schema\n - worked examples for identified specialized states\n Andrew and Dave S have volunteered to review the document\n\n> From July 17 F2F\n- BES-WG chairs to ask the data group to define the\n filesystems as their work product\n\n-- \nHiro Kishimoto\n\n\n\n\n\n\n\n\n SUMMARY:OGSA Teleconference PRIORITY:5 X-MICROSOFT-CDO-IMPORTANCE:1 CLASS:PUBLIC END:VEVENT END:VCALENDAR

1 0

Please review the OGSA Data documents
by Dave Berry 27 Jul '06

27 Jul '06

This is a reminder that OGSA WG members are requested to review the current versions of the OGSA Data documents and send us your thoughts and comments. The current drafts of the OGSA Data Architecture and OGSA Data Services documents can be found at https://forge.gridforum.org/sf/go/doc13635?nav=1 and https://forge.gridforum.org/sf/go/doc13605?nav=1 respectively. Best wishes, Dave Berry Deputy Director, Research & E-infrastructure Development National e-Science Centre, 15 South College Street Edinburgh, EH8 9AA Tel: +44 131 651 4039

1 0

Final Glossary 1.5 uploaded
by Treadwell, Jem 24 Jul '06

24 Jul '06

Hi, Thanks to everyone who participated in the "last-call" discussion, especially to Dave Snelling and Dave Berry for the final wording. I've now uploaded drafts 10 & 11 of the Glossary, for Andreas to submit for publication. Draft 10 incorporates the last-call comments and has all of the 1.5 markup, and Draft 11 has all changes accepted. These are the two definitions that changed, per discussion at last week's f2f: Agreement: An agreement defines a dynamically established and dynamically managed relationship between two parties. The object of the relationship is the exchange of services between the parties within the context of the agreement. The management of this relationship is achieved by agreeing on the respective roles, rights and obligations of the parties. The agreement may specify not only functional properties for identification or creation of services, but also non-functional properties of the services such as performance or availability. Entities can dynamically establish and manage agreements via Web service interfaces. See https://forge.gridforum.org/projects/graap-wg for information about work being carried out by the GGF's Grid Resource Allocation Agreement Protocol (GRAAP) working group. Endpoint, end point: A specific location to which a client may bind in order to access a Web service, using a specific protocol and data format. - Jem ________________________________ Jem Treadwell Hewlett-Packard Company 6000 Irwin Road Mount Laurel, NJ 08054 Phone: 856-638-6021 Fax: 856-638-6190 E-mail: Jem.Treadwell(a)hp.com <mailto:Jem.Treadwell@hp.com>

1 0