Hi,
- As I -explained in an earlier mail, "limited" here means that the PGI profile -shall precisely described in a self-contained way the minimum set of EPR -elements which must be supported by conforming inplementations.
So far, I guess we only depend on the wsa:To element of the specification with the URI making it the minimum element of it. With WS-Naming this would be expanded using wsa:metadata and ws-naming elements of course. Isn't our usual procedure to take the URI - encode an EPR (with wsa:To) and send it to the BES systems? Or is this maybe only my narrow UNICORE view of how we do it? Q: What is meant by accessing a CREAM-BES and A-REX with URI (instead of EPRs)? Thanks for clarification, Morris ------------------------------------------------------------ Morris Riedel SW - Engineer Distributed Systems and Grid Computing Division Jülich Supercomputing Centre (JSC) Forschungszentrum Juelich Wilhelm-Johnen-Str. 1 D - 52425 Juelich Germany Email: m.riedel@fz-juelich.de Info: http://www.fz-juelich.de/jsc/JSCPeople/riedel Phone: +49 2461 61 - 3651 Fax: +49 2461 61 - 6656 Skype: MorrisRiedel "We work to better ourselves, and the rest of humanity" Sitz der Gesellschaft: Jülich Eingetragen im Handelsregister des Amtsgerichts Düren Nr. HR B 3498 Vorsitzende des Aufsichtsrats: MinDirig'in Bärbel Brumme-Bothe Vorstand: Prof. Dr. Achim Bachem (Vorsitzender), Dr. Ulrich Krafft (stellv. Vorsitzender)
------Original Message----- -From: Moreno Marzolla [mailto:moreno.marzolla@pd.infn.it] -Sent: Friday, March 20, 2009 10:29 AM -To: m.riedel@fz-juelich.de -Cc: pgi-wg@ogf.org -Subject: Re: [Pgi-wg] Sec: Agreement on WS-Naming (ref by strawman) - -m.riedel@fz-juelich.de wrote: -[...] -> # (A) Which middleware platform is adopting it currently and has -> precise plans to adopt it in the near future. We can list for now -> GENESIS-II adopting it while I know that UNICORE does not and has no -> precise plans for it now - what about others like gLite, ARC, or -> NAREGI? - -Hi all, - -as far as I know, iEPRs are not currently used in gLite (for sure they -are not currently used in the job management components). I am aware of -no specific short-to-medium term plans to support them. - -Nevertheless, I think that Secure Addressing is a nice solution to the -problem of advertising the security profile adopted by an endpoint. As -Aleksandr correctly points out, if EPRs are not going to be used as -complete replacements of URIs (in which case major modifications to most -of middleware components would be required, and that would be very -problematic), I support the idea of using a limited form of EPRs. As I -explained in an earlier mail, "limited" here means that the PGI profile -shall precisely described in a self-contained way the minimum set of EPR -elements which must be supported by conforming inplementations. - -Moreno. - --- -Moreno Marzolla -INFN Sezione di Padova, via Marzolo 8, 35131 PADOVA, Italy -EMail: moreno.marzolla@pd.infn.it Phone: +39 049 8277103 -WWW : http://www.dsi.unive.it/~marzolla Fax : +39 049 8756233