From jim_pruyne at hp.com  Wed Mar  1 02:49:38 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 01 Mar 2006 00:49:38 -0800
Subject: [graap-wg] telecon on 3/1
Message-ID: <44056022.3090004@hp.com>

We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
the same.
The time is:
9:00AM Central Time US (GMT-0600, I think)
which should be:
10:00AM Eastern Time US
1500 UK
1600 Germany
midnight Japan
2200 Thailand

Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
US.
Conference code #8578310.

--- Jim




From jim_pruyne at hp.com  Mon Mar  6 11:48:22 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Mon, 06 Mar 2006 11:48:22 -0600
Subject: [graap-wg] [Fwd: [ogsa-wg] CFP: Special Session on "Service Level Agreements"
 at HPCC-06]
Message-ID: <440C75E6.2080804@hp.com>



-------- Original Message --------
Subject: 	[ogsa-wg] CFP: Special Session on "Service Level Agreements" 
at HPCC-06
Date: 	Mon, 6 Mar 2006 12:55:16 +0100
From: 	Benno Overeinder <bjo at cs.vu.nl>
To: 	ogsa-wg at gridforum.org



Please accept our apologies for cross-posting.

**********************************************************************

Call for Papers: Special Session on "Service Level Agreements" at HPCC-06

In distributed environments, applications often make use of
pre-defined resources (and services) defined statically at the start
of application execution. However, such resources may either not be
appropriate or available every time execution is requested --
therefore requiring the use of a registry service to discover
resources dynamically.

It is also possible that resources may be owned by
institutions/individuals within another administrative domain --
outside the direct control of the application manager. It is therefore
necessary to make use of Service Level Agreements (SLAs) to provide
the interface between application users making demands on resources,
and resource providers determining what should be made available for
external use.

An SLA may define: (i) requirements that such an application would
place on resources (and services) owned by another third party; (ii)
check whether these requirements have been met during use. The
complexity of an SLA can vary from a static description of resource
names (specified in terms of IP addresses) to complex constraints
defined as functions that can be evaluated at deployment time.

The aim of this special session is to bring together researchers in
high performance computing, networking infrastructure and application
sciences to demonstrate how SLAs may be defined, managed, updated and
used.

The following topics provide some guidance on content appropriate for
this special session:

    * Description techniques for SLAs
    * Static vs. dynamic SLAs
    * Validation techniques for SLA parameters
    * Matchmaking approaches for SLA comparisons
    * Discovering resources based on SLA descriptions
    * Comparison of SLA and policy descriptions
    * Penalty clauses for SLAs + legal issues
    * Managing user expectations via SLAs
    * SLA descriptions and Quality of Service
    * Multi-party SLAs
    * Aggregating multiple SLAs
    * SLAs in Virtual Organizations (both multi-party and multiple SLAs)
    * Negotiating SLAs dynamically
    * SLA-based co-scheduling and resource reservation
    * SLAs and Registry Services
    * SLA-based trust management 

SUBMISSION GUIDELINES

Submissions must include an abstract, five to ten keywords, the e-mail
address of the corresponding author and should not exceed ten pages
including tables and figures. All paper submissions must already be
formatted according to the guidelines for Lecture Notes in Computer
Science (LNCS) and represent unpublished and original
work. Manuscripts must be submitted in PDF format, usage of LaTeX as a
document preparation system is strongly encouraged. Submission of a
paper should be regarded as an undertaking that, should the paper be
accepted, at least one of the authors will register for the conference
and present the work. Submissions to HPCC-06 will be conducted
electronically on the conference website.

IMPORTANT DATES
Paper submission:		March 13, 2006
Acceptance notification: 	May 29, 2006
Camera ready version:		June 26, 2006
Conference:			September 13-15, 2006

PUBLICATION

The accepted papers will be published in proceedings of the HPCC-06
conference by Springer's Lecture Note in Computer Science (LNCS).

SPECIAL SESSION WEB SITE
http://www.cs.vu.nl/~bjo/sla/sla-cfp.html

CONFERENCE WEB SITE
http://hpcc06.lrr.in.tum.de/
http://www.hpcc-conference.org/2006/

-- 
 Benno Overeinder		 IIDS Group, Section Computer Systems,
 voice: (+31) 20 598 7634	 Department of Computer Science, Faculty 
 fax:   (+31) 20 598 7653	 of Sciences, Vrije Universiteit Amsterdam
 e-mail: bjo at cs.vu.nl		 Boelelaan 1081a, NL-1081 HV Amsterdam





From pruyne at hpl.hp.com  Tue Mar  7 18:20:39 2006
From: pruyne at hpl.hp.com (Jim Pruyne)
Date: Tue, 07 Mar 2006 18:20:39 -0600
Subject: [graap-wg] telecon on 3/8
Message-ID: <440E2357.2080607@hpl.hp.com>

We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
the same.
The time is:
9:00AM Central Time US
which should be:
10:00AM Eastern Time US
1500 UK
1600 Germany
midnight Japan
2200 Thailand

Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
US.
Conference code #8578310.

--- Jim




From jim_pruyne at hp.com  Wed Mar  8 09:12:48 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 08 Mar 2006 09:12:48 -0600
Subject: [Fwd: Re: [graap-wg] minutes from 2/8 telecon]
Message-ID: <440EF470.7090808@hp.com>

Forward of Toshi's most recent comment tracking spreadsheet.

--- Jim

-------- Original Message --------
Subject: 	Re: [graap-wg] minutes from 2/8 telecon
Date: 	Thu, 09 Feb 2006 01:33:31 +0900
From: 	Toshiyuki Nakata <nakata at mtg.biglobe.ne.jp>
Reply-To: 	t-nakata at cw.jp.nec.com
Organization: 	NEC Corporation
To: 	Jim Pruyne <jim_pruyne at hp.com>
CC: 	GRAAP-WG <graap-wg at gridforum.org>
References: 	<43EA1870.5060101 at hp.com>



Public Comment List updated.

Toshi

Jim Pruyne wrote:

> They are attached.  Next week is GGF, so there will be no conference 
> call.  We'll plan to have one the following week, on the 22nd, unless no 
> one is ready to do so soon after GGF.  Also, and updated version of the 
> spec. from today's call will be uploaded to grid-forge in a moment.
> 
> --- Jim
> 
> 


-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060208.xls
Type: application/vnd.ms-excel
Size: 100352 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060308/5dfa4e9a/attachment.xls 

From jim_pruyne at hp.com  Wed Mar  8 10:06:33 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 08 Mar 2006 10:06:33 -0600
Subject: [graap-wg] Minutes from 3/8 telecon
Message-ID: <440F0109.9040600@hp.com>

Are attached.  We'll meet next week as usual.

--- Jim


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Mar0806-minutes.txt
Url: http://www.ogf.org/pipermail/graap-wg/attachments/20060308/d6b31cc4/attachment.txt 

From nakata at mtg.biglobe.ne.jp  Wed Mar  8 10:23:37 2006
From: nakata at mtg.biglobe.ne.jp (Toshiyuki Nakata)
Date: Thu, 09 Mar 2006 01:23:37 +0900
Subject: [graap-wg] Minutes from 3/8 telecon
In-Reply-To: <440F0109.9040600@hp.com>
References: <440F0109.9040600@hp.com>
Message-ID: <440F0509.1020903@mtg.biglobe.ne.jp>

Excel Sheet Updated.

#If there's any mistakes, please let me know.
##I am abit sleepy right now. :-)
Jim Pruyne wrote:

