Re: New Version Notification for draft-maglione-radext-ipv6-acct-extensions-00

[Alan DeKok <aland@deployingradius.com>]

Maglione Roberta wrote:
> I'm not sure we could use the Acct-Multi-Session-Id for this purpose because according to the definition in RFC 2866, Acct-Multi-Session-Id links together multiple sessions with different Acct-Session-Id
> 
> "5.11  This attribute is a unique Accounting ID to make it easy to link
>       together multiple related sessions in a log file.  Each session
>       linked together would have a unique Acct-Session-Id but the same
>       Acct-Multi-Session-Id."
> 
> While in the described scenario there is a single session that carries multiple traffic flows: IPv4 and IPv6.

  Yes, I understood that.  I still proposed the solution because:

(a) it works
(b) it's not actually forbidden by the RFCs
(c) it seems to be a practical use-case for Acct-Multi-Session-Id

> In addition I see an operational issue in terms of efficiency in doubling the number of Accounting streams, because we usually have around 20-30 thousand active subscribers in a single NAS thus  sending the Accounting stream twice may affect the performance of the NAS.

  RADIUS isn't perfect.  You have to make trade-offs somewhere.   The
choice is between more traffic for the NAS (but with well-defined
semantics), or more attributes in the standard space.

  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/>