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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oic message

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


Subject: OIC TC 2013-02-06 Meeting Minutes


OIC COORDINATION CALL
Date:  Wednesday 6 February 2013
Time:  14:30 - 15:25 UTC

 
1. LOGISTICS

The chat room: http://webconf.soaphub.org/conf/room/oic
(doesn't count for attendance) 
 
The call-in numbers: 
https://www.teleconference.att.com/servlet/glbAccess?process=1&accessCode=84367726&accessNumber=2158616239
 
Meeting agenda also provides the pass codes and the commonly-used call-in numbers
https://lists.oasis-open.org/archives/oic/201302/msg00003.html

The action items (log-in required):
http://www.oasis-open.org/apps/org/workgroup/oic/members/action_items.php


1.1 ROLL CALL AND QUORUM CHECK

The 2/3 voting members present did satisfy the 2/3 quorum requirement for start of the meeting. 

    MEMBERS IN ATTENDANCE
    * Bart Hanssens, Fedict (Chair)
    * Andreas Guelzow, Individual
      Dennis Hamilton, Individual
      Svante Schubert, Individual
      Louis Suarez-Potts, Individual

      [* = Voting Member at start of meeting (2)
       + = becoming Voting Member at conclusion of meeting (0)
       = = Persistent Non-Voting Member (0)]
 
    MEMBERS ABSENT
      Charles Schulz, Ars Aperta
      Peter Junge, Beijing Sursen International
      Alex Wang, Beijing Sursen International 
      Jeremy Allison, Google Inc.
      Don Harbison, IBM
      Mingfei Jia, IBM
      Rob Weir, IBM
      Zhun Guo, Individual
      Cherie Ekholm, Microsoft
      John Haug, Microsoft
      Doug Mahugh, Microsoft
      Eric Patterson, Microsoft
    - Chris Rae, Microsoft
      Kazmer Koleszar, MultiRacio
      Péter Rakyta, MultiRacio
      Suresh Chande, Nokia
      Thorsten Behrens, Novell
      Alan Clark, Novell
      Sven Jacobi, Oracle
      Andrew Rist, Oracle
      Jerry Smith, US Department of Defense

      [* = Voting Member at start and end of meeting (0)
       - = Voting Member becoming non-voting Member at end of meeting (1)
       = = Persistent Non-Voting Member (0)
       ! = Voting Member on leave-of-absence through the specified date (0)
         ]
 
1.2 PREVIOUS MEETING MINUTES AND NOTES

The previous Meetings Minutes and the Meeting Notes are approved without comments.
- https://lists.oasis-open.org/archives/oic/201212/msg00002.html
- https://lists.oasis-open.org/archives/oic/201301/msg00003.html

1.3 TODAY'S AGENDA

The agenda is approved.
- https://lists.oasis-open.org/archives/oic/201302/msg00003.html


2. STATUS OF ACTION ITEMS

  #0015 Template Scenarios.  No report.
  #0041 Battery of ODF 1.2 Assessment Documents.  No report.
  #0044 Split up Advisory 00002.  Work in progress.
  #0046 Update Advisory 00007.  Work in progress.
  #0047 Confirmation of Advisory 00008 test documents. Work in progress.
  #0051 Check advisory 00005. Work in progress.
  #0052 Draft 2nd Status of Interop report. Closed.


3. THE OIC TC IN 2013

* Bart questions what the TC really can deliver in 2013, given the limited resources.
He volunteers to continue working on the second State of Interoperability report,
and (if time permits) work on signatures advisories.

* Louis notes that, without the active participation of major implementors in the TC,
it will not be possible to really achieve anything useful.
He suggests to add a feature matrix to the interop report, and to make it a live document.
Especially with the work being done on ODF 1.3, it would be useful to see what the current issues are,
and what is - or is expected to be - solved.
Organizing ODF plugfests and using Officeshots.org may help to compile said matrix.

Dennis likes the focused view and thinks that a feature matrix can be useful.
However, it will be hard to do this without naming specific implementations.

Svante mentions that OpenDoc Society contacted RedHat to set up a validator (http://odfvalidator.org)
Louis wants to know if Jan Wildeboer (RedHat) is focused on one implementation in particular.
Svante says this that Jan is indeed geared towards one implementation, but that this must not be a problem,
as Jan is happy to cooperate with developers from other implementations.

* Svante suggests that part of the work of the Advanced Document Collaboration SC could be transferred to the OIC TC.


4. DELIVERABLES / TEST CASES

4.1 Second "State of Interoperability" Report

Bart has uploaded a new working draft of the "2nd State of Interoperability" report.
This time it is written using the OASIS ODT template for Committee Note (White Paper style)

The comments on the OIC TC Wiki and the first "State of Interoperability report" served as input.
Some more "beef" should be added to the report, perhaps by adding some test files to demonstrate known issues.
- https://www.oasis-open.org/committees/document.php?document_id=48154&wg_abbrev=oic


4.2 Other Interop Advisories

No new advisories and no updates.


5. ROUND TABLE

* Svante read an (old) article on XML Encryption and AES-CBC, and wonders if this applies to ODF as well
He also raises the question what should be done when (parts of) standards referenced by ODF are deemed insecure.
- http://www.h-online.com/security/news/item/Researchers-XML-encryption-standard-is-insecure-1364074.html
- http://www.w3.org/TR/2013/PR-xmlenc-core1-20130124/#sec-cbcBlockEncryptionAttacks

Dennis thinks that, while ODF allows for AES in CBC mode, this attack is not applicable to ODF.
On a related note, however, at least one implementation used to use Blowfish by default when encrypting ODF,
but switched to AES in more recent versions, which caused interoperability issues with older versions.
Both encryption algorithms are permitted by the ODF specification, by the way, but Blowfish is considered legacy.
Publishing an Advisory might be helpful in these cases.

* Louis asks if someone could report on FOSDEM, but no-one on the call participated in this event.

* Bart mentions that the plugfest will almost certainly take place in Lisbon, but this is still not 100% sure.
He will check with the local organizer and report on the plugfest mailing list.

* No comments or announcements from Andreas.


6. FUTURE MEETING PLANNING

The next call will be on February 20th, 14:30 UTC.


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