RE: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified

["Yalcinalp, Umit" <umit.yalcinalp@sap.com>]

I would like to  delay i053 as we are waiting for more data from our
implementation tea on this regard. 

--umit


> -----Original Message-----
> From: Marc Goodner [mailto:mgoodner@microsoft.com] 
> Sent: Thursday, Nov 03, 2005 12:52 PM
> To: Tom Rutt; paul@wso2.com
> Cc: ws-rx@lists.oasis-open.org
> Subject: RE: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified
> 
> I would also like to remind the TC that we left a motion on the table
> for issue i053. We need to address that before moving on to other
> issues.
> 
> As Anish's proposal for i002 has been out there longer than any of the
> others up for discussion, and his alternate proposal he just sent is
> very easy to understand, I suggest adding that to the agenda following
> i053.
> 
> The new proposals around i022 are easy enough to discuss and 
> are clearly
> related to the proposal Bob submitted some time ago so I think leaving
> that on the agenda after these issues makes sense.
> 
> As for the remaining issues, most of these had no proposal on 
> the table
> until late yesterday afternoon. Personally I'm not sure we have had
> enough time as a group to consider any of these proposals for adoption
> yet.
> 
> Of these issues discussing i054 still makes sense to get a sense of
> where the TC would like to go on i055 and i056. The new proposal for
> i023 is significantly different from the proposal that has been on the
> table to date. As the i055 and i056 proposal that were so 
> interrelated I
> would suggest we talk about i023 before those as it is at 
> least a single
> issue discussion.
> 
> As such I would suggest the following reordering of the 
> remaining issues
> for today's call:
> i053
> i002
> i022
> i054
> i023
> i055
> i056
> i050 - No proposal, so it should remain last.
> 
> -----Original Message-----
> From: Tom Rutt [mailto:tom@coastin.com] 
> Sent: Thursday, November 03, 2005 11:54 AM
> To: paul@wso2.com
> Cc: ws-rx@lists.oasis-open.org
> Subject: Re: [ws-rx] Groups - WS-RX TC Weekly Conference Call modified
> 
> paul@wso2.com wrote:
> 
> >Updated agenda with proposal links and new issues link
> >
> > -- Mr. Paul Fremantle
> >  
> >
> I have a concern about discussion issue 006 before issue 008 is
> resolved.
> 
> Also, Issue 008 depends on the resolution of issue 21.
> 
> Thus I would prefer we take issue 006 off the discusion list 
> for today's
> 
> call.
> 
> Tom Rutt
> Fujitsu
> 
> >
> >WS-RX TC Weekly Conference Call has been modified by Mr. 
> Paul Fremantle
> >
> >Date:  Thursday, 03 November 2005
> >Time:  01:00pm - 02:30pm PT
> >
> >Event Description:
> >Dial-in Number: 	1-641-297-5500  (St. Marys, IA) 	
> >Participant Access Code 	003502
> >
> >mute = 6
> >
> >IRC/Q Mgmt(thanks to DougD): 
> http://webconf.soaphub.org/conf/room/wsrx
> >
> >Agenda:
> >Agenda:
> >1) Roll Call
> >
> >2) Review and approval of this agenda
> >
> >3) Approval of the previous meeting minutes
> >http://www.oasis-open.org/apps/org/workgroup/ws-rx/download.p
> hp/15110/M
> inutesWSRX-102705.htm
> > 
> >4) Administrative Issues
> >Status of CD posting and stable URLs
> >Attendance ballot for Sunnyvale F2F
> >
> >5) AI Review
> >http://www.oasis-open.org/apps/org/workgroup/ws-rx/members/ac
> tion_items
> .php
> >
> >6) New issues since last conf-call
> >http://lists.oasis-open.org/archives/ws-rx/200511/msg00057.html
> >
> >7) Issue Discussion:
> >Note new stable URL:
> http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssues.xml
> >(Thanks to Paul Cotton for proposal analysis)
> >
> >-------------------------
> >i022	Vikas Deolaliker	RM Policy Assertion Model's Base
> Retransmission Interval Clarification Needed
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i02
> 2
> >
> >Aug 8 proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200508/msg00033.html 
> >
> >Sep 22 counter proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200509/msg00254.html 
> >
> >Nov 2 counter proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200511/msg00021.html
> >-------------------------
> >i023	Marc Goodner	Robust recovery from low-resource conditions
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i02
> 3
> >
> >Proposal from original issue:
> >http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/arch
> ives/20050
> 7/msg00252.html 
> >
> >Oct 12 counter proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200510/msg00062.html 
> >
> >Nov 2nd proposals:
> >http://lists.oasis-open.org/archives/ws-rx/200511/msg00041.html
> >------------------------- 
> >i054	Umit Yalcinalp	Target of RM Assertion parameters are confusing
> with respect to how they are specified
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i05
> 4
> >
> >Oct 18 proposal (message has no subject field):
> >http://lists.oasis-open.org/archives/ws-rx/200510/msg00156.html 
> > 
> >-------------------------
> >i055	Marc Goodner	Whose Inactivity Timeout is it anyway?
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i05
> 5
> >
> >Original issue:
> >http://lists.oasis-open.org/archives/ws-rx/200510/msg00157.html 
> >
> >Proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200511/msg00037.html
> >
> >-------------------------
> >i056	Chris Ferris How can RMS communicate the Base Retransmission
> Interval, Exponential Backoff and Inactivity Timeout values?
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i05
> 6
> >
> >Original issue with proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200510/msg00159.html 
> >
> >Nov proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200511/msg00040.html
> >
> >-------------------------
> >i006	Tom Rutt	Source based delivery QoS policy assertion
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i00
> 6
> >
> >Original issue with proposal:
> >http://lists.oasis-open.org/archives/ws-rx/200510/msg00050.html 
> >
> >-------------------------
> >i050	Marc Goodner	spec talks about delivery assurances but does
> not clearly relate them to the protocol
> >http://docs.oasis-open.org/ws-rx/issues/ReliableMessagingIssu
> es.xml#i05
> 0
> >
> >Original issue with proposal:
> >http://www.oasis-open.org/apps/org/workgroup/ws-rx/email/arch
> ives/20050
> 9/msg00269.html 
> >
> >-------------------------
> >
> >8) Any other business
> >
> >Minutes:
> >
> >
> >This event is one in a list of recurring events.
> >Other event dates in this series:
> >
> >Thursday, 06 October 2005, 01:00pm to 02:30pm PT
> >Thursday, 13 October 2005, 01:00pm to 02:30pm PT
> >Thursday, 20 October 2005, 01:00pm to 02:30pm PT
> >Thursday, 27 October 2005, 01:00pm to 02:30pm PT
> >Thursday, 10 November 2005, 01:00pm to 02:30pm PT
> >Thursday, 17 November 2005, 01:00pm to 02:30pm PT
> >
> >View event details:
> >http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.php?
> event_id=8
> 759
> >
> >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.
> >
> >  
> >
> >-------------------------------------------------------------
> ----------
> -
> >
> >BEGIN:VCALENDAR
> >METHOD:PUBLISH
> >VERSION:2.0
> >PRODID:-//Kavi Corporation//NONSGML Kavi Groups//EN
> >X-WR-CALNAME:My Calendar
> >BEGIN:VEVENT
> >CATEGORIES:MEETING
> >STATUS:TENTATIVE
> >DTSTAMP:20051103T000000Z
> >DTSTART:20051103T210000Z
> >DTEND:20051103T223000Z
> >SEQUENCE:14
> >SUMMARY:WS-RX TC Weekly Conference Call
> >DESCRIPTION:Dial-in Number: 	1-641-297-5500  (St. Marys\, IA)
> \nParticipant
> >  Access Code 	003502\n\nmute = 6\n\nIRC/Q Mgmt(thanks 
> to DougD):
> >  http://webconf.soaphub.org/conf/room/wsrx\n\nGroup: OASIS Web
> Services
> >  Reliable Exchange (WS-RX) TC\nCreator: Mr. Paul Fremantle
> >URL:http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.
> php?event_
> id=8759
> >UID:http://www.oasis-open.org/apps/org/workgroup/ws-rx/event.
> php?event_
> id=8759
> >END:VEVENT
> >END:VCALENDAR
> >
> 
>