editorial: Level 2 cr snapshot (#530)

* Fixed URL fragment for field order in HTTP

* CR exit criteria

* Update link to implementation report

* Update spec/02-sotd.md

* Update index.html to retrigger checks

---------

Co-authored-by: Bastian Krol <[email protected]>
Co-authored-by: J. Kalyana Sundaram <[email protected]>

index.html

@@ -7,7 +7,7 @@
   <script class='remove'>
     var respecConfig = {
       specStatus: "ED",
-      implementationReportURI: "https://github.com/w3c/trace-context/#reference-implementations",
+      implementationReportURI: "https://w3c.github.io/trace-context/implementations",
       /* previousMaturity: "CR",
       previousPublishDate : "2019-08-13",
       crEnd: "2019-10-08",*/
@@ -59,7 +59,6 @@
         companyURL: "https://dynatrace.com",
         w3cid: "90530"
       }],
-
       github: {
         repoURL: "https://github.com/w3c/trace-context/",
         branch: "main",

spec/02-sotd.md

@@ -1 +1,3 @@
 This new version adds considerations for the generation of the `trace-id` and `span-id` fields, and adds the random trace ID flag.
+
+As an exit criteria, the Working Group intends to demonstrate at least 2 implementations adopting this specification and making use of it, using a test suite.

spec/20-http_request_header_format.md

@@ -260,7 +260,7 @@ In order to increase interoperability across multiple protocols and encourage su
 
 ### tracestate Header Field Values
 
-The `tracestate` field may contain any [=opaque=] value in any of the keys. Tracestate MAY be sent or received as multiple header fields. Multiple tracestate header fields MUST be handled as specified by <a data-cite='!RFC9110#field.order'>RFC9110 Section 5.3 Field Order</a>. The `tracestate` header SHOULD be sent as a single field when possible, but MAY be split into multiple header fields. When sending `tracestate` as multiple header fields, it MUST be split according to <a data-cite='!RFC9110#field.order'>RFC9110</a>. When receiving multiple `tracestate` header fields, they MUST be combined into a single header according to <a data-cite='!RFC9110#field.order'>RFC9110</a>.
+The `tracestate` field may contain any [=opaque=] value in any of the keys. Tracestate MAY be sent or received as multiple header fields. Multiple tracestate header fields MUST be handled as specified by <a data-cite='!RFC9110#name-field-order'>RFC9110 Section 5.3 Field Order</a>. The `tracestate` header SHOULD be sent as a single field when possible, but MAY be split into multiple header fields. When sending `tracestate` as multiple header fields, it MUST be split according to <a data-cite='!RFC9110#name-field-order'>RFC9110</a>. When receiving multiple `tracestate` header fields, they MUST be combined into a single header according to <a data-cite='!RFC9110#name-field-order'>RFC9110</a>.
 
 This section uses the Augmented Backus-Naur Form (ABNF) notation of [[!RFC5234]], including the DIGIT rule in <a data-cite='!RFC5234#appendix-B.1'>appendix B.1 for RFC5234</a>. It also includes the `OWS` rule from <a data-cite='!RFC9110#whitespace'>RFC9110 section 5.6.3</a>.