From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Young Subject: Re: WiMAX extensions Date: Mon, 28 May 2007 13:15:25 -0500 Message-ID: <20070528181525.GP25295@che.ojctech.com> References: <50721.65.74.1.247.1178691838.squirrel@webmail.cs.umd.edu> <20070513033218.GL20770@che.ojctech.com> <465B128D.9070904@cs.umd.edu> <465B144F.2070403@alum.mit.edu> <465B184C.1000306@cs.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <465B184C.1000306-VX+DGZyGJwM3uPMLIKxrzw@public.gmane.org> Sender: radiotap-admin-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org Errors-To: radiotap-admin-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: radiotap-rN9S6JXhQ+WXmMXjJBpWqg@public.gmane.org List-Id: radiotap@radiotap.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 the following would be globally useful: > > IEEE80211_RADIOTAP_TSFT > IEEE80211_RADIOTAP_RATE > IEEE80211_RADIOTAP_DB* > IEEE80211_RADIOTAP_ANTENNA > IEEE80211_RADIOTAP_FLAGS (though you might need a general flag set and a > protocol-specific flag set) > > Is Radiotap meant to be used on outgoing packets as well? If so, there > are a variety of outgoing packet fields that might also be useful. I am going to use radiotap for that. I believe someone has already done it. I have some funding and a plan to add to NetBSD both socket options and packet ancillary data for sending/receiving packets with radiotap. I will be bringing proposals to the list in the next few months. Dave -- David Young OJC Technologies dyoung-eZodSLrBbDpBDgjK7y7TUQ@public.gmane.org Urbana, IL * (217) 278-3933 ext 24