Hi Vipul,
here are a few comments about the proposal for managed mode:
A. One is related to the problem with automatic transition to managed
mode now that it becomes optional, that I already mentioned in the
issue049 thread.
B. Other than that, most of my comments are on form:
B.1 I thought the example in the introduction was already a bit "heavy"
as introduction to the spec, doubling its size for the managed mode with
essentially the same information makes things worse. I would suggest to
drop the managed mode part of the example.
B.2 I think Section 3 (Model) is not very clear and need some additional
work: at the moment, it starts directly with operation modes. I think
roles (TS, Client, DP) should be better introduced, messages and their
semantics too, and finally operation modes.
The section outline could be something like:
3.1 Roles
Target Service
Client
Discovery Proxy
3.2 Messages and their semantics
3.3 Operation modes and message exchanges patterns
Ad hoc mode
Managed mode
Automatic transition
B.3 More generally, I think the new emphasis on managed mode changes the
scope of the document, as now ad hoc and managed mode are on the same
footing, while the DP mechanism was really an optional mechanism in the
previous version. We are actually doing two specs in a single document.
In order to make things clearer, we could reorganise the document as
follows:
1. Introduction
2. Terminology and Notation
3. Model
4. Discovery messages
4.1 Hello and Bye
4.2 Probe and Probe Match
4.3 Resolve and Resolve Match
5. Ad hoc mode
5.x Protocol bindings
6. Managed mode
6.x Protocol bindings
7. Application sequencing (could be moved to ad hoc mode)
8. Security (could be split between ad hoc and managed mode, as
different rules apply)
I am aware that the two last points cannot be addressed for CD1, but it
could maybe be a subject for discussion in future audios.
Cheers
Antoine
Vipul Modi a écrit :
>
> Hello all,
>
> Please find attached documents that incorporate the proposal for the
> following “managed cluster” issues.
>
> 022 request-response MEP for communicating with proxy
>
> 034 Discovery proxy and multicast suppression requirement
>
> 035 define protocol assignment/binding for managed mode
>
> 036 discovery messages and managed mode
>
> 049 forced managed mode transition for the client
>
> Following documents are attached with this email:
>
> *1.* *wsdd-discovery-1.1-spec-wd-02-managed-02.docx*: Includes the
> proposed changes with change bars. Note that some of the links may be
> broken or you might see some weird formatting of the text within the
> change bars. These gets fixed when the changes are accepted (see
> document 2).
>
> *2. wsdd-discovery-1.1-spec-wd-02-managed-02-nochangebars.docx*:
> Includes the proposed changes without any change bars.
>
> *3. wsdd-discovery-1.1-wsdl-wd-02-managed.wsdl*: Modified WSDL file
>
> Thanks,
>
> Vipul
>
> ------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> 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
> ------------------------------------------------------------------------
>
>
> Internal Virus Database is out of date.
> Checked by AVG - http://www.avg.com
> Version: 8.0.173 / Virus Database: 270.7.6/1711 - Release Date: 06/10/2008 17:37
>
>