> Are attached.  We'll meet next week as usual.
> 
> --- Jim
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060308.xls
Type: application/vnd.ms-excel
Size: 95744 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060309/377c2c0a/attachment.xls 

From O.F.Rana at cs.cardiff.ac.uk  Sat Mar 11 17:12:36 2006
From: O.F.Rana at cs.cardiff.ac.uk (Omer F Rana)
Date: Sat, 11 Mar 2006 23:12:36 +0000
Subject: [graap-wg] Negotiation/GGF17?
Message-ID: <20060311231236.GB10212@lapis.cs.cf.ac.uk>

Hi, 

At the last GGF in Athens, Wolfgang and Toshi mentioned that there was
some discussion on gathering negotiation requirements for WS-Agreement,
and that an "information" document was being produced for release in
the near future. 

Is this document already available for comment? 

I was also wondering if there is likely to be a session on GRAAP at
GGF17. 

regards
Omer

-- 
http://www.cs.cf.ac.uk/User/O.F.Rana/index.html / work-fax:+44(0)29-2087-4598
work:+44(0)29-2087-5542 / other:+44(0)7956-299981 / distributed collaborative
computing / room n2.14 / school of computer science / cardiff university 
  queen's buildings / newport road / cardiff cf24 3aa / wales / uk 




From Wolfgang.Ziegler at scai.fraunhofer.de  Sun Mar 12 02:58:01 2006
From: Wolfgang.Ziegler at scai.fraunhofer.de (Wolfgang Ziegler)
Date: Sun, 12 Mar 2006 09:58:01 +0100
Subject: [graap-wg] Negotiation/GGF17?
In-Reply-To: <20060311231236.GB10212@lapis.cs.cf.ac.uk>
References: <20060311231236.GB10212@lapis.cs.cf.ac.uk>
Message-ID: <4413E299.5060405@scai.fraunhofer.de>

Dear Omer,

Omer F Rana wrote:
> Hi, 
> 
> At the last GGF in Athens, Wolfgang and Toshi mentioned that there was
> some discussion on gathering negotiation requirements for WS-Agreement,
> and that an "information" document was being produced for release in
> the near future. 
> 
> Is this document already available for comment? 

no, that is still in the pipeline of the todos

> I was also wondering if there is likely to be a session on GRAAP at
> GGF17. 

yes, I plan to organise GRAAP sessions at GGF17. I think we will discuss
this during the next telecon on Wednesday.

Best regards

Wolfgang
> 
> regards
> Omer
> 

-- 
       Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI)
   Schloss Birlinghoven, D-53754 Sankt Augustin, Germany    scai.fraunhofer.de
Tel: +49 2241 14 2258   Fax: +49 2241 14 42258   scai.fraunhofer.de/ziegler.html 


                CoreGRID Network of Excellence   www.coregrid.net
        Collaboration Gateway   www.coregrid.net/mambo/content/viev/53/74/
           Institute on Resource Management and Scheduling coregrid.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3761 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060312/05aa136f/attachment.bin 

From jim_pruyne at hp.com  Tue Mar 14 22:53:02 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Tue, 14 Mar 2006 22:53:02 -0600
Subject: [graap-wg] telecon on 3/15
Message-ID: <44179DAE.2050100@hp.com>

We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
the same.
The time is:
9:00AM Central Time US
which should be:
10:00AM Eastern Time US
1500 UK
1600 Germany
midnight Japan
2200 Thailand

Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
US.
Conference code #8578310.

--- Jim




From hiro.kishimoto at jp.fujitsu.com  Tue Mar 14 23:03:00 2006
From: hiro.kishimoto at jp.fujitsu.com (Hiro Kishimoto)
Date: Wed, 15 Mar 2006 14:03:00 +0900
Subject: [graap-wg] Re: [dmis-bof] Updated Charter
In-Reply-To: <44178439.6090302@jp.fujitsu.com>
References: <005c01c647a5$f76e6160$7312dd8c@mcs.anl.gov> <44178439.6090302@jp.fujitsu.com>
Message-ID: <4417A004.1040608@jp.fujitsu.com>

Hi Bill,

One more comment.

Scope section says
> This Working Group will define two Web Service interfaces. The first
 > interface deals with the agreement on a particular transport protocol
 > used for a data movement. The second interface defines the invocation
 > of the data movement itself, and the associated aspects of
 > reliability, transfer scheduling, granularity, performance settings,
 > control, and progress.

Are you familiar with WS-Agreement specification by GRAAP-WG?
Can you include investigation of applicability of WS-Agreement to
your interface as an WG's activity?

Thanks,
----
Hiro Kishimoto

