Re: Updating to RFC6434 to deal with 8200-style header insertion by IPIP

[Michael Richardson <[e-mail]>]

Brian E Carpenter <[e-mail]> wrote:
    >    Note that it is impossible for a node to distinguish between an
    > unrecognized extension header and an unrecognized upper layer

Does "unrecognized" mean unknown to the writer of the code at the time of
writing, or does it mean a header which the node has no support for?

Or to put it in C, what goes into TBD?

retry:
  switch(proto) {
  case IPPROTO_UDP:
       udp_rcv();
       break;
  case IPPROTO_TCP:
       tcp_rcv();
       break;
  case IPPROTO_AH:
       if(ipsec_enabled) ipsec_rcv();
       else TBD;
  case IPPROTO_HOPOPT:
       process_hopopt();
       goto retry;
  case IPPROTO_MOBILITY_HEADER:
       skip_hopopt();
       goto retry;
  default:
       return_icmp(1);
  }

-- 
Michael Richardson <[e-mail]>, Sandelman Software Works
 -= IPv6 IoT consulting =-