Will it be accepted to contribute non-OTLP HTTP encoding in OTLP/HTTP receiver on top protobuf/JSON encoding

[thiruvikraman-subburaman]

Current, OTLP/HTTP receiver is accepting signals only in OTLP JSON format but is it allowed to have a contribution in OTLP/HTTP receiver to support non-OTLP HTTP encoding as well so could be generic to accept both OTLP/non-OTLP formats and especially will benefit with the smooth migration for the users from different sources already following non-OTLP json schema towards OpenTelemetry?