Reorder points on ID generation

open-telemetry · Dec 15, 2020 · 2581331 · 2581331
1 parent b973639
commit 2581331
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/spec-compliance-matrix.md b/spec-compliance-matrix.md
@@ -69,7 +69,7 @@ status of the feature is not known.
 |Allow samplers to modify tracestate           |   | +  |   | +    |    | +    |   | +  |   |    |     |
 |ShouldSample gets full parent Context         |   | +  | + | +    |    | +    |   |    |   |    |     |
 |[New Span ID created also for non-recording Spans](specification/trace/sdk.md#sdk-span-creation) |   |    |   | +    |    |      |   |    |   |    |     |
-|SDK Trace & Span ID generation is customizable|   | +  |   |+     |    |      |   |    |   | +  |
+|SDK Trace & Span ID generation is customizable|   | +  |   |+     |    |      |   |    |   | +  |   |
 
 ## Baggage
 

diff --git a/specification/trace/sdk.md b/specification/trace/sdk.md
@@ -222,12 +222,12 @@ Note: Implementation-wise, this could mean that `Tracer` instances have a
 reference to their `TracerProvider` and access configuration only via this
 reference.
 
+The SDK MUST by default randomly generate the bytes for both the `TraceId` and
+the `SpanId`.
+
 The SDK MUST provide a mechanism for customizing the way IDs are generated for
 both the `TraceId` and the `SpanId`.
 
-The SDK SHOULD by default randomly generate the bytes for both the `TraceId` and
-the `SpanId`.
-
 The SDK MAY provide this functionality by allowing custom implementations of
 an interface like `IdsGenerator` below, which provides extension points for two
 methods, one to generate a `SpanID` and one to generate a `TraceId`.