Bid Request Interoperability Standards

Compliant

For the above items marked as Compliant

·         Hypertext Transfer Protocol (HTTP/1.1)

Verastream Host Integrator includes and uses Apache Web Server and Jetty Servlet Engine which document supporting RFC2616 which has been broken down into RFC 7230, 7231, 7232, 7233, 7234, 7235, 7236, 7237 listed above.

·         Lightweight Directory Access Protocol (LDAP)

Verastream Host Integrator Administrative Console has support for Active Directory, Apache DS, OpenLDAP, and Generic LDAP that allows you to define your own schema. https://documentation.microfocus.com/help/index.jsp?topic=%2Fcom.attachmate.vhi.webbuilder.help%2Fhtml%2Freference%2Fwb_introduction.xhtml

(Note:  Our proposed solution design has authentication being addressed via the web server(s) to LDAP and advanced authentication servers)

·         Hypertext Markup Language 5 (HTML5)

Verastream Host Integrator Web Builder component has the ability to display mainframe applications using HTML5.  https://documentation.microfocus.com/help/index.jsp?topic=%2Fcom.attachmate.vhi.webbuilder.help%2Fhtml%2Freference%2Fwb_introduction.xhtml

Non-compliant

·         Upgrading to TLS within HTTP/1.1(HTTPS)       RFC2817   

Verastream Host Integrator does not comply with RFC2817; it does comply with RFC 2818 https://tools.ietf.org/html/rfc2818 which describes the usage of TLS over the same port as an HTTP session.   This enables increased security rather than allowing an HTTP connection to upgrade to an HTTPS connection: we require HTTPS to begin with, and users can shut off the HTTP port if they wish, allowing only secure connections.

Non-applicable

·         The Extensible Hypertext Markup Language (XHTML v1.0)(in use for HTML 4)   XTML 1.0

Our proposed solution design will not use HTML 4.