Mailing List Archive: RADIUS / Implementation of additional Vendor Specific Attributes

RADIUS / Implementation of additional Vendor Specific Attributes

Jun 14, 2005, 6:33 AM

Post #1 of 6 (585 views)

Dear RADIUS experts,

Would you be so kind to implement the decoding of some more Vendor Specific Attributes for the convenience of the WLAN RADIUS Roaming community.

The Attributes / Vendors are:

the T-Mobile Vendor ID 3414 for T-Mobile-originated VSAs

Attribute Name # Type Comments
Venue-UTC-Offset 41 Integer UTC offset at venue location
Venue-DST-Flag 42 Integer Daylight Savings Time 0 = No, 1 = Yes
Venue-EOD 43 Integer End of day time (24 hour clock) at venue

The vendor ID (IANA number) 16787 of T-Systems Nova International GmbH

# Attribute Comments
1 Location-ID Unique ID of the Location (Hotspot) where the End User is using the service. E.g. Berlin_TegelAirport_100
2 Location-Name Name of the Location (Hotspot) where the end-customer is using the service. "Tegel_Airport_Gate_A"
3 Logoff-URL URL for the end-customer to perform explicit logoff. E.g. HTTP://www.berlinwisp.de/logout.html
4 Redirection URL After Login at a WISP hotspot, end-customer SHOULD be redirected to the given URL
5 Bandwidth-Min-Up Minimal upstream bandwidth which should be reserved to the end-customer (b/s)
6 Bandwidth-Min-Down Minimal downstream bandwidth which should be reserved to the end-customer (b/s)
7 Bandwidth-Max-Up Maximal upstream bandwidth the end-customer is allowed to use (b/s)
8 Bandwidth-Max-Down Maximal downstream bandwidth the end-customer is allowed to use (b/s)
9 Session-Terminate-Time Absolute time for terminating the end-customers session
10 Session-Terminate-End-Of-Day If flag is set to one, end-customers session MUST be terminated at the end of the billing day
11 Billing-Class-Of-Service Describes the service(s) the end-customer demands to use (authorization). Example: wireless_internet_sunrise
12 Service-Name The service the end-customer is using in this accounting session. Service-Name has to be the same as defined in Billing-Class-of-Service. Example: wireless_internet_sunrise
13 Price-Of-Service (Accepted) Price for an offered service per unit
14 Visiting-Provider-Code The carrier code of the WISP. A unique carrier code is assigned to each WISP/provider by T-Systems.

Hopefully, the provided information's are helpful.
If you have questions, do not hesitate to contact me.

Thanks in advanced & regards,
Manuel Biewald

RADIUS / Implementation of additional Vendor Specific Attributes [ In reply to ]

Manuel.Biewald at t-mobile

Jun 15, 2005, 6:05 AM

Post #2 of 6 (583 views)

Permalink

Hi,

How should I start,

"Vendor ID 3414 belongs to Voice Stream Wireless, Inc.", that's as well true as T-Mobile US because it is now the same company.
All I know about the subtypes is:
{40, RADIUS_INTEGER4, "", NULL, NULL},
{41, RADIUS_INTEGER1, "Venue-UTC-Offset ", NULL, NULL},
{42, RADIUS_INTEGER4, "Venue-DST-Flag ", NULL, NULL},
{43, RADIUS_INTEGER, "Venue-EOD ", NULL, NULL},
Remarks:
40, I found these subtype while tracing.
41, length 3 -> Value one octet, don't know if RADIUS_INTEGER1 is possible.
43, no trace, just description from doc.

T-Systems Nova International GmbH 16787, therefore the most subtypes are from the description I've posted yesterday. Most of your attributes seems correct, but maybe subtype 9 is a RADIUS_TIMESTAMP (I'm just guessing)

{1, RADIUS_STRING, "Location-ID ", NULL, NULL},
{2, RADIUS_STRING, "Location-Name ", NULL, NULL},
{3, RADIUS_STRING, "Logoff-URL ", NULL, NULL},
{4, RADIUS_STRING, "Redirection-URL ", NULL, NULL},
{5, "Bandwidth-Min-Up ", NULL, NULL},
{6, "Bandwidth-Min-Down ", NULL, NULL},
{7, "Bandwidth-Max-Up ", NULL, NULL},
{8, "Bandwidth-Max-Down ", NULL, NULL},
{9, RADIUS_TIMESTAMP, "Session-Terminate-Time ", NULL, NULL},
{10, "Session-Terminate-End-Of-Day ", NULL, NULL},
{11, RADIUS_STRING, "Billing-Class-Of-Service ", NULL, NULL},
{12, RADIUS_STRING, "Service-Name ", NULL, NULL},
{13, "Price-Of-Service ", NULL, NULL},
{14, "Visiting-Provider-Code ", NULL, NULL},

