Almost. I added an objection comment as the current spec is not at all
close to what we agreed to earlier in the year. So, I would hold off
implementing anything.

On Fri, 2 Jun 2023, ccaffy wrote:

> XRootD supports packet marking with UDP firefly: https://xrootd.slac.stanford.edu/doc/dev56/xrd_config.htm#_Toc135684345
>
> This functionality works with XrootD. The user can pass the information about the experiment and its activity by specifying in the opaque data of a transfer the following key/value: `scitag.flow=<experimentID><<6|<activityID>` .
>
> For HTTP TPC transfer, the user will pass these information via specific headers as described here: https://docs.google.com/document/d/1x9JsZ7iTj44Ta06IHdkwpv5Q2u4U2QGLWnUeN2Zf5ts/edit#heading=h.ksbp08p3u6lb
>
> - `TransferFlowExperiment`
> - `TransferHeaderFlowExperiment`
> - `TransferFlowActivity`
> - `TransferHeaderFlowActivity`
>
> I believe I just need to pass the information coming from the headers to the xroot layer by appending `scitag.flow=expe|activity` ?
>
> --
> Reply to this email directly or view it on GitHub:
> https://github.com/xrootd/xrootd/issues/2024
> You are receiving this because you are subscribed to this thread.
>
> Message ID: ***@***.***>

—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.

[ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/xrootd/xrootd/issues/2024#issuecomment-1574153935", "url": "https://github.com/xrootd/xrootd/issues/2024#issuecomment-1574153935", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

Use REPLY-ALL to reply to list

To unsubscribe from the XROOTD-DEV list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1