Sub-TLVs how to have the same kind of descriptor twice

[David Peterson]

Here is an example of two flows, one for management of the CPE and one for
data:


Alvarion-R3-IF-Name	+=	MGMT_PrivateIP
Alvarion-PDFID	+=	1
WiMAX-Packet-Data-Flow-Id	+=	1
WiMAX-Service-Data-Flow-Id	+=	1
WiMAX-Direction	+=	3
WiMAX-Transport-Type	+=	1
WiMAX-Uplink-QOS-Id	+=	1
WiMAX-Downlink-QOS-Id	+=	1
WiMAX-ClassifierID	+=	1
WiMAX-Classifier-Priority	+=	1
WiMAX-Classifier-Direction	+=	1
WiMAX-IP-TOS-DSCP-Range-and-Mask	+=	0x1818FF
WiMAX-Transport-Type	+=	1
WiMAX-ClassifierID	+=	2
WiMAX-Classifier-Priority	+=	1
WiMAX-Classifier-Direction	+=	2
WiMAX-IP-TOS-DSCP-Range-and-Mask	+=	0x0000FF
WiMAX-QoS-Id	+=	1
WiMAX-Schedule-Type	+=	2
WiMAX-Traffic-Priority	+=	1
WiMAX-Maximum-Sustained-Traffic-Rate	+=	1024000
Alvarion-R3-IF-Name	+=	VPLS
Alvarion-PDFID	+=	21
Alvarion-PDFID	+=	22
WiMAX-Packet-Data-Flow-Id	+=	21
WiMAX-Service-Data-Flow-Id	+=	21
WiMAX-Direction	+=	1
WiMAX-Transport-Type	+=	3
WiMAX-Uplink-QOS-Id	+=	2
WiMAX-Downlink-QOS-Id	+=	2
WiMAX-ClassifierID	+=	3
WiMAX-Classifier-Priority	+=	1
WiMAX-Classifier-Direction	+=	1
WiMAX-VLAN-ID	+=	25
WiMAX-QoS-Id	+=	2
WiMAX-Schedule-Type	+=	2
WiMAX-Traffic-Priority	+=	1
WiMAX-Maximum-Sustained-Traffic-Rate	+=	10240000
WiMAX-Packet-Data-Flow-Id	+=	22
WiMAX-Service-Data-Flow-Id	+=	21
WiMAX-Direction	+=	2
WiMAX-Transport-Type	+=	3
WiMAX-Uplink-QOS-Id	+=	3
WiMAX-Downlink-QOS-Id	+=	3
WiMAX-ClassifierID	+=	4
WiMAX-Classifier-Priority	+=	1
WiMAX-Classifier-Direction	+=	2
WiMAX-VLAN-ID	+=	25
WiMAX-QoS-Id	+=	3
WiMAX-Schedule-Type	+=	2
WiMAX-Traffic-Priority	+=	1
WiMAX-Maximum-Sustained-Traffic-Rate	+=	25000000


-----Original Message-----
From:
freeradius-users-bounces+davidp=wirelessconnections.net at lists.freeradius.org
[mailto:freeradius-users-bounces+davidp=wirelessconnections.net at lists.freera
dius.org] On Behalf Of Sven Tantau
Sent: Thursday, December 20, 2012 2:04 PM
To: freeradius-users at lists.freeradius.org
Subject: Re: Sub-TLVs how to have the same kind of descriptor twice

Hi David,

thanks for your quick reply.

On 12/20/2012 03:35 PM, David Peterson wrote:
> You follow the dictionary in the order set inside of it.  

The dictionary:

ATTRIBUTE       WiMAX-QoS-Descriptor                    29      tlv
ATTRIBUTE       WiMAX-QoS-Id                            29.1    byte
ATTRIBUTE       WiMAX-Global-Service-Class-Name         29.2    string #
6 octets
ATTRIBUTE       WiMAX-Service-Class-Name                29.3    string
ATTRIBUTE       WiMAX-Schedule-Type                     29.4    byte
ATTRIBUTE       WiMAX-Traffic-Priority                  29.5    byte
ATTRIBUTE       WiMAX-Maximum-Sustained-Traffic-Rate    29.6    integer
ATTRIBUTE       WiMAX-Minimum-Reserved-Traffic-Rate     29.7    integer
ATTRIBUTE       WiMAX-Maximum-Traffic-Burst             29.8    integer
ATTRIBUTE       WiMAX-Tolerated-Jitter                  29.9    integer
ATTRIBUTE       WiMAX-Maximum-Latency                   29.10   integer
ATTRIBUTE       WiMAX-Reduced-Resources-Code            29.11   byte
ATTRIBUTE       WiMAX-Media-Flow-Type                   29.12   byte
ATTRIBUTE       WiMAX-Unsolicited-Grant-Interval        29.13   short
ATTRIBUTE       WiMAX-SDU-Size                          29.14   short
ATTRIBUTE       WiMAX-Unsolicited-Polling-Interval      29.15   short
ATTRIBUTE       WiMAX-Media-Flow-Description-SDP        29.16   string

One of my QoS flows:

>         WiMAX-QoS-Id+=2,
>         WiMAX-Schedule-Type+=2,
>         WiMAX-Traffic-Priority+=1,
>         WiMAX-Maximum-Sustained-Traffic-Rate+=128000,

Since I get good results if I use only one QOS profile, I assume that I can
skip attributes and that I'm not required to use them all.
(Please correct me if I'm wrong.)

> Once you hit the
> end of your list of attributes the QoS profile is complete.  

And this is the part that I do not understand:

If I continue by using a second QoS profile:

>         WiMAX-QoS-Id+=3,
>         WiMAX-Schedule-Type+=2,
>         WiMAX-Traffic-Priority+=1,
>         WiMAX-Maximum-Sustained-Traffic-Rate+=128000

I expected freeradius to see that WiMAX-QoS-Id is an element of a new tlv.
And then create a new WiMAX-QoS-Descriptor for it. (Instead of combining the
data for the two QoS profiles into one WiMAX-QoS-Descriptor.)

Is my ASN violating some standard by not accepting one WiMAX-QoS-Descriptor
containing data from two QoS profiles?

If that is the case, is there another workaround beside putting something
between the two QoS profiles? (This is what I did by adding
"Acct-Interim-Interval+=60".)


Thanks,
best regards,
Sven

--
Internet Technologies Angola / Systems Department
Tel:    +244 (227) 286 000 / (924) 770 290 / (924) 770 291
Skype: internet-technologies-angola
Mobile: +244 931 696413
Mail: sven at internet.ao

-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 4158 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20121220/892ec733/attachment.bin>