[rbak-nsp] IP Address Assignment Methods

[David Freedman]

Both, depends on the type of subscriber and service
they receive. 

Residential subscribers that don't ask for a static
address end up with a dynamically allocated pool address.

Either way, we aggregate both sets of addresses as much
as possible in the network such to minimise scaling concerns.

Dave.



From:  Caillin Bathern <sp.solutions.architect at gmail.com>
Date:  Friday, 3 August 2012 10:53
To:  "redback-nsp at puck.nether.net" <redback-nsp at puck.nether.net>
Subject:  [rbak-nsp] IP Address Assignment Methods


Hi List,
I am just wondering how other SP's are managing their IP address
assignments.

Are you using IP Pools to randomly assign an IP to a subscriber when they
initiate a session OR are you maintaining the IP address for a subscriber
bu pushing it back with the framed-ip-address attribute?

I know of SPs using both methods however each provides its own issues such
as route table scale, ability or inability to keep track of subscriber IPs
(Lawful intercept issues, flow based billing issues, etc) which are all
highlighted when you have 1+1 redundancy
 of the BRAS'.

Which methods have you chosen?  Why?  How have you overcome the
limitations of each issue?

Cheers.