Forwarding to a few mailing lists in case anyone did not receive this through the other distribution channels.

You are invited to attend a 3-day Interop Workshop covering the WS-Policy and WS-PolicyAttachment specifications from April 25-27, 2006 at SAP's Walldorf offices from 9am to 5pm with breakfast available from 8am.

To attend this event, the attached feedback agreement MUST be reviewed and signed by each attendee - either before or at the workshop event. The purpose of the feedback agreement is to ensure that everyone involved in influencing the specifications is committed to keeping the specification royalty free. Also, as this is an Interop Workshop, participants will need to bring an implementation based on the specifications below.

The 3-day interop workshop is an ad-hoc, open forum for companies who have WS-Policy and WS-PolicyAttachment implementations based on the specifications published March 2006, and who want to test their implementations with other companies' implementations. Attendees bring their own laptops, their implementations and any other tools they feel would be needed; testing among all attendees will occur throughout the day.  A scenario document for use in the Interop Workshop is provided in this invitation. Progress of interoperating implementations will be tracked throughout the event.

This workshop will be held at SAP AG in Walldorf, Germany, see below for location details.

An internet connection will be available during the workshop.

Breakfast, lunch, and afternoon snacks will be served, but participants will be responsible for their own dinner arrangements. Please make any special dietary requirements known in advance, and every effort will be made to accommodate them.

As with previous workshops, these events are open to anyone who desires to participate and who can bring an implementation based on the specifications listed above.

If you are interested in participating, please reply to Claus von Riegen, claus.von.riegen@..., +49 6227 742589.

A signed feedback agreement must be faxed to Claus von Riegen, fax +49 6227 7819953.

Feel free to pass this invitation along, either in your company or elsewhere.
This is an open forum. No invitation is required, but an RSVP is appreciated by the event hosts to facilitate accurate logistics planning. The list of attendees and general workshop results will be made public after the workshop.

Thank you and we look forward to your participation.

BEA Systems, IBM, Microsoft, SAP AG, Sonic Software, VeriSign

Workshop Location Details
Building 1, Room Biel, 6th floor
Dietmar-Hopp-Allee 16
69190 Walldorf, Germany

Maps, public transportation information, driving directions, hotel recommendations and other useful visitor information can be obtained from the attached document.

<<2006.04.Policy-Interop-Workshop.zip>>

Sorry to hear you’ll be missing all the fun.

http://www.infoworld.com/article/05/11/03/HNjavanet_1.html

