Hadriel Kaplan writes: > Openser will send back a CRLF when it gets a CRLF? Interesting, but > it's proprietary. There is nothing in SIP to say "send back a CRLF > when you get a CRLF". This draft is proposing a standardized way to > do that, for both transport types.
openser will send back back single CRLF later this week, it it receives double CRLF over tcp connection. i have not claimed that this practise has been standardized somewhere. the behavior is simply implemented, because several sip UAs, for example, all nokia ones, do send double-CRLFs without any negotiation if they are behind nats. as i have told, i don't see any reason to negotiate this behavior at least when UA is using tcp. > See my other email - it was what I meant - not getting the keep=yes > means the other end doesn't support this draft. this is what you say now, not what you said yesterday. as i said in my previous posts, what you say now is fine with me as long as the draft clearly says that if UA does not get back keep=yes, then this draft does not specify what the UA should do. this allow current products keep on working without this (at least in tcp case) useless negotiation stuff that the draft is proposing. -- juha _______________________________________________ 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
