Register OTLP/HTTP port 4318 with IANA #1846
Assignees
Labels
spec:protocol
Related to the specification/protocol directory
Comments
tigrannajaryan
added
the
spec:protocol
|
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files I suggest we hold this issue and don't submit to IANA just yet until we have more clarity on this. Depending on the outcome we may need to do things a bit differently here in the spec. |
|
@tigrannajaryan We are expected to do a monthly release by EOW. What do you think we should do? Revert this change for now? |
@carlosalberto yes, I think reverting is a good idea. Let's aim to settle this for the release after this one. |
|
I will submit a PR. |
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-specification
that referenced
this issue
Aug 4, 2021
This reverts commit cce1d59 until we have the final decision about the ability to have a single port, see: open-telemetry#1846 (comment)
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-specification
that referenced
this issue
Aug 4, 2021
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d59 until we have the final decision about the ability to have a single port, see: open-telemetry#1846 (comment)
|
Reverting PR submitted: #1847 |
tigrannajaryan
added a commit
that referenced
this issue
Aug 6, 2021
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d59 until we have the final decision about the ability to have a single port, see: #1846 (comment)
|
Closing this issue for now to avoid accidentally moving forward with IANA. I will reopen if needed. |
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-proto
that referenced
this issue
Apr 20, 2023
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
tigrannajaryan
added a commit
to tigrannajaryan/opentelemetry-proto
that referenced
this issue
Apr 21, 2023
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
tigrannajaryan
added a commit
to open-telemetry/opentelemetry-proto
that referenced
this issue
Apr 27, 2023
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
|
I think we should reconsider this: port 4318 is documented and used quite often, and I think it might make sense to register this port with IANA. Should a new issue be created, or is it OK to just reopen this? |
|
IIRC, IANA did not want to register a second port. |
|
+1 to Tigran’s comment. He and I requested a second port a few years ago, and they told us to just use the first one for multiple purposes. We asked for reconsideration (with an explanation) and were told no.
…________________________________
From: Tigran Najaryan ***@***.***>
Sent: Friday, March 15, 2024 7:34:43 PM
To: open-telemetry/opentelemetry-specification ***@***.***>
Cc: Morgan McLean ***@***.***>; Mention ***@***.***>
Subject: Re: [open-telemetry/opentelemetry-specification] Register OTLP/HTTP port 4318 with IANA (#1846)
IIRC, IANA did not want to register a second port.
—
Reply to this email directly, view it on GitHub<#1846 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAIXLK22OZ43DEQQ5FPVLO3YYNENHAVCNFSM5BQTCI72U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMBQGAZTEOJUGI2Q>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
joaopgrassi
pushed a commit
to dynatrace-oss-contrib/semantic-conventions
that referenced
this issue
Mar 21, 2024
open-telemetry#1847) Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
|
Thank you for the extra context, I was not aware of those attempts. |
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this issue
Jun 21, 2024
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this issue
Jun 21, 2024
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this issue
Jun 21, 2024
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
VinozzZ
pushed a commit
to VinozzZ/opentelemetry-proto
that referenced
this issue
Jun 21, 2024
Apparently there is new evidence that one port may work after all: https://github.com/open-telemetry/opentelemetry-collector/pull/3765/files This reverts commit cce1d5996873de38a68e05eafa4d5e224df9b8f1 until we have the final decision about the ability to have a single port, see: open-telemetry/opentelemetry-specification#1846 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We have recently added a new OTLP/HTTP port 4318 to the specification (in addition to previously existing OTLP/gRPC port 4317).
We need to register the new port with IANA. Port 4317 description currently says "OpenTelemetry Protocol". For port 4318 we can probably use "OpenTelemetry Protocol, HTTP Transport" or "OpenTelemetry Protocol, OTLP/HTTP". Ideally also change description for port 4317 to be uniform to something like "OpenTelemetry Protocol, gRPC Transport" or "OpenTelemetry Protocol, OTLP/gRPC".
@mtwo you did the IANA submission for port 4317, can you help with the new port as well?
The text was updated successfully, but these errors were encountered: