From cb76f33351fa97a6e57e9401abc3f4943a4320a2 Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Mon, 26 Oct 2020 16:43:39 +0100 Subject: [PATCH 1/5] Remove the need to mantain third party propagators. --- specification/context/api-propagators.md | 13 +------------ 1 file changed, 1 insertion(+), 12 deletions(-) diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index f0da27275f8..9b19517c67d 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -321,18 +321,7 @@ organization and MUST be distributed as OpenTelemetry extension packages: Additional `Propagator`s implementing vendor-specific protocols such as AWS X-Ray (Note, AWS is used as an example, not as a requirement) trace header -protocol can be either maintained and distributed by their respective vendors or -as part of the OpenTelemetry organization. The reasons for maintaining those as -a community are: - -- Propagators are small pieces of code and their functionality is often publicly - documented (unlike exporters). -- People will often need to use propagators that are not specific to their - tracing or metrics vendor. For example, customers of tracing vendor may still - want to use an Cloud vendor-specific propagator for requests to the services - of this cloud vendor. -- Only a small number of propagators will need to exist, and this number will - shrink as vendors and users shift to W3C TraceContext. +protocol MUST be maintained and distributed by their respective vendors. ### B3 Requirements From 2009fa3d23ba3f5f674523b3d5b60c8a37548475 Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Wed, 11 Nov 2020 17:45:53 +0100 Subject: [PATCH 2/5] Update the docs to be more liberal. --- specification/context/api-propagators.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index 9b19517c67d..c1c1817c030 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -320,8 +320,10 @@ organization and MUST be distributed as OpenTelemetry extension packages: * [Jaeger](https://www.jaegertracing.io/docs/latest/client-libraries/#propagation-format). Additional `Propagator`s implementing vendor-specific protocols such as AWS -X-Ray (Note, AWS is used as an example, not as a requirement) trace header -protocol MUST be maintained and distributed by their respective vendors. +X-Ray trace header protocol MUST NOT be maintained nor distributed as part of +the core OpenTelemetry repositories. + +Note: AWS is used as an example, not as a requirement. ### B3 Requirements From 929b008c60685cb1b3d9736ff3594e5a23f445b3 Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Wed, 11 Nov 2020 17:56:53 +0100 Subject: [PATCH 3/5] Update specification/context/api-propagators.md Co-authored-by: Yuri Shkuro --- specification/context/api-propagators.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index 895664752b4..38e573ac9a8 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -320,7 +320,7 @@ organization and MUST be distributed as OpenTelemetry extension packages: * [Jaeger](https://www.jaegertracing.io/docs/latest/client-libraries/#propagation-format). Additional `Propagator`s implementing vendor-specific protocols such as AWS -X-Ray trace header protocol MUST NOT be maintained nor distributed as part of +X-Ray trace header protocol MUST NOT be maintained or distributed as part of the core OpenTelemetry repositories. Note: AWS is used as an example, not as a requirement. From d9d04a6ca40685061cf5eee78140d8cc4a4436bf Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Wed, 11 Nov 2020 19:08:30 +0100 Subject: [PATCH 4/5] Update specification/context/api-propagators.md Co-authored-by: (Eliseo) Nathaniel Ruiz Nowell --- specification/context/api-propagators.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index 38e573ac9a8..b94a24c7882 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -321,7 +321,7 @@ organization and MUST be distributed as OpenTelemetry extension packages: Additional `Propagator`s implementing vendor-specific protocols such as AWS X-Ray trace header protocol MUST NOT be maintained or distributed as part of -the core OpenTelemetry repositories. +the Core OpenTelemetry repositories. Note: AWS is used as an example, not as a requirement. From 937941052e226582de1fe01dbe9a2b1986d65d48 Mon Sep 17 00:00:00 2001 From: Carlos Alberto Cortez Date: Wed, 11 Nov 2020 19:09:14 +0100 Subject: [PATCH 5/5] Remove the mention of XRay propagator. --- specification/context/api-propagators.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/specification/context/api-propagators.md b/specification/context/api-propagators.md index b94a24c7882..1f573942450 100644 --- a/specification/context/api-propagators.md +++ b/specification/context/api-propagators.md @@ -323,8 +323,6 @@ Additional `Propagator`s implementing vendor-specific protocols such as AWS X-Ray trace header protocol MUST NOT be maintained or distributed as part of the Core OpenTelemetry repositories. -Note: AWS is used as an example, not as a requirement. - ### B3 Requirements B3 has both single and multi-header encodings. It also has semantics that do not