Issue 049 - WS-Discovery - Forced managed mode transition for theclient

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

From: Vipul Modi
Sent: Wednesday, September 17, 2008 11:31 AM
To: Ram Jeyaraman
Subject: NEW Issue - WS-Discovery - Forced managed mode transition for the client

Please defer discussions on this issue until a time this issue is accepted and is assigned a number.

Description:

The current specification (Section 3) requires the Client to switch from ad-hoc to managed mode when it receives a multicast suppression Hello message in response to Probe or Resolve. The section also describes the client states and the transition between the ad-hoc and managed modes. While switching from ad-hoc to managed mode improves the network performance a Client may not trust the proxy that is sending the multicast suppression message. The client may have reasons to believe that the proxy may not be representing all of the available services on the network. The decision to switch to managed mode from an ad-hoc mode is typically scenario driven. There may be many other data points that are not foreseen by this specification, that client must consider before deciding to switch to a managed mode. Thus it is not appropriate to force the client to switch to managed mode always upon receiving a multicast suppression Hello. Furthermore the client state switching diagram is confusing.

Proposed Resolution:

The requirement on the client to switch to managed mode upon receiving a multicast suppression Hello should be relaxed from MUST.

ws-dd message