[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Simple] (Very) late MSRP questions, version number in request?



Ignacio Más Ivars (KI/EAB) wrote:

I have a question about MSRP that stroke me the last days while
implementing some MSRP code: SIP, HTTP and RTSP (for example) signal the
version in the header line (SIP/2.0, HTTP/1.1...) for different reasons
(compatibility and so...) Wouldn't it be a good idea to do the same with
MSRP, say 'MSRP/1.0 transactionID SEND'.


This comes up often enough that we might to add some motivating text in the document.


I'll quote Ben Campbell from a message dated 6/28/2004:

This was discussed in the working group some time back. The consensus was that there was no use for a version indicator, since MSRP would never negotiate versions.

Since MSRP is _always_ negotiated with an external signaling protocol, any version negotiation belongs there. Any version updates to MSRP must describe how to indicate the new version in the sdp exchange.


/a

_______________________________________________
Simple mailing list
Simple at ietf.org
https://www1.ietf.org/mailman/listinfo/simple