<?xml version="1.0" encoding="UTF-8"?>
  <?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?>
  <!-- generated by https://github.com/cabo/kramdown-rfc version 1.7.43 (Ruby 3.4.12) -->


<!DOCTYPE rfc  [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">

]>


<rfc ipr="trust200902" docName="draft-rkr-synthetic-twin-header-00" category="info" submissionType="IETF" tocInclude="true" sortRefs="true" symRefs="true">
  <front>
    <title abbrev="Synthetic-Twin Field">The Synthetic-Twin HTTP Field</title>

    <author initials="A. K." surname="Ravipati" fullname="Ajay Kumar Ravipati">
      <organization>RKR Networks</organization>
      <address>
        <email>aj@rkr-networks.com</email>
      </address>
    </author>

    <date year="2026" month="November" day="15"/>

    <area>Web and Internet Transport</area>
    
    <keyword>synthetic twin</keyword> <keyword>synthetic traffic</keyword> <keyword>test traffic</keyword> <keyword>HTTP</keyword> <keyword>structured fields</keyword>

    <abstract>


<?line 55?>

<t>This document defines the Synthetic-Twin HTTP field. A sender adds the
field to an HTTP request or response to say that the message was made by,
or for, a synthetic twin and is not real user activity. A synthetic twin
is a software model of a network estate, existing or planned. The field
says which kind of synthetic message it is and can carry one opaque
identifier. This lets operators keep synthetic messages apart from
production messages in logs, analytics, billing, and alerting.</t>



    </abstract>



  </front>

  <middle>


<?line 65?>

<section anchor="introduction"><name>Introduction</name>

<t>A synthetic twin is a software model of a network estate, existing or
planned. Operators use a synthetic twin to try out changes and to run
what-if tests before, or without, touching the real estate.</t>

<t>This work produces HTTP messages that are not real user activity. Some
of them stay inside the synthetic twin. Others are sent on purpose to
real services. Today these messages are hard to tell apart from real
traffic. As a result:</t>

<t><list style="symbols">
  <t>synthetic messages can distort analytics, billing, capacity data, and
security alerts;</t>
  <t>a synthetic message that reaches a service it was not meant for is
hard to spot; and</t>
  <t>there is no common way to link a message back to the work that made
it.</t>
</list></t>

<t>Tools often solve this with private fields that differ from product to
product, or with special User-Agent values. Neither works across
products.</t>

<t>This document defines one HTTP field, Synthetic-Twin, that carries a
small, fixed set of facts: that the message is synthetic, which of two
kinds it is, and an optional opaque identifier. It uses Structured Field
Values <xref target="RFC9651"/>, following the advice for new HTTP fields in
<xref target="RFC9205"/>.</t>

<t>The field is a label. It is not proof of anything, and it gives no extra
rights to the sender (see <xref target="security"/>).</t>

<t>This document does not say when a sender may send synthetic messages to
a service. That is a matter between the sender and the operator of the
service.</t>

<section anchor="notational-conventions"><name>Notational Conventions</name>

<t>The key words "<bcp14>MUST</bcp14>", "<bcp14>MUST NOT</bcp14>", "<bcp14>REQUIRED</bcp14>", "<bcp14>SHALL</bcp14>", "<bcp14>SHALL
NOT</bcp14>", "<bcp14>SHOULD</bcp14>", "<bcp14>SHOULD NOT</bcp14>", "<bcp14>RECOMMENDED</bcp14>", "<bcp14>NOT RECOMMENDED</bcp14>",
"<bcp14>MAY</bcp14>", and "<bcp14>OPTIONAL</bcp14>" in this document are to be interpreted as
described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they
appear in all capitals, as shown here.</t>

<?line -18?>

<t>This document uses the Structured Field types Item, Token, and String,
and Parameters, from <xref target="RFC9651"/>.</t>

</section>
</section>
<section anchor="terminology"><name>Terminology</name>

<dl>
  <dt>Synthetic twin:</dt>
  <dd>
    <t>A software model of a network estate, existing or planned.</t>
  </dd>
  <dt>Modeled service:</dt>
  <dd>
    <t>A service that exists only inside a synthetic twin.</t>
  </dd>
  <dt>Real service:</dt>
  <dd>
    <t>Any service that is not a modeled service.</t>
  </dd>
  <dt>Synthetic message:</dt>
  <dd>
    <t>An HTTP request or response made by, or for, a synthetic twin, and not
by real user or production activity.</t>
  </dd>
  <dt>Administrative domain:</dt>
  <dd>
    <t>The set of networks and services run by one operator, or by parties
that have agreed to treat each other's synthetic messages as their
own.</t>
  </dd>
</dl>

</section>
<section anchor="field"><name>The Synthetic-Twin Field</name>

<t>The Synthetic-Twin field is an Item Structured Field
(<xref section="3.3" sectionFormat="of" target="RFC9651"/>). It can appear in requests and in
responses. Its value is a Token that gives the kind of synthetic
message.</t>

<t>This document defines two values:</t>

<dl>
  <dt>model:</dt>
  <dd>
    <t>The message was made inside a synthetic twin and is addressed to a
