And my current thoughts are that since routers will be ones routing between BACnet/SC and BACnet/IP and/or MSTP, we would be implementing as necessary to achieve Internet NAT Routing features using possibly SmartX Servers (ES/AS). This technology requires a BACnet/SC Hub, so we will need to have that feature available. But all BACnet/SC are going to require certificates to manage who is in the secure group or not.
This is where I am going to derail my own discussion because we need to have a way to manage certificates for BACnet/SC AND existing services (HTTPS for Webstation and possibly ES/AS Communication (aka CSP). It is difficult to manage these certificates and there is a technology available to do so that I think needs to be backed into EBO BEFORE BACnet/SC is implemented and that is Automated Certificate Management Environment (ACME v2) that is available and standards compliant to automatically manage certificates. If automation was not awesome enough features, this lets one use shorter expiration dates and not have to bother with broken revocation schemes that IT industry has yet to get correctly implemented.
Like others I am hopeful to get BACnet/SC in the future of EBO, but I hope we get certificate management sooner that will help current features and the future BACnet/SC feature.
PLEASE CONTINUE the BACnet/SC discussion here as I would love for our community to evaluate different views of the technology as we look to embrace it in the future.