complication in ikev2

[Ravi <ravivsn@roc.co.in>]

May I know why ikev2 should listen on both 500 and 4500.?What purpose does
      it solve? In my view, we are complicating the protocol and implementation by doing
      this. 
      If both IKEv1 and IKEv2 exist (most probably they exist as separate processes
      or tasks and it is easy if we let IKEv1 and V2 exist separately), ikev1 can listen
      on port 500 and ikev2 listen on 4500.

      On the initiating side, if it has both v1 and v2, first it can try contacting the
      responder with port 4500 i.e. IKEv2. If it does not get response in certain
      duration, it can assume that IKEV2 is not supported by the responder and it can
      fallback onto the ikev1 which sends packets onto port 500.

      Also implementation wise it makes it easy and ikev1 and ikev2 can come from
      two different vendors and typically TCP/IP stacks don't allow two sockets 
      listening on same port.

-- 


The views presented in this mail are completely mine. The company is not responsible for whatsoever.
----------
Ravi Kumar CH
Rendezvous On Chip (i) Pvt Ltd
Hyderabad, India
Ph: +91-40-2335 1214 / 1175 / 1184

ROC home page