modeled service, or is a response from a modeled service. It is not
meant to reach a real service.</t>
  </dd>
  <dt>probe:</dt>
  <dd>
    <t>The message is a synthetic request sent on purpose to a real service,
or a response to such a request. It is not user activity.</t>
  </dd>
</dl>

<t>This document defines one Parameter:</t>

<dl>
  <dt>id:</dt>
  <dd>
    <t><bcp14>OPTIONAL</bcp14>. A String that identifies the work the message belongs to.
The value is opaque: it has meaning only to the sender. It <bcp14>MUST</bcp14> be 1
to 64 characters long and <bcp14>MUST</bcp14> use only the characters a-z, A-Z, 0-9,
"-", and "_".</t>
  </dd>
</dl>

<t>For example:</t>

<figure><sourcecode type="http-message"><![CDATA[
Synthetic-Twin: probe; id="7f3a9c2104b8e6d1"
]]></sourcecode></figure>

<t>Senders <bcp14>MUST NOT</bcp14> send more than one Synthetic-Twin field line in a
message, and <bcp14>MUST NOT</bcp14> send the field in a trailer section
(<xref section="6.5" sectionFormat="of" target="RFC9110"/>).</t>

<section anchor="invalid"><name>Handling Unknown and Invalid Values</name>

<t>Receivers <bcp14>MUST</bcp14> ignore Parameters they do not understand. This allows
later documents to add Parameters.</t>

<t>If the Token is a value the receiver does not understand, the receiver
<bcp14>MUST</bcp14> still treat the message as a synthetic message, and <bcp14>MUST</bcp14> handle it
as "probe". This gives one fallback: the message is synthetic, and it
may be reaching a real service.</t>

<t>If the id Parameter is not a String, or breaks the length or character
rules above, the receiver <bcp14>MUST</bcp14> ignore the id Parameter and use the rest
of the field.</t>

<t>If the field cannot be parsed as an Item, or the Item is not a Token,
the receiver <bcp14>MUST</bcp14> ignore the field, as <xref section="4.2" sectionFormat="of" target="RFC9651"/>
requires for parse failures. This is also the result when a message
has more than one Synthetic-Twin field line. A receiver <bcp14>MAY</bcp14> record that
an invalid Synthetic-Twin field was present, but <bcp14>MUST NOT</bcp14> treat the
message as a synthetic message for any other purpose.</t>

<t>A receiver <bcp14>MUST</bcp14> ignore the field when it appears in a trailer section.</t>

</section>
</section>
<section anchor="semantics"><name>Semantics</name>

<section anchor="meaning"><name>Meaning</name>

<t>The presence of a valid Synthetic-Twin field means: "the sender states
that this message is a synthetic message of the given kind." It does not
mean that the sender is trusted, allowed, or authenticated.</t>

<t>The absence of the field means nothing. A message without the field is
not proven to be production traffic.</t>

</section>
<section anchor="senders"><name>Senders</name>

<t>A synthetic twin, or a tool acting for it, <bcp14>SHOULD</bcp14> add the field to every
synthetic HTTP request it sends: with the value "model" when the request
is addressed to a modeled service, and with the value "probe" when it is
addressed to a real service.</t>

<t>A modeled service <bcp14>SHOULD</bcp14> add the field, with the value "model", to its
responses.</t>

<t>A sender that uses the id Parameter <bcp14>SHOULD</bcp14> use the same value for all
messages that belong to the same piece of work, so that a receiver can
group them.</t>

<t>A user agent that follows <xref target="FETCH"/> treats this field as one that needs
a preflight request when it is added to a cross-origin request. Tools
that drive a browser need to allow for the extra request.</t>

</section>
<section anchor="propagation"><name>Propagation</name>

<t>A service that makes further HTTP requests in order to handle a
synthetic request <bcp14>SHOULD</bcp14> add the Synthetic-Twin field, unchanged, to
those requests when they stay inside its administrative domain. Without
this, the work done further along on behalf of a synthetic request looks
like production activity.</t>

<t>A service <bcp14>MUST NOT</bcp14> add the field to a request that was not caused by a
synthetic request.</t>

</section>
<section anchor="receivers"><name>Receivers</name>

<t>A receiver <bcp14>MAY</bcp14> use the field to:</t>

<t><list style="symbols">
  <t>keep synthetic messages out of analytics, billing, and capacity data;</t>
  <t>tag logs, traces, and flow records as synthetic, with the id;</t>
  <t>send synthetic messages to a test path or a test data store; and</t>
  <t>raise an alert when a "model" message reaches a real service.</t>
</list></t>

<t>A real service that receives a "model" message <bcp14>SHOULD</bcp14> log it as
misdirected.</t>

<t>A receiver <bcp14>MUST NOT</bcp14> use the field alone to skip authentication,
authorization, rate limits, input checks, or security monitoring. See
<xref target="security"/>.</t>

</section>
<section anchor="caching"><name>Responses and Caching</name>

<t>A real service that receives a request with a valid Synthetic-Twin field
<bcp14>MAY</bcp14> add the same field, unchanged, to its response, to confirm that it
saw the label.</t>

