DYNES-Deployments

[Jason Zurawski <>]

Hey Roy;

The original task of the DYNES design was focused on distributed data 
movement via dynamic networking and intelligent applications.  While it is 
possible to integrate in something like a router proxy, it was not a critical 
component at the time.  The same can be said about the concept of the science 
DMZ - the instrumentation that DYNES provides integrates into such an 
architecture, but one is not a critical cog to the functionality to the 
other.  We have encouraged all sites to adopt the basic ideas, and thus send 
the dynamic circuits around the firewall, but security policies do vary from 
institution to institution so it is not a universal truth that everyone will 
be running things in the same manner.  It will not be possible for the DYNES 
PIs to operate such a service given the grant does not fund continuous 
operations, however we would encourage the community to consider offering 
this service if there is general interest.  

Thanks;

-jason

On Jan 23, 2013, at 3:44 PM, "Hockett, Roy" 
<>
 wrote:

> Was any thought given to providing a router proxy for the DYNES 
> Switch/router, or
> including it in the Science DMZ architectures?  It seems that many problems 
> are 
> the cause of path preference and while a traceroute will tell you the path 
> it doesn't
> tell you why that path is preferred.  A router/switch proxy would give the 
> remote network
> engineers this capability.  Such a service could be protected using 
> shibboleth as most
> Internet2 schools have implemented shibboleth.
> 
> Thanks,
> -Roy Hockett
> 
> Network Architect,
> ITS Communications Systems and Data Centers
> University of Michigan
> Tel: (734) 763-7325
> Fax: (734) 615-1727
> email: 
>