[gfs-wg] Naming requirements document/Directory Services discussion

[Christopher Jordan]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

For those not on the OGSA-Naming or OGSA-WG mailing lists.

There will be a call tomorrow morning to discuss the WS-Naming and  
requirements drafts, as well as coming to closure on consensus  
regarding RNS. I will be attending the call specifically to advocate  
for the work we're currently undertaking with RNS refactoring, and  
also to make sure we get a good list of requirements in case there  
are any that haven't already been communicated to Manuel, but I  
encourage other members of the GFS-WG to attend as well, since this  
work is obviously crucial to our own progress. Details are below.

You can get the draft documents in question, including WS-Directory,  
from GridForge, in the OGSA-Naming area. As Andrew requested, please  
read the documents beforehand if you plan on actively participating.

Thanks.

Begin forwarded message:

> From: Hiro Kishimoto <hiro.kishimoto at jp.fujitsu.com>
> Date: April 27, 2006 8:11:14 PM PDT
> Subject: Re: [ogsa-naming-wg] Re: [ogsa-wg] Naming requirements  
> document
>
> Hi Mike,
>
> I think the call is Friday April 28th, at 10 AM eastern
> dial in information is 1-877-422-0033 Passcode: 348140
> ----
> Hiro Kishimoto
>
>> Andrew Grimshaw wrote:
>>> All,
>>>
>>> Recall that back at the January face-to-face Frank and Dave took  
>>> an action
>>> to write up their take on the requirements for (low-level)  
>>> naming. Attached
>>> is their draft.
>>>
>>>
>>> A few comments of mine based on my read and discussions of the  
>>> document with
>>> Dave.
>>>
>>>
>>>
>>> 1)    This is not intended as a replacement for the existing work.
>>>
>>> 2)    It is requirements - not specifications. Rather, it is a  
>>> call for
>>> specifications that address the requirements.
>>>
>>> 3)    Several of the requirements are met by the existing WS- 
>>> Naming draft
>>> specification, though some are not.
>>>
>>> 4)    Two of the proposed "specifications", 5.2 and 5.4 are  
>>> covered by the
>>> existing WS-Name specification. A variant of 5.3 is covered in  
>>> the WS-Name
>>> spec. The variant specified a technique that could be used to  
>>> ensure that
>>> identifying information would be sent with the headers  -  
>>> specifically embed
>>> names in the reference parameters. Personally I fell that 5.3 is  
>>> a fine
>>> replacement for that if desired. 5.1 is not covered at all, and I  
>>> must
>>> confess that it seems so obvious that I had implicitly assumed it  
>>> true. Dave
>>> says it is not - so having a spec that says it must be true seems  
>>> ok to me.
>>>
>>> 5)    I think that with a small amount of work on this document  
>>> and the
>>> WS-Name spec we can make them dovetail quite nicely.
>>>
>>>
>>>
>>>
>>>
>>> GGF is a scant two weeks away. I'd like to schedule a  
>>> teleconference with
>>> the following agenda on Friday April 28th, at 10 AM eastern.   
>>> (Dial in
>>> information as soon as I find a dial in number we can use.)  If  
>>> you plan on
>>> attending, PLEASE read both the existing draft WS-Name spec and this
>>> document before the call.
>>>
>>>
>>>
>>> Proposed Agenda:
>>>
>>> Max time             Subject
>>>
>>> 5 minutes            Agenda bashing
>>>
>>> 30 minutes          Discuss draft requirements document including  
>>> vis a vis
>>> existing draft WS-Name document
>>>
>>> 30 minutes          Discuss approval of DRAFT WS-Names document  
>>> to send to
>>> GFSG for GFSG approval. Note                                  we  
>>> will
>>> prepare a version that does not include the language that  
>>> overlaps 5.3.
>>>
>>> 25 minutes          Attempt to come to closure on working group  
>>> consensus
>>> regarding WS-Directory, RNS, or
>>>                             failing that, at least what the  
>>> issues are.
>>>

- ----------------------------------------------------
Chris Jordan
HPC Systems Engineer
High End Computing Systems Group
San Diego Supercomputer Center
ctjordan at sdsc.edu
858.534.8347

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEUY+3PCVtcXn6kg8RAnKUAKCzFZ+WlmUPgTcxGuZK5fGMcjar3ACgjVok
1X5tq5TPiKcr/AwErL5KZeM=
=b15y
-----END PGP SIGNATURE-----