public inbox for radiotap@archiver.kernel.org
 help / color / mirror / Atom feed
From: David Young <dyoung-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org
Subject: Re: WiMAX extensions
Date: Sun, 24 Jun 2007 00:28:17 -0500	[thread overview]
Message-ID: <20070624052817.GO19613@che.ojctech.com> (raw)
In-Reply-To: <465B184C.1000306-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org>

On Mon, May 28, 2007 at 01:58:36PM -0400, Charles Clancy wrote:
> Guy Harris wrote:
> >>There would certainly be overlap with 802.11.  However most 
> >>implementations I've seen seem to prefix the fields with IEEE80211_, 
> >>so I'd think these would all need to be replicated for 802.16.  I'm 
> >>not sure the best way to handle it.
> >
> >Replicated, or renamed, with the old names kept around for source 
> >compatibility - or with IEEE80211_ and IEEE80216_ names for the same value?
> 
> Ideally, I'd think renaming fields that apply to any wireless standard 
> would be best, keeping around the old values for compatibility, of 
> course.  Then there could be protocol-specific fields for each standard.

I think that what you mean is, for the fields that WiMax and WiFi
have in common, add a generic alias---e.g., IEEE80211_RADIOTAP_RATE =
RADIOTAP_RATE, but do not assign new presence bits for common fields.

That sounds ok to me.

> I think the following would be globally useful:
> 
> IEEE80211_RADIOTAP_TSFT
> IEEE80211_RADIOTAP_RATE
> IEEE80211_RADIOTAP_DB*
> IEEE80211_RADIOTAP_ANTENNA

All of those fields have specific definitions.  Do they apply equally
well to WiMax?

> IEEE80211_RADIOTAP_FLAGS (though you might need a general flag set and a 
> protocol-specific flag set)

Sure.  The flags have almost run out, though. :-)

Dave

-- 
David Young             OJC Technologies
dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org      Urbana, IL * (217) 278-3933 ext 24

  parent reply	other threads:[~2007-06-24  5:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-09  6:23 WiMAX extensions Charles Clancy
     [not found] ` <50721.65.74.1.247.1178691838.squirrel-2RFepEojUI1Vf4MZnIYnAze48wsgrGvP@public.gmane.org>
2007-05-13  3:32   ` David Young
     [not found]     ` <20070513033218.GL20770-eZ+MEZF6i8Dc+919tysfdA@public.gmane.org>
2007-05-28 17:34       ` Charles Clancy
     [not found]         ` <465B128D.9070904-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org>
2007-05-28 17:41           ` Guy Harris
     [not found]             ` <465B144F.2070403-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2007-05-28 17:58               ` Charles Clancy
     [not found]                 ` <465B184C.1000306-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org>
2007-05-28 18:01                   ` Johannes Berg
2007-05-28 18:15                   ` David Young
2007-06-24  5:28                   ` David Young [this message]
2007-05-28 18:00               ` Johannes Berg
2007-06-27 23:45           ` Guy Harris
     [not found]             ` <2A4D4978-D308-40EA-89D5-A2304A5947C7-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org>
2007-06-28  1:10               ` David Young

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=20070624052817.GO19613@che.ojctech.com \
    --to=dyoung-e+axbwqsrlaavxtiumwx3w@public.gmane.org \
    --cc=radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.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