- From: Asir Vedamuthu <asirveda@microsoft.com>
- Date: Wed, 2 May 2007 19:48:18 -0700
- To: Fabian Ritzmann <Fabian.Ritzmann@Sun.COM>, Paul Cotton <Paul.Cotton@microsoft.com>
- CC: "public-ws-policy-interop@w3.org" <public-ws-policy-interop@w3.org>, Christopher B Ferris <chrisfer@us.ibm.com>, Abbie Barbir <abbieb@nortel.com>
>I assume you are saying the remote clients would >help outside the event if parties can set up their >endpoints on a public endpoint? That is correct. A requester inside the firewall can reach a provider within the firewall or outside the firewall. A requester outside the firewall can only reach a provider outside the firewall. Regards, Asir S Vedamuthu Microsoft Corporation -----Original Message----- From: public-ws-policy-interop-request@w3.org [mailto:public-ws-policy-interop-request@w3.org] On Behalf Of Fabian Ritzmann Sent: Wednesday, May 02, 2007 11:55 AM To: Paul Cotton Cc: public-ws-policy-interop@w3.org; Christopher B Ferris; Abbie Barbir Subject: Re: May F2F interop event Paul Cotton wrote: >> We do not have static IP addresses and a firewall may be in the way. >> > > We believe that this restriction is going to make remote testing difficult if not impossible during the Ottawa interop event. > > Note that some interop participants (e.g. IBM and Microsoft) have setup remote Round3 clients to avoid this kind of problem: > Remote clients are no good during the interop event if you can't penetrate the firewall. I assume you are saying the remote clients would help outside the event if parties can set up their endpoints on a public endpoint? Fabian
Received on Thursday, 3 May 2007 02:48:53 UTC