Changes between Version 20 and Version 21 of TIED


Ignore:
Timestamp:
07/17/09 10:09:34 (10 years ago)
Author:
hdempsey@bbn.com
Comment:

move extra description text to Technical Documents section (SOW is just the SOW from the contract (or part of it) for all GENI projects on the wiki)

Legend:

Unmodified
Added
Removed
Modified
  • TIED

    v20 v21  
    2727The scope of work on this project is to develop and evangelize a control framework that particularly emphasizes usability across different communities, through federation, rich trust/security models, and similar enabling mechanisms.
    2828
    29 TIED is based on the [http://fedd.isi.deterlab.net TIED/DETER federation system], which allows a researcher to construct experiments that span testbeds by dynamically acquiring resources from other testbeds and configuring them into a single experiment. As closely as possible that experiment will mimic a single DETER/Emulab experiment.
    30 
    31 This model fundamentally supports creation of cohesive experiments (slices) from independently administered resources (components/aggregates).  Because resources are independently administered and serves different communities, the authorization system needs to support a rich delegation structure, formal semantics, efficient negotiation, and clear auditing.  The [http://www.isso.sparta.com/research_projects/security_infrastructure/abac_overview.html ABAC] system meets those requirements; TIED is integrating this into the federation system.
    32 
    33 To make use of widely distributed components it is helpful to establish guaranteed network connections between them.  TIED is addressing this by federating with testbeds that represent dynamically allocatable wide-area network resources.  The prototyping plan is to use DRAGON interfaces to configure these resources.
    3429
    3530= Milestones =
     
    4742
    4843= Project Technical Documents =
     44
     45TIED is based on the [http://fedd.isi.deterlab.net TIED/DETER federation system], which allows a researcher to construct experiments that span testbeds by dynamically acquiring resources from other testbeds and configuring them into a single experiment. As closely as possible that experiment will mimic a single DETER/Emulab experiment.
     46
     47This model fundamentally supports creation of cohesive experiments (slices) from independently administered resources (components/aggregates).  Because resources are independently administered and serves different communities, the authorization system needs to support a rich delegation structure, formal semantics, efficient negotiation, and clear auditing.  The [http://www.isso.sparta.com/research_projects/security_infrastructure/abac_overview.html ABAC] system meets those requirements; TIED is integrating this into the federation system.
     48
     49To make use of widely distributed components it is helpful to establish guaranteed network connections between them.  TIED is addressing this by federating with testbeds that represent dynamically allocatable wide-area network resources.  The prototyping plan is to use DRAGON interfaces to configure these resources.
     50
    4951
    5052 [http://fedd.isi.deterlab.net The TIED/DETER Federation architecture and implementation]::