Transcript
Page 1: Acknowledgements This research was funded by IWT

AcknowledgementsThis research was funded by IWT.

Further informationSam MichielsK.U.Leuven – Dept. ComputerwetenschappenDistriNet Research GroupCelestijnenlaan 200A3001 Leuven (Heverlee), [email protected]

Supervisors: Pierre Verbaeten Wouter JoosenTel.: +32 16 32 70 68Fax: +32 16 32 79 96www.cs.kuleuven.ac.be

Problem context Research relevance

DiPS+ Strategy

Gold users Silver

usersBronze users

I II III

I II III

I II III

In = 30 r/s

In = 30 r/s

In = 30 r/s

In = 30 r/s

In = 60 r/s

In = 30 r/s

In = 60 r/s

In = 30 r/sIn = 30 r/s

Non DiPS+ RADIUS randomly drops packets

DiPS+ server protects itself against overload

(self-healing)

In = 30 r/sOut = 30 r/s

In = 30 r/sOut = 20 r/s

In = 300 r/sOut = 200 r/s

In = 200 r/sOut = 200 r/s

Authentication requests

Authentication requests

Accounting requests

Accounting requests

UDP/IP protocol stackUDP/IP protocol stack

RADIUS accountingRADIUS authentication

G S B

schedulerstrategy

•Protocol stack problems & characteristics

•Poor separation of concerns

•Poor customizability

•Poor reusability

•Unpredictable load conditions

•Protocol stack development productivity must increase

•Growing demand for application-specific customizations

•Customizable protocol stacks require powerful software design concepts

Distrinet Protocol Stack component framework

Protocol stacksin control

Sam MichielsDept. of Computer Science

Research results

Functional/concurrency/dispatching components

Separate data & management plane

Software architecture(pipe & filter, blackboard, layered)

Self-healing system behavior(e.g. load management)

Headerparser

Concurrencycomponent

DC

Attributeparser

NASchecker

AuthenticatorAccept replypreparatorReject replypreparator

Attributeconstructor

Headerconstructor

Headerparser

Attributeparser

NASchecker

Headerconstructor

Attributeconstructor

Acct replypreparator

AccounterAcctReqAut

hchecker

Concurrencycomponent