|
Andreas Savva: 06/30/2008 10:48 PM EDT
|
|
Comment: |
Assigned category due to minor expected tweaks as a result of the experience document
|
|
Action: |
Update
Category set to Version 1.0
|
|
Andreas Savva: 07/27/2005 6:01 PM EST
|
|
Comment: |
Confirmed in draft 33.
|
|
Action: |
Update
|
|
Andreas Savva: 07/27/2005 6:01 PM EST
|
|
Action: |
Update
artifact_status changed from Fixed to Closed
close_date changed from - to 2005-07-28 08:01:45
|
|
David Snelling: 07/25/2005 6:23 PM EST
|
|
Comment: |
Change "permitted" to "recommended" in line 483.
|
|
Action: |
Update
|
|
David Snelling: 07/25/2005 6:23 PM EST
|
|
Action: |
Update
artifact_status changed from Pending to Fixed
|
|
Andreas Savva: 07/15/2005 1:23 AM EST
|
|
Comment: |
July 13 minutes discussion:
- Sec.8.1.2: On mandating the use of mutual authentication
- Latha's comment needs followup. Since Latha is not on the call,
follow up by email and finalize at next Monday's call.
- Agreed that this requirement is very restrictive.
- This was discussed at the Security session at GGF14. The reason
given for mandating it, is that the profile addresses
inter-organization (server to server) interactions and that the
expectation is that those interactions must be secured. If
operating in some special environment it might be possible to do
things differently but then interoperability is not the main
concern.(?)
- The concern with mandating this requirement is that it sets too
high a bar, especially for existing middleware. Very few, if
any, systems do this at the moment. (The mechanism of acquiring
and validating credentials is the problem not their usage
afterwards.) It seems overly restrictive and many people might
not be able to comply to this profile because of this.
- The consensus on the call was therefore to soften this
requirement. Specifically to change the requirement from MUST to
SHOULD (or possibly RECOMMENDS; semantically equivalent to
SHOULD but slightly different nuance).
|
|
Action: |
Update
|
|
Andreas Savva: 07/15/2005 1:23 AM EST
|
|
Action: |
Update
artifact_status changed from Open to Pending
|
|
|