<t>A response that carries the field, or that differs because the request
carried the field, is not meant to be reused by a cache for a
production request. A server that sends such a response <bcp14>MUST</bcp14> either:</t>

<t><list style="symbols">
  <t>mark it with the "no-store" response directive
(<xref section="5.2.2.5" sectionFormat="of" target="RFC9111"/>); or</t>
  <t>list "Synthetic-Twin" in the Vary response field
(<xref section="12.5.5" sectionFormat="of" target="RFC9110"/>).</t>
</list></t>

<t>When the id Parameter changes from one piece of work to the next,
"no-store" is preferred, because Vary would keep a separate cache entry
for each id value.</t>

</section>
<section anchor="intermediaries"><name>Intermediaries</name>

<t>Proxies and gateways <bcp14>SHOULD</bcp14> forward the field unchanged inside an
administrative domain.</t>

<t>A gateway that sends a message out of its administrative domain <bcp14>SHOULD</bcp14>
remove the id Parameter, unless the operator has chosen to keep it. It
<bcp14>MAY</bcp14> remove the whole field.</t>

<t>A gateway that receives the field on a message from outside its
administrative domain has no reason to believe it. The gateway <bcp14>SHOULD</bcp14>
either remove the field or record that it arrived from outside, unless
the sender has been authenticated as a known source of synthetic
messages (see <xref target="security"/>).</t>

</section>
<section anchor="relation-to-other-fields"><name>Relation to Other Fields</name>

<t>The field does not replace trace context fields such as traceparent
<xref target="TRACE-CONTEXT"/>. A message can carry both: traceparent links the
message to a trace, and Synthetic-Twin says that the trace is synthetic.</t>

<t>The baggage field <xref target="BAGGAGE"/> can carry any key and value chosen by an
application, so two products rarely agree on one. Synthetic-Twin gives
one registered name and one fixed meaning that proxies, log tools, and
alert rules can match without knowing the application.</t>

<t>The User-Agent field (<xref section="10.1.5" sectionFormat="of" target="RFC9110"/>) names the software
that made a request. It does not say whether the request is synthetic,
and it is not sent on responses.</t>

</section>
</section>
<section anchor="examples"><name>Examples</name>

<t>A probe sent to a real service:</t>

<figure><sourcecode type="http-message"><![CDATA[
GET /health HTTP/1.1
Host: app.example.net
Synthetic-Twin: probe; id="7f3a9c2104b8e6d1"
]]></sourcecode></figure>

<t>The real service confirms that it saw the label, and keeps the response
out of caches:</t>

<figure><sourcecode type="http-message"><![CDATA[
HTTP/1.1 200 OK
Content-Type: application/json
Cache-Control: no-store
Synthetic-Twin: probe; id="7f3a9c2104b8e6d1"
]]></sourcecode></figure>

<t>A response from a modeled service inside the synthetic twin:</t>

<figure><sourcecode type="http-message"><![CDATA[
HTTP/1.1 200 OK
Content-Type: application/json
Synthetic-Twin: model; id="7f3a9c2104b8e6d1"
]]></sourcecode></figure>

<t>The smallest valid field:</t>

<figure><sourcecode type="http-message"><![CDATA[
Synthetic-Twin: probe
]]></sourcecode></figure>

<t>A field with a value this document does not define. The receiver treats
the message as synthetic and handles it as "probe":</t>

<figure><sourcecode type="http-message"><![CDATA[
Synthetic-Twin: other
]]></sourcecode></figure>

<t>Two field lines. The combined value is not an Item, so the receiver
ignores the field:</t>

<figure><sourcecode type="http-message"><![CDATA[
Synthetic-Twin: probe
Synthetic-Twin: model
]]></sourcecode></figure>

</section>
<section anchor="security"><name>Security Considerations</name>

<t>The field is set by the sender and has no integrity protection of its
own. Anyone can add it, remove it, or change it. This includes
script in a web page, which can set the field on requests it makes
(on cross-origin requests, after a preflight). Receivers need to think
about four cases.</t>

<dl>
  <dt>Spoofing to hide:</dt>
  <dd>
    <t>An attacker can add the field to real attack traffic so that it is
dropped from alerts or analytics. For this reason a receiver <bcp14>MUST NOT</bcp14>
relax security checks or monitoring because of the field alone. A
receiver that wants to act on the field <bcp14>SHOULD</bcp14> first check that the
message came from a known source of synthetic messages, for example
by client certificate, network source, or an HTTP Message Signature
<xref target="RFC9421"/> that covers the field.</t>
  </dd>
  <dt>Spoofing to cause harm:</dt>
  <dd>
    <t>An attacker can add the field to real user traffic so that it is
dropped from billing, or sent to a test path. Receivers <bcp14>SHOULD</bcp14> only
take such actions for authenticated sources of synthetic messages.</t>
  </dd>
  <dt>Removal:</dt>
  <dd>
    <t>An intermediary can remove the field, so synthetic messages look
real. Operators that rely on the field <bcp14>SHOULD</bcp14> protect it, for example
with TLS and with HTTP Message Signatures <xref target="RFC9421"/>.</t>
  </dd>
  <dt>Unwanted load:</dt>
  <dd>
    <t>Synthetic requests sent to a real service use its resources like any
