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


Help: OASIS Mailing Lists Help | MarkMail Help

security-services message

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

Subject: RE: Issue "states"? (was: [security-services] Updated Issues List )


I noticed that the Issue:[UC-2-05] pertaining to B2B 
authentication is currently has Status: 
	"Voted, No conclusion".

This issue/requirement was a close one: I believe with 
7 voting for inclusion, and 4 for not including. Since 
this issue implied a SAML object model requirement for
support of an extensible application level Credential, 
which we decided not to support in SAML 1.0, I propose 
that we classify this issue:2-05 as deferred.

Furthermore, in retrospect, I would have liked to have
characterized this issue as an A2A (application to application)
authenticted message exchange issue since that is one 
of the intents of the use case description included
in the issue 2-05. I rather not close the issue and see
the implied requirements get lost in the future.

Please clarify if my understanding of the status is 


-----Original Message-----
From: Jeff Hodges [mailto:jhodges@oblix.com]
Sent: Friday, January 18, 2002 3:22 PM
To: security-services@lists.oasis-open.org
Subject: Issue "states"? (was: [security-services] Updated Issues List)

Presently the issues-07 doc employs two states for issues: open or closed. 

We've danced around the topic of issue "states" on concalls, and a notion of
"deferred" has been at least mentioned. 

So, folding "deferred" in with "open" and "closed", what do folks,
Hal, think of these issue state semantics..

  open: the issue's been at least raised. the one raising it is nominal
        unless the mantle is passed (e.g. by someone volunteering and/or the
        tugging sleeves). 

  closed: as Hal puts it "we're never going to talk about it anymore". 

  deferred: we're not going to address this issue in the present in-process
            specification version, but we want to keep the issue around for 
            consideration in future versions. The champion is preserved, and

            can be changed in the same manner as open issues. 


So, for example, there's likely at least a few issues in issues-07 that we
ought to "defer" rather than simply "close". 

And we want to move open issues to either "closed" or "deferred" because we
need to not have any open issues in order to enter Last Call. 



To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

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

Powered by eList eXpress LLC