[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-dd] Issue 012 - Add size constraint to SOAP-over-UDP messages
Proposed text for the resolution: R00xxx: A SERVICE or CLIENT MAY reject a TEXT SOAP ENVELOPE sent over UDP with more than MAX_UDP_ENVELOPE_SIZE octets. Because SOAP-over-UDP messages covered by the DPWS specification only include WS-Discovery messages, this requirement does not constrain applications that would require the use of larger messages for application-specific services. Proposed value for MAX_UDP_ENVELOPE_SIZE: 4096 octets (to be discussed/adjusted based on feedback) Open question: does anyone understand the requirement numbering rules in DPWS? If so, I would be glad to have an explanation. Antoine Mensch a écrit : > Additional info: > Impact: Implementation change > Urgency: Low > Priority: High > > > Ram Jeyaraman a écrit : >> 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 >>> >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe from this mail list, you must leave the OASIS TC that >> generates this mail. Follow this link to all your TCs in OASIS at: >> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php >> >> ------------------------------------------------------------------------ >> >> >> No virus found in this incoming message. >> Checked by AVG - http://www.avg.com Version: 8.0.169 / Virus >> Database: 270.6.21/1674 - Release Date: 16/09/2008 08:15 >> >> > > --------------------------------------------------------------------- > To unsubscribe from this mail list, you must leave the OASIS TC that > generates this mail. Follow this link to all your TCs in OASIS at: > https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - http://www.avg.com > Version: 8.0.169 / Virus Database: 270.7.4/1695 - Release Date: 27/09/2008 13:11 > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]