=== Topic 3  GENI I&M Resources ===

Team members:
  Vic Thomas - BBN/GPO  (yes)[[BR]]
  Jim Griffioen* - Univ Kentucky (yes)[[BR]]
  Martin Swany - Univ Delaware (yes)[[BR]]
  Camilo Viecco - Indiana Univ (yes)[[BR]]	
  Brian Hay – Univ Alaska  (yes)[[BR]]
  Giridhar Manepalli - CNRI (yes)[[BR]]
  
  *agreed to organize first writing and discussion

Significant question uncovered at workshop:[[BR]] 
Jim on 6/25 via email:  We should involve Rob Ricci in the discussion.[[BR]]

Consider these resources for I&M capabilities:[[BR]]
  1. Hosts, VMs, etc.
  2. Network connectivity
  3. Software, e.g., I&M software that can be included in an experiment
  4. I&M services
  5. I&M data flows and file transfers
  6. I&M data files stored in archives
  
For each item, consider how to:[[BR]]
  Create[[BR]]
  Name[[BR]]
  Register and discover[[BR]]
  Authorize and assign[[BR]]
  
Does each item have:[[BR]]
  Unique and persistent name?[[BR]]
  Unique and persistent identifier?[[BR]]
  Need to carefully consider this for all of GENI[[BR]] 
  
For each item, consider:[[BR]]
  Ownership[[BR]]
  What sort of policies the owner may want to apply[[BR]]
 
How are each of these discovered, specified, authorized and assigned:
  Always by mechanisms provided by the CF?
  With CF plus additional mechanisms?  

  Consider example of LS in perfSONAR  [[BR]]
  Consider example of data file stored in archive, owned by an experimenter
  Need to define and then compare these options[[BR]]
  Need to understand interop with CF for each option[[BR]]
  Does CF setup secondary authorization mechanisms in some cases?  If so, how?[[BR]]