RE: [Sip] INFO considered harmful

["Dean Willis" <dean.willis@softarmor.com>]

> The big huge difference I have been trying to point out is 
> that EVENTS 
> DEFINES SEMANTICS, whereas INFO doesn't.

No, EVENTS doesn't define semantics. Event PACKAGES define the semantics of
particular instances of the event methods. All that 3265 gives us is
subscription to and notification of otherwise undefined blobs, and a
framework for defining event packages. It is up to a specific event package
to define a specific blob, including how it is named, how it is encoded, and
what it means. And one of the interesting things is that 3265 and sipchange
establishes a lower threshold-of-review over event packages (which are NOT
considered protocol extensions) than for new SIP methods (which obviously
ARE protocol extensions).

INFO also needs a blob-describing-and-encoding framework, so that the
various uses of INFO can, as appropriate, be effectively documented and
negotiated. 


--
Dean

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@cs.columbia.edu for questions on current sip
Use sipping@ietf.org for new developments on the application of sip