From: Aaron - Jehun Lee <jehun.lee@newracom.com>
To: Johannes Berg <johannes@sipsolutions.net>,
Richard Sharpe <realrichardsharpe@gmail.com>,
"radiotap@radiotap.org" <radiotap@radiotap.org>,
Ray Wang <rwang@wi-fi.org>, Tasheng Lin <tlin@wi-fi.org>
Subject: RE: A modified, and maybe final, proposal for an S1G header for RadioTap
Date: Mon, 6 Dec 2021 22:12:58 +0000 [thread overview]
Message-ID: <TY2PR0101MB2800849D0A7DE202F0FF3905856D9@TY2PR0101MB2800.apcprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <2f1e81e6f5771793f44940dea500357870035b8d.camel@sipsolutions.net>
Hi Johannes,
Thank you for your email. I have no objection.
Best,
Aaron
-----Original Message-----
From: Johannes Berg <johannes@sipsolutions.net>
Sent: Monday, December 6, 2021 12:10 PM
To: Richard Sharpe <realrichardsharpe@gmail.com>; radiotap@radiotap.org; Ray Wang <rwang@wi-fi.org>; Aaron - Jehun Lee <jehun.lee@newracom.com>; Tasheng Lin <tlin@wi-fi.org>
Subject: Re: A modified, and maybe final, proposal for an S1G header for RadioTap
On Sun, 2019-04-14 at 08:57 -0700, Richard Sharpe wrote:
> Hi folks,
>
> Here is an updated proposal for this header.
>
I think we should just adopt this. Years have literally passed, and I'm pretty sure it's actually used as-is in the wild.
Any objections? If not I'll go add it to the spec soon.
johannes
prev parent reply other threads:[~2021-12-06 23:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 15:57 A modified, and maybe final, proposal for an S1G header for RadioTap Richard Sharpe
2021-02-01 15:00 ` Richard Sharpe
2021-02-02 20:59 ` Johannes Berg
2021-02-04 17:57 ` Richard Sharpe
2021-12-06 20:10 ` Johannes Berg
2021-12-06 22:12 ` Aaron - Jehun Lee [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=TY2PR0101MB2800849D0A7DE202F0FF3905856D9@TY2PR0101MB2800.apcprd01.prod.exchangelabs.com \
--to=jehun.lee@newracom.com \
--cc=johannes@sipsolutions.net \
--cc=radiotap@radiotap.org \
--cc=realrichardsharpe@gmail.com \
--cc=rwang@wi-fi.org \
--cc=tlin@wi-fi.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).