Hiro Kishimoto wrote:
> Hi Bill,
> 
> Thank you very much for revising WG charter document.
> In general, it sounds good to me.
> 
> The following is my comments;
> 
> (1) Goals section
> Given that GFSG is now asking all WG/RG co-chairs to maintain web based
> "Living Charter" (see attached OGSA-WG example), I recommend to
> organize goals section based on deliverable documents.
> 
> Goals section has list of documents and each document has
> - title
> - abstract
> - type
> - milestones (date for first draft, public comment, publication)
> 
> (2) transport document
> Goals section says this WG will create "transport document" but
> focus/purpose and scope sections don't mention this. Please
> explain what is transport document in these previous sections.
> 
> (3) 7 Q&A document
> Please update and send out 7 Q&A document as well as charter.
> You need to provide both to your area director for WG approval.
> 
> (4) reference
> 
> "OGSA WSRF Basic Profile Rendering 1.0, GFD.59, T. Maguire, D. Snelling,
>  Global Grid Forum, January 2006"
> 
> should be
> 
> "[OGSA WSRF BP] OGSA WSRF Basic Profile 1.0, Foster, I., Maguire, T.,
> and Snelling, D. Global Grid Forum, GWD-R, September 2005.
> http://www.ggf.org/Public_Comment_Docs/Documents/Oct-2005/draft-ggf-ogsa-wsrf-basic-profile-v43.pdf" 
> 
> 
> (5) Management issues
> I would add the following sentence to this section;
> 
> The WG will have joint review discussion with the OGSA-WG and the 
> OGSA-D-WG before every milestone.
> 
> (5) DMI
> The Desktop Management Interface (DMI) is rather well known in
> IT industry. Do you have any other alphabet soup (e.g. Interface
> of Data Movement: IDM).
> 
> p.s.
> OGSA-WG will have interim F2F meeting in San Francisco Bay Area
> from April 4-7. If you want to have session at this F2F meeting
> please provide agenda and how long do you need.
> 
> https://forge.gridforum.org/projects/ogsa-wg/document/200604F2F_session
> 
> Thanks,
> ----
> Hiro Kishimoto
> 
> William E. Allcock wrote:
> 
>> Ok, next iteration is attached.  We tried to address the comments we had
>> received so far.
>>
>> Bill
>>
>>> -----Original Message-----
>>> From: owner-dmis-bof at ggf.org [mailto:owner-dmis-bof at ggf.org] On 
>>> Behalf Of Robert B. Wood
>>> Sent: Tuesday, March 14, 2006 10:07 AM
>>> To: Michel Drescher
>>> Cc: allcock at mcs.anl.gov; dmis-bof at ggf.org
>>> Subject: Re: [dmis-bof] Updated Charter
>>>
>>> In my opinion, "4th party data transfer" as a term such as described 
>>> below offers more debate than value.  To my understanding, a 3rd 
>>> party copy operation is a data transfer between two data stores that 
>>> is initiated by [at least] one of the data stores or devices 
>>> themselves, without the aid or instruction of the user or their 
>>> server/application code.  It was originally coined in the realm of 
>>> data backup.
>>>
>>> When an agent of the user (including the user him or herself) 
>>> initiates a data transfer and the data transfer path includes the 
>>> user's system, that is a first party operation.  When an agent 
>>> initiates a data transfer directly between two data stores or 
>>> devices, without placing their server in the data stream, this is an 
>>> extended data movement operation; what is referred to as extended 
>>> copy or serverless backup in the data backup realm.
>>>
>>> The usage of these terms is pretty well codified in the SCSI-3 
>>> specification and implemented in storage products.
>>> I'm not suggesting that management of agents, like the "truly 
>>> independent service" that Michel describes is trivial, in fact the 
>>> data security aspects can be quite challenging.  Also the line 
>>> between direct control and independent operations is pretty fuzzy, as 
>>> data movements rarely occur without some user involvement, be it 
>>> simply an exersize of a service level agreement with the data storage 
>>> service provider[s].
>>>
>>> Just a couple of comments to the comments to the comments ... Bob
>>>
>>> Michel Drescher wrote:
>>>
>>>
>>>> Bill,
>>>>
>>>> some comments, related to the comments you put in the 
>>>
>>>
>>> charter document:
>>>
>>>> 4th party data transfer:
>>>> I see 3 different scenarios for data movement. Let's assume 
>>>
>>>
>>> we have a 
>>>
>>>> (data) source and a (data) destination. We also have a user that  
>>>> wants data moved. If the user is the source, we have a direct pull  
>>>> case, if the user is the destination, then we have a direct push  
>>>> case. If the user tells the source to move some data to the  
>>>> destination, then this is 3rd party push, if the user tells the  
>>>> destination to get some data, then this is 3rd party pull.
>>>> Well, if the user tells a truly independent service to initiate a  
>>>> data transfer from source to target, then this is very 
>>>
>>>
>>> similar to 3rd 
>>>
>>>> party data transfer, but different enough as there is a 4th 
>>>
>>>
>>> instance 
>>>
>>>> participating in the data movement.
>>>>
>>>> Transport protocols:
>>>> Yes I meant application level protocols from a network 
>>>
>>>
>>> point of view, 
>>>
>>>> such as GridFTP, HTTP, FTP, etc.
>>>>
>>>>
>>>> Regarding the timeline:
>>>> The short term planning is ambitious, but manageable, I think,  
>>>> especially if we can appreciate broad contribution support.
>>>>
>>>> Cheers,
>>>> Michel
>>>>
>>>> On 13 Mar 2006, at 22:41, William E. Allcock wrote:
>>>>
>>>>
>>>>> All,
>>>>>
>>>>> Michel and I have updated the charter based on discussions 
>>>
>>>
>>> that  took
>>>
>>>>> place
>>>>> at GGF16.  They are already scheduling slots for next GGF, so we  
>>>>> need to
>>>>> ratify this charter ASAP and become a full fledged working 
>>>
>>>
>>> group.  The
>>>
>>>>> charter is short, only a couple of pages of text and a table with  
>>>>> goals and
>>>>> timelines.  This shouldn't take long, so please take a few 
>>>
>>>
>>> minutes 
>>>
>>>>> now and
>>>>> review this.
>>>>>
>>>>> In particular we would like comments on:
>>>>>
>>>>> - Do you agree with the focus and scope
>>>>> - Do you think the Goals and timeline are reasonable?  
>>>
>>>
>>> Are we missing
>>>
>>>>> anything?
>>>>> - Which documents / implementations would you be willing 
>>>
>>>
>>> to work on?
>>>
>>>>> Thanks, and I hope to see you in Tokyo.
>>>>>
>>>>> Bill
>>>>>
>>>>> ---------------------------------------------------------------
>>>>> William E. Allcock
>>>>> Argonne National Laboratory
>>>>> Bldg 221, Office B-139
>>>>> 9700 South Cass Ave
>>>>> Argonne, IL 60439-4844
>>>>> Email:           allcock at mcs.anl.gov
>>>>> Office Phone:    +1-630-252-7573
>>>>> Office Fax:      +1-630-252-1997
>>>>> Cell Phone:      +1-630-854-2842
>>>>>
>>>>> <charter-v3.doc>
>>>>
>>>>
>>>>
>>> -- 
>>> Bob Wood
>>> Network Storage Architecture Office
>>> Sun Microsystems Inc.
>>>
>>> 303.395.3801 (x43011)
>>> Robert.B.Wood at Sun.com
>>>
>>>




From nakata at mtg.biglobe.ne.jp  Wed Mar 15 05:51:09 2006
From: nakata at mtg.biglobe.ne.jp (Toshiyuki Nakata)
Date: Wed, 15 Mar 2006 20:51:09 +0900
Subject: [graap-wg] telecon on 3/15
In-Reply-To: <44179DAE.2050100@hp.com>
References: <44179DAE.2050100@hp.com>
Message-ID: <4417FFAD.8050000@mtg.biglobe.ne.jp>

