Re: [Isms] tmsm issue #5: session table (p39)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Isms] tmsm issue #5: session table (p39)



Hi -

> From: "Juergen Schoenwaelder" <j.schoenwaelder at iu-bremen.de>
> To: <isms at ietf.org>
> Sent: Wednesday, May 17, 2006 11:58 AM
> Subject: [Isms] tmsm issue #5: session table (p39)
>
> tmsm issue #5: session table (p39)
> 
>   Should it be possible for a manager to create or modify rows in the
>   session table?  If so, then we may need the rowstatus object.  If
>   the session table is read-only then we can probably eliminate the
>   rowstatus.  If the tabel is not read-only, then we need to list the
>   tables and objects and state why they are sensitive.
> 
>   -> strawman: the session table is read-only
...

The only reasons I can think for having a session table visible to
management are:
    - to monitor who is accessing a system at the moment
    - to provide a way for an administrator to terminate other sessions
    - for debugging

None of these seems very persuasive to me.  I suggest eliminating
the table.

Randy


_______________________________________________
Isms mailing list
Isms at lists.ietf.org
https://www1.ietf.org/mailman/listinfo/isms




Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.