9095 2010-02-20 00:09:37 +0000 WS-Enumeration - Calling Pull or Release operations after EndOfSequence has been issued 2010-07-27 20:28:27 +0000 1 1 1 Unclassified WS-Resource Access Enumeration LC PC Windows NT CLOSED REMIND P2 normal --- 1 ram.jeyaraman ram.jeyaraman dug public-ws-resource-access-notifications oldest_to_newest 32463 0 ram.jeyaraman 2010-02-20 00:09:37 +0000 WS-Enumeration already states [1] in section 3. The enumeration context will become invalid once EndOfSequence is issued. Given that, I suggest removing [2]. [] http://www.w3.org/2002/ws/ra/edcopies/wsenum.html#EnumMsgs An enumeration context can become invalid for any reason including: Enumeration completed (i.e. an EndOfSequence has been returned in a Pull response) Enumeration released Enumeration expired Enumeration ended (i.e. ended via an EnumerationEnd message from data source Enumeration context replaced in the response to another Pull request In addition, the data source MAY invalidate an enumeration context at any time, as necessary. When processing a Pull, Renew, GetStatus or Release operation, a data source MUST generate an wsen:InvalidEnumerationContext fault if it determines that the enumeration context supplied by the consumer in the request is invalid. [2] http://www.w3.org/2002/ws/ra/edcopies/wsenum.html#Pull The consumer MUST NOT issue additional Pull request messages after a Pull response containing a wsen:EndOfSequence element has been received. Similarly, upon receipt of a Pull response containing a wsen:EndOfSequence element, the consumer MUST NOT issue a Release operation to signal that the enumeration context is no longer needed. 32748 1 dug 2010-03-02 02:48:42 +0000 There really are two different concepts being discussed in the quoted text. In [1] it says what a Data Source MUST do in the case of receiving a msg with an invalid context. The text in [2] is different, its talking about what the Consumer MUST (or MUST NOT) do once it knows the enumeration is invalid. These are two very different thing. I'm ok with remove the text in [2], but only if we add something to the generic section (like after the text in [1]) that says something like: --- Once a Consumer determines that an enumeration context is invalid, it MUST NOT issue any more WS-Enumeration request messages referencing that enumeration context. --- This will prevent any confusion as to what the expectations are for the Consumer. For example, does it need to perform any clean up by sending a Release to the Data Source? 34159 2 bob 2010-03-30 19:52:44 +0000 Resolved with comment #1