[Ns-bugs] [Bug 592] New: pointer to packet likely needed for RouteOutput() call

[code@nsnam.ece.gatech.edu]

http://www.nsnam.org/bugzilla/show_bug.cgi?id=592

           Summary: pointer to packet likely needed for RouteOutput() call
           Product: ns-3
           Version: ns-3-dev
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P5
         Component: routing
        AssignedTo: ns-bugs at isi.edu
        ReportedBy: tomh at tomh.org
   Estimated Hours: 0.0


The new API for base class Ipv4RoutingProtocol::RouteOutput should most likely
be changed to pass also a packet pointer:

-   virtual Ptr<Ipv4Route> RouteOutput (const Ipv4Header &header, uint32_t oif,
Socket::SocketErrno &sockerr) = 0;
+   virtual Ptr<Ipv4Route> RouteOutput (Ptr<Packet> p, const Ipv4Header
&header, uint32_t oif, Socket::SocketErrno &sockerr) = 0;

The anticipated use case is NixVector routing, which is a simulation specific
routing mechanism under development in which a packet tag with a strict source
route is planned to be added to the packet.

Now, whether to make this Ptr<const Packet>?  Ptr<const Packet> is all that is
needed to add a NixVector tag, but note that RouteOutput is a synchronous
operation, and we could make the assumption that it is allowed to change the
packet (e.g. a future user may add some kind of a true source route header
option).


-- 
Configure bugmail: http://www.nsnam.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.