resend: multiple routing table roadmap (format fix)

[Bruce M. Simpson]

Julian Elischer wrote:
>>
>> OK, but we should think about it in the future. In theory, routing 
>> socket's messages are easily extendable with FIB number in uint16_t, 
>> as message keeps it's length...
>
> I will do that with the advice of people who know that protocol better 
> than I do.

I'm afraid Linux is still ahead of the game here. They adopted a 
tag-length-value protocol called NETLINK which solves many of the 
problems inherent in PF_ROUTE. It even has an RFC.

BMS