A little bit of info. added for discussion (in red chars).
(I'll try to attend but really depends on my family waking me up...)

Best Regards
Toshi
Jim Pruyne wrote:

> We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
> the same.
> The time is:
> 9:00AM Central Time US
> which should be:
> 10:00AM Eastern Time US
> 1500 UK
> 1600 Germany
> midnight Japan
> 2200 Thailand
> 
> Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
> US.
> Conference code #8578310.
> 
> --- Jim
> 
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060314.xls
Type: application/vnd.ms-excel
Size: 96256 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060315/c1319638/attachment.xls 

From jim_pruyne at hp.com  Wed Mar 15 10:11:16 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 15 Mar 2006 10:11:16 -0600
Subject: [graap-wg] minutes from 3/15 telecon
Message-ID: <44183CA4.5020307@hp.com>

Are attached.  We'll meet next week at the usual time.

--- Jim


-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Mar1506-minutes.txt
Url: http://www.ogf.org/pipermail/graap-wg/attachments/20060315/8843389b/attachment.txt 

From nakata at mtg.biglobe.ne.jp  Wed Mar 15 10:32:18 2006
From: nakata at mtg.biglobe.ne.jp (Toshiyuki Nakata)
Date: Thu, 16 Mar 2006 01:32:18 +0900
Subject: [graap-wg] Re: [dmis-bof] Updated Charter
In-Reply-To: <4417A004.1040608@jp.fujitsu.com>
References: <005c01c647a5$f76e6160$7312dd8c@mcs.anl.gov> <44178439.6090302@jp.fujitsu.com> <4417A004.1040608@jp.fujitsu.com>
Message-ID: <44184192.2010409@mtg.biglobe.ne.jp>

Hi: My name is Toshiyuki Nakata (or just Toshi) one of the members of 
GRAAP-WG.
(Hiro: Thank you very much for the pointer)

The WS-Agreement Spec that had been submitted for review can be found in
http://forge.gridforum.org/projects/graap-wg/document/WS-AgreementSpecificationDraft.doc/en/17

There is also a newer one ( which we're currently working on trying to 
reflect all the valuable comments made during the Public Comments Period) in

https://forge.gridforum.org/projects/graap-wg/document/WS-AgreementSpecificationDraft.doc/en

  I can also send you some tutorial material that I together with 
another group member made if you like.

Hope you find it useful.
Best Regards
Toshi


Hiro Kishimoto wrote:

> Hi Bill,
> 
> One more comment.
> 
> Scope section says
> 
>> This Working Group will define two Web Service interfaces. The first
> 
>  > interface deals with the agreement on a particular transport protocol
>  > used for a data movement. The second interface defines the invocation
>  > of the data movement itself, and the associated aspects of
>  > reliability, transfer scheduling, granularity, performance settings,
>  > control, and progress.
> 
> Are you familiar with WS-Agreement specification by GRAAP-WG?
> Can you include investigation of applicability of WS-Agreement to
> your interface as an WG's activity?
> 
> Thanks,
> ----
> Hiro Kishimoto
> 
> Hiro Kishimoto wrote:
> 
>> Hi Bill,
>>
>> Thank you very much for revising WG charter document.
>> In general, it sounds good to me.
>>
>> The following is my comments;
>>
>> (1) Goals section
>> Given that GFSG is now asking all WG/RG co-chairs to maintain web based
>> "Living Charter" (see attached OGSA-WG example), I recommend to
>> organize goals section based on deliverable documents.
>>
>> Goals section has list of documents and each document has
>> - title
>> - abstract
>> - type
>> - milestones (date for first draft, public comment, publication)
>>
>> (2) transport document
>> Goals section says this WG will create "transport document" but
>> focus/purpose and scope sections don't mention this. Please
>> explain what is transport document in these previous sections.
>>
>> (3) 7 Q&A document
>> Please update and send out 7 Q&A document as well as charter.
>> You need to provide both to your area director for WG approval.
>>
>> (4) reference
>>
>> "OGSA WSRF Basic Profile Rendering 1.0, GFD.59, T. Maguire, D. Snelling,
>>  Global Grid Forum, January 2006"
>>
>> should be
>>
>> "[OGSA WSRF BP] OGSA WSRF Basic Profile 1.0, Foster, I., Maguire, T.,
>> and Snelling, D. Global Grid Forum, GWD-R, September 2005.
>> http://www.ggf.org/Public_Comment_Docs/Documents/Oct-2005/draft-ggf-ogsa-wsrf-basic-profile-v43.pdf" 
>>
>>
>> (5) Management issues
>> I would add the following sentence to this section;
>>
>> The WG will have joint review discussion with the OGSA-WG and the 
>> OGSA-D-WG before every milestone.
>>
>> (5) DMI
>> The Desktop Management Interface (DMI) is rather well known in
>> IT industry. Do you have any other alphabet soup (e.g. Interface
>> of Data Movement: IDM).
>>
>> p.s.
>> OGSA-WG will have interim F2F meeting in San Francisco Bay Area
>> from April 4-7. If you want to have session at this F2F meeting
>> please provide agenda and how long do you need.
>>
>> https://forge.gridforum.org/projects/ogsa-wg/document/200604F2F_session
>>
>> Thanks,
>> ----
>> Hiro Kishimoto
>>
>> William E. Allcock wrote:
>>
>>> Ok, next iteration is attached.  We tried to address the comments we had
>>> received so far.
>>>
>>> Bill
>>>
>>>> -----Original Message-----
>>>> From: owner-dmis-bof at ggf.org [mailto:owner-dmis-bof at ggf.org] On 
>>>> Behalf Of Robert B. Wood
>>>> Sent: Tuesday, March 14, 2006 10:07 AM
>>>> To: Michel Drescher
>>>> Cc: allcock at mcs.anl.gov; dmis-bof at ggf.org
>>>> Subject: Re: [dmis-bof] Updated Charter
>>>>
>>>> In my opinion, "4th party data transfer" as a term such as described 
>>>> below offers more debate than value.  To my understanding, a 3rd 
>>>> party copy operation is a data transfer between two data stores that 
>>>> is initiated by [at least] one of the data stores or devices 
>>>> themselves, without the aid or instruction of the user or their 
>>>> server/application code.  It was originally coined in the realm of 
>>>> data backup.
>>>>
>>>> When an agent of the user (including the user him or herself) 
>>>> initiates a data transfer and the data transfer path includes the 
>>>> user's system, that is a first party operation.  When an agent 
>>>> initiates a data transfer directly between two data stores or 
>>>> devices, without placing their server in the data stream, this is an 
>>>> extended data movement operation; what is referred to as extended 
>>>> copy or serverless backup in the data backup realm.
>>>>
>>>> The usage of these terms is pretty well codified in the SCSI-3 
>>>> specification and implemented in storage products.
>>>> I'm not suggesting that management of agents, like the "truly 
>>>> independent service" that Michel describes is trivial, in fact the 
>>>> data security aspects can be quite challenging.  Also the line 
>>>> between direct control and independent operations is pretty fuzzy, 
>>>> as data movements rarely occur without some user involvement, be it 
>>>> simply an exersize of a service level agreement with the data 
>>>> storage service provider[s].
>>>>
>>>> Just a couple of comments to the comments to the comments ... Bob
>>>>
>>>> Michel Drescher wrote:
>>>>
>>>>
>>>>> Bill,
>>>>>
>>>>> some comments, related to the comments you put in the 
>>>>
>>>>
>>>>
>>>> charter document:
>>>>
>>>>> 4th party data transfer:
>>>>> I see 3 different scenarios for data movement. Let's assume 
>>>>
>>>>
>>>>
>>>> we have a
>>>>
>>>>> (data) source and a (data) destination. We also have a user that  
>>>>> wants data moved. If the user is the source, we have a direct pull  
>>>>> case, if the user is the destination, then we have a direct push  
>>>>> case. If the user tells the source to move some data to the  
>>>>> destination, then this is 3rd party push, if the user tells the  
>>>>> destination to get some data, then this is 3rd party pull.
>>>>> Well, if the user tells a truly independent service to initiate a  
>>>>> data transfer from source to target, then this is very 
>>>>
>>>>
>>>>
>>>> similar to 3rd
>>>>
>>>>> party data transfer, but different enough as there is a 4th 
>>>>
>>>>
>>>>
>>>> instance
>>>>
>>>>> participating in the data movement.
>>>>>
>>>>> Transport protocols:
>>>>> Yes I meant application level protocols from a network 
>>>>
>>>>
>>>>
>>>> point of view,
>>>>
>>>>> such as GridFTP, HTTP, FTP, etc.
>>>>>
>>>>>
>>>>> Regarding the timeline:
>>>>> The short term planning is ambitious, but manageable, I think,  
>>>>> especially if we can appreciate broad contribution support.
>>>>>
>>>>> Cheers,
>>>>> Michel
>>>>>
>>>>> On 13 Mar 2006, at 22:41, William E. Allcock wrote:
>>>>>
>>>>>
>>>>>> All,
>>>>>>
>>>>>> Michel and I have updated the charter based on discussions 
>>>>
>>>>
>>>>
>>>> that  took
>>>>
>>>>>> place
>>>>>> at GGF16.  They are already scheduling slots for next GGF, so we  
>>>>>> need to
>>>>>> ratify this charter ASAP and become a full fledged working 
>>>>
>>>>
>>>>
>>>> group.  The
>>>>
>>>>>> charter is short, only a couple of pages of text and a table with  
>>>>>> goals and
>>>>>> timelines.  This shouldn't take long, so please take a few 
>>>>
>>>>
>>>>
>>>> minutes
>>>>
>>>>>> now and
>>>>>> review this.
>>>>>>
>>>>>> In particular we would like comments on:
>>>>>>
>>>>>> - Do you agree with the focus and scope
>>>>>> - Do you think the Goals and timeline are reasonable?  
>>>>
>>>>
>>>>
>>>> Are we missing
>>>>
>>>>>> anything?
>>>>>> - Which documents / implementations would you be willing 
>>>>
>>>>
>>>>
>>>> to work on?
>>>>
>>>>>> Thanks, and I hope to see you in Tokyo.
>>>>>>
>>>>>> Bill
>>>>>>
>>>>>> ---------------------------------------------------------------
>>>>>> William E. Allcock
>>>>>> Argonne National Laboratory
>>>>>> Bldg 221, Office B-139
>>>>>> 9700 South Cass Ave
>>>>>> Argonne, IL 60439-4844
>>>>>> Email:           allcock at mcs.anl.gov
>>>>>> Office Phone:    +1-630-252-7573
>>>>>> Office Fax:      +1-630-252-1997
>>>>>> Cell Phone:      +1-630-854-2842
>>>>>>
>>>>>> <charter-v3.doc>
>>>>>
>>>>>
>>>>>
>>>>>
>>>> -- 
>>>> Bob Wood
>>>> Network Storage Architecture Office
>>>> Sun Microsystems Inc.
>>>>
>>>> 303.395.3801 (x43011)
>>>> Robert.B.Wood at Sun.com
>>>>
>>>>
> 
> 
> 




From nakata at mtg.biglobe.ne.jp  Wed Mar 15 10:54:47 2006
From: nakata at mtg.biglobe.ne.jp (Toshiyuki Nakata)
Date: Thu, 16 Mar 2006 01:54:47 +0900
Subject: [graap-wg] minutes from 3/15 telecon
In-Reply-To: <44183CA4.5020307@hp.com>
References: <44183CA4.5020307@hp.com>
Message-ID: <441846D7.3040506@mtg.biglobe.ne.jp>

Usual list attached.
Best Regards
Toshi

Jim Pruyne wrote:

> Are attached.  We'll meet next week at the usual time.
> 
> --- Jim
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060315.xls
Type: application/vnd.ms-excel
Size: 98816 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060316/3d240299/attachment.xls 

From asit at us.ibm.com  Wed Mar 15 09:40:21 2006
From: asit at us.ibm.com (Asit Dan)
Date: Wed, 15 Mar 2006 10:40:21 -0500
Subject: [graap-wg] telecon on 3/15
In-Reply-To: <4417FFAD.8050000@mtg.biglobe.ne.jp>
Message-ID: <OF5E99D685.29419A7D-ON85257132.0055C274-85257132.00561C95@us.ibm.com>

Jim, Toshi,
 
 Here is a rewording for the penalty statement.

This element (defined below) when present expresses the penalty to be 
assessed for not meeting an objective. If multiple Penalty statements are 
present, for example penalty statements expressed per week and per month 
basis for an availability objective, the longest assessment duration 
resulting in highest assessment value will be applied. In the above 
example, multiple weekly violations within a month may result in a higher 
penalty amount as assessed by the monthly penalty statement rather than 
the cumulative weekly assessments. 

Regards.
Asit Dan, Ph.D.
SWG SOA Design Requirements
Phone: (914) 766-1767 
Internet: asit at us.ibm.com
ICSOC 06 PC Chair (http://www.icsoc.org)



Toshiyuki Nakata <nakata at mtg.biglobe.ne.jp> 
Sent by: owner-graap-wg at ggf.org
03/15/2006 06:51 AM
Please respond to
t-nakata at cw.jp.nec.com


To
Jim Pruyne <jim_pruyne at hp.com>
cc
GRAAP-WG <graap-wg at gridforum.org>
Subject
Re: [graap-wg] telecon on 3/15






A little bit of info. added for discussion (in red chars).
(I'll try to attend but really depends on my family waking me up...)

Best Regards
Toshi
Jim Pruyne wrote:

> We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 

> the same.
> The time is:
> 9:00AM Central Time US
> which should be:
> 10:00AM Eastern Time US
> 1500 UK
> 1600 Germany
> midnight Japan
> 2200 Thailand
> 
> Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 

> US.
> Conference code #8578310.
> 
> --- Jim
> 
> 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.ogf.org/pipermail/graap-wg/attachments/20060315/e887b23b/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060314.xls
Type: application/vnd.ms-excel
Size: 96256 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060315/e887b23b/attachment.xls 

From t-nakata at cw.jp.nec.com  Thu Mar 16 01:25:56 2006
From: t-nakata at cw.jp.nec.com (Toshiyuki Nakata)
Date: Thu, 16 Mar 2006 16:25:56 +0900
Subject: [graap-wg] minutes from 3/15 telecon
In-Reply-To: <44183CA4.5020307@hp.com>
Message-ID: <000001c648ca$dee8a4e0$ab84380a@ISIBASI>

<Begin Quote>
- Comment row 21: On terminate operation: concern here is that there
  may be penalties associated with termination, but this is domain
  dependent.  Terminate might still be followed by a destroy
  operation.  The proposal is also to introduce a agreement state
  called terminated in section 7.1 that says that additional penalty
  may associated with entering the terminated state.  Updates may
  require changes in the schema (e.g. in section 9.5).  The new port
  type for the terminate operation would be introduced around section
  9.4.  We also need to introduce some discussion of the relationship
  between terminate and wsrl:Destroy.  Toshi to start to pursue some
  of these updates, and send the proposed changes to the mailing list.
<End Quote>

Actually, most of the work had been resurrection of previously deleted
material, 
with the exception of introduction of the Terminated State.
(I am still not sure whether introduction of Teminated State is good or bad.
Eg. what would be the difference between killing an NQS job using an
 NQS script (in which case I suppose 
the Agreement State would end in Complete and
Using Terminate to teminate an executing job?)

I do have a Word doc but excerpts from it may be easier to see.

Please note <<...>> means some words exist but has not been changed so not
included
to make it easier to see.
<<words>> are my comments.

Section 7.1
7.1 Agreement States
The overall Agreement has a state derived from the Agreement protocol.
* Pending. 
<<...>>
* Complete. The Complete state means that an Agreement offer has been
received and accepted, and that all activities pertaining to the Agreement
are
finished This state MAY follow Observed.

<<Begin Addition>>
* Terminated. The terminated state means that an Agreement offer has been
terminated by the Agreement Initiator and that the obligation no longer
exists.
This state May follow Pending or Observed. The fact that the Agreement is in
this state MAY imply that a domain specific penalty is imposed.
<<End of Addition >><<Please note that due to a race condition, Terminated
might follow Complete..>>

The Pending and Rejected states indicate that the responder is not obligated
in any
way. 
<<....>>
The accepted Agreement is Complete only when all service states
are Complete, and the accepted Agreement is otherwise Observed. 

<<Begin Addition>>
The Terminated
state indicate that neither parties are obligated.
<< End Addition>>
 <<9.4 is mostly resurrection except for the wording 
"Terminating an Agreement may result in
domain-specific penalty imposed on the Agreement Initiator."

<<Should may above be MAY??>>

9.4 Port Type wsag:Agreement
9.4.1 . Operation wsag:Terminate
Terminates an Agreement, if permissible. Terminating an Agreement may result
in
domain-specific penalty imposed on the Agreement Initiator.
9.4.1.1 Input
The form of the wsag:Terminate input message is:
<wsag:TerminateInput>
xsd:any
</wsag:TerminateInput>
The contents of the input message are further described as follows:
/wsag:terminate/xsd:any
Any domain-specific content may be added. This content may be used for a
variety of purposes such as logging the termination condition, or evaluating
if a
domain-specific cause for termination is sufficient to permit the agreement
to be
terminated.
9.4.1.2 Result
The result of the wsag:Terminate operation is always empty.
<wsag:TerminateResponse>
</wsag:TerminateResponse>
9.4.1.3 Faults
A fault response indicates that the termination was rejected and may also
indicate
domain-specific reasons.

<<Adding Terminated state >>
9.5.1 Resource Property wsag:AgreementState
The property exposes an Agreement state for the whole agreement as defined
in
section 7.1.
The property has the following structure:
<wsag:AgreementState>
<wsag:Pending>
<xsd:any##other/> *
</wsag:Pending> ?
<<...>>
<wsag:Terminated>
<xsd:any##other/> *
</wsag:Terminated> ?

/wsag:AgreementState
This element MUST have exactly one child from: Pending, Observed, Rejected,
Complete and Terminated to indicate the overall state of the Agreement
resource. Each of these states for the entire agreement have open content so
that additional domain-specific state information can be expressed. The
individual states are as described in Section 7.1.
/wsag:AgreementState/wsag:Pending
An agreement state which is in state Pending.
<<...>>
/wsag:AgreementState/wsag:Terminated
An agreement state which is in state Terminated.

I've also added WSDL definitions and Agreement Statetpes Schema but 
won't put them here.
-----
Toshiyuki Nakata ??????
Executive Chief Engineer, Central Research Lab. NEC 
1753, Shimonumabe, Nakahara-Ku, 
Kawasaki,Kanagawa 211-8666,Japan 
Tel +81-44-431-7653 (NEC Internal 22-60035)
Fax +81-44-431-7609 (NEC Internal 22-60509) 

> -----Original Message-----
> From: owner-graap-wg at ggf.org [mailto:owner-graap-wg at ggf.org] 
> On Behalf Of Jim Pruyne
> Sent: Thursday, March 16, 2006 1:11 AM
> To: GRAAP-WG
> Subject: [graap-wg] minutes from 3/15 telecon
> 
> Are attached.  We'll meet next week at the usual time.
> 
> --- Jim
> 
> 
> 




From t-nakata at cw.jp.nec.com  Thu Mar 16 03:06:59 2006
From: t-nakata at cw.jp.nec.com (Toshiyuki Nakata)
Date: Thu, 16 Mar 2006 18:06:59 +0900
Subject: [graap-wg] minutes from 3/15 telecon
In-Reply-To: <000001c648ca$dee8a4e0$ab84380a@ISIBASI>
Message-ID: <000301c648d8$fcabef60$ab84380a@ISIBASI>

Hi: Found ways to just extract the updated part in an PDF File.

Best regards
Toshi

-----
Toshiyuki Nakata ??????
Executive Chief Engineer, Central Research Lab. NEC 
1753, Shimonumabe, Nakahara-Ku, 
Kawasaki,Kanagawa 211-8666,Japan 
Tel +81-44-431-7653 (NEC Internal 22-60035)
Fax +81-44-431-7609 (NEC Internal 22-60509) 

> -----Original Message-----
> From: owner-graap-wg at ggf.org [mailto:owner-graap-wg at ggf.org] 
> On Behalf Of Toshiyuki Nakata
> Sent: Thursday, March 16, 2006 4:26 PM
> To: 'Jim Pruyne'; 'GRAAP-WG'
> Subject: RE: [graap-wg] minutes from 3/15 telecon
> 
> <Begin Quote>
> - Comment row 21: On terminate operation: concern here is that there
>   may be penalties associated with termination, but this is domain
>   dependent.  Terminate might still be followed by a destroy
>   operation.  The proposal is also to introduce a agreement state
>   called terminated in section 7.1 that says that additional penalty
>   may associated with entering the terminated state.  Updates may
>   require changes in the schema (e.g. in section 9.5).  The new port
>   type for the terminate operation would be introduced around section
>   9.4.  We also need to introduce some discussion of the relationship
>   between terminate and wsrl:Destroy.  Toshi to start to pursue some
>   of these updates, and send the proposed changes to the mailing list.
> <End Quote>
> 
> Actually, most of the work had been resurrection of 
> previously deleted material, with the exception of 
> introduction of the Terminated State.
> (I am still not sure whether introduction of Teminated State 
> is good or bad.
> Eg. what would be the difference between killing an NQS job 
> using an  NQS script (in which case I suppose the Agreement 
> State would end in Complete and Using Terminate to teminate 
> an executing job?)
> 
> I do have a Word doc but excerpts from it may be easier to see.
> 
> Please note <<...>> means some words exist but has not been 
> changed so not included to make it easier to see.
> <<words>> are my comments.
> 
> Section 7.1
> 7.1 Agreement States
> The overall Agreement has a state derived from the Agreement protocol.
> * Pending. 
> <<...>>
> * Complete. The Complete state means that an Agreement offer 
> has been received and accepted, and that all activities 
> pertaining to the Agreement are finished This state MAY 
> follow Observed.
> 
> <<Begin Addition>>
> * Terminated. The terminated state means that an Agreement 
> offer has been terminated by the Agreement Initiator and that 
> the obligation no longer exists.
> This state May follow Pending or Observed. The fact that the 
> Agreement is in this state MAY imply that a domain specific 
> penalty is imposed.
> <<End of Addition >><<Please note that due to a race 
> condition, Terminated might follow Complete..>>
> 
> The Pending and Rejected states indicate that the responder 
> is not obligated in any way. 
> <<....>>
> The accepted Agreement is Complete only when all service 
> states are Complete, and the accepted Agreement is otherwise 
> Observed. 
> 
> <<Begin Addition>>
> The Terminated
> state indicate that neither parties are obligated.
> << End Addition>>
>  <<9.4 is mostly resurrection except for the wording 
> "Terminating an Agreement may result in domain-specific 
> penalty imposed on the Agreement Initiator."
> 
> <<Should may above be MAY??>>
> 
> 9.4 Port Type wsag:Agreement
> 9.4.1 . Operation wsag:Terminate
> Terminates an Agreement, if permissible. Terminating an 
> Agreement may result in domain-specific penalty imposed on 
> the Agreement Initiator.
> 9.4.1.1 Input
> The form of the wsag:Terminate input message is:
> <wsag:TerminateInput>
> xsd:any
> </wsag:TerminateInput>
> The contents of the input message are further described as follows:
> /wsag:terminate/xsd:any
> Any domain-specific content may be added. This content may be 
> used for a variety of purposes such as logging the 
> termination condition, or evaluating if a domain-specific 
> cause for termination is sufficient to permit the agreement 
> to be terminated.
> 9.4.1.2 Result
> The result of the wsag:Terminate operation is always empty.
> <wsag:TerminateResponse>
> </wsag:TerminateResponse>
> 9.4.1.3 Faults
> A fault response indicates that the termination was rejected 
> and may also indicate domain-specific reasons.
> 
> <<Adding Terminated state >>
> 9.5.1 Resource Property wsag:AgreementState The property 
> exposes an Agreement state for the whole agreement as defined 
> in section 7.1.
> The property has the following structure:
> <wsag:AgreementState>
> <wsag:Pending>
> <xsd:any##other/> *
> </wsag:Pending> ?
> <<...>>
> <wsag:Terminated>
> <xsd:any##other/> *
> </wsag:Terminated> ?
> 
> /wsag:AgreementState
> This element MUST have exactly one child from: Pending, 
> Observed, Rejected, Complete and Terminated to indicate the 
> overall state of the Agreement resource. Each of these states 
> for the entire agreement have open content so that additional 
> domain-specific state information can be expressed. The 
> individual states are as described in Section 7.1.
> /wsag:AgreementState/wsag:Pending
> An agreement state which is in state Pending.
> <<...>>
> /wsag:AgreementState/wsag:Terminated
> An agreement state which is in state Terminated.
> 
> I've also added WSDL definitions and Agreement Statetpes 
> Schema but won't put them here.
> -----
> Toshiyuki Nakata ??????
> Executive Chief Engineer, Central Research Lab. NEC 1753, 
> Shimonumabe, Nakahara-Ku, Kawasaki,Kanagawa 211-8666,Japan 
> Tel +81-44-431-7653 (NEC Internal 22-60035) Fax 
> +81-44-431-7609 (NEC Internal 22-60509) 
> 
> > -----Original Message-----
> > From: owner-graap-wg at ggf.org 
> [mailto:owner-graap-wg at ggf.org] On Behalf 
> > Of Jim Pruyne
> > Sent: Thursday, March 16, 2006 1:11 AM
> > To: GRAAP-WG
> > Subject: [graap-wg] minutes from 3/15 telecon
> > 
> > Are attached.  We'll meet next week at the usual time.
> > 
> > --- Jim
> > 
> > 
> > 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: WS-AgreementSpecification-with-Terminate(extracted).pdf
Type: application/pdf
Size: 114797 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060316/e8cb6f9b/attachment.pdf 

From t-nakata at cw.jp.nec.com  Thu Mar 16 22:44:09 2006
From: t-nakata at cw.jp.nec.com (Toshiyuki Nakata)
Date: Fri, 17 Mar 2006 13:44:09 +0900
Subject: [graap-wg] minutes from 3/15 telecon
In-Reply-To: <441846D7.3040506@mtg.biglobe.ne.jp>
Message-ID: <000101c6497d$6e7181b0$ab84380a@ISIBASI>

Hello:I've updated the Commentslist
1)Moved the ones which have already been discussed to the done page.
(The entries are not in item order, as I need to be able to distinguish
between  the ones already 
discussed in GGF16. and the oned needed to be explained in GGF17)

2)Added 18 of Karl's comments.
Best regards
Toshi

-----
Toshiyuki Nakata ??????
Executive Chief Engineer, Central Research Lab. NEC 
1753, Shimonumabe, Nakahara-Ku, 
Kawasaki,Kanagawa 211-8666,Japan 
Tel +81-44-431-7653 (NEC Internal 22-60035)
Fax +81-44-431-7609 (NEC Internal 22-60509) 

> -----Original Message-----

> Usual list attached.
> Best Regards
> Toshi
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060317.xls
Type: application/vnd.ms-excel
Size: 114176 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060317/abecc678/attachment.xls 

From jim_pruyne at hp.com  Tue Mar 21 23:44:25 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Tue, 21 Mar 2006 23:44:25 -0600
Subject: [graap-wg] telecon on 3/22
Message-ID: <4420E439.2060700@hp.com>

We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
the same.
The time is:
9:00AM Central Time US
which should be:
10:00AM Eastern Time US
1500 UK
1600 Germany
midnight Japan
2200 Thailand

Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
US.
Conference code #8578310.

--- Jim




From Wolfgang.Ziegler at scai.fraunhofer.de  Wed Mar 22 00:52:44 2006
From: Wolfgang.Ziegler at scai.fraunhofer.de (Wolfgang Ziegler)
Date: Wed, 22 Mar 2006 07:52:44 +0100
Subject: [graap-wg] telecon on 3/22
In-Reply-To: <4420E439.2060700@hp.com>
References: <4420E439.2060700@hp.com>
Message-ID: <4420F43C.4040605@scai.fraunhofer.de>

Hi Jim,

I will attend a project workshop today that is used to prepare
a project review we will have next week. Thus I will not be able
to joint the telecon today.

Best regards

Wolfgang


Jim Pruyne wrote:
> We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
> the same.
> The time is:
> 9:00AM Central Time US
> which should be:
> 10:00AM Eastern Time US
> 1500 UK
> 1600 Germany
> midnight Japan
> 2200 Thailand
> 
> Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
> US.
> Conference code #8578310.
> 
> --- Jim
> 

-- 
       Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI)
            Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
     Tel: +49 2241 14 2258    Fax: +49 2241 14 42258   www.scai.fraunhofer.de

               CoreGRID Network of Excellence   www.coregrid.net
        Collaboration Gateway   www.coregrid.net/mambo/content/viev/53/74/
        Institute on Resource Management and Scheduling   www.coregrid.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3761 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060322/fa87c6e8/attachment.bin 

From t-nakata at cw.jp.nec.com  Wed Mar 22 02:07:24 2006
From: t-nakata at cw.jp.nec.com (Toshiyuki Nakata)
Date: Wed, 22 Mar 2006 17:07:24 +0900
Subject: [graap-wg] telecon on 3/22
In-Reply-To: <4420E439.2060700@hp.com>
Message-ID: <000801c64d87$a8693a30$ab84380a@ISIBASI>

I've added some page info for some of the comments.

I'll try to attend today's meeting but might not be able to due to a
combination of cold and hay fever.
Best Regards
Toshi

-----
Toshiyuki Nakata ??????
Executive Chief Engineer, Central Research Lab. NEC 
1753, Shimonumabe, Nakahara-Ku, 
Kawasaki,Kanagawa 211-8666,Japan 
Tel +81-44-431-7653 (NEC Internal 22-60035)
Fax +81-44-431-7609 (NEC Internal 22-60509) 

> -----Original Message-----
> From: owner-graap-wg at ggf.org [mailto:owner-graap-wg at ggf.org] 
> On Behalf Of Jim Pruyne
> Sent: Wednesday, March 22, 2006 2:44 PM
> To: GRAAP-WG
> Subject: [graap-wg] telecon on 3/22
> 
> We will have a telecon. on Wed. morning/evening. Dial-in 
> numbers will be the same.
> The time is:
> 9:00AM Central Time US
> which should be:
> 10:00AM Eastern Time US
> 1500 UK
> 1600 Germany
> midnight Japan
> 2200 Thailand
> 
> Phone Number: 866-673-8466 in the US. 702-477-6031 for those 
> outside the US.
> Conference code #8578310.
> 
> --- Jim
> 
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: PublicComments060317rev1.xls
Type: application/vnd.ms-excel
Size: 114176 bytes
Desc: not available
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060322/e3d35b08/attachment.xls 

From jim_pruyne at hp.com  Wed Mar 29 01:45:25 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 29 Mar 2006 01:45:25 -0600
Subject: [graap-wg] telecon on 3/29
Message-ID: <442A3B15.5080603@hp.com>

We will have a telecon. on Wed. morning/evening. Dial-in numbers will be 
the same.
The time is:
9:00AM Central Time US
which should be:
10:00AM Eastern Time US
1500 UK
1600 Germany
midnight Japan
2200 Thailand

Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside the 
US.
Conference code #8578310.

--- Jim




From t-nakata at cw.jp.nec.com  Wed Mar 29 02:48:05 2006
From: t-nakata at cw.jp.nec.com (Toshiyuki Nakata)
Date: Wed, 29 Mar 2006 17:48:05 +0900
Subject: [graap-wg] telecon on 3/29
In-Reply-To: <442A3B15.5080603@hp.com>
Message-ID: <000d01c6530d$7f074160$ab84380a@ISIBASI>

Hi:
I think Daylight Saving Time started this week in Europe.
but not in USA yet.

So below should be...
> 
> We will have a telecon. on Wed. morning/evening. Dial-in 
> numbers will be the same.
> The time is:
> 9:00AM Central Time US
> which should be:
> 10:00AM Eastern Time US
> 1500 UK 16:00 UK 
> 1600 Germany 17:00 Germany
> midnight Japan
> 2200 Thailand
> 
> Phone Number: 866-673-8466 in the US. 702-477-6031 for those 
> outside the US.
> Conference code #8578310.
> 
> --- Jim
> 

Best Regards
Toshi




From Wolfgang.Ziegler at scai.fraunhofer.de  Wed Mar 29 03:01:01 2006
From: Wolfgang.Ziegler at scai.fraunhofer.de (Wolfgang Ziegler)
Date: Wed, 29 Mar 2006 11:01:01 +0200
Subject: [graap-wg] telecon on 3/29
In-Reply-To: <000d01c6530d$7f074160$ab84380a@ISIBASI>
References: <000d01c6530d$7f074160$ab84380a@ISIBASI>
Message-ID: <442A4CCD.2070707@scai.fraunhofer.de>

Dear Toshi,

thanks for taking care of this: I forgot that already and would
only have remembered myself when I were the only one to dial in one
hour earlier than expected ;-)


Best regards

Wolfgang


Toshiyuki Nakata wrote:
> Hi:
> I think Daylight Saving Time started this week in Europe.
> but not in USA yet.
> 
> So below should be...
>> We will have a telecon. on Wed. morning/evening. Dial-in 
>> numbers will be the same.
>> The time is:
>> 9:00AM Central Time US
>> which should be:
>> 10:00AM Eastern Time US
>> 1500 UK 16:00 UK 
>> 1600 Germany 17:00 Germany
>> midnight Japan
>> 2200 Thailand
>>
>> Phone Number: 866-673-8466 in the US. 702-477-6031 for those 
>> outside the US.
>> Conference code #8578310.
>>
>> --- Jim
>>
> 
> Best Regards
> Toshi
> 

-- 
           Wolfgang Ziegler    www.scai.fraunhofer.de/ziegler.html
     Fraunhofer-Institute for Algorithms and Scientific Computing (SCAI)
            Schloss Birlinghoven, D-53754 Sankt Augustin, Germany
                Tel: +49 2241 14 2258; Fax: +49 2241 14 42258

               CoreGRID Network of Excellence   www.coregrid.net
                  Collaboration Gateway   www.coregrid.net/cg
        Institute on Resource Management and Scheduling   www.coregrid.net/irms
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3761 bytes
Desc: S/MIME Cryptographic Signature
Url : http://www.ogf.org/pipermail/graap-wg/attachments/20060329/5e1ca8d9/attachment.bin 

From o.f.rana at cs.cardiff.ac.uk  Wed Mar 29 05:57:02 2006
From: o.f.rana at cs.cardiff.ac.uk (Omer F. Rana)
Date: Wed, 29 Mar 2006 12:57:02 +0100
Subject: [graap-wg] telecon on 3/29
In-Reply-To: <442A4CCD.2070707@scai.fraunhofer.de>
References: <000d01c6530d$7f074160$ab84380a@ISIBASI> <442A4CCD.2070707@scai.fraunhofer.de>
Message-ID: <442A760E.10307@cs.cardiff.ac.uk>

Hi Jim,

Is there an agenda for the telecon discussion today?

regards
Omer

Wolfgang Ziegler wrote:

> Dear Toshi,
>
> thanks for taking care of this: I forgot that already and would
> only have remembered myself when I were the only one to dial in one
> hour earlier than expected ;-)
>
>
> Best regards
>
> Wolfgang
>
>
> Toshiyuki Nakata wrote:
>
>> Hi:
>> I think Daylight Saving Time started this week in Europe.
>> but not in USA yet.
>>
>> So below should be...
>>
>>> We will have a telecon. on Wed. morning/evening. Dial-in numbers 
>>> will be the same.
>>> The time is:
>>> 9:00AM Central Time US
>>> which should be:
>>> 10:00AM Eastern Time US
>>> 1500 UK 16:00 UK 1600 Germany 17:00 Germany
>>> midnight Japan
>>> 2200 Thailand
>>>
>>> Phone Number: 866-673-8466 in the US. 702-477-6031 for those outside 
>>> the US.
>>> Conference code #8578310.
>>>
>>> --- Jim
>>>
>>
>> Best Regards
>> Toshi
>>
>

