[Bro-Dev] #803: topic/jsiwek/routing0

[Bro Tracker]

#803: topic/jsiwek/routing0
----------------------------+------------------------
  Reporter:  jsiwek         |      Owner:
      Type:  Merge Request  |     Status:  new
  Priority:  Normal         |  Milestone:  Bro2.1
 Component:  Bro            |    Version:  git/master
Resolution:                 |   Keywords:
----------------------------+------------------------

Comment (by seth):

 > It seemed important to be able to use the final destination of packets
 > with an RH0 as the endpoint of connections in case there's still nodes
 out
 > there that do RH0 processing according to RFC 2460, but I'm also feeling
 > like it's a bit wasteful or makes the code more complex than necessary
 > since RH0 is deprecated by RFC 5095 anyway and going to be uncommon.
 Any
 > opinions?

 Yeah, I don't think we need the code to deal with that due to the
 deprecation.

 > Would it make sense to just raise a weird (already do that in my
 changes)
 > and stop analyzing a packet that contains an RH0 with non-zero segments
 > left on the grounds that it's supposed to be deprecated and the analysis
 > isn't going to be correct unless we make extra effort to understand the
 > final destination?

 I think that's exactly the right thing to do.  In the script land we can
 watch for correct implementation by routers of RFC 5095 by watching for
 the ICMPv6 parameters problem message as specified in 5095.

-- 
Ticket URL: <http://tracker.bro-ids.org/bro/ticket/803#comment:0>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker