> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Dean Willis > Sent: 17 July 2008 20:03 > To: Tschofenig, Hannes (NSN - FI/Espoo) > Cc: SIP IETF; Cullen Jennings > Subject: [Sip] saml proposal > > > On Jul 17, 2008, at 1:50 PM, Tschofenig, Hannes (NSN - > FI/Espoo) wrote: > > > > > If I ignore the ongoing SIP Identity discussions then I > could finish > > the > > document next week. > > > > > Would it be reasonable to write the SAML doc against RFC 4474, > documenting the issues with RFC 4474 that you've raised, and then > publish as experimental? Then if we ever get Identity > revised, we can > come back to the SAML document. And it gets one more thing off our > plate for now. [JRE] Sounds reasonable. I know SAML is becoming important in the applications world and it seems very likely that integration with SIP will become important sometime in the future. However, I don't see the drivers at present.
> > And I'd still like to have a SAML tutorial. We've had lunchtime > tutorials on things like XCAP in the past that were well > attended. All > we need is a sponsor (asking people to pay for buffet lunch doesn't > work) or a facility that is amenable to "brown bag" lunches in a > conference room. And of course, we need somebody to organize and > present said material . . . [JRE] I would try to attend such a session. One thing I am missing from the draft is a set of real life use cases - I guess these were in RFC 4484, but something to link the two together would be good, i.e., how exactly SIP/SAML would operate to solve each of these. Maybe it is just me, but if you were to explain that in a tutorial it would be helpful. John _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
