-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Iljitsch van Beijnum wrote: > On 19 mei 2009, at 20:14, Joe Touch wrote: > >> Does ROHC allow through packets that are not ROHC-tagged? > >> a) send the packet without ROHC > >> b) send a copy of the packet with no payload >> with the ROHC tags > > That doesn't help much, because the only thing you save here is the "hey > set up state for what follows" indicator in ROHC. Being unfamiliar with > ROHC I'll go out on a limb and assume this is only a byte or so. The tag is a byte, but we're refreshing the whole IP (and TCP) header context for the subsequent packets. > Assuming that we can predict if and how well a certain flow will > compress, we could also simply drop a) and send back a too big with the > size that will compress to what fits inside the MTU and just send b) > through the tunnel. I'm trying to avoid having ROHC interfere with the E2E MTU of a non-ROHC path. Your solution tells the endpoint that all packets have to be smaller, even when subsequent packets with the large MTU would have headers that compressed enough to make space for the ROHC header. Joe -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKEv/ME5f5cImnZrsRAlvUAJ4lBzS/4Am3aU7E0KkiVjiF3daUpQCgjsTp VSi9Bi0hfrGvPjvEBSi5oK8= =x7X9 -----END PGP SIGNATURE-----
