Values
Recall that all attributes must have values, even if the value of the attribute is null. Values represent the information that each particular attribute was designed to convey. They carry the “meat” of the information. Values must conform to the attribute type rules outlined previously. Table 2-1 shows examples of each attribute type and the expected value field payload for each.
|
Attribute type |
Length (in octets) |
Size/Range |
Example payloads |
|
Integer (INT) |
4 |
32-bit unsigned |
6 256 2432 65536 |
|
Enumerated (ENUM) |
4 |
32-bit unsigned |
3 = Callback-Login 4 = Callback-Framed 13 = Framed-Compression 26 = Vendor-Specific |
|
String (STRING) |
1-253 |
Variable |
"Charlotte" "Raleigh" "206.229.254.2" "aslyterdesign.com" |
|
IP Address (IPADDR) |
4 |
32-bit |
0xFFFFFE 0xC0A80102 0x1954FF8E 0x00000A |
|
Date (DATE) |
4 |
32-bit unsigned |
0xC0A80102 0xFFFFFE 0x00000A 0x1954FF8E |
|
Binary (BINARY) |
1 |
1 bit |
1 |
Each of these value properties is enumerated (pun intended) and explained in the RADIUS RFC.