w3c/trace-context

Issues

• Should tracing headers be included in 304 Not Modified responses?

  #554 opened 8 months ago by mitar
  14

• Add more normative text for flags processing in traceresponse

  #540 opened 7 months ago by kalyanaj
  0

• Proposal: Allow common base64 encoding in tracestate values

  #551 opened 9 months ago by feldentm-SAP
  5

• tracestate response header proposal

  #483 opened 2 years ago by dyladan
  4

• Proposal: Add a "propagation-only-parent" flag to be set to true if parents is a no-tracing service

  #550 opened 9 months ago by bogdandrutu
  4

• Document handling of tracestate duplicate keys

  #548 opened 8 months ago by pellared
  6

• Does this specification define a way to handle retries?

  #549 opened 9 months ago by ben221199
  4

• Autopublishing level2/Level3 specs need to work with multiple markdown files

  #545 opened a year ago by kalyanaj
  0

• Random part of trace ID should be uniformly distributed

  #544 opened a year ago by oertl
  2

• Enable automatic publishing for Level 2 branch

  #502 opened 2 years ago by kalyanaj
  0

• Level 3 spec: Update privacy section to include information about traceresponse headers.

  #542 opened a year ago by kalyanaj
  0

• Incorporate Level 2 changes (random trace id flag) into traceresponse header in Level 3

  #532 opened a year ago by kalyanaj
  0

• Update tests to test Trace Context level 2 by default

  #529 opened a year ago by kalyanaj
  0

• Trace Context Level 2: Self review for i18n

  #498 opened a year ago by kalyanaj
  1

• Trace Context Level 2: Self-review for accessibility

  #499 opened 2 years ago by kalyanaj
  0

• Self-Review Questionnaire for Trace Context Level 2: Security and Privacy

  #496 opened a year ago by kalyanaj
  1

• Need to publish latest draft of trace-context-2

  #493 opened 2 years ago by kalyanaj
  3

• Start Wide Review for Trace Context Level 2 Spec

  #492 opened a year ago by kalyanaj
  6

• Trace Context: Apache Kafka protocol specification

  #504 opened 2 years ago by ppatierno
  5

• Change the defining document for HTTP from RFC7230 to RFC9110

  #519 opened a year ago by kalyanaj
  2

• specification of lowercase is incomplete

  #506 opened 2 years ago by aphillips
  4

• Incorrect randomness claim in 50-privacy.md

  #481 opened a year ago by dyladan
  4

• When headers should be propagated in browsers should be made more clear

  #510 opened a year ago by pes10k
  2

• Version number relationship to ASCII and UTF-8

  #507 opened 2 years ago by aphillips
  1

• Why should keys be restricted to lowercase ASCII?

  #508 opened 2 years ago by aphillips
  7

• Adopt either span-id or parent-id for section headings

  #509 opened 2 years ago by pes10k
  4

• Update wording on "response headers" in privacy section to disambiguate from traceresponse headers.

  #487 opened 2 years ago by kalyanaj
  1

• Request to republish level-1 spec (to publish a recent editorial change)

  #503 opened 2 years ago by kalyanaj
  0

• Inconsistent text style

  #485 opened 2 years ago by dyladan
  2

• Randomness flag bit

  #467 opened 2 years ago by bogdandrutu
  7

• Clarify tracestate keys MUST be unique

  #446 opened 3 years ago by codefromthecrypt
  31

• Expected behavior with regard to starting a trace should be spelled out explicitly

  #442 opened 3 years ago by basti1302
  2

• Release trace context level-1

  #469 opened 3 years ago by dyladan
  9

• term `negative sampling decision` may not be very clear to a reader

  #444 opened 3 years ago by dyladan
  0

• Vendor information in the response from traced service

  #466 opened 3 years ago by wjch-krl
  5

• Add "request" to glossary

  #452 opened 3 years ago by SergeyKanzhelev
  1

• Consider trace context support for probability sampling

  #463 opened 3 years ago by jmacd
  2

• Confusion between vendor and tenant in tracestate keys

  #459 opened 3 years ago by taylor-hunt-kr
  2

• Level-1 Erratum Invalid ABNF

  #461 opened 3 years ago by dyladan
  1

• level-1 branch contains changes not in level-1

  #460 opened 3 years ago by dyladan
  1

• Behavior when passing tracestate of ''

  #470 opened 3 years ago by bizob2828
  4

• Clarify how tracestate can or cannot be used by application developers

  #439 opened 3 years ago by gfraiteur
  2

• Use of W3C Trace-Context with multiple agents in a single process, inject issue

  #451 opened 3 years ago by pavolloffay
  3

• Rename master branch to main

  #454 opened 3 years ago by dyladan
  1

• Microsoft nominates new member as Chair

  #453 opened 3 years ago by Kanwaldeep
  3

• Should a tracestate key always be allowed to start with a lowercase letter or digit?

  #441 opened 3 years ago by MrAlias
  2

• Define entry/value length/size consistently

  #449 opened 3 years ago by dyladan
  0

• Move response header Returning the traceresponse Field to non-normative processing section.

  #445 opened 3 years ago by dyladan
  0

• How should tracestate list members be truncated when they exceed 32?

  #440 opened 3 years ago by MrAlias
  1

• Consider renaming parent-id / child-id to span-id

  #447 opened 3 years ago by mwear
  8