> -----Original Message----- > From: Robert Sparks [mailto:[EMAIL PROTECTED] > Sent: Friday, October 26, 2007 11:48 > To: Audet, Francois (SC100:3055) > Cc: Dean Willis; Sanjay Sinha (sanjsinh); sip List; Adam Roach > Subject: Re: [Sip] INFO: A recap, sense of consensus and a > proposal for direction. > > So, the thing we're talking about then is not a subscription. > (You will not use the same code to service it that you would > have used to service a subcription).
Fair enough. > And if you accept that the fates are tightly coupled (as I > think you are asserting here), then we _don't_ have separate > usages that spring into being and disappear at the same time. > There's only one usage - the INVITE usage. Agree. > And forgive me for continuing to point, but are you going to > address the authorization mechanics and if not, what are the > simplifying assumptions that let us ignore them. I don't know. Again, I'm not the one pushing for this :^) _______________________________________________ Sip mailing list https://www1.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
