In your previous mail you wrote:
Another option for products that want to look at layer 4 information is
to define a new destination option. One can put whatever they want in
those.
=> this idea is not so silly if this destination option is at the new
position, ie. between the routing header and the fragment header.
This will solve the fragment classification issue (to keep some state
works only if fragments are in the suitable order, at least one common OS
sends to last fragment first). Of course an encapsulation device can
repeat it in the outer header (like tunnel encapsulation limit option).
[EMAIL PROTECTED]
PS: I prefer this solution than to hack some bits in the flowlabel.
I'd like to have Thomas Eklund's opinion (ie. is to chase for this
option easy enough?)
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
