Re: INFO Framework - one pakage per INFO

Dean Willis <[email protected]>
Newsgroups gmane.ietf.sip
Message-ID <[email protected]>
Anders Kristensen wrote:
> 
> 
> Dean Willis wrote:
>> Anders Kristensen wrote:
>>
>>> I think we're talking past each other. The problem is not correlating to
>>> the dialog, it's correlating the app-level response to a particular
>>> app-level request within a given dialog.
>>
>>
>> Use a transaction-correlation ID in your application-level protocol
>> (i.e, in the package specification) if you need this sort of function.
>> It's not SIP's problem.
> 
> I don't think I'm trying to make it "SIP's problem".
> 
> I'm arguing that if a response is needed it's much simpler and just all
> around better to do the response-to-request correlation by sending the
> app-level response in the 200 response to INFO as opposed to sending it
> in a separate INFO going in the opposite direction. It doesn't violate
> layering and I haven't heard of any real problem with it.

It means that the stack can't send a 200 response to INFO until it has
been directed to by the application. That seems like a layering problem
to me, not to mention a major stack rewrite.

--
Dean
_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.