other request. The field does not change this. A real service applies
its normal limits to labeled requests.</t>
  </dd>
</dl>

<t>The id Parameter is an identifier, not a credential. Senders <bcp14>MUST NOT</bcp14>
put secrets, credentials, or tokens in it, and receivers <bcp14>MUST NOT</bcp14> treat
knowledge of an id value as proof of anything.</t>

<t>Cached responses are covered in <xref target="caching"/>.</t>

</section>
<section anchor="privacy-considerations"><name>Privacy Considerations</name>

<t>The field is designed to carry no personal data. Senders <bcp14>MUST NOT</bcp14> put
personal data, user names, host names, or customer names in the id
Parameter. The id <bcp14>SHOULD</bcp14> be a random or otherwise opaque value, not a
descriptive name.</t>

<t>An id that is reused across many messages links those messages
together. This is the intended use inside an administrative domain.
Outside it, the same link could help an observer follow a sender's
activity. For this reason gateways remove the id Parameter from
messages that leave the domain (see <xref target="intermediaries"/>), in line with
the advice on correlation in <xref target="RFC6973"/>.</t>

<t>The presence of the field tells an observer that the sender uses a
synthetic twin. Operators who do not want to reveal this outside their
administrative domain can remove the whole field at the edge.</t>

</section>
<section anchor="iana-considerations"><name>IANA Considerations</name>

<t>IANA is requested to add the following entry to the "Hypertext Transfer
Protocol (HTTP) Field Name Registry" at
<eref target="https://www.iana.org/assignments/http-fields">https://www.iana.org/assignments/http-fields</eref>, following the template
in <xref section="16.3.1" sectionFormat="of" target="RFC9110"/> and the Structured Type column defined
in <xref target="RFC9651"/>:</t>

<dl>
  <dt>Field Name:</dt>
  <dd>
    <t>Synthetic-Twin</t>
  </dd>
  <dt>Status:</dt>
  <dd>
    <t>provisional</t>
  </dd>
  <dt>Structured Type:</dt>
  <dd>
    <t>Item</t>
  </dd>
  <dt>Reference:</dt>
  <dd>
    <t>This document</t>
  </dd>
  <dt>Comments:</dt>
  <dd>
    <t>(none)</t>
  </dd>
</dl>

<t>This document does not create a new IANA registry. The values "model"
and "probe" and the id Parameter are defined here only. New values and
Parameters are added by documents that update this one.</t>

</section>


  </middle>

  <back>


<references title='References' anchor="sec-combined-references">

    <references title='Normative References' anchor="sec-normative-references">



<reference anchor="RFC9110">
  <front>
    <title>HTTP Semantics</title>
    <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
    <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
    <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes.</t>
      <t>This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="97"/>
  <seriesInfo name="RFC" value="9110"/>
  <seriesInfo name="DOI" value="10.17487/RFC9110"/>
</reference>
<reference anchor="RFC9111">
  <front>
    <title>HTTP Caching</title>
    <author fullname="R. Fielding" initials="R." role="editor" surname="Fielding"/>
    <author fullname="M. Nottingham" initials="M." role="editor" surname="Nottingham"/>
    <author fullname="J. Reschke" initials="J." role="editor" surname="Reschke"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.</t>
      <t>This document obsoletes RFC 7234.</t>
    </abstract>
  </front>
  <seriesInfo name="STD" value="98"/>
  <seriesInfo name="RFC" value="9111"/>
  <seriesInfo name="DOI" value="10.17487/RFC9111"/>
</reference>
<reference anchor="RFC9651">
  <front>
    <title>Structured Field Values for HTTP</title>
    <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
    <author fullname="P-H. Kamp" surname="P-H. Kamp"/>
    <date month="September" year="2024"/>
    <abstract>
      <t>This document describes a set of data types and associated algorithms that are intended to make it easier and safer to define and handle HTTP header and trailer fields, known as "Structured Fields", "Structured Headers", or "Structured Trailers". It is intended for use by specifications of new HTTP fields.</t>
      <t>This document obsoletes RFC 8941.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9651"/>
  <seriesInfo name="DOI" value="10.17487/RFC9651"/>
</reference>
<reference anchor="RFC2119">
  <front>
    <title>Key words for use in RFCs to Indicate Requirement Levels</title>
    <author fullname="S. Bradner" initials="S." surname="Bradner"/>
    <date month="March" year="1997"/>
    <abstract>
      <t>In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="2119"/>
  <seriesInfo name="DOI" value="10.17487/RFC2119"/>
</reference>
<reference anchor="RFC8174">
  <front>
    <title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title>
    <author fullname="B. Leiba" initials="B." surname="Leiba"/>
    <date month="May" year="2017"/>
    <abstract>
      <t>RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="14"/>
  <seriesInfo name="RFC" value="8174"/>
  <seriesInfo name="DOI" value="10.17487/RFC8174"/>
</reference>



    </references>

    <references title='Informative References' anchor="sec-informative-references">



