|Carlisle Adams||Jan 26, 2001 8:58 am|
|Jeremy Epstein||Jan 26, 2001 9:09 am|
|Geor...@tivoli.com||Jan 26, 2001 9:19 am|
|Orchard, David||Jan 26, 2001 9:24 am|
|Orchard, David||Jan 26, 2001 9:29 am|
|Alex Berson||Jan 26, 2001 10:15 am|
|Philip Hallam-Baker||Jan 26, 2001 10:16 am|
|Eric Olden||Jan 26, 2001 10:57 am|
|Geor...@tivoli.com||Jan 26, 2001 11:27 am|
|Chanliau, Marc||Jan 26, 2001 12:16 pm|
|Subject:||RE: New Name ! (A new suggestion)|
|From:||Alex Berson (Alex...@entrust.com)|
|Date:||Jan 26, 2001 10:15:12 am|
Title: RE: New Name ! (A new suggestion)
Great suggestion, Carlisle!
Of course, this name may invite shorter derivatives, for example, eXtensible Credentials Exchange Specification, or XCES (pronounced "excess"?!), but you can not beat the phonetics of "access" in AXCES.
Alex Berson VP / CTO Portal Technologies & Applications Entrust Technologies CA Office: 408-222-7800 ext 7725 NYC Office: 646-495-5097 Direct: 732-967-9188 Fax: 732-390-5784 Mobile: 732-991-1850 Alex...@entrust.com
-----Original Message----- From: Carlisle Adams [mailto:carl...@entrust.com] Sent: Friday, January 26, 2001 11:53 AM To: secu...@lists.oasis-open.org; 'Eve L. Maler' Subject: RE: New Name ! (A new suggestion)
I believe that the group has (rough) consensus that "S2ML" should be changed as the overall name of this OASIS TC spec because "Security Services" is too broad. I, for one, would not want to be in the shoes of the PR spokesperson (currently Eve!) trying to explain to some analyst or press representative why XKMS -- which is clear a security service -- is not within the scope of this TC.
Perhaps not surprisingly, I have no objections to "A2ML", but I can understand the hesitation on the part of some who either feel that "Authentication" implies too much, or that "Authentication and Authorization" may be too narrow in scope.
Therefore, I will offer another name for consideration (if only so that we have some competition for SEX-ML!). It seems to me that what this group would like to do is create a specification for the exchange of credentials. These credentials (today covering both authentication credentials and authorization credentials, but open in the future to other kinds of credentials that we may choose to embrace) will be expressed in XML. Furthermore, I think it is fair to say that the payload to be exchanged will always include at least one "active" -- that is, currently valid -- credential (name assertion, entitlement assertion, whatever).
Thus, my suggestion is: "Active XML Credentials Exchange Specification", which has the intuitive and somewhat appropriate acronym "AXCES" (pronounced "access").