Issue 012 - Add size constraint to SOAP-over-UDP messages

[Ram Jeyaraman <Ram.Jeyaraman@microsoft.com>]

This issue is assigned the number 012. For further discussions on this issue, please refer to this issue number or use this thread.

-----Original Message-----
From: Antoine Mensch [mailto:antoine.mensch@odonata.fr]
Sent: Tuesday, September 16, 2008 3:38 PM
To: Ram Jeyaraman
Subject: Re: NEW Issue - Add size constraint to SOAP-over-UDP messages

Forgot to mention location

Document: DPWS
Location (defaults to line number): 199


Antoine Mensch a écrit :
> Please defer discussions on this issue until a time this issue is
> accepted and is assigned a number.
>
> Document:
> Location (defaults to line number):
> Owner: Antoine Mensch
>
> Description:
> DPWS could specify a stronger constraint than 64kbytes for datagram
> size: as a UDP datagram must be read in one chunk (unlike TCP
> streams), supporting SOAP-over-UDP means that a device should be
> prepared to read any datagram (up to 64 kbytes), which is not always
> possible in memory-constrained environments (we typically use buffers
> of a few kbytes). R0029 partially addresses this issue for a different
> reason (reliability), but it is only a SHOULD (with a limit, the MTU,
> which is actually probably too low as an absolute constraint) and only
> for messages sent by services (and not by clients). R0003 also add a
> constraint, but it is too high (32 kbytes) for our purpose and not
> specific to UDP messages.
>
> Proposed resolution:
> Proposed max size of UDP messages that MUST be supported by all
> devices: 4k
>