<reference anchor="RFC6973">
  <front>
    <title>Privacy Considerations for Internet Protocols</title>
    <author fullname="A. Cooper" initials="A." surname="Cooper"/>
    <author fullname="H. Tschofenig" initials="H." surname="Tschofenig"/>
    <author fullname="B. Aboba" initials="B." surname="Aboba"/>
    <author fullname="J. Peterson" initials="J." surname="Peterson"/>
    <author fullname="J. Morris" initials="J." surname="Morris"/>
    <author fullname="M. Hansen" initials="M." surname="Hansen"/>
    <author fullname="R. Smith" initials="R." surname="Smith"/>
    <date month="July" year="2013"/>
    <abstract>
      <t>This document offers guidance for developing privacy considerations for inclusion in protocol specifications. It aims to make designers, implementers, and users of Internet protocols aware of privacy-related design choices. It suggests that whether any individual RFC warrants a specific privacy considerations section will depend on the document's content.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="6973"/>
  <seriesInfo name="DOI" value="10.17487/RFC6973"/>
</reference>
<reference anchor="RFC9205">
  <front>
    <title>Building Protocols with HTTP</title>
    <author fullname="M. Nottingham" initials="M." surname="Nottingham"/>
    <date month="June" year="2022"/>
    <abstract>
      <t>Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet but might be applicable in other situations.</t>
      <t>This document obsoletes RFC 3205.</t>
    </abstract>
  </front>
  <seriesInfo name="BCP" value="56"/>
  <seriesInfo name="RFC" value="9205"/>
  <seriesInfo name="DOI" value="10.17487/RFC9205"/>
</reference>
<reference anchor="RFC9421">
  <front>
    <title>HTTP Message Signatures</title>
    <author fullname="A. Backman" initials="A." role="editor" surname="Backman"/>
    <author fullname="J. Richer" initials="J." role="editor" surname="Richer"/>
    <author fullname="M. Sporny" initials="M." surname="Sporny"/>
    <date month="February" year="2024"/>
    <abstract>
      <t>This document describes a mechanism for creating, encoding, and verifying digital signatures or message authentication codes over components of an HTTP message. This mechanism supports use cases where the full HTTP message may not be known to the signer and where the message may be transformed (e.g., by intermediaries) before reaching the verifier. This document also describes a means for requesting that a signature be applied to a subsequent HTTP message in an ongoing HTTP exchange.</t>
    </abstract>
  </front>
  <seriesInfo name="RFC" value="9421"/>
  <seriesInfo name="DOI" value="10.17487/RFC9421"/>
</reference>

<reference anchor="TRACE-CONTEXT" target="https://www.w3.org/TR/trace-context/">
  <front>
    <title>Trace Context</title>
    <author >
      <organization>W3C</organization>
    </author>
    <date year="2021" month="November" day="23"/>
  </front>
  <seriesInfo name="W3C" value="Recommendation"/>
</reference>
<reference anchor="BAGGAGE" target="https://www.w3.org/TR/baggage/">
  <front>
    <title>Baggage</title>
    <author >
      <organization>W3C</organization>
    </author>
    <date />
  </front>
</reference>
<reference anchor="FETCH" target="https://fetch.spec.whatwg.org/">
  <front>
    <title>Fetch Living Standard</title>
    <author >
      <organization>WHATWG</organization>
    </author>
    <date />
  </front>
</reference>


    </references>

</references>


<?line 437?>

<section numbered="false" anchor="acknowledgments"><name>Acknowledgments</name>

<t>The author thanks the reviewers at RKR Networks.</t>

</section>


  </back>

