Changes between Version 3 and Version 4 of FeddPubs


Ignore:
Timestamp:
Oct 25, 2008 8:10:44 AM (16 years ago)
Author:
faber
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • FeddPubs

    v3 v4  
    1 = Deter Federation Architecture Publications =
     1= Deter Federation Architecture =
    22
    3  * Ted Faber and John Wroclawski, "[http://www.usenix.org/events/cset08/tech/full_papers/faber/faber_html/ Access Control for Federation of Emulab-based Network Testbeds]," In Proceedings of the !CyberSecurity Experimentation and Test (CSET) Workshop, San Jose, (July 2008). ([http://www.usenix.org/events/cset08/tech/full_papers/faber/faber.pdf pdf])
    4  * Ted Faber, John Wroclawski, and Kevin Lahey, "[http://www.usenix.org/events/deter07/tech/full_papers/faber/faber_html/  A DETER Federation Architecture]," Proceedings of the DETER Community Workshop on Cyper Security Experimentation and Test, Boston, MA, (August 2007). ([http://www.usenix.org/events/deter07/tech/full_papers/faber/faber.pdf pdf])
    5 
    6 These papers lay out the general model for DETER's Federation and fedd's role in it, and reading them is very helpful in understading the software.  As a starting point, the [http://www.usenix.org/events/cset08/tech/full_papers/faber/faber_html/ 2008 CSET paper] describes the architecture, as follows.
     3The papers below lay out the general model for DETER's Federation and fedd's role in it, and reading them is very helpful in understanding the software.  As a starting point, the [http://www.usenix.org/events/cset08/tech/full_papers/faber/faber_html/ 2008 CSET paper] describes the architecture, as follows.
    74
    85The full federation architecture must meet three goals. First, it must provide experimenters and their tools with sufficient information to guide the process of decomposing experiments into testbeds. To accomplish this the architecture must provide scalable channels for testbeds to advertise or respond to queries about the resources they permit to be federated; this information may be filtered based on the identity of the experimenter or abstracted for scaling. Secondly, experiments must be decomposed and embedded into federated testbeds – we focus on this below. Finally the architecture must support experimentation across the federated experiment. Part of this goal is to generate a cohesive, scalable experimental environment that may be represented differently to different experimenters. For example, experimenters representing attackers and defenders in a competitive experiment may be provided limited knowledge of their opponents' topology. This paper focuses on the decomposition and embedding facets of the architecture – specifically the access control.
    … …  
    1916
    2017On the other end, the federator must communicate with federant testbeds for two basic operations: requesting resource allocation within the federant and embedding a topology subgraph on that federant. Emulab-based testbeds have interfaces for embedding topologies remotely, and the DETER architecture uses those interfaces directly.
     18
     19Fedd is our implementation of the federator in the diagram above.
     20
     21 * Ted Faber and John Wroclawski, "[http://www.usenix.org/events/cset08/tech/full_papers/faber/faber_html/ Access Control for Federation of Emulab-based Network Testbeds]," In Proceedings of the !CyberSecurity Experimentation and Test (CSET) Workshop, San Jose, (July 2008). ([http://www.usenix.org/events/cset08/tech/full_papers/faber/faber.pdf pdf])
     22 * Ted Faber, John Wroclawski, and Kevin Lahey, "[http://www.usenix.org/events/deter07/tech/full_papers/faber/faber_html/  A DETER Federation Architecture]," Proceedings of the DETER Community Workshop on Cyper Security Experimentation and Test, Boston, MA, (August 2007). ([http://www.usenix.org/events/deter07/tech/full_papers/faber/faber.pdf pdf])