Meeting notes for 5/9/01 Atlas Network Proposal Meeting

Shawn, Tom and Abhijit

Tasks for writing pre-proposal for Atlas Networking

1. Define as precisely as possible the following requirements:
   1. User requirements for networking
   2. Requirements for BW based on dataset sizes and necessary minimum transfer rate
   3. Projected requirements – a timeline for what requirements need to be met when

2. Survey existing and on-going work
   1. Survey existing work and determine how existing work can fulfill the requirements and what the gaps are.
   2. Survey on-going work in areas pertinent to requirements and determine how proposed work will fulfill the requirements and what the gaps are.

3. Identify gaps between requirements and existing and ongoing work and the requirements.

4. Propose work to bridge the gap

5. Spec out time, FTE, etc. required to bridge the gap.

Process:

1. Atlas Network committee needs to be formed (Rob Gardner).
2. Initiate work on item 2 above. (Survey existing and on-going work)
3. May go to Brookhaven, but we would like it to go here
4. If it goes to us, we initiate the work on task 1.
5. Once user requirements are written, we pass it around the Atlas community for review and sign-off
6. Take the user requirements, and perform tasks 2 through 5 above to produce network proposal
7. Pass the network proposal document around Atlas community for review and sign-off
8. Seek Atlas community’s blessing to go forward to funding agencies
9. Send proposal to funding agencies.

Back to top