Re: [radext] draft-cheng-behave-cgn-cfg-radius-ext-07 feedback

[Alan DeKok <[e-mail]>]

  After some other discussion with Arran, I think there is another way
to solve this problem.

  As background, this document allows for a NAS to communicate a TCP/UDP
port set information for specific hosts.  It seems duplicate effort to
re-define all of the port / protocol information in a RADIUS document.
These information elements are already defined in IPFIX:

http://www.iana.org/assignments/ipfix/ipfix.xhtml

  Port ranges, protocols, etc. are all there.

  I wrote a document for IPFIX to RADIUS mappings:

http://tools.ietf.org/html/draft-dekok-radius-ipfix-00

  The intent was to allow for flow-specific accounting in RADIUS.  That
goal was talked about a lot 2-3 years ago, but has since been ignored.
I believe that we can re-use it here.

  The only change necessary to my IPFix document is to add the following:

- use of Acct-Multi-Session-Id to have flow-specific accounting streams

- use Acct-Multi-Session-Id and Acct-Status-Type start / stop to
indicate port range allocate / de-allocate.


  The benefits here are numerous, I think.  RADIUS gains flow-specific
accounting, and port range allocation signaling.  However, RADIUS does
*not* need to manage any attributes related to ports, protocols, ranges,
etc.  All of that is already defined in IPFIX.  We could just reference
IPFIX, and be done.

  Alan DeKok.