docs: Adding research papers section to ndnSIM website
model+tracers: Implementing ability to trace satisfied/timed out interests

Implementing satsified/timed out interest tracing in L3AggregateTracer and L3RateTracer (only numbers)
model: Add ns3::ndn::Pit::MaxPitEntryLifetime to configure maximum time for which routers are willing to accept any incoming interest

Actual PIT lifetime should be minimum of MaxPitEntryLifetime and
InterestLifetime specified in the Interest packet.
model: Huge bug with ndn::pit::Entry

Not setting PIT entry lifetime in the constructor resulted in immediate
removal of the PIT entries in some cases.  Reverting back behavior
changed by the previous commit.
build: Update wscript for waf-1.7.x
build: no longer require fake `ns3' directory in NS-3's root folder
python bindings: Rescanned
apps: Fixing bug with ns3::ndn::ConsumerWindow::InFlight trace source

Thanks to Junxiao Shi for catching the bug.

closes #34
apps: Fixing bug with randomization configuration of ndn::ConsumerCbr

Thanks to Junxiao Shi for reporting the bug.

fixes #35
build: allowing compilation with boost 1.46; removing requirement of boost-iostream library, requiring boost-graph library
build: fixing bug with detection of installed boost libraries

Thanks to Menghan Li for reporting the bug
examples: Make sure that examples are linked against all compiled NS-3 modules

Such linking is necessary on some platforms to run examples in visualizer
utils/tracers: Fixing bug that resulted in segmentation faults in L3(Aggregate|Rate)Tracer
examples: Correcting output header in ndn-simple-with-pit-count-stats
apps: Adding MaxSeq parameter to ndn::ConsumerWindow as an alternative to Size parameter

refs #36
plugins/topology: Adding ability for AnnotatedTopologyReader to save topology in .dot format

Also, RocketfuelWeightsReader now supports SetDefaultBandwidth and
SetDefaultQueue parameters, which are necessary if the topology needs to
be converted into AnnotatedTopologyReader format
model: Fixing limit borrowing bug in PerOutFaceLimit and PerFibLimit

When the application sends an Interest, router will borrow limit after
forwarding the Interest. If Data gets dropped in the middle, the
application will retransmit the Interest, and router will borrow another
limit. When Data comes back, limit is only returned once. This may cause
the limit to be wasted.

http://redmine.named-data.net/projects/ndnsim refs #1001
GitHub Issues refs #37