[Softwires] Proposal for extension of Radius Accounting

Bruno STEVANT <bruno.stevant@enst-bretagne.fr> Fri, 03 February 2006 13:43 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F51DI-0001jo-HY; Fri, 03 Feb 2006 08:43:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F51DD-0001j6-NJ for softwires@megatron.ietf.org; Fri, 03 Feb 2006 08:43:00 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28091 for <softwires@ietf.org>; Fri, 3 Feb 2006 08:41:08 -0500 (EST)
Received: from laposte.rennes.enst-bretagne.fr ([192.44.77.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F51Od-00027f-8V for softwires@ietf.org; Fri, 03 Feb 2006 08:54:44 -0500
Received: from l2.rennes.enst-bretagne.fr (l2.rennes.enst-bretagne.fr [192.44.77.4]) by laposte.rennes.enst-bretagne.fr (8.11.6p2/8.11.6/2003.04.01) with ESMTP id k13Dfte10991; Fri, 3 Feb 2006 14:41:55 +0100
Received: from [192.44.77.162] (dhcpe62 [192.44.77.162]) (authenticated bits=0) by l2.rennes.enst-bretagne.fr (8.13.1/8.13.1) with ESMTP id k13DfsW2019646 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO); Fri, 3 Feb 2006 14:41:55 +0100
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <06F2FF70-FC38-4F79-BF79-49173C2503CE@enst-bretagne.fr>
Content-Transfer-Encoding: 7bit
From: Bruno STEVANT <bruno.stevant@enst-bretagne.fr>
Date: Fri, 03 Feb 2006 14:42:05 +0100
To: radiusext@ops.ietf.org
X-Mailer: Apple Mail (2.746.2)
X-Virus-Scanned: by amavisd-milter (http://amavis.org/) at enst-bretagne.fr
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Content-Transfer-Encoding: 7bit
Cc: softwires@ietf.org, Laurent Toutain <Laurent.Toutain@irisa.fr>
Subject: [Softwires] Proposal for extension of Radius Accounting
X-BeenThere: softwires@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: softwires wg discussion list <softwires.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/softwires>
List-Post: <mailto:softwires@ietf.org>
List-Help: <mailto:softwires-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/softwires>, <mailto:softwires-request@ietf.org?subject=subscribe>
Sender: softwires-bounces@ietf.org
Errors-To: softwires-bounces@ietf.org

Good day all

We at Point6 are working in the Softwires WG on a solution for IPv6  
access for Home Networks, as described in draft-toutain-softwire- 
point6box-00.txt
In this solution we use L2TP/PPP for IPv6 tunneling. Access AAA  
parameters are managed with Radius.

We found an issue with current FreeBSD PPP implementation on Radius  
accounting :
Attributes Acct-{Input,Output}-Octets and Acct-{Input,Output}-Packets  
are only based on accounting informations from IPCP. Since our  
solution only use IPV6CP, we have to modify the code in PPP to send  
IPV6CP accounting information in these Radius attributes.

The basic solution may be just to add IPCP and IPV6CP values and to  
transmit these sums as value for these attributes.
Another solution may also to have separate accounting attributes for  
IPv4 and IPv6. We think this may be only relevant for packets (as it  
is done in system MIBs for instance). Our proposal is to have two  
more attributes for Radius accounting : Acct-IPv6-Input-Packets and  
Acct-IPv6-Output-Packets.

The rational of this proposal is to give operators who deploy dual  
stack access solution some accounting information about IPv6/IPv4  
usage ratio.
We ask the Radext WG to take position on this proposal. Some inputs  
may also come from the Softwires WG.

Regards,
-- 
Bruno STEVANT - Point6

_______________________________________________
Softwires mailing list
Softwires@ietf.org
https://www1.ietf.org/mailman/listinfo/softwires