-- 
http://www.cs.cf.ac.uk/User/O.F.Rana/index.html / work-fax:+44(0)29-2087-4598
work:+44(0)29-2087-5542 / other:+44(0)7956-299981 / distributed collaborative
computing / room n2.14 / school of computer science / cardiff university 
  queen's buildings / newport road / cardiff cf24 3aa / wales / uk 




From jim_pruyne at hp.com  Wed Mar 29 12:29:06 2006
From: jim_pruyne at hp.com (Jim Pruyne)
Date: Wed, 29 Mar 2006 12:29:06 -0600
Subject: [graap-wg] minutes from 3/29 telecon
Message-ID: <442AD1F2.3030706@hp.com>

They are attached.  We'll meet at the "usual" times next week.  Usual is 
defined w.r.t. the US.  However, the US is changing to daylight savings 
time over the weekend, this should make it one hour earlier in most 
other parts of the world.

Further, there is some interest in holding additional phone conferences 
during April to try to make sure we're completed by GGF in Tokyo.  If we 
do this, I would propose the same time of day as usual (i.e. 9AM Central 
time in the US), but on Friday's.  I realize this makes it late night in 
Asia on a Friday night which might be considered unattractive.  Please 
give feedback on the need for additional calls, and on preferred 
days/times for them.

