Re: [security-services] Discussion of Future Work of the SSTC

[Greg Whitehead <greg.whitehead@hp.com>]

I would also like to understand, under Oasis rules, how the ongoing
maintenance of actively used specifications is expected to happen. In
particular, who would manage the errata process if we disbanded?

Given that SAML is a core security specification it seems especially
important to ensure that a group of knowledgeable people are available to
evaluate issues as they arise and recommend solutions that maintain (or in
the worst case restore) the integrity of the protocols.

-Greg


On 7/27/06 9:04 AM, "Hal Lockhart" <hlockhar@bea.com> wrote:

> On the last call it was rightly noted that to determine what charter the
> SSTC should have and even if it should continue beyond April 2007, we
> need to identify the work to be done. This email is intended to
> stimulate discussion on this topic.
> 
> Obviously Errata will continue to accumulate against the current
> Standards. However I do not think errata publication alone is a
> sufficient reason for a TC to exist.
> 
> I am aware of the following proposed items. Please add to this list.
> 
> The five items which just finished public review:
> 
> - Metadata Profile for the OASIS Security Assertion Markup Language
> (SAML)
> - SAML Attribute Sharing Profile for X.509 Authentication-Based Systems
> - SAML XPath Attribute Profile
> - SAML Metadata Extension for Query Requesters
> - SAML Protocol Extension for Third-Party Requests
> 
> The shared credentials work:
> 
> - SharedCredential Authn Context Extension
> - RequestedAuthnContexts Extension proposal
> 
> Other:
> 
> - Technical Overview
> - "New" LDAP/X.509 Profile
> - Profile of WS-SecurityPolicy to describe SAML Assertions (Tokens)
> 
> Hal
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>