While IBM will not be attending this event I'd like to remind people of IBM's interop endpoints (listed at:  http://wsi.alphaworks.ibm.com:8080/interop/index.html ) which supports the full interop scenario documents as specified by the specific interop workshop event.  If anyone runs into any problems with these endpoints please drop me a note.
thanks
-Doug

Thanks Doug,
 
It’s good to hear about IBM’s continuing interest in WS-* interop testing.
 
You seem to have misunderstood my mail – this is an invite to a F2F meeting - the Windows Communication Foundation (aka Indigo) interop *plug-fest* we will hold in Redmond on November 7^th – 10th.  
 
The event is focused on the product-level interop with WCF. Unlike the previous WS-* Workshops, this event is not focused on getting feedback for the WS-* specs.  Based on our experience with soapbuilders, such F2F events are super-effective at advancing interoperability between products.
 
We are encouraged by the wide support from the WS-* community for this plug-fest, and we look forward to IBM joining us at the F2F in November.
 
 

From: wsdl@yahoogroups.com [mailto:wsdl@yahoogroups.com] On Behalf Of Doug Davis
Sent: Friday, October 07, 2005 4:22 PM
To: soapbuilders@yahoogroups.com
Cc: ws-eventing-workshops@yahoogroups.com; WS-RM-Workshops@yahoogroups.com; WS-Security-Workshops@yahoogroups.com; WS-TX-Workshops@yahoogroups.com; wsdl@yahoogroups.com
Subject: [wsdl] Re: [soapbuilders] Indigo / Windows Communication Foundation (WCF) Interop Plug-fest - 7-10 Nov 2005
 

Kirill,
 Thanks for the notice of your interop endpoints.  IBM has endpoints up for most of WS-* specifications you mentioned covering the scenarios as specified in the interop workshop's scenario documents.  The endpoints should cover the full range of features specified in those scenario documents and not just the subset your version of the scenario documents mention.  Based on the activity logs they seem to be widely used and appear to be quite useful to the WS community.  We welcome MSFT's efforts to join this adhoc/off-line testing process and hope you keep your endpoint up indefinitely as we hope to.  Please see the respective WS-* Yahoo group for the URL of the endpoint of interest - or feel free to contact me at dug@... if you're unable to locate the URL.
thanks
-Doug

Hey to all you Web Services Toolkits implementers out there!
 
We are planning a 4-day Windows Communications Foundation (WCF, a.k.a Indigo) Interop Plug-fest on Monday November 7, 2005 to Thursday November 10, 2005 at Microsoft Redmond campus.
 
The WCF (Indigo) Interop Plug-fest is an ad-hoc, open forum for implementers of various Web Services protocols to meet with engineers from the WCF(Indigo) team and test interoperability with the upcoming release.
 
Please reply to kirillg@... and jthelin@... introducing your implementation if you’re interested in attending.
 
Scenarios drafts as well as pointers to test endpoints are available online - http://mssoapinterop.org/ilab/wcfinteroplab.htm . We recommend you to join the WS-Builders@yahoogroups.com discussion group and use it for questions around scenarios documents and WCF(Indigo) interoperability.
 
Here is an invite with further logistics info: http://mssoapinterop.org/ilab/WCFInteropPlugFest_invite.doc
 
Thank you and we hope to see you November 7^th !

Doug,

We love interop face-to-face events of all kinds. Lack of interop events is what hurts.

Kirill wrote on 10/10/2005 02:24:47 PM:

> Thanks Doug,
>  
> You seem to have misunderstood my mail – this is an invite to a F2F meeting - the
> Windows Communication Foundation (aka Indigo) interop *plug-fest* we will hold in
> Redmond on November 7th – 10th.  

I understood - just wanted to make sure you, and others, were aware of IBM's
full-scenario endpoints - which are there for continued full spec interop testing
and not just for 'feedback' on the specs as you suggest below.

> The event is focused on the product-level interop with WCF. Unlike the previous WS-
> * Workshops, this event is not focused on getting feedback for the WS-* specs.
> Based on our experience with soapbuilders, such F2F events are super-effective at
> advancing interoperability between products.

NxM full spec interop events yes.  A '1xM subset of the spec' event is something
different isn't it?  :-)
 
> We are encouraged by the wide support from the WS-* community for this plug-fest,
> and we look forward to IBM joining us at the F2F in November.

I can't speak to whether or not IBM will participate in the event.

thanks
-Doug

Thanks Doug,

It’s good to hear about IBM’s continuing interest in WS-* interop testing.

You seem to have misunderstood my mail – this is an invite to a F2F meeting - the Windows Communication Foundation (aka Indigo) interop *plug-fest* we will hold in Redmond on November 7^th – 10th.  

The event is focused on the product-level interop with WCF. Unlike the previous WS-* Workshops, this event is not focused on getting feedback for the WS-* specs.  Based on our experience with soapbuilders, such F2F events are super-effective at advancing interoperability between products.

We are encouraged by the wide support from the WS-* community for this plug-fest, and we look forward to IBM joining us at the F2F in November.

Kirill,
  Thanks for the notice of your interop endpoints.  IBM has endpoints up for most of WS-* specifications you mentioned covering the scenarios as specified in the interop workshop's scenario documents.  The endpoints should cover the full range of features specified in those scenario documents and not just the subset your version of the scenario documents mention.  Based on the activity logs they seem to be widely used and appear to be quite useful to the WS community.  We welcome MSFT's efforts to join this adhoc/off-line testing process and hope you keep your endpoint up indefinitely as we hope to.  Please see the respective WS-* Yahoo group for the URL of the endpoint of interest - or feel free to contact me at dug@... if you're unable to locate the URL.
thanks
-Doug

Hey to all you Web Services Toolkits implementers out there!
 
We are planning a 4-day Windows Communications Foundation (WCF, a.k.a Indigo) Interop Plug-fest on Monday November 7, 2005 to Thursday November 10, 2005 at Microsoft Redmond campus.
 
The WCF (Indigo) Interop Plug-fest is an ad-hoc, open forum for implementers of various Web Services protocols to meet with engineers from the WCF(Indigo) team and test interoperability with the upcoming release.
 
Please reply to kirillg@... and jthelin@... introducing your implementation if you’re interested in attending.
 
Scenarios drafts as well as pointers to test endpoints are available online - http://mssoapinterop.org/ilab/wcfinteroplab.htm . We recommend you to join the WS-Builders@yahoogroups.com discussion group and use it for questions around scenarios documents and WCF(Indigo) interoperability.
 
Here is an invite with further logistics info: http://mssoapinterop.org/ilab/WCFInteropPlugFest_invite.doc
 
Thank you and we hope to see you November 7^th !

-----------------------------------------------------------------
This group is a forum for builders of SOAP implementations to discuss implementation and interoperability issues.  Please stay on-topic.

YAHOO! GROUPS LINKS

•  Visit your group "soapbuilders" on the web.
   
•  To unsubscribe from this group, send an email to:
  soapbuilders-unsubscribe@yahoogroups.com
   
•  Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.

Hey to all you Web Services Toolkits implementers out there!

We are planning a 4-day Windows Communications Foundation (WCF, a.k.a Indigo) Interop Plug-fest on Monday November 7, 2005 to Thursday November 10, 2005 at Microsoft Redmond campus.

The WCF (Indigo) Interop Plug-fest is an ad-hoc, open forum for implementers of various Web Services protocols to meet with engineers from the WCF(Indigo) team and test interoperability with the upcoming release.

Please reply to kirillg@... and jthelin@... introducing your implementation if you’re interested in attending.

Scenarios drafts as well as pointers to test endpoints are available online - http://mssoapinterop.org/ilab/wcfinteroplab.htm . We recommend you to join the WS-Builders@yahoogroups.com discussion group and use it for questions around scenarios documents and WCF(Indigo) interoperability.

Here is an invite with further logistics info: http://mssoapinterop.org/ilab/WCFInteropPlugFest_invite.doc

Thank you and we hope to see you November 7^th !

At this time, the Microsoft WS-RM service endpoints are still located at:

http://131.107.153.195/SecureReliableMessaging/ReliableOneWay.svc [anonymous clients, no security]

http://131.107.153.195/SecureReliableMessaging/ReliableOneWayDual.svc [addressable clients, no security]

http://131.107.153.195/SecureReliableMessaging/SecureReliableOneWay.svc [anonymous clients, with security]

http://131.107.153.195/SecureReliableMessaging/SecureReliableOneWayDual.svc [addressable clients, with security]

http://131.107.153.195/SecureReliableMessaging/ReliableRequestReplyDual.svc [addressable clients, no security, echoString]

Our client driver is located at http://131.107.153.195/RM/RMClient.asmx. Please contact onhrebic@... and kirillg@... with questions and issues.

Ondrej

+1

Attached are the minutes from the RM+SC interop workshop last week.

Please let me know if there are any errors or omissions.

As per previous workshop practice, the results table in the minutes is anonymous.

May thanks to everyone that participated in this meeting.

Participants at the workshop meeting re-iterated their intention to keep their interop endpoints online to facilitate on-going interop testing. Anyone that couldn’t join us for this workshop is welcome to continue testing online.

- Jorgen

Kirill,

    Did they ever agree on a single cert pair?

If so, where can I get them?

        George

What do people think about using the certificates pair from the OASIS X509 interop demo (Alice and Bob) that Jan has this morning for all clients and services?

It would simplify client testing if we can agree on a single cert pair…

Thanks!

I’m still in discussions with our networking and security folks to see what inbound ports we can get opened to allow remote testing for this workshop.

If you are interested in joining in remotely, I suggest you check back at 10:30am tomorrow (Wednesday) when the picture should be clearer.

Hi Alan,

Yes, you are correct – the info in WS-* workshop invitations are public, so they are definitely quotable in your article.

If you wish to point to an online reference, this info is posted on MSDN for public consumption:

http://msdn.microsoft.com/webservices/community/workshops/composability042005.aspx

I realize you probably know this already, but just to repeat for the record, the following is public data:

            - Contents of workshop invitations

            - A general summary of workshop meetings

- Which companies participated in each workshop meeting

Pretty much the only thing that you can’t quote publicly is the _specific_ results of individual companies.
The reason is simply that we want to have an environment that respects that companies may bring pre-release code to these workshops, so their results at that time may not necessarily bear any relation to the code they eventually ship to market.

Also, should you wish to provide some background links in your article about the WS-* Workshop process, there’s an article on MSDN with an Overview of the WS-* Workshop Process which you are welcome to link to.

http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/wkshopprocess.asp

Let me know if you need any additional info, or if you would like an extra pair of eyes to review your article before submission.

Best regards,

Jorgen

I am writing an article on the interop testing of two sets of specs:
1] WS-RM'g and WS Secure Conversation
2] WS-Reliability and WS Security

