open alliance to network the physical world

1
open alliance to network the physical world
2 Nov. 2005 David E. Culler
2
IETF

• Mission
• produce high quality, relevant technical and
  engineering documents that influence the way
  people design, use, and manage the Internet in
  such a way as to make the Internet work better.
  These documents include protocol standards, best
  current practices, and informational documents of
  various kinds.
• Corporate Structure
• IETF WGs in Areas, Area Directors form IESG, IAB
  provides oversight, IESG and IAB are chartered by
  ISOC
• Membership
• ISOC has members, IETF has individual
  participants
• Participation
• Open process. Anyone can participate, must come
  and do work
• IP policy
• No confidential contributions.
• IP not in RFCs, avoid proprietary possible, notes
  at http//www.ietf.org/ipr.html
• Output
• RFCs, internet drafts
• Code is external. Part of building consensus
  on running code
• Compliance is delegated to the market
• Funding
• ISOC members

3
OSDL

• Mission
• To be the recognized center of gravity for Linux
  the central body dedicated to accelerating the
  use of Linux for enterprise computing through
• Enterprise-class testing and other technical
  support for the Linux development community.
• Marshalling of Linux-industry resources to focus
  investment on areas of greatest need thereby
  eliminating inhibitors to growth.
• Practical guidance to our members - vendors and
  end users alike - on working effectively with the
  Linux development community.
• Corporate Structure
• Strong BOD of corp. members, create committees
• User advisory Comm ---- Streering Comm -gt Tech
  Comm  Marketing Comm
• Projects proposed by members, approved by
  director
• Membership
• Range of paid corporate members, free non-voting
  individual, 50 members
• Participation
• Must be member, only paid vote.
• IP policy
• IP developed by OSDL employees licensed as open
  source, Members can assign IP, IP notification
• Open source license
• Output
• Code and APIs. Feed into distributions.
• Funding

4
OSGi

• Mission
• specify, create, advance, and promote an open
  service platform for the delivery and management
  of multiple applications and services to all
  types of networked devices in home, vehicle,
  mobile and other environments.
• Corporate Structure
• Non-profit, BOD, officers
• OSGi Comm Requirements Comm Marketing comm
  Expert Groups
• Membership
• Contrib (10k), full (20k), 40 members
• Participation
• Members
• IP policy
• Included in membership agreement, grant IP to
  members and affiliates
• Confidential material
• Output
• OSGi Service Platform Create a specification, a
  reference implementation and a test suite
• Companies produce and sell own implementations
• Funding
• members

5
Apache

• Mission
• provides support for the Apache community of
  open-source software projects. The Apache
  projects are characterized by a collaborative,
  consensus based development process, an open and
  pragmatic software license, and a desire to
  create high quality software that leads the way
  in its field. We consider ourselves not simply a
  group of projects sharing a server, but rather a
  community of developers and users.
• Corporate Structure
• The management of the Foundation is overseen by a
  board of directors, who are elected by the ASF
  membership
• Membership
• By invitation, individuals, not companies.
  Large.
• Participation
• Members, Meritocracy
• IP policy
• Accept contributions under Apache license, ASF
  owns code
• Output
• Collection of open source projects. Artifacts
  more than architecture
• Funding
• donations

6
Zigbee

• Mission
• Association of companies working together to
  enable reliable, cost-effective, low-power,
  wirelessly networked, monitoring and control
  products based on an open global standard.
• Define network, security, and appln software
  layers
• Providing interoperability and conformance
  testing specifications
• Promoting the ZigBee brand globally to build
  market awareness
• Managing the evolution of the technology
• Corporate Structure
• Heavy non-profit
• Membership
• Corporate, , 150 members.
• Participation
• Members only, late publication
• IP policy
• Members contribute IP, IP is made available to
  members. Complex.
• Members produce own, closed implementations
• Output
• Marketing, Specs
• Funding
• Member companies

7
WINA, Infiniband, ATM,

• Mission
• Corporate Structure
• Membership
• Participation
• IP Policy
• Output
• Funding

8
XETF (Xternet Engineering and Technology Forum)

• Mission
• Foster an open, innovative, and technically sound
  ecosystem around interconnecting the physical
  world with modern networking and information
  technology through the creation of technical
  documents, protocols, reference implementations
  and APIs.
• Corporate Structure
• Lean non-profit with BOD, steering comm,
  collection of Areas with working groups. Park
  under CNRI or some existing organization.
• Volunteer (except support staff)
• Membership
• Individual participants, corporate, academic, and
  govt supporting members
• Expect lots of academics and little start up.
• Participation
• Open. Role determined by contribution. Typical
  escalation process
• IP Policy
• Non-confidential contributions, IP disclosure
  process. IP contribution vehicle. Companies can
  develop own implementation.
• Apache-like credit (why not MPL?) BSD?
• Output
• RFC-like documents, reference implementations,
  forum for exchange and viz.
• Rough consensus AND running code
• Funding
• Member contributions, donations, govt support

9
XETF areas (proposed)

• System support
• TinyOS working group, Linux working group
• Embedded protocols
• Mesh routing, DTN
• Internet Interfaces
• Xsensor gt Xology
• Management
• Instrumentation
• Security
• Privacy
• Reliability
• Hardware Interfaces