[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Some comments on draft-winter-radext-fancyaccounting-00
- To: Stefan Winter <stefan.winter@restena.lu>
- Subject: Some comments on draft-winter-radext-fancyaccounting-00
- From: Jacni Qin <jacniq@gmail.com>
- Date: Wed, 27 Apr 2011 14:18:09 +0800
- Cc: radiusext@ops.ietf.org
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=C/Ku8rsJkZsOGYJB4SAx41Qbj36aIUOw8C++h1Rg/OWfoIUF/aVnGSDEcYnn+agxyI 67MG0S4dYxTNj15ofXC6xxkvdPb/CfpMwTQeYnPAOC9MxJr3tMsMP+kptWD+OOurb9Qj Yv+45OpnhJTB2reP8VV5VBzXi1oDGVnAJeiic=
Dear Stefan & all,
I skimed the draft and got some comments, see below please.
* "Section 2.2.1.Acct-Traffic-Class-Id
attribute" seems to be redundant, I perfer to only keep the Name
attribute which is STRING formatted and defined by BNG (configurable).
The traffic classes are specified based on the capability of the BNG. No
further IANA activities are needed in the future.
* For the Input-* & Output-* attributes (Section 2.2.3 ~ 2.2.6),
Shall we "re-use" the type specified in RFC2866, like 245.1.47,
etc.
* An attribute similar to Type#44 Acct-Session-Id is
necessary, since this is widely implemented in practice, for example, as
an identification of user for policy changes initiated by AAA server.
Name it "Acct-Traffic-Class-Id"? But the value should be a random number
assigned by BNG. Some other attributes may also need to be considered.
Or, I can propose some text if you want.
Cheers,
Jacni