Are there any problems with publishing the following (this is taken
from the workshop announcement mail sent by Jurgen):

BEA Systems Inc, International Business Machines, Microsoft
Corporation and TIBCO Software Inc., co-developers of the WS-Reliable
Messaging specification, are hosting a two day Composability Interop
Workshop on April 13 and 14, 2005 at Microsoft's Silicon Valley
Campus in Mountain View.  The two day interop workshop is an ad-hoc,
open forum for companies who have WS-Reliable Messaging and WS-Secure
Conversation  implementations, and who want to test their
implementations with other companies' implementations. Attendees
bring their own laptops, their implementations and any other tools
they feel would be needed; testing among all attendees will occur
throughout the day.  As with previous WS-* workshops, these events
are open to anyone who desires to participate and who can bring an
implementation based on the specifications listed above.
A revised test scenario document for use in the Interop Workshop was
recently made available to interop participants.
Footnote:
1.   Web Services Secure Conversation Language (WS-
SecureConversation):
This specification defines extensions that build on [WS-Security] and
[WS-Trust] to provide secure communication across one or more
messages. Specifically, this specification defines mechanisms for
establishing and sharing security contexts, and deriving keys from
established security contexts (or any shared secret).

If not, I will include the above in the article, which I will submit
to gridtoday.com and web services pipelines (where I have previously
published.

Thanks

alan Weissberger

Alan Weissberger
DCT
2013 Acacia Ct
Santa Clara, CA 95050-3482
1 408 863 6042 voice
1 408 863 6099 fax

Hi Alan,

Yes, you are correct – the info in WS-* workshop invitations are public, so they are definitely quotable in your article.

If you wish to point to an online reference, this info is posted on MSDN for public consumption:

http://msdn.microsoft.com/webservices/community/workshops/composability042005.aspx

I realize you probably know this already, but just to repeat for the record, the following is public data:

            - Contents of workshop invitations

            - A general summary of workshop meetings

- Which companies participated in each workshop meeting

Pretty much the only thing that you can’t quote publicly is the _specific_ results of individual companies.
The reason is simply that we want to have an environment that respects that companies may bring pre-release code to these workshops, so their results at that time may not necessarily bear any relation to the code they eventually ship to market.

Also, should you wish to provide some background links in your article about the WS-* Workshop process, there’s an article on MSDN with an Overview of the WS-* Workshop Process which you are welcome to link to.

http://msdn.microsoft.com/webservices/default.aspx?pull=/library/en-us/dnwebsrv/html/wkshopprocess.asp

Let me know if you need any additional info, or if you would like an extra pair of eyes to review your article before submission.

Best regards,

Jorgen

I am writing an article on the interop testing of two sets of specs:
1] WS-RM'g and WS Secure Conversation
2] WS-Reliability and WS Security

