Advisory Council Briefing: IETF 74

1
Advisory Council Briefing IETF 74
Engaging with the Identity Community - or What
in the World is IDTBD?
Lucy Lynch Director for Trust and Identity
Initiatives 27 March 2009
2
T/Id A Three Program Initiative

• Identity and Trust Elevating "Identity" to a
  core issue in network research and standards
  development
• Architecture and Trust
• Implementing open trust mechanisms
  throughout the
• full cycle of Internet research,
  standardization,
• development and deployment
• Current Problems/Solutions and
  Trust Mitigating the social, policy, and
  economic factors that may hinder development
  and deployment for trust enabling technologies

3
Trust and Identity Goals

• End users understand their options for identity
  management and demand appropriate tools and
  services to support the full range of use cases.
• Developers think in terms of trust, interaction,
  and sustaining global reach (end-to-end) when
  designing the next generation of reliance
  technologies and standards.
• ISOC continues to support the open, transparent,
  bottom up nature of Internet development and is
  an active partner in the standards process as the
  Internet Model expands. ISOC is a primary
  advocate for architectural issues that support
  and increase the value of the Internet as well as
  an active promoter of "best current practices"

4
ISOC and the Identity Community

• Throughout 2008 ISOC worked to build a strong
  technical and social foundation in the identity
  sphere.
• We have partnered with Internet 2, Liberty
  Alliance/IDTBD wait, Ill get there, and the
  Identity Commons on small projects and are
  working to expand those relationships.
• This model of broad-based technical and community
  engagement will now be leveraged to support our
  consultation on User Managed Identity.

5
Engagement

• ISOC understands that our partner relationships
  are dependent on some established external
  agendas and organizations.
• We are now positioned to support these external
  efforts and can be proactive in supporting ISOC
  values such as openness and transparency.
• ISOC is still viewed as a relative newcomer to
  the space, but our interest has been welcomed.
  Our input on process related to standards, the
  Internet Model, and end-user engagement is also
  highly valued.

6
Engagement continued

• ISOC has become a recognized voice in the
  identity community, and is now well placed to
  help develop a stronger set of identity
  organizations focused on interoperability,
  transparency, and a shared framework.
• Which is why ISOC recently joined the Board of
  the Liberty Alliance for 2009.
• ... or did we?

7
Liberty Alliance is not IDTBD

• Although ISOC signed on to the Management Board,
  our LA membership will be converted to a Founding
  Member seat on the board of a proposed "NewOrg"
  ( often referred to as IDTBD).
• The new IDTBD structure is the result of a
  series of consultations across multiple sectors
  in the identity technology community.
• IDTBD meets the real need for a neutral
  consortium organization that can interface
  between identity developers and the potential
  adopters and end-users of identity solutions.

8
Quick IDTBD Backgrounder

• Liberty Alliance (LA) committed to transitioning
  it's identity activities to be more inclusive and
  open.
• LA engaged in a consultation with its members and
  other identity communities to explore the new
  structure.
• LA formed a working group with ISOC, Identity
  Commons, DataPortability Project, OpenID
  Foundation, as well as with non-LAP companies
  (e.g. Microsoft) though not all communities
  remain engaged.
• The proposed New Organization (a.k.a NewOrg)
  was codenamed IDTBD (i.e. Identity Project To Be
  Determined).
• LA plans to move most (if not all) activities to
  IDTBD

9
Just a little Identity word salad
10
Why IDTBD?

• There is no clear unified voice for Identity
• After looking at various small foundations and
  Identity Commons as well as the proposed IDTBD
  structure, IDTBD appears to the best chance of
  achieving a stable, inclusive, neutral base for
  identity technologies to address a wider
  audience.
• The core principals outlined for IDTBD are well
  aligned with ISOC values
• The Vision of NewOrg IDTBD is to ensure secure,
  identity-based, on-line interactions while
  preventing misuse of personal information so that
  networks will become privacy protecting, and more
  natively trustworthy environments.

11
And why ISOC

• Our participation will allow ISOC to help shape
  the new organization in ways that
• encourage and support new entrants, especially
  from some of the more open communities,
• shelter interesting work from small projects that
  will need access to both an organizational
  structure and funding,
• encourage and promote interoperability
• and provide a unified voice on identity questions
  from those outside the current development sphere.

12
The 2009 T/Id work plan

• A report on the Trust and Identity work plan
  for 2009 is included in the materials provided
  for the March 2009 Board of Trustees meeting and
  can be found here
• http//www.isoc.org/isoc/general/trustees/agenda-m
  ar-09.shtml
• see item VIII - Key Initiative Reviews and down
  load
• trust-identity.pdf

13
Goals for IDTBD

• Accelerate marketplace adoption through clear
  messages, defined processes, and open community
  collaboration that brings vendors, deployers,
  individuals, and organizations together to solve
  real problems.
• Bring together technical, business, legal, and
  policy experience to achieve holistic identity
  management solutions.
• Establish an open and transparent governance
  model with no financial barrier to participation.
• Implement an operational structure with nimble
  processes, procedures, and oversight, and a
  viable financial model.

• Foster positive dialogue across all relevant
  organizations to assure coordination,
  harmonization, and re-use of all applicable open
  content (specs, policy, etc.).
• Establish programs with unique brands for
  technical and operational output to promote
  interoperability, compliance and/or conformance.
• Commit to open standards and encourage
  interoperable implementations from both the
  Commercial Off-The-Shelf (COTS) product and open
  source development communities.
• From the DRAFT NewOrg Member Agreement