| From | Sent On | Attachments |
|---|---|---|
| John Tolbert | May 7, 2012 11:27 am | |
| Danny Thorpe | May 7, 2012 1:29 pm | |
| Tolbert, John W | May 7, 2012 1:44 pm | |
| Danny Thorpe | May 7, 2012 2:24 pm | |
| Hal Lockhart | May 17, 2012 8:19 am | .docx |
| John Tolbert | May 17, 2012 8:54 am |
| Subject: | RE: [xacml] Groups - Proposed response to Plasma uploaded | |
|---|---|---|
| From: | Danny Thorpe (Dann...@quest.com) | |
| Date: | May 7, 2012 2:24:30 pm | |
| List: | org.oasis-open.lists.xacml | |
Much clearer, thanks.
Danny Thorpe
Product Architect | | Quest Software - Now including the people and products of
BiTKOO | www.quest.com<http://www.quest.com>
From: Tolbert, John W [mailto:john...@boeing.com] Sent: Monday, May 07, 2012 1:46 PM To: Danny Thorpe; xac...@lists.oasis-open.org Subject: RE: [xacml] Groups - Proposed response to Plasma uploaded
My comment is intended to support the use of URIs/URNs as policy references in
their proposed architecture.
How about this:
The use of URIs/URNs has been shown to be an effective way of representing
values in a request context, particularly when the values are fairly static.
This would be the preferred structure for passing policy references.
From: Danny Thorpe
[mailto:Dann...@quest.com]<mailto:[mailto:Dann...@quest.com]>
Sent: Monday, May 07, 2012 1:30 PM
To: Tolbert, John W;
xac...@lists.oasis-open.org<mailto:xac...@lists.oasis-open.org>
Subject: RE: [xacml] Groups - Proposed response to Plasma uploaded
In this section:
----
By name. This is where a reference to the policy is directly associated with the
data. e.g. a URI or a URN which identifies the policy to be enforced or points
to where the policy is published. For example with S/MIME the ESS label
identifies the applicable policy by an OID. When an access request is made to
the data, the PDP finds the policy based on the identifier and then compares the
access request to the referenced policy. (p. 38)
The use of URIs/URNs has been shown to be an effective way of representing
values in a request context, particularly when the values are fairly static.
----
It's unclear to me what this comment is about. Is the comment providing support
for the original text, or is the purpose of the comment to suggest that URI/URNs
should be used instead of S/MIME?
Other than that, the rest of the doc looks good and makes sense.
-Danny
Danny Thorpe
Product Architect | | Quest Software - Now including the people and products of
BiTKOO | www.quest.com<http://www.quest.com>
From: xac...@lists.oasis-open.org<mailto:xac...@lists.oasis-open.org>
[mailto:xac...@lists.oasis-open.org] On Behalf Of John Tolbert
Sent: Monday, May 07, 2012 11:28 AM
To: xac...@lists.oasis-open.org<mailto:xac...@lists.oasis-open.org>
Subject: [xacml] Groups - Proposed response to Plasma uploaded
Submitter's message
Attached is a draft of my proposed response to Plasma. Please review and make
comments and edits if needed. Once we are in agreement about the content, I
would like for us (as the TC) to submit a response to
https://www.ietf.org/mailman/listinfo/plasma in accordance with the IETF draft
comment process.
Thanks
-- Mr. John Tolbert
Document Name: Proposed response to
Plasma<http://www.oasis-open.org/apps/org/workgroup/xacml/document.php?document_id=45943>
________________________________
No description provided.
Download Latest
Revision<http://www.oasis-open.org/apps/org/workgroup/xacml/download.php/45943/latest/Proposed%20response%20to%20Plasma.docx>
Public Download
Link<http://www.oasis-open.org/committees/document.php?document_id=45943&wg_abbrev=xacml>
________________________________ Submitter: Mr. John Tolbert Group: OASIS eXtensible Access Control Markup Language (XACML) TC Folder: repository Date submitted: 2012-05-07 11:27:40






.docx