OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-sx message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: WS-SX TC Minutes, Oct 31 2007 - VER2


VER2 – Added roll call

 

WS-SX TC Minutes, Oct 31 2007

 

Summary of new Action Items:

Marc to send note to Policy WG with results of our review of Primer and Guidelines

 

1. Call to order/roll call

   

Present:

Status change

None

 

Attendance

Denis Pilipchuk;BEA Systems, Inc.

Corinna Witt;BEA Systems, Inc.

Toshihiro Nishimura;Fujitsu Limited*

Henry (Hyenvui) Chung;IBM

Michael McIntosh;IBM

Anthony Nadalin;IBM

Bruce Rich;IBM

Mike Lyons;Layer 7 Technologies Inc.*

Jan Alexander;Microsoft Corporation

Greg Carpenter;Microsoft Corporation

Marc Goodner;Microsoft Corporation

Chris Kaler;Microsoft Corporation

Norman Brickman;Mitre Corporation*

Abbie Barbir;Nortel

Lloyd Burch;Novell*

Steve Carter;Novell*

Rich Levinson;Oracle Corporation

Martijn de Boer;SAP AG*

Don Adams;TIBCO Software Inc.

 

2. Reading/Approving minutes of last meeting (Oct 17)

http://www.oasis-open.org/archives/ws-sx/200710/msg00021.html

Adopted unanimously.

 

3. TC Logistics (10 minutes or less)

Reminder we are on every other week schedule.

 

4. Issues list

http://docs.oasis-open.org/ws-sx/issues/Issues.xml

   

a) Review of action items

Marc to review example doc for questions on token profile usage with WSS 1.1

http://lists.oasis-open.org/archives/ws-sx/200710/msg00022.html

Hopefully answer this week

 

b) Issues in Review status

 

  None.

 

   

c) New issues

i151: Update SP per Policy 1.5 guidelines

http://www.oasis-open.org/archives/ws-sx/200710/msg00032.html

 

In response to note from W3C Policy WG request

http://www.oasis-open.org/archives/ws-sx/200709/msg00019.html

 

Accepted, moved to pending and assigned to editors

 

Marc assigned to provide Policy WG with results of our review

 

ER015: Change key to crucial in SC text

http://www.oasis-open.org/archives/ws-sx/200710/msg00031.html

Accepted, moved to pending and assigned to editors

 

 

d) Active issues

 

i135 - Need provision in the spec/schema for attachment content signature

Tony doesn’t believe this fits as stated, attachments don’t fit into parts element, encrypted parts not intended for attachments

Closed with no action

 

ER006 - The specification states that if [Timestamp] is false, then wsu:Timestamp should not be present inside <wsse:Security> header.

http://www.oasis-open.org/archives/ws-sx/200710/msg00016.html

Rich thinks there is an ambiguity with the spec here, policy can’t control what is accepted by the service

If the service accepts something that doesn’t meet the service policy it must abide by the content of the message

Marc pointed out that SP already permits a service to accept extra information such as a unrequested Timestamp in the header if present. See section 2.3

http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702/ws-securitypolicy-1.2-spec-os.html#_Toc161826506   

“Note also that a service may choose to accept messages that do not conform to its policy.”

Discussion that this text should be in a global section of document.

Move to pending, add statement consistent with above text to a global section of document.

 

ER012 - Review normative RFC 2119 language in WS-Trust

In progress.

 

ER013 - Review normative RFC 2119 language in WS-SecureConversation

In progress.

 

ER014 - Review normative RFC 2119 language in WS-SecurityPolicy

In progress.

 

 

f) Pending issues

i148 - Syntax of XPath for Signed, Encrypted and Required Elements

 

i150 - Add conformance statements to new versions of Trust/SC/SP

 

 

g) Deferred issues

Reopen issue i141, proposal in message is current

 

5. AOB

 

Marc asked on behalf of RX TC for an estimate as to when we can have CDs of the next versions of our specs available. RX, and TX, specifications depend on SX specifications but not vice versa. Therefore we need to produce new CDs before they can complete their work. Can we target getting our issues closed for the next versions of the specs by the end of the year and produce new CDs in Jan 08?

No objections to setting the above as our goal for schedule.

Chris asked TC members to work to get any new issues in for the next versions of the specs soon so we can meet this target.

 

6. Adjournment

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]