[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-rx] Proposals for MakeConnection issues summary
Marc Goodner <mgoodner@microsoft.com>
11/14/2006 09:57 PM |
|
Issue | Close No Action | Proposal 2 | Notes |
1 | Solved | Solved | |
15 | Open | Open | Both sides seem to agree that an assertion for MakeConnection is an idea worth exploring. No proposals on the table yet. |
27 | Open | Open | Both sides seem to doubt there is an issue here. This might be close with no action either way. If it isn’t there may only be clarifying text required. |
28 | Open | Closed | No proposal if 1 is closed with no action |
29 | Open | Closed | No proposal if 1 is closed with no action |
30 | Open | Closed | No proposal if 1 is closed with no action |
31 | Open | Closed | No proposal if 1 is closed with no action |
WSA WG dependency* | Open | Closed | CR33 is still not closed. There is still
a potential impact on the RM anon URI. Earlier actions taken in relation
to CR33 certainly do not support the notion of other specs defining their
own anonymous URIs any longer.
Proposal 2 does not have any WSA WG dependencies as it does not define its own special URI requiring support from that WG’s outputs. |
Potential security composition issue** | Open | Closed | There has been an open question in the
implementation subcommittee for a month on how to relate the proper token
to a sequence created through the use of MakeConnection. There may not
be an issue with the current spec, but there is the open question.
Proposal 2 has advice that a new security token should be issued for any new sequence created through MakeConnection so there isn’t an open question there. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]