Hadriel Kaplan wrote:
>
>> The key point here is that NOTIFY will inherently
be associated with an
>> event package, which provides enough information
for the recipient to
>> know what to do with the body. INFO, lacking such
information, is
>> ambiguous. And, as before, the hardest problem
isn't interpreting what
>> is sent to you; it is indicating what *can* be sent
to you.
>>
>
> Sure, but we could (if we had to) define the same
concept for INFO as
> sub-not has in that regard.
>
Which is what. I've been saying. This. Whole. Time.
Perhaps the confusion here arises because I've _also_ been
pointing out
why this is Bad Idea for a _different_ set of reasons (which
are
admittedly more philosophical than practical), but at least
it makes the
INFO situation tenable.
/a
_______________________________________________
Sip mailing list https://ww
w1.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 sippingietf.org for new developments on the application of
sip
|
