A route manager application may send complete route table updates to an RMR based application, or may send updates. Starting with version 1.0.24, RMR supports the ability for the Route Manger route manger to send partial route table updates rather than requiring that the whole table be sent each time. This page describes the update interface.
Request
...
Formats
RMr RMR expects an update to consist of at least three new line separated records which may arrive in one or multiple messages from the Route Table Manager. The start and end records are similar to the newrt start and end records which are used when sending a complete table. The request tag on each is updatert; the exact syntax is shown below:
...
updatert | startupdatert | end | <count>
When RMr RMR encounters a start update request in the stream from the Route Manager it will create a copy of the current table which will be updated with any rte/mse requests which are received before the end request is received. The end request carries one additional piece of information: the number of update requests that were sent between start and end. If RMr RMR did not receive the indicated number when the end request is received, the table is discarded.
Entry
...
Updates
The mse and rte requests which are recognised as a part of a full table are used to change existing, and add new, entries. Entries in the current table which are not changed with new data remain the same.
Deleting Entries
One new request is recognised to delete an existing entry. The delete request, syntax below, is needed only if an entry is to be removed from the table; the Route Manger does not need to specifically delete an entry before updating it.
Replacement Order
All of the entries in a single update are applied to the current table atomically, such that if the entries in the update are related, they will all appear for use to the application at the same time. In other words, there will not be a point where only some of the updates have been applied.