Re: INFO Framework - to send-info or not to send-info

Hi, 

>1. Remove Send-Info. It takes away a bunch of race conditions. The
value of having it is theoretical. We can always add 
>it in later, so we will keep the header name "Recv-Info".

Could someone explain those race conditions to me, or point to a thread
where they are described?

In SDP o/a, for example, I think the advantages of being able to better
describe also what-I-can-send capabilities would be more than
theoretical.

If we don't want to use two headers, we can of course have a single
header with direction parameters.

E.g; Info-Package: dtmf-package;sendonly, isup-package;sendrecv

I think we have historical examples on when adding restrictions,
withoout any really good reason, later causes problems.

Regards,

Christer

_______________________________________________
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