I suspect that this number might wind up varying (depending on how fast the device and host are, maybe), but fixing that could be a followup bug if it turns out to be the case.