RE: [Capwap] [Gen-art] IETF LC review:draft-ietf-capwap-protocol-binding-ieee80211-07

2008-08-05 Thread Pat Calhoun (pacalhou)
Great. I had forgotten to mention that I had created tracker #174 for this issue. I will mark this one resolved. PatC -Original Message- From: Joel M. Halpern [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 6:42 PM To: Pat Calhoun (pacalhou) Cc: [EMAIL PROTECTED]; [EMAIL

RE: [Gen-art] IETF LC review: draft-ietf-capwap-protocol-binding-ieee80211-07

2008-08-04 Thread Pat Calhoun (pacalhou)
Thanks for your review, Joel. Please see my comments below. Question: The document (in section 2.5) calls for specific DSCP values (46 and 34) to be used on management frames. Two questions: Is this the decimal value of the 6 bit DSCP field, or the decimal value of the 8 bit ToS field

RE: [Capwap] Last call comments for capwap-protocol-binding-ieee80211-07

2008-07-30 Thread Pat Calhoun (pacalhou)
Hi Pasi, Finally over your comments on the base protocol, and just getting around to the binding spec. I will only create issues where needed, and therefore indicated below. Otherwise I will simply address them in this e-mail. > I was under the impression that 802 (or at least 802.11) required

RE: [Capwap] Last call comments for capwap-protocol-binding-ieee80211-07

2008-07-30 Thread Pat Calhoun (pacalhou)
Hi Pasi, Finally over your comments on the base protocol, and just getting around to the binding spec. I will only create issues where needed, and therefore indicated below. Otherwise I will simply address them in this e-mail. > I was under the impression that 802 (or at least 802.11) required

RE: [Capwap] Last call comments for capwap-protocol-specification-11

2008-07-28 Thread Pat Calhoun (pacalhou)
Thanks for the review, Pasi. We use tracker to keep track of all of our issues. My plan is to create a unique tracker entry for all of the substantial issues you raised here, and a single one for the minor claritifications/nits you include below. Please see below for information on the issues I cr