Bug 64

Summary:	whether routing API needs to be split from Ipv4 API
Product:	ns-3	Reporter:	Tom Henderson <tomh>
Component:	routing	Assignee:	Tom Henderson <tomh>
Status:	RESOLVED FIXED
Severity:	minor	CC:	craigdo, ns-bugs
Priority:	P2
Version:	pre-release
Hardware:	All
OS:	All
Bug Depends on:
Bug Blocks:	384

Description Tom Henderson 2007-08-06 00:51:33 UTC

discussion from the list:
>> - whether to continue to write to the existing IPv4 API or load a static
>> >> router component into the node such as Gustavo's OLSR code does
> >
> >I am not sure I understand what the alternatives are here: the routing
> >code should be written to use our public Ipv4 API, without doubt. 

Whether to split off the IPv4 API into a routing API is an issue left for further study.

Comment 1 Tom Henderson 2009-02-16 00:58:57 UTC

sliding to ns-3.5

Comment 2 Tom Henderson 2009-05-29 17:24:46 UTC

fixed in changeset e20a31541404