RE: [wss] issue 136 - partially open still.

[<Frederick.Hirsch@nokia.com>]

I got confused, apologies.

The editorial issue (#1) is closed.

The BinarySecurity token issue should be discussed - maybe a new issue.

Should the text (merged)

292 (005) <xxx:CustomToken wsu:Id="MyID" xmlns:xxx="http://fabrikam123/token">
293 (006) FHUIORv...
294 (007) </xxx:CustomToken>

instead be

<wsse:BinarySecurityToken wsu:Id="MyID" " wsse:ValueType="http://fabrikam123/token">

FHUIORv...
</wsse:BinarySecurityToken>

The spec seems to imply tokens are either Username, XML tokens or BinarySecurityTokens, from section 6, so I'd argue for the latter.

regards, Frederick

Frederick Hirsch
Nokia Mobile Phones



-----Original Message-----
From: ext [mailto:Frederick.Hirsch@nokia.com]
Sent: Tuesday, December 16, 2003 9:28 AM
To: drsecure@us.ibm.com; wss@lists.oasis-open.org
Subject: [wss] issue 136 - resolved in latest core, close


Tony

Issue 136 had two points. (http://lists.oasis-open.org/archives/wss/200309/msg00007.html )
You made the requested change  for the first editorial point in the latest core draft. This change was to update the example text to match the example, removing text about username token. This is Done.
The second point was to ask whether the example should use a BinarySecurityToken with a ValueType instead of a CustomToken element. I believe your revised text makes this point moot, since it is clear now that this is an XML token from your changes in wording.
I propose we close issue 136 as done.


regards, Frederick

Frederick Hirsch
Nokia Mobile Phones




> -----Original Message-----
> From: ext drsecure@us.ibm.com [mailto:drsecure@us.ibm.com]
> Sent: Tuesday, December 16, 2003 1:31 AM
> To: wss@lists.oasis-open.org
> Subject: [wss] Groups - WSS-SOAPMessageSecurity-121503.pdf uploaded
>
>
> The document WSS-SOAPMessageSecurity-121503.pdf has been
> submitted by Anthony Nadalin (drsecure@us.ibm.com) to the
> OASIS Web Services Security TC document repository.
>
> Document Description:
> Which AI are addressed in this interim revision:
>
>
>
> 127, 133, 135, 138, 139, 140, 141, 142, 143, 144, 145, 146,
> 167, 168, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180,
> 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192,
> 194, 197, 198, 199, 203, 205, 206, 230, 231, 232, 233
>
>
>
> Which AI are not addressed in this interim revision:
>
>
>
> 136       Waiting on Frederick
>
> 194       Wording/editorial
>
> 200       Waiting on Hal
>
> 201       Wording/editorial
>
> 202       Wording/editorial
>
> 204       Wording/editorial
>
> 207       Table with the exact values
>
> 208       Editorial
>
> 235       Wording/editorial
>
> 236       Wording/editorial
>
> 237       Editorial
>
> 238       Waiting on Hal
>
> 240       We introduce a  which is
>
> Download Document:
> http://www.oasis-open.org/apps/org/workgroup/wss/download.php/
> 4532/WSS-SOAPMessageSecurity-121503.pdf
>
> View Document Details:
> http://www.oasis-open.org/apps/org/workgroup/wss/document.php?
> document_id=4532
>
>
> PLEASE NOTE:  If the above links do not work for you, your
> email application
> may be breaking the link into two pieces.  You may be able to
> copy and paste
> the entire link address into the address field of your web browser.
>
>
>
> To unsubscribe from this mailing list (and be removed from
> the roster of the OASIS TC), go to
> http://www.oasis-open.org/apps/org/workgroup/wss/members/leave
> _workgroup.php.
>
>