RE: Session Management Use case, scenario and issues

["Orchard, David" <dorchard@jamcracker.com>]

Darren,

Thanks for the quick review.  I will take your comments and send out an
updated document.  I hope to do that by end of day Saturday or Sunday, but I
can make no promises for work time on the weekend especially with leaving
for 2 weeks of travel on Sunday :-)

I purposefully redid the issue numbers on the assumption that the whole doc
would be cut 'n pasted into the issues doc, thus replacing the existant
issue #s.  We had discussed no issues on session management above and beyond
the first one, so I didn't think re-ording was an issue (so to speak).  

One of the issues (#4 I think) didn't appear relevent to session management,
so it was indeed removed.  Good catch, I suggest that it be placed
elsewhere.

I also did my own cut at the "FirstContact" issue into here, with some
additional verbage.  It seems closely related to session management so I
copied it in here.  Where it seems to fit is on the notion that the
destination web site is the first point of contact, and has to request the
source to create the session.  I can also see(?understand) an argument along
the lines that firstContact is dependent on sign-on, not session.  I'm
comfortable either way, you decide.  If you choose to keep it where it is,
then my wording can be interpreted as suggested additional wording.

Cheers,
Dave

> -----Original Message-----
> From: Darren Platt [mailto:dplatt@securant.com]
> Sent: Friday, February 16, 2001 2:12 PM
> To: Orchard, David; UseCaseList
> Subject: RE: Session Management Use case, scenario and issues
> 
> 
> Thanks, David.
> 
> My specific comments are inline in blue text in the attached 
> doc.  Here are
> my hi-level comments:
> 	- There are issues that are on the issue list that are 
> not in your doc.
> 	- The issue numbering is inconsistent with the 
> numbering in the issues doc.
> That will cause confusion.  What may happen is that as you 
> investigate this
> issue group, you discover additional issues, which should be 
> added to the
> end of the list.  Propose resolution text for voting for 
> these new issues as
> well if you can.  If we are unable to resolve them via vote, 
> they will be
> added to the issue list of the next strawman.
> 	- We need to propose resolutions which can be voted on 
> for each issue.
> 
> Regards,
> 
> Darren
> 
> 
> 
> > -----Original Message-----
> > From: Orchard, David [mailto:dorchard@jamcracker.com]
> > Sent: Thursday, February 15, 2001 5:36 PM
> > To: 'security-use@lists.oasis-open.org'
> > Subject: Session Management Use case, scenario and issues
> >
> >
> > Apologies for the slight delay, here is what I have been 
> able to come up
> > with.
> >
> >
> >
> > Dave Orchard
> > XML Architect
> > Jamcracker Inc.,    19000 Homestead Dr., Cupertino, CA 95014
> > p: 408.864.5118     m: 604.908.8425    f: 408.725.4310
> >
> > Named to Red Herring's list of 100 Most Important Companies:
> > www.redherring.com/mag/issue79/herring100/jamcracker.html
> >
> >
>