About Us
 Working Groups
 How to Join
 Email Reflector
 Ref Implement
 Contributions  Test
 Conference Calls
 Next Meeting
 Past Meetings
 Press Releases


The DAT Collaborative was formed to define and standardize a transport-independent and OS-independent set of APIs that exploit RDMA capabilities such as those present in IB and VI.

DAT Collaborative Objectives:
  • Transport independence (VI, IB, iWARP)
  • Platform (OS) independence
  • Improve performance and ease of use for NFS-RDMA, sockets, databases, HPC, clusters, and other data center applications
  • Define user- (uDAPL) and kernel-level (kDAPL) APIs
  • Promote DAT implementation adoption by Linux and other OS vendors
  • Consider extensions beyond current functionality provided by VI, IB and iWARP
  • Encourage the development of open source reference implementations and validation suites
  • Track and adopt developments at RDMA transport standards
  • Promote application level interoperability
Initial objective: produce kDAPL definition and specification

DAT Collaborative Structure:
  • Lightweight, low overhead
  • No promoters
  • No sponsors
  • Members have all the rights of promoters and sponsors
  • Any member can publish, add, modify, and bring forward anyone's contributions to any standards body
Voting Rules
For issues requiring a vote, the following rules will apply:
  • One vote per member, as identified by a signed contributor's agreement
  • A member is considered in good standing:
    • initially, when the member signs the contributor's agreement
    • continuously, until member participation has lapsed for 2 consecutive meetings
    • again (reinstated) at the second consecutive meeting that they participate in
  • Any member in good standing can call for a vote of a written proposal at a meeting
  • Meetings must be announced on the reflector at least 1 week in advance
  • A good faith effort will be made to announce significant votes 1 week in advance
  • A quorum will be established if 40% of the members in good standing are participating in person at a meeting, over the phone bridge, or electronically, in a vote
  • A vote is decided when the number of affirmative or negative votes is greater than the number of opposite votes, when a quorum is participating in a vote
  • Any changes to these voting rules will require the approval of at least 60% of the members in good standing
  • A vote is concluded when all members participating in a meeting have voted or abstained, or if so indicated when the vote was called, on the seventh calendar day after the vote was called