Ray, We have different prespectives. The next version of the draft will try to make the case a bit clearer. On one specific point:
>> Thinking out loud, we could potentially define yet another new extension >> header >> that defines a fork in the header chain: next header field = following >> (optional) header extensions, plus length to reach the next header as per >> RFC6564; final header field (contained as header specific data within the >> new >> header) = top level protocol of the final header value e.g. TCP= 6, plus >> offset >> to reach the final payload header in either octets or 8-octet units. Please look at http://tools.ietf.org/id/draft-zhang-6man-offset-option-01.txt, although it got no traction here. Brian -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
