[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [ws-rx] Mailing list discussion
Paul +1. Except maybe 126 which might not be straightforward. However, I would like time on the agenda to get an update on security from Gil, Marc, Martin, Chris and the others who have been working on it. So I suggest that we timebox the discussion on these issues to leave the last 30 mins for security. Paul Paul Cotton wrote: >> i133 Duplicate text in fault section >> i127 Make Accept/AcksTo consistent >> i129 Define "discard" >> i130 what does ack interval refer to >> i125 Protocol precondition requires knowledge of policies >> i126 unclear text regarding wsa:Action >> > > Can we amend today's agenda to process this set of issues first (before > the security issues)? > > /paulc > > Paul Cotton, Microsoft Canada > 17 Eleanor Drive, Ottawa, Ontario K2E 6A3 > Tel: (613) 225-5445 Fax: (425) 936-7329 > mailto:Paul.Cotton@microsoft.com > > > > > > >> -----Original Message----- >> From: Paul Fremantle [mailto:paul@wso2.com] >> Sent: June 15, 2006 11:02 AM >> To: wsrx >> Subject: [ws-rx] Mailing list discussion >> >> Looking at the schedule >> > (http://www.oasis-open.org/apps/org/workgroup/ws- > >> rx/email/archives/200606/msg00008.html) >> * June 22nd Target for all issues closed >> >> I am highly concerned that we will not meet this target without a >> > greater > >> level of participation - in particular more discussion on the mailing >> list. >> >> In particular I would like to get to the point where we can resolve >> > issues > >> effectively on the calls which means >> 1) having concrete proposals >> 2) having had those proposals discussed on the mailing list >> 3) using the calls to reach consensus or vote >> >> If there is no discussion on the list it is only reasonable that the >> owners of the issues assume that their proposals are acceptable. >> The onus is on the TC to review the issues before the call and to >> > raise > >> concerns BEFORE the calls. >> >> In particular I would expect us to be able to deal quickly and >> > effectively > >> with these issues: >> >> i133 Duplicate text in fault section >> i127 Make Accept/AcksTo consistent >> i129 Define "discard" >> i130 what does ack interval refer to >> i125 Protocol precondition requires knowledge of policies >> i126 unclear text regarding wsa:Action >> >> I also expect IBM, BEA, and Microsoft to be trying to resolve each >> > others > >> concerns on the security issues. >> >> Paul >> >> -- >> >> Paul Fremantle >> VP/Technology, WSO2 and OASIS WS-RX TC Co-chair >> >> http://feeds.feedburner.com/bloglines/pzf >> paul@wso2.com >> >> "Oxygenating the Web Service Platform", www.wso2.com >> > > > -- Paul Fremantle VP/Technology, WSO2 and OASIS WS-RX TC Co-chair http://feeds.feedburner.com/bloglines/pzf paul@wso2.com "Oxygenating the Web Service Platform", www.wso2.com
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]