Currently the OTLP exporter only export using the grpc protocol. Both the HTTP protocols required by the specification, http/json and http/protobuf, need to be supported.

Additionally, having gRPC libraries included in dependencies by default for all use of the OTLP exporter can be problematic for many users. Especially if these uses plan to use one of these HTTP protocols. When splitting out the supported protocols design thought needs to given to how we can possibly support a separated model. Possibly having a sub-module of the OTLP exporter module that contains "drivers", similar to the database/sql/driver, can achieve this.