=?utf-8?B?SXNzdWUgMDk1IC0gRFBXUyAtIENsYXJpZmljYXRpb24gb24gRmF1bHQgSGE=?==?utf-8?B?bmRsaW5nIG9mIFN1YnNjcmlwdGlvbiBFeHBpcmF0aW9uVHlwZSDigJxkdXJh?==?utf-8?B?dGlvbuKAnQ==?=

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

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

From: Scott de Deugd [mailto:dedeugd@us.ibm.com]
Sent: Sunday, November 30, 2008 11:49 AM
To: Ram Jeyaraman
Cc: Doug Davis; Mike Kaiser; Travis M Grigsby
Subject: New WS-DD Issue: Clarification on Fault Handling of Subscription ExpirationType “duration”

 

Clarification on Fault Handling of Subscription ExpirationType “duration”
Description:
Document: DPWS 1.1-spec-wd-02-1
Line number:  Line 900
Owner: Scott de Deugd

Section 6.2 says:
R3016: A HOSTED SERVICE MUST NOT generate a wse:UnsupportedExpirationType SOAP Fault in response to a Subscribe or Renew SOAP ENVELOPE with an Expiration type of xs:duration.

Is this trying to specify that the type "duration" must be supported or, that the event sink must support any length duration?  


Proposed Resolution (changes in red):