| From | Sent On | Attachments |
|---|---|---|
| Thomas Schaeck | Jan 17, 2003 12:16 pm | .bin |
| Rich Thompson | Jan 20, 2003 5:10 am | |
| Rich Thompson | Jan 20, 2003 5:16 am | |
| Richard Jacob | Jan 20, 2003 5:26 am | |
| Rich Thompson | Jan 20, 2003 5:33 am | |
| Rich Thompson | Jan 20, 2003 5:36 am | |
| Rich Thompson | Jan 20, 2003 5:37 am | |
| Rich Thompson | Jan 20, 2003 5:38 am | |
| Rich Thompson | Jan 20, 2003 5:58 am | |
| Rich Thompson | Jan 20, 2003 6:13 am | |
| Rich Thompson | Jan 20, 2003 9:49 am | |
| Rich Thompson | Jan 20, 2003 11:58 am | |
| Rich Thompson | Jan 20, 2003 12:01 pm | |
| Rich Thompson | Jan 21, 2003 6:32 am | |
| Rich Thompson | Jan 21, 2003 6:34 am | |
| Rich Thompson | Jan 21, 2003 6:57 am | |
| Rich Thompson | Jan 21, 2003 2:31 pm | |
| Rich Thompson | Jan 22, 2003 10:00 am | |
| Rich Thompson | Jan 23, 2003 5:00 am | |
| Rich Thompson | Jan 23, 2003 5:06 am | |
| Rich Thompson | Jan 23, 2003 5:10 am | |
| Rich Thompson | Jan 23, 2003 5:23 am | |
| Rich Thompson | Jan 23, 2003 5:31 am | |
| Rich Thompson | Jan 23, 2003 5:38 am | |
| Rich Thompson | Jan 23, 2003 5:45 am | |
| Rich Thompson | Jan 23, 2003 6:13 am | |
| Rich Thompson | Jan 23, 2003 6:39 am | |
| Rich Thompson | Jan 24, 2003 6:26 am | |
| Rich Thompson | Jan 24, 2003 6:28 am | |
| Rich Thompson | Jan 24, 2003 6:34 am | |
| Rich Thompson | Jan 24, 2003 6:40 am | |
| Rich Thompson | Jan 24, 2003 7:28 am | |
| Rich Thompson | Jan 24, 2003 7:34 am | |
| Rich Thompson | Jan 24, 2003 7:42 am | |
| Rich Thompson | Jan 24, 2003 7:42 am | |
| Rich Thompson | Jan 24, 2003 7:44 am | |
| Rich Thompson | Jan 24, 2003 7:48 am | |
| Rich Thompson | Jan 24, 2003 7:50 am | |
| Rich Thompson | Jan 24, 2003 7:53 am | |
| Rich Thompson | Jan 24, 2003 8:00 am | |
| Rich Thompson | Jan 24, 2003 8:01 am | |
| Rich Thompson | Jan 24, 2003 8:05 am | |
| Rich Thompson | Jan 24, 2003 8:07 am | |
| Rich Thompson | Jan 24, 2003 8:09 am | |
| Rich Thompson | Jan 24, 2003 8:11 am | |
| Rich Thompson | Jan 24, 2003 8:16 am | |
| Rich Thompson | Jan 24, 2003 8:19 am | |
| Rich Thompson | Jan 24, 2003 8:22 am | |
| Rich Thompson | Jan 24, 2003 8:27 am | |
| Rich Thompson | Jan 24, 2003 8:34 am | |
| Rich Thompson | Jan 24, 2003 8:40 am | |
| Rich Thompson | Jan 24, 2003 8:50 am | |
| Rich Thompson | Jan 24, 2003 8:53 am | |
| Rich Thompson | Jan 24, 2003 8:55 am | |
| Rich Thompson | Jan 24, 2003 9:01 am | |
| Rich Thompson | Jan 24, 2003 9:03 am | |
| Rich Thompson | Jan 24, 2003 9:05 am | |
| Rich Thompson | Jan 24, 2003 9:07 am | |
| 252 later messages | ||
| Subject: | [wsrp-wsia] [change request #2] Restricting access based onregistration handle | |
|---|---|---|
| From: | Rich Thompson (ric...@us.ibm.com) | |
| Date: | Jan 20, 2003 5:38:14 am | |
| List: | org.oasis-open.lists.wsrp-wsia | |
Document: WSRP spec Section: 5.2 Page/Line: 29/11-14 Requested by: Rich Thompson Old text: Producers may also find it useful to restrict the information returned to those portions of the service that the registration context will allow the Consumer to access on subsequent invocations. Producers using various security standards (e.g. WS-Security or SSL) to secure the communication should delegate this access control issue to the relevant security context.
Proposed text: (delete these 2 sentences)
Reasoning: When our security people read through the spec, they found these two sentences not useful for several reasons, primarily: 1 - They don't really say anything beyond the sentence at line 7. 2 - By raising the question of delegating such decisions without fully specifying how such delegation would work, the spec does more to confuse than to help. 3 - It really isn't the role of the WSRP spec to define how implementations will also support various security standards.






.bin