1 / 7

CoAP Size Option Extension

CoAP Size Option Extension. draft-li-core-coap-size-option-01. Client. Server. Post/Put: Blocks. Current Issue 1: Post/Put. Data is too big to be accepted. 4.13 Request Entity Too Large. Using Post/Put for a large object. Transmission failed.

brice
Download Presentation

CoAP Size Option Extension

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CoAP Size Option Extension draft-li-core-coap-size-option-01

  2. Client Server Post/Put: Blocks Current Issue 1: Post/Put . . . Data is too big to be accepted 4.13 Request Entity Too Large Using Post/Put for a large object Transmission failed Issue: In this case the whole transmission has failed, and the previous received data will be useless. This is a waste of transmission resources.

  3. Current feature: • Use link-format to retrieve the maximum estimated size • Issues • It is not accurate, and the resource size may be changed • It is not possible for the requester to know exactly how many blocks will be transmitted, therefore, concurrent Get can't be supported. Current Issue 2: Get

  4. Definition +-------+------+---------+--------------+-----------+---------------+ | Type | C/E | Name | Data type | Length | Default | +-------+------+---------+---------------+----------+---------------+ | 12 | E | Size | uint | 1-4 B | | +-------+------+---------+---------------+----------+---------------+ Size Option • Usage • In Put/Post request and Get response: • --Indicate the resource size • In Get request with Size=0: • --Get the resource size, not the payload

  5. CLIENT SERVER | | | CON [MID=1234], GET, /status ------> | | | | <------ ACK [MID=1234], 2.00 OK, 0/1/128, Size: 5000 | | | | CON [MID=1235], GET, /status, 1/0/128 ------> | | | | <------ ACK [MID=1235], 2.00 OK, 1/1/128 | | | | ... ... | | | | CON [MID=1280], GET, /status, 40/0/128 ------> | | | | <------ ACK [MID=1280], 2.00 OK, 40/0/128 | | | Size Option in a Get response

  6. CLIENT SERVER | | | | | CON [MID=1234], Put, /options, 1/0/128, Size: 5000 ----> | | | | <------ ACK [MID=1234], 4.13 Request Entity Too Large | | | | | | | | | Size Option in a Put request

  7. Open Issues from the discussion in the mailing list • Should the Size option be Elective or Critical? • Need analysis about the influence of the Block1/Block2 design • Need to check implementations about this option • Next steps • Is it OK for the group to accept this as a WG item? Conclusion

More Related