Alan,It's actually 17 ASCII characters ( 12 hex + 5 dashes ). Alcatel-Lucent will be submitting change request (CR) to change NWG R1 Stage 3 to use RFC 3580 compliant format. Alcatel-Lucent ASN-GW and AAA assumed RFC 3580 compliant Calling-Station-Id and recently noticed binary version proposed by NWG R1 Stage 3. Even if Calling-Station-Id format was not RFC 3580 compliant, I think traditionally it has always been an ASCII value not binary. I believe a position from RADIUS Extensions WG could help support WiMAX Forum CR. So far it appears there is agreement on a RFC 3580 compliant Calling-Station-Id for use with WiMAX. Given Calling-Station-Id is an IETF attribute not a WiMAX Forum VSA, I think IETF has some say in the matter.
Thanks, Mike Michael Bean (Mike) Alcatel-Lucent AAA Product Group 3461 Robin Ln, Ste 1 Cameron Park, CA 95682 Email: bean@alcatel-lucent.com Phone: 530 672 7577 Fax: 530 676 3442 Alan DeKok wrote:
Glen Zorn wrote:Are there reasons why this would not be the case? Not that I know of; in fact, the last time I checked that was what the WiMAX docs specified.NWG R1 v1.2 Stage 3.doc, page 446 says: 5.4.1.6.3 User Identification ... Calling-Station-Id 31 The MAC address in binary format of the MS Ugh. And it really is in binary. It's 6 octets of the Ethernet address, not 15 octets of the ASCII version of the Ethernet address. Also, the GMT-Timezone-offset attribute (3) is a 32-bit "signed" integer, as a time-zone offset from GMT: -12 to +12. Instead of 0-24. Alan DeKok.
-- to unsubscribe send a message to radiusext-request@ops.ietf.org with the word 'unsubscribe' in a single line as the message text body. archive: <http://psg.com/lists/radiusext/>