enrollment/mgt operations

[Stephen Farrell <stephen.farrell@xxxxxxxxxxxx>]

Hi All,

I'm looking through the comments we got on the requirements and
would like to get some opinions about how much detail to include
(in the requirments document) about management operations.

Right now, there's just a generic requirement that the
protocols must support mgt operations. Self-enrollment was
mentioned on the list and should at least get a mention too.

I guess the overall list of operations might be something
like:

GET      for downloads from a CS
PUT      to update/change a credential or direct transfer one
ENROLL   could be a special case of PUT?
DELETE   to zap a credential (carefully:-)

So, questions:

- Should the requirements document specify these separately, 
  each with associated MUSTs etc?
- If yes, then what other management operations might there be? 
  (e.g. do we need an interoperable form of DISABLE/ENABLE to 
  temporarily make credentials unavailable, MODIFY to change
  an existing credential...)
- Does all this just apply to the credential server case, or
  also for direct transfers?

Regards,
Stephen.

BTW: Dale and Magnus have taken on drafting a framework document
(thanks guys:-) so we should have one to discuss in San Diego if
they manage to make the cutoff.

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 647 7406
61 Fitzwilliam Lane,                    fax: +353 1 647 7499
Dublin 2.                mailto:stephen.farrell@xxxxxxxxxxxx
Ireland                             http://www.baltimore.com