Are there any problems with publishing the following (this is taken
from the workshop announcement mail sent by Jurgen):

BEA Systems Inc, International Business Machines, Microsoft
Corporation and TIBCO Software Inc., co-developers of the WS-Reliable
Messaging specification, are hosting a two day Composability Interop
Workshop on April 13 and 14, 2005 at Microsoft's Silicon Valley
Campus in Mountain View.  The two day interop workshop is an ad-hoc,
open forum for companies who have WS-Reliable Messaging and WS-Secure
Conversation  implementations, and who want to test their
implementations with other companies' implementations. Attendees
bring their own laptops, their implementations and any other tools
they feel would be needed; testing among all attendees will occur
throughout the day.  As with previous WS-* workshops, these events
are open to anyone who desires to participate and who can bring an
implementation based on the specifications listed above.
A revised test scenario document for use in the Interop Workshop was
recently made available to interop participants.
Footnote:
1.   Web Services Secure Conversation Language (WS-
SecureConversation):
This specification defines extensions that build on [WS-Security] and
[WS-Trust] to provide secure communication across one or more
messages. Specifically, this specification defines mechanisms for
establishing and sharing security contexts, and deriving keys from
established security contexts (or any shared secret).

If not, I will include the above in the article, which I will submit
to gridtoday.com and web services pipelines (where I have previously
published.

Thanks

alan Weissberger

Thanks Jan,

> As to #2, I would rather completely remove wsse11:SignatureConfirmation from all messages, because this has no status in any current WSS specification.

Secure RM needed a way to prevent secure session hijack at the initiation step.

Signature confirmation is used in situations where initiator needs confirmation that the message received was indeed generated in response to a message it initiated in its unaltered form. This prevents certain class of man in the middle attacks (e.g.: maliciously adding signatures, man in the middle adding additional headers without awareness of the initiator).

The current OASIS SOAP Message security 1.1 draft [1] contains signature confirmation (see section 8.5, starting at line 1170).

Given that we needed a way to demonstrate mitigation of the session hijack threat, instead of introducing a custom mechanism, we re-used a pattern that is already being worked on inside the OASIS WSS TC.

[1] http://www.oasis-open.org/apps/org/workgroup/wss/download.php/11535/oasis-2004xx-wss-soap-message-security-1.1-changes.pdf

Folks, haven’t heard much feedback from participants – is everyone ok with making these changes?

thanks