Subject: Re: link state + arrival/departure routing socket messages
To: Jason Thorpe <email@example.com>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 03/05/2000 15:46:18
On Thu, Mar 02, 2000 at 10:26:42AM -0800, Jason Thorpe wrote:
> Hi folks...
> One of the things that routing daemons like is to know when an interface's
> link goes down or comes back up. They might also like to know when new
> interfaces arrive on the system (this is also useful for e.g. DHCP).
> The obvious place to put link state is in the current "info" message,
> but doing so would require we either:
> (1) Break binary compatibility.
> -- or --
> (2) Version the message again.
> I don't think it's worth versioning the message again; the new "info"
> message is marked as "1.5 and later", so I think we should just bust
> the binary compat with -current.
The same issue came with other things. The position was to not assure
binary compat with older -current, just with the releases.
> For the arrival/departure issue, I've created a new message type. See
> the diffs for more info.
> While I haven't added support for actually frobbing the link state in
> the interface info or sending the arrival/departure messages, I think
> we should get these parts in before 1.5 at least, so that the data
> structures are defined and ready to go for when the guts are actually
Manuel Bouyer <email@example.com>