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

[Robert Sparks <rjsparks at nostrum.com>]

Hello Ignacio,

This topic has been extensively discussed in the past.

MSRP is never used without an encompassing signaling protocol. The base
doc puts requirements on such a signaling protocol, one of which is  
to have
sufficient feature negotiation capability to deal with future changes  
that are
not backward compatible:

      The rendezvous mechanism MUST provide mechanisms for the
      negotiation of any supported MSRP extensions that are not
      backwards compatible.

RjS

On Nov 11, 2005, at 11:52 AM, Ignacio Más Ivars (KI/EAB) wrote:

> Hi folks,
>
> 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'. I think it would ease  
> upgrading
> MSRP if need be in the future. Has it been discussed before? Does it
> make sense?
>
> Thanks!
> /Ignacio
>
>
> --
> Ignacio Más Ivars
> Service enablers and protocols, Ericsson Research (EAB/TBG/B)
> Ericsson AB                     Phone: +46 8 4045580
> Torshamsgatan 23                Fax:   +46 8 4049500
> SE-164 80 Stockholm, Sweden     mailto: ignacio.mas.ivars at ericsson.com
>
> _______________________________________________
> Simple mailing list
> Simple at ietf.org
> https://www1.ietf.org/mailman/listinfo/simple


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