This phenomenon was explored: <a href="http://www.cs.uml.edu/~xinwenfu/paper/CCS09_Fu.pdf">http://www.cs.uml.edu/~xinwenfu/paper/CCS09_Fu.pdf</a>.<br><br>Equal-sized cells at the application layer does not mean equal-sized packets at the IP layer. <br>
<br>Xinwen Fu<br><br><div class="gmail_quote">On Fri, Dec 3, 2010 at 12:18 PM, Nick Mathewson <span dir="ltr"><<a href="mailto:nickm@freehaven.net">nickm@freehaven.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div></div><div class="h5">On Fri, Dec 3, 2010 at 6:25 AM, Weidong Shao <<a href="mailto:weidongshao@gmail.com">weidongshao@gmail.com</a>> wrote:<br>
> Hi<br>
> I did a packet capture and found that the IP datagram size for TLS between<br>
> my browser and the first relay has different sizes, some of which are 638,<br>
> which corresponds to the fixed TOR cell size of 512. But I also see sizes<br>
> of 1500, and other values.<br>
> Does it mean that there are IP packets other than the 512-byte tor cell in<br>
> the same TLS connection?<br>
<br>
</div></div>It's just as likely that the packets aren't always getting sent in<br>
multiples of one cell. The current code puts cells in a buffer as<br>
it's about to send them, and lets the buffers and ratelimiting<br>
backends decide how much to send at a time.<br>
</blockquote></div><br>