IETF 77 RADEXT WG

RADIUS Accounting extensions for IPv6

draft-maglione-radext-ipv6-acct-extensions-01

R. Maglione – Telecom ItaliaB. Varga - Magyar Telekom

S. Krishnan, A. Kavanagh – EricssonJ. Kaippallimalil – Huawei

IETF 77 RADEXT WG

Background

RFC 2866 and RFC 2869 specify RADIUS attributes to carry statistics about packets/octets/Gigawords sent/received over a port

This document introduces new RADIUS attributes to carry IPv6 volume counters in RADIUS Accounting messages

IETF 77 RADEXT WG

Deployment Scenario

Residential Gateway

Access Node

AAA Radius Server

Single PPP Session for both IPv4 and IPv6

BRAS

Broadband environments: dual-stack IPv4/IPv6 scenario

IETF 77 RADEXT WG

Why new attributes?

There is a suggestion on list to re-use existing attributes by duplicating the accounting stream for each single session:

one stream for IPv4 another for IPv6 traffic Acct-Multi-Session-Id used to link the two streams

together This approach seems operational too heavy for

both the BRAS and the RADIUS system Defining new attributes appears a simpler

solution

IETF 77 RADEXT WG

RADIUS Accounting Attributes

Current Attribute New IPv6 Attribute

Acct-Input-Octets IPv6-Acct-Input-Octets(Acct-IPv6-Input-Octets)

Acct-Output-Octets IPv6-Acct-Output-Octets(Acct-IPv6-Output-Octets)

Acct-Input-Packets IPv6-Acct-Input-Packets (Acct-IPv6-Input-Packets)

Acct-Output-Packets IPv6-Acct-Output-Packets (Acct-IPv6-Output-Packets)

Acct-Input-Gigawords IPv6-Acct-Input-Gigawords(Acct-IPv6-Input-Gigawords)

Acct-Output-Gigawords IPv6-Acct-Output-Gigawords (Acct-IPv6-Output-Gigawords)

Suggestion from the list

Initial proposal

IETF 77 RADEXT WG

Questions?

IETF 77 RADEXT WG

Next Step

Adopt as a WG item?