Bug 64 – whether routing API needs to be split from Ipv4 API

Bug 64 - whether routing API needs to be split from Ipv4 API


Summary:	whether routing API needs to be split from Ipv4 API

Status:	RESOLVED FIXED

Product:	ns-3
Classification:	Unclassified
Component:	routing
Version:	pre-release
Hardware:	All All

Importance:	P2 minor
Assigned To:	Tom Henderson

URL:
Keywords:

Depends on:
Blocks:	384
	Show dependency tree / graph

Reported:	2007-08-06 00:51 EDT by Tom Henderson
Modified:	2009-05-29 17:24 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

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

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 EST

sliding to ns-3.5

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

fixed in changeset e20a31541404