--- Jim

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: Mar2906-minutes.txt
Url: http://www.ogf.org/pipermail/graap-wg/attachments/20060329/ff01bd79/attachment.txt 

From nakata at mtg.biglobe.ne.jp  Wed Mar 29 16:39:49 2006
From: nakata at mtg.biglobe.ne.jp (Toshiyuki Nakata)
Date: Thu, 30 Mar 2006 07:39:49 +0900
Subject: [graap-wg] minutes from 3/29 telecon
In-Reply-To: <442AD1F2.3030706@hp.com>
References: <442AD1F2.3030706@hp.com>
Message-ID: <442B0CB5.7040903@mtg.biglobe.ne.jp>

Hi: Friday would be best for me as I can sleep as much as I want on
Saturdays.

Best Regards
Toshi


Jim Pruyne wrote:

> They are attached.  We'll meet at the "usual" times next week.  Usual is 
> defined w.r.t. the US.  However, the US is changing to daylight savings 
> time over the weekend, this should make it one hour earlier in most 
> other parts of the world.
> 
> Further, there is some interest in holding additional phone conferences 
> during April to try to make sure we're completed by GGF in Tokyo.  If we 
> do this, I would propose the same time of day as usual (i.e. 9AM Central 
> time in the US), but on Friday's.  I realize this makes it late night in 
> Asia on a Friday night which might be considered unattractive.  Please 
> give feedback on the need for additional calls, and on preferred 
> days/times for them.
> 
> --- Jim
>