Introduction and Comparison of ISTP and HTTP
Today's Internet uses a best-effort model for delivery. This approach works very well for applications such as the web and protocols like HTTP. Unfortunately, it cannot support the seamless quality of experience necessary to offer high quality television services as well as other high bandwidth applications. Any new approach for delivering rich media content over the network ultimately requires service guarantees by network operators. These service guarantees are enabled under the Mediated Bandwidth Agreement (MBA) under the InterStream approach. Thus a new protocol, ISTP or the InterStream Transit Protocol, is required to work with that agreement and the service guarantee infrastructure. A comparison of HTTP and ISTP follows with an emphasis on the layering of the connection-oriented architecture on top of the Internet's existing best-effort delivery system. The necessity to layer and transition from a best-effort system to a guaranteed delivery system requires some similar and fundamentally different protocol intrinsics for ISTP versus HTTP.
Existing HTTP Methods
ISTP Intrinsics for Media Grid and Media Grid Objects
Request Connection Attributes
Request Media Grid Object (MGO) Attributes
Trace Connection (for Diagnostics)