From 3db304a7660116a8b1df90c902ff62f6c9ed5a51 Mon Sep 17 00:00:00 2001
From: Robb Kidd <robb@thekidds.org>
Date: Wed, 4 Jan 2023 14:47:49 -0500
Subject: [PATCH] Correct exporter user-agent format  (#3052)

---
 CHANGELOG.md                       | 3 +++
 specification/protocol/exporter.md | 2 +-
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 40e15feed3f..9fa8748835b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,9 @@ release.
 
 ## Unreleased
 
+- Remove spaces from example exporter User-Agent header to conform to RFC7231 & RFC7230.
+  [#3052](https://github.com/open-telemetry/opentelemetry-specification/pull/3052)
+
 ### Context
 
 ### Traces
diff --git a/specification/protocol/exporter.md b/specification/protocol/exporter.md
index 1404c33fd7c..4d58a4d3870 100644
--- a/specification/protocol/exporter.md
+++ b/specification/protocol/exporter.md
@@ -165,7 +165,7 @@ For OTLP/HTTP, the errors `408 (Request Timeout)` and `5xx (Server Errors)` are
 OpenTelemetry protocol exporters SHOULD emit a User-Agent header to at a minimum identify the exporter, the language of its implementation, and the version of the exporter. For example, the Python OTLP exporter version 1.2.3 would report the following:
 
 ```
-OTel OTLP Exporter Python/1.2.3
+OTel-OTLP-Exporter-Python/1.2.3
 ```
 
 The format of the header SHOULD follow [RFC 7231][rfc-7231]. The conventions used for specifying the OpenTelemetry SDK language and version are available in the [Resource semantic conventions][resource-semconv].