Hi guys
Following the discussions we had with regard to management flows and
when to exchange what management information in RINA, I propose to
perform these changes in IRATI as well. Since these changes could be far
reaching, I am writing this mail to inform you of this, and to spark
discussion if needed.
Proposed changes:
* Decouple enrollment from setting up management flows by providing two
distinct operations to the ipcm. (enroll-to-dif, allocate-n-1-flow)
* Provide a policy hook for the connectivity graph of the management
flows. Default policy could be to connect with all other IPCPs that are
reachable over shared N-1 DIFs.
* Provide different policies for choosing the connectivity graph for
management flows in order to assess their pros/cons.
* Performing the exchange of dynamic information (for instance the FSDB)
on management flows only (so move that part out of enrollment)
If there are no major objections I will start to perform these changes
and have my code land on the pristine-1.3 branch. These changes are
required for routing experiments.
Furthermore, I would like to encourage people to use this mailing list
more often, since I get the feeling a lot of information is lost by
using the chat only. A lot of major decisions are being taken without
discussing them beforehand.
Kind regards
Sander
--
Sander Vrijders
Department of Information Technology
Internet Based Communication Networks and Services (IBCN)
Ghent University - iMinds
Gaston Crommenlaan 8 (Bus 201), B-9050 Gent, Belgium
T: +32 9 33 14977 ; T Secr: +32 9 33 14900
F: +32 9 33 14899
E: sander.vrijders@xxxxxxxxxxxxxx
W : www.ibcn.intec.UGent.be
