Acct-Authentic in Accounting-On and Accounting-Off forms of Accounting-Request. Valid?

[Alan DeKok]

On May 21, 2015, at 12:14 PM, Nick Lowe <nick.lowe at gmail.com> wrote:
> Sorry, less haste more speed... RFC 3580 specifies it's scoped on a
> per-AP/SSID basis:
> 
> "In IEEE 802.11, where the SSID is known, it SHOULD be appended to the
> Access Point MAC address, separated from the MAC address with a ":".
> Example "00-10-A4-23-19-C0:AP1".

  That's *content*.  It's not *scope*.

  It means that the packets contain ASCII text.  It does NOT mean that ASCII text has any *meaning*.

> Ambiguity: Does this mean the wired or wireless MAC address?

  The standards don't say.  It's *a* MAC address.

> Enterprise APs operate these days on a per VAP basis, operating with
> multiple radios. This wasn't the case when RFC 3580 was written.
> So, AP vendors should set this value in Access-Request packets with
> BSSID:SSID, not AP_WIRED_MAC:SSID or CONTROLLER_WIRED_MAC:SSID. Most
> vendors do, I think, already do this.
> 
> Perhaps this needs some cogent, joined up thinking to come up with
> something suited for the future?

  It needs a spec, TBH.

  Alan DeKok.