Opened 10 years ago

Closed 9 years ago

#206 closed editorial (fixed)

Clarify that atomic Block1 transfers match per token *and* endpoint

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

Description

Anthony Blaire notes:

at the interop in Paris, we noticed one client implementation using a different UDP source port for each request in a blockwise transfer.

There is no mentions about UDP port numbers in draft-ietf-core-block-08.

While the client port number does not matter most of the time, there are possible problems in case of atomic Block1 transfers.

If two clients running on the same host are updating the same resource, then the server cannot distinguish for a certainty between the blocks of the two clients.

I would suggest adding one paragraph to Section 2.2:
In the blockwise tranfer of a request payload (e.g., a PUT or POST) that the server is processing atomically, the client MUST originate every request from the same UDP source port. The reassembler MUST compare the UDP source port of the request when reassembling the blocks of an atomic operation. If atomic processing is not desired, there is no need to process the UDP source port.

Since the UDP port is not the only parameter that could vary (DTLS connection or IPv6 source address come to mind), the two paragraphs at the end of section 2.2 (page 12) probably should be rephrased to clarify that the combination of endpoint and token is what is used to perform the matching, with a reference to the matching rules in 5.3 in core-coap.

Change History (3)

comment:1 Changed 10 years ago by hartke@…

  • Version set to block-08

comment:2 Changed 10 years ago by cabo@…

Some editorial work remains even after the main issue is covered by #210 and block-10: The last paragraph of 2.4 is the only one in block-10 to mention the importance of the endpoint. So some additional text is still needed to indicate that servers that run buffered transfers (e.g., for atomic semantics) will allocate them per endpoint.

comment:3 Changed 9 years ago by cabo@…

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

Fixed in [1265]:

Fix #203
Fix #206
Fix #209
Fix #210
Fix #245

Note: See TracTickets for help on using tickets.