The WS-Policy meeting will be adjourned at 3pm ET to permit members to
join the WS-RX TC distributed meeting. Our host, IBM, will be providing
a separate meeting room to facilitate participation in the RX TC
meeting.
Chris Ferris, myself and several others will be taking advantage of
this.
/paulc
Paul Cotton, Microsoft Canada
17 Eleanor Drive, Ottawa, Ontario K2E 6A3
Tel: (613) 225-5445 Fax: (425) 936-7329
mailto:
> -----Original Message-----
> From: Ashok Malhotra [mailto:]
> Sent: July 12, 2006 9:32 PM
> To: ;
> Subject: RE: [ws-rx] Groups - WS-RX TC Weekly Meeting modified
>
> Sanjay:
> Some of us, Umit, Jeff, I and possibly others, will be flying back
from
> the WS-Policy
> meeting tomorrow and may not be able to make the call.
>
> All the best, Ashok
>
>
> > -----Original Message-----
> > From: [mailto:]
> > Sent: Wednesday, July 12, 2006 1:36 PM
> > To:
> > Subject: [ws-rx] Groups - WS-RX TC Weekly Meeting modified
> >
> >
> > WS-RX TC Weekly Meeting has been modified by Mr Sanjay Patil
> >
> > Date: Thursday, 13 July 2006
> > Time: 01:00pm - 02:30pm PT
> >
> > Event Description:
> > Dial-in details (thanks to Novell):
> > US Toll Free: 1-888-791-6044
> > US Toll/International: 1-210-234-0004
> > Passcode: 15457
> > Mute/Unmute: *6
> >
> > IRC/Q Mgmt(thanks to DougD):
http://webconf.soaphub.org/conf/room/wsrx
> >
> > Agenda:
> > 1) Roll Call
> >
> > 2) Review and approval of the agenda
> >
> > 3) Approval of the Jul 6th, 2006 meeting minutes
> >
> > http://www.oasis-open.org/committees/download.php/19082/Minute
> > sWSRX-070606.html
> >
> > 4) Sponsors for conf-call facilities for upcoming weeks
> >
> > 5) AI Review
> >
> > http://www.oasis-open.org/apps/org/workgroup/ws-rx/members/act
> > ion_items.php
> >
> > 6) New issues since last conf-call
> > Watch for Marcs email
> >
> > 7) Issue Discussion:
> > a> i122 security profiles
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i122
> > b> i124 security composition policy
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i124
> > c> i123 security profile agreement
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i123
> > d> i139 Inappropriate Fault destination
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i139
> > e> i113 Tightening up the state tables
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i113
> > f> i147 Extensibility (or not) of the Protocol Elements
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i147
> > g> i140 add sub-headings to fault descriptions
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i140
> > h> i143 messages have to be received for them to be examined
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i143
> > i> i144 RMS MessageNumberRollover behavior unclear
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i144
> > j> i145 Implications of Sequence Expiration not specified
> >
> > http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssue
> > s.xml#i145
> > 8) Any other business
> >
> >
> > Minutes:
> >
> >
> > This event is one in a list of recurring events.
> > Other event dates in this series:
> >
> > Thursday, 29 June 2006, 01:00pm to 02:30pm PT
> > Thursday, 06 July 2006, 01:00pm to 02:30pm PT
> > Thursday, 20 July 2006, 01:00pm to 02:30pm PT
> > Thursday, 27 July 2006, 01:00pm to 02:30pm PT
> > Thursday, 03 August 2006, 01:00pm to 02:30pm PT
> > Thursday, 10 August 2006, 01:00pm to 02:30pm PT
> > Thursday, 17 August 2006, 01:00pm to 02:30pm PT
> > Thursday, 24 August 2006, 01:00pm to 02:30pm PT
> > Thursday, 31 August 2006, 01:00pm to 02:30pm PT
> > Thursday, 07 September 2006, 01:00pm to 02:30pm PT
> >
> > View event details:
> > http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.php?e
> > vent_id=12126
> >
> > PLEASE NOTE: If the above link does 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.
> >
> >
> >