What is the meaning of the last two parameters (NULL, NULL)?
After a closer look through the traces I found three more unknown vendor ID's, 2937, 6490 and 161.
Generally I try to get more information's directly from the vendors.

Thanks for your support,
Regards,
Manuel

Re: RADIUS / Implementation of additional Vendor Specific Attributes [ In reply to ]

mwood at IUPUI

Jun 15, 2005, 7:11 AM

Post #3 of 6 (582 views)

Permalink

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As an Omnipoint customer I can confirm that VoiceStream Wireless (which
bought Omnipoint) was bought by T-Mobile.

(Imagine here the old cartoon showing small fish being eaten by
not-so-small fish being eaten by middling fish being eaten by larger
fish....)

- --
Mark H. Wood, Lead System Programmer mwood@IUPUI.Edu
Open-source executable: $0.00. Source: $0.00 Control: priceless!

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: pgpenvelope 2.10.2 - http://pgpenvelope.sourceforge.net/

iD8DBQFCsDchs/NR4JuTKG8RAgJ1AJ9CP7uDJvysd38uiilK9fN+Uoh2wwCeIQs9
rPehARUCHVMLkVWyY1Kr7ss=
=OPUM
-----END PGP SIGNATURE-----

RADIUS / Implementation of additional Vendor Specific Attributes [ In reply to ]

Manuel.Biewald at t-mobile

Jun 16, 2005, 1:30 AM

Post #4 of 6 (580 views)

Permalink

Hi Anders, Hi all,

It's true that T-Systems uses some (maybe all) attributes of the WiFi-Alliance, but they also added some other attributes.

I mailed to all the responsible persons, to get more detailed information's. Hope that helps!

It should be no problem to send you some traces, but I don't know how, alternatively to witch address.

For my knowledge, where do you have to implement these new attributes? Is it just a config file and I could also modify it by myself, or is it based in the code and just available after compiling?

Cheers,
Manuel

RADIUS / Implementation of additional Vendor Specific Attributes [ In reply to ]

Manuel.Biewald at t-mobile

Jun 17, 2005, 2:00 AM

Post #5 of 6 (581 views)

Permalink

Hello,

As I saw at the traces, id 41 is a string value and not integer.
Id 42 (integer) needs a definition like "Daylight Savings Time 0 = No, 1 = Yes"
The integer value of id 43 displays a 24 hour time.

Below you find a answer of an email request:

I can provide some information for 3414.
id 40 is "Venue Class". It's an integer. It's a billing control parameter that is defined between WISP roaming partners for T-Mobile US. It was dropped from the WBA documents because they didn't understand it. The other three:
{41, RADIUS_INTEGER1, "Venue-UTC-Offset ", NULL, NULL},
{42, RADIUS_INTEGER4, "Venue-DST-Flag ", NULL, NULL},
{43, RADIUS_INTEGER, "Venue-EOD ", NULL, NULL},
Are included in some messaging today, but they are all but dead. There is no pair of roaming partners that I know of who are using these attributes in the manner intended. The first two may be included on end user bills to identify the local time of use. The third was intended to drive inter-operator charging and it is not in use anyway.

Regards,
Manuel

RADIUS / Implementation of additional Vendor Specific Attributes [ In reply to ]

Manuel.Biewald at t-mobile

Jun 22, 2005, 4:37 AM

Post #6 of 6 (585 views)

Permalink

Hi Guys,

Unfortunately I have to correct my one mistake, the subtype 41 of the vendor 3414 isn't a string value.
See these description:
Venue-UTC-Offset is a signed integer value indicating the time offset of the local venue against UTC. For example, a Starbucks in the Eastern Standard Timezone of the USA would populate with -5.

@Anders Broman: Are the Traces helpful for your implementation?

Regards,
Manuel