I think that we should not go with any of these for this release, but just note that we plan to deprecate these in next release and that these are still required algorithms for this release along with the new ones
Anthony Nadalin | Work 512.838.0085 | Cell 512.289.4122
Bill Parducci ---01/29/2009 11:17:08 AM---This appears to be what the IETF defines in this area:
From:
Bill Parducci <>
To:
XACML TC <>
Date:
01/29/2009 11:17 AM
Subject:
[xacml] deprecation
This appears to be what the IETF defines in this area:
/*
If a definition is "deprecated" then it simply means that it's no
longer of major importance...and need not be implemented except for
backwards compatibility with older agents that do implement them. It
also means that at some point in the future those definitions may have
replacements and the old definitions will be made "obsolete".
If it's "obsolete" then it usually means that are new definitions that
replace the old ones and the new ones should be used in any new
implementation (and, if possible, old implementations should be
brought in line with the new definitions).
*/
...my thinking is that whichever way we go we will need to have
explicit definition within our spec that defines those things being
teed up for replacement and those that are no longer valid.
b
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
