Opened 9 years ago

Closed 9 years ago

#334 closed protocol enhancement (fixed)

MUST for in-order block transfer

Reported by: kovatsch@… Owned by: draft-ietf-core-block@…
Priority: major Milestone: post-WGLC-1
Component: block Version:
Severity: In WG Last Call Keywords:


A benefit of fragmentation at the application layer is that the application can start to process incomplete messages. This is very useful when buffer sizes are limited. 6LoWPAN fragmentation for instance must wait for the final fragment until the re-assembled IP packet is handed up to the next layer (unless the implementation starts with cross-layer optimizations).

To benefit from fragment-/block-wise processing, they need to arrive in order. Currently, this is not assured and could break interoperability.

The -block draft should make it a MUST to always start with block zero and send the following in order.

Change History (1)

comment:1 Changed 9 years ago by cabo@…

  • Resolution set to fixed
  • Status changed from new to closed

Covered in -13: Clarify that a server can send 4.08 for out-of-order request blocks, and admonish clients that don't want that to happen to send blocks in order.

Note: See TracTickets for help on using tickets.