Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Moby Dick Consolidated System Integration Plan
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
D0103v1.doc Version 1 6.7.2003<br />
Registration<br />
protocoll<br />
handler<br />
ATTENDANT<br />
AAAC protocol<br />
handler<br />
AAAC<br />
Server<br />
Mapper, Mediator, Event gen.<br />
AAAC client<br />
Attendant<br />
log<br />
Session<br />
Status<br />
Trigger,<br />
remove<br />
S.A.<br />
Configure,<br />
Meter data<br />
Security<br />
Manager<br />
Metering<br />
Figure 43: AAAC Attendant<br />
User-space application residing on the AR<br />
The Attendant communicates with the MN and AAAC. F. The Attendant uses:<br />
- UDP for communication with the MN<br />
- TCP for communication with the AAAC.f<br />
Main function:<br />
- allowing / denying a MN the access to the Net<br />
- metering / accounting<br />
Behaviour:<br />
There are two main external events that trigger some actions from this entity i.e. receiving an MNARq on<br />
the AAAC-signalling-interface and Upon receiving an ARA.f<br />
At receiving a MNARq at its AAAC-signalling interface from MN, the Attendant will execute the<br />
following actions<br />
Upon receiving an MNARq on the AAAC-signalling-interface:<br />
• the Attendant generates an DH key /FORWHOM /<br />
• generates an ARR.f message; generates the following AVPS:<br />
• Session-Id, Origin-Host, Origin-Realm, Destination-Realm (by taking the realm part of the<br />
NAI sent by the MN)<br />
• Att-DH-PV (keying material for setting up an SA btw. the MN and the Att.<br />
• constructs an ARR.f to be relayed/proxied thru one of the AAAC servers (relay/proxy agent)<br />
in its realm<br />
• AAAC.f; keeps some info related to this message (the interface on which the MNARq was<br />
received, the MN CoA, MN-DH-PV) into the list of pending requests (LPR)<br />
Upon receiving an ARA.f from the AAAC.f :<br />
• check the AAAC Result-Code<br />
• sets up the SA with the MN using MN-DH-PV<br />
• constructs an MNARp and sends it to the MN using the info related to this MN (i.e.<br />
interface, CoA and so on.)<br />
• sets up the policy related to IP routing for this MN accordingly.<br />
AAAC Client has an Integrated Logger which generates Availability and User Registration Event Logs,<br />
and sends them to the Local Log Management. The Availability Event Logs are generated periodically.<br />
Each time AAAC Client receives a valid MNARq it logs this event for later auditing. After sending the<br />
response MNARp to MN, this event will also be logged.<br />
D0103v1.doc 56 / 168
Change language