<!-- ##markdown-source:
H4sIAAAAAAAAA61b25IbN5J9x1dgqYexHCTVbMmyRXs825Zbl7Buo6bW652Y
mACrQLLcxSpOodgUp6P9Lfst+2VzMhNAXUjKCsdaDyaLKCDveTITPRqNVJ3V
uZ3qwWxl9dW+qFe2zpLRbJcV+sVs9k4/y2yeDpSZzyt7g3W9Nf7ntEwKs8Y+
aWUW9ai6rkYuLqyxcLSyJrXV6OxMJaa2y7LaT3VWLErltvN15lxWFvV+gx1e
Xs6eqWxTTXVdbV19fnb25OxcmcoanP6znWtTpPplUduqsLWeVaZwm7KqB+ra
7ndllU6VHul4uKbDe09A4iJL6GFtXd3+ThzzYhyd1NvKpnpBDDrlahz7D5OX
BUjcW6c22VT/rS6ToXY4vbILh0/7NX34u1JmW6/KikhRGv9lhZvqi7H+aazf
m5tsY+qMn4vMLn41e/3Tdm2q7q9ltTRF9i98LYupfv/Te/3G1mDx2vHPdm2y
fKrNr/9J4i78T+OkXCtVlNUa791YkKDfP3v6ZDI5az5OwsfHX+GjIjV0lz9+
8vXDsOb87Kvw8dE5vzl7f/H0cvT07ZvZ5X/PpkxLtKLKJFY/hS7tR6iEfzLV
0tZTvarrjZs+eLDb7ca7h2Mw92D2/kFNL4wSeeEBvxBlp70Qpvrnh0/5awrT
merzs/PJaDIZnT/kh85WmXXERHgHyyEvC0msbZGy/PDLDxfPn188v+wS/INZ
Ls3Sfg6pc1n6mUQuTO4svj+7nD190T3zma2TlX6V3WTFUl+RYZkqPU7BgpaO
3cYm493K1LslE3OSghcXs5+fHxChRqORNnNHsq6Vmq0yp+GwWwin1qldZIV1
uj7h/2z/Y30BMRdwYG3SlBcr/kHXJfxRVlb2n1vyp7LCR/hk4Sz97GDcNWjn
E9bWOchQ74zTawQEPd8PFV6AAQ616bktezpoLcoaO5pcbx0RkMBQs3rPNHXd
HGuxR7modwgXel2mNtflAs+8c2iQB7kMtf2YuZqkj6M3uSkKCxYpAjJTCiQ7
vVtl0NJ1BhqwR3NSYCGriTYiMYEEElNVe43ooMuNgRxUlkK6GfaraGeszG3t
8KOtTF1WTl9buzncFRtuTFXrRQUv3lRlijAE621+hlTycolYYwqT7/EmPs6z
PAczQybG5LYi1sai9nWWpjlM4B6FzLifUn3Z6T8iOxVl9zbyBR0dKhJmUJN4
trVOVqZgPgs2nmpbKLLsUbbgaOz03MIYcA5Us8tg4tt6iIXbZEVnkg2xKQg1
Y2/NTKCIC1uzNUaJse0RT6fM6KpcWwVWsfcakR/minAN9fFhXUbAKL6BS9rP
kftAN5tttSnZ1hVvj91vMtABvZcpG791tqVgvLqCw7NQbJ63NM7kKZ+PYN+k
ErjSNq8Rpb88Zi1kein0gRR01CISbJ6AS4oHhg1EUcBMthU9ZFtx32Jrc8TA
WXCgKFlZtg1hi+yevJekubYGIoC6YD3YN3AF36+/5bO+JObBLzuxpngMee1I
JqUGgdfYNpw2N8k1iwRCZ3Xy8RQjsHNWk6bLMocHLWpbwFDzG6KQdA8jge6z
G9iDz9bybpotFlA0C9a7EunIf4wGpim6ZtDbB3A4uliSVm9MviUFvrEZMcAE
QQZJVToXNnDjU6GUokATO4e9sDoU6ihgZCRY5dYmz4dY/BFwwwHTwBYXME9A
hoO4ieOiooY+RJHp7kpFkcpJVPKRoEC4IW8HbxKUdDsovazJERwSUMQ6DObU
fzHz+vbWI4S7OxBX5nm5Cx5oUrYEUnxhdy1eKT4peRGw4e6OReS1IhEmN3Ob
8+E+sEOaYIAiTbGvVzGMgY8l8AjbDZBBZVSVLVcID95EfDb6wlkLSoNF393d
P9RKaeUkSkS7FYzHhLfXeEIfj3kWLCXaPEVwI+Ee79SAnohS9c5irxYtHNFW
NsZ4LTFFhU0QhO/pN2VtvE6Akm5IHUiUIiYAWLI0SHHw+sPVbDCU/+s3b/nz
+8u/fnj5/vJH+nz14uLVq/hB+RVXL95+ePVj86l58+nb168v3/woL+Op7jxS
g9cXvwxE8IO372Yv3765eDWgXFN3REmhC/Kfw5AIf28qW8NqjFOpdUmVzfEF
7/zw9N3//e/kEdTyHzCE88nkyd2d//LN5OtH+EJakNPKIt/7rxDVXpnNxgIG
U+5HZET0ympAGKyF3a/KXaEpnECSX/6NJPP3qf5unmwmj773D4jhzsMgs85D
ltnhk4OXRYhHHh05Jkqz87wn6S69F790vge5tx5+9xcESatHk2/+8r3q2zU7
L6O2ngNrqqMcXMyuh0hB10HWWEfupejzO1Oh9IAOIVsOkC1vJ0PVM1uts6IE
1tgrddVJglM1Jej1B2GWUq/pBQ517Bd+O59dOOLxe06Mw+fiPqTAPu9byZY3
KfbdbXyEMUJic+K4zZF3eNngNJANYFWfAqsiY5yHdDXft4AG8d4AuQg7AMFS
SDgjVE6VFxSLeo6FO+OYwnkgVHW8eQAWBJroDEGbEmyYMDwjLIG0AiJYBCuD
nc2yslbwBsiCeA1lDUpsf3JHISjbVVZhE7icmMNhdSC2dnuPg/udRLDekibu
F2yOh7nmi9vbKyuSeTh+SBxHM7zPWYIAThMUvGZEHEg1QT2O1jpJ2xKm2e5F
BpJHyFMOwLzyPJ9M5ZC+BwNAYGxGQUEHlcwJQw1FDOomUOtEDwai7RklKzDz
iE9sjh3z0Hqb5Em7MAQjIM1aNboNQcEWTG9u+zQL1o9kBns/BLS9/YZkEVWb
REJ7W38ub9JO7V2c/Sm0FMMRdSNSIjdEQ6ryJHB5nw4IxrWRYsMa0EVZLCl9
j6lTgV+iUQgGmhK0WJHSIDmOTRRlOqiCeeB0gkw3IVcq9eNHVLlQAU3wn85g
xfIqKnlkF2zRWmVG/xrqi9H/DPXZ6AnJbjAKSfYfA8jjGWRpP5r1JoeG1G+/
/cZl/8izorrONNWsym8hgT8Pvl48NE+S88nZo/k39nE6GdDbiGpMvtMhFQq4
WZcVB8SCRX3URTnNkK0Ghxg23MV96gbJEYZC3MpQP1A1wSVly5Ufj78KrjyZ
nAkoA/Z5gT2pLNEfiuuCkrl08qCgLNUBdd7L5MEdBfjEwncDQ9myIE6a1MWQ
AQYlxsasUzPF19uGEKtTuSG4FqyO8SNcsbULaHvJQM3HDHYOMRqpNoWIBkc2
Jw07KxRTiYQH5CKBtm2Yxh0rslpyXpF0qLxSWDpgZQ88KxLBSHsLcEWV0vQT
VYHAZ0Xgdm4lLpDQD0KD5zprCaNJmR4scFbBe9fibrktlqiY8DCauaq2OeWM
eXlju/LoaO3gJKKSHEfecLWvwH2/KVInBocsQGSBHeQ3x5gz5BQmkVZygon0
C+5Rn6THl2eGap1guo/G550spCiuZSCQqx0+HUrIcuQw57XDtubKwAmq9VBm
BE/mcPN5XkjxriH44hf6UlJZjeAH5Ka9dxzfgHIRQDnF8aGeb+vGgaM9qk/b
I3OJSkzgQcgEBFZ+R4zCMkKrJGt3NEYwlLiya6SsLCFfd+HzHQeI1xKSBUsI
I8ByDC0/wTUFctTKg1YpxvjTKV8+Z+5U5guPve2RnxWMEsYDygHB5RUd0RTj
/hDsxRMKSzZEwYY+kPi2WERcgYbUV8BmHnlpRMaE0/7kn6T4iCmk79WOuE75
YpkolBqshSpDy4ilGLIAiZc/3R22+4RQbFTmnKERH7iNA7vxJQ4FyeZ8nGih
+71qtulA5YzRQwo1cEuljnl3wOhlIOYhHsJvqANIdAiIKET0t5O4GK0Ncunt
0gtyF/1tj/I3PEE2dR5xjGsBTZalGAAbRCzDOtHNHxICnMNjvzM7WJ6rbn9S
YEuEIbR8k1kxGMI4NGXynczGEREV1bIqtxtuXTJlArm4h8WrpW9DAY7nEKi9
ORI48QrRrZHUwusLFAoQKTnfIqeGS9RwI3ESXZA2d8RGZZUtG3ROfc8y996X
VlTbGCQRkGErPoBfJbpYGMQwd3ji+2zF7yrgtSX3SmDJm+abWHO7zluba4rP
24pjVtsuOQwhfJKyypBhjTqEvj2jOBZnhkj80rymvF+CPcLI8aBg4PtOCzmj
WuVYnTfWP4uTK9LEsAGzKad5z4thq4AE5nZlcmmTHQHueVleA+lk1/ZUqRkF
FjPCgX9H+YtQQ483MVvyLZSWR+Qmqoo4rZsmkLyC/YdDuI19avJBEY/7gMcH
G51WNvWsa7P0sxAeIvqu54LsSpImV7Ltdmnw8Syl9093/igykiA2RsCO/0oH
a+q129DdRnqjcUchnfSQ9kPMC+G86aEfBKf2g9BwZ/m5I/t4IwXPnGidWmcu
BTZJJM/0UzRpuasAHl9zzXadbdp5CuYy9DNrP28egrcagC9bw4SHMOcNz25s
cu04d8QZwrosMoiEM9iVtardjA3m4WMn6+eph6O39xL5dPe7coghiPT3KSig
yOaCYXMQPea57JQhoPODpCwWWbX2FWatnNkJ3OVmtdAXCt52776VP8qqPXSg
KRY7TiflyWudtLMGftAe2lY2epom2fhc0XJpFSOsOHTIQZx6m0Lck8pGIAMM
9ru1QXjJ6sYNBkU5YnMeNC+JPUHwKFdbFd1X43P8a1V11KD5lkaAX8JGwEPv
XohvHluUddW+1dFgLXV2nmDb4+Ui3/FY2zQzLGyqDNsPYDfIER8zb1dIDnZH
c1vvJZDdjudR0fqjEcRWTaGOx2bSuN+vLeBmWOVD1cno7omAvtblzWHxQwaJ
osl1xwVUJSSUVBjgcZTMuJ+ipA6IW+1WZd4USj1So980jJetWkSaSqA/pKfj
ImBiCu4qudIDzjwDBGSSCNGGQz2nflDWotKfXbUrGI5bFUGCtENIEIhqwWui
YE4jlg6elrpF2geu3FYCkQ4aeu74ZIijUS6gAjzxMFc6ka49qYqlfmU3OV1o
4QSj/S2VMOoSf3PyIypD0Ijo17kcgxDYgvXNPYE5MP+0/SJPQ12nQJM0REt8
+74b8PiOQixJhMB2H8AXHv7Simfs9tZfggEQbKiheo9mT3SKgFRvhhSKCprJ
5CFJMAzdlSEmIY6C/HwvLWYytJJK2B6p3L5QlHoqu4SlWer/0tUnPwKyfvYZ
OnLM1UZ8e8jpjuoUye9KMq00HYiFtaHLNKFiIsOIU8qGbi+M1oRX5NGOQ2fj
ST8OMZHiSWHcoeJYutfz7I8Z2bRa0b/bpFF+xun7FaHz2i4z7ulL6Q0yrOK6
R9YdlDnHmofPL2f6wQqLEOsJET+YjCfqRenqKcll7NuO48LWf6DPOAu3MELG
9gnURSfvZFCxXwpoLjRJmEvlwygnO3eMi0C5Pj87029/UnyxrKhHM74p2FLw
g18RphRhCzuiRVWZT3VIb3+Aw1bGP96FP31H5P+Bjz69fPbvaoTvEZClCUBi
C//svnJg2zdzItLa2t4MONq59O8lGUTgKdWl6jU+GwGRIUgZ5gTDhor+cwjl
npTnFzGoaZo5oSIp13N8S5uWP/cCQ58wtuh8u1ZaWK1E+fnCOqogoYz6Lx4a
Q8tkIxVrVvoxPhn1rkXQsG++798l8CmYUM+S98PZtY9WAj4Ujedo7kkxlCdl
aco9HJ+GM7nlIrCHM3fTUg+FODWfrpWZky8ukFCxj8Sfq01ZLjJpSqzAhp+Q
mro2ybV0Hw6LSI4KsiQ0pWLnQto1Wqeo5TcBAMgVJC6yQt031s8YTWcuwA9z
WNlgHyQe87EpRKQ4oZ2akiTC8E7fjcsgyI33CIYrNW+YECQcjptXAqjMKufL
oJh7eQgXEvw6xouTECUWmkPG9z4Sy9Q4AcaCjyV0hW/BgGcYh+qylTTu/KD6
dSgMYcqGxqrYRQb5j84n1OvhYqW88bOSCBnbqhX5rEy1/nwFc5fps9QbK3gu
GUPyisV12yC9iGmQRiM3c209wkrEfRb91qqXiDsuXb4gAC8wueerVT3smbc+
VuUIcaQfQN0VNhWTty86erSd749aivdVdsGumjm2zl5dNe3N47p0bVWCmw8F
mSfYzkvDI9KrfjfGncAH3AXwRa8XGfeKgPtooOuBe+jdHaJgHz/II2U80dqa
cxffN6AD+Np57rsGfMmP8j9oDhR6INafOdFgI15NG/oRTgKYSM9I7P3JpqJ2
BFy/stSdaFZKc6Km4Q/3/kj8JOeqO0qMIxFFbgoCZQbAZPjswaOU3tU0UM8Q
I22AGt+JYheTy0+3t6GtIfdo3tHFxKSfC3rxP7UOWpd4LJAccR+G5vieGLWd
DiWgIQHVWTMUv2TMOtRA8HX4TDlgCyi0Dj+H6jxLVdSDqD6LFjxnhAvhUZlW
iZnsqN3l7xKymLyu/AWwDVeQdALVpSzMcBHHNzfkCiXwM0qOxsF87VO2rsmq
ulwyhm6GbEww4SbqPrNJhzL+RItVvY1l7rBpCfG906TcQvQrm2/4muTcd1Ok
XR4vCP4J1XG8JtxPSrHhcKLIlzvc3TZ/bo1f6ctsX6X2Oht394d80Zum8hQh
GE/5S5c4GeV0FapYNjn/FxvxvmV7dNaK3jbPXYfd/kSLZxntNq+/8xxj3m5V
hnn7Lt47uaF4wJIJbYWabw8dbyz0Im+rl6E9MeSN7DsvL95cHDgOP2QtcETx
04SQpuI1VYSDKl7rGLwAzq64due/F1oA/b1DgC6TMtdfUPi9768zvSELec9V
arUfgCL1XfuPQTKAFP4LDOPIY/lGwQPGi9IT+L5/UxbAc0M3EBTrKdaaj8cP
UQy0a814e7R1RYqqAyg7364Lj7ZTFfQt02kg1obuTk5gYIpMXyOXOPqFRoeZ
45un9LhzCP1OGJlSJmRDpiNXhlrAH6GP/5ym5t2+KACh7p+8aptQbLV8I3An
aqy8TMfNnRwXGtxcDIfJXpBD97IAgqyXAN8AZZRA17N3YStqDbRuhtALMqaa
79uXP3hit6E/jvEWW1j/hxJ0q4KM7iIJKYFfUbfTYrueU3j/84D/nGbg0bu0
y3mkfx3q2pvM7vj4uvPnWmP1b/FbYMtqNwAA

-->

</rfc>

