XSEDEnet, currently implemented as an L3VPN on the Internet2 backbone, is designed to offer an isolated path for the exchange of data between XSEDE resources, particularly at Level 1 and Level 2 sites. However, if a site's routing policies, either internal or XSEDEnet-facing, would be demonstrably simplified by routing over XSEDEnet a superset of the routes associated with XSEDE resources, up to and including the site's Science DMZ, then that should be considered an appropriate use of XSEDEnet.