Re: [Sip] Re: [Simple] -05 MESSAGE and Expires header

[Ben Campbell <bcampbell@dynamicsoft.com>]

Vijay K. Gurbani wrote:
> Adam Roach wrote:
> 
>>> -----Original Message-----
>>> From: Vijay K. Gurbani [mailto:vkg@lucent.com]
>>>
>>> Adam has proposed the 'Urgency' header
>>
>>
>> No, I didn't.
> 
> 
> Okay; my apologies.  I did detect the irony, but absent a face-
> to-face conversation, I wasn't sure if you were being serious or
> flippant.  Glad to know we won't be making up a new header.
> 
>> I attempted to outline that what we're talking about isn't
>> priority in any sense of the word.
>>
>> We're talking about urgency.
> 
> 
> If I may, I think we are imparting urgency to an IM based on the
> *content* of the IM.  In other words, to use one of your examples:
> 
>> High Priority, Low Urgency:
>>   Note to new residents: failure to file income taxes by April
>>   15th can lead to substantial penalties.
> 
> 
> Absence other information (like the date that this IM was sent),
> urgency is meaningless.  For example, if this IM was sent on April
> 14th, I would think that it would be classified with high urgency.
> If, OTOH, it was sent on April 16th, its urgency is extremely low.
> And a relay should not be put in position to use many heuristics
> for figuring out which IMs should get immediate attention.
> 

OK, let me extend Adam's example: The message is sent on March 15. It 
has high priority, but low urgency. (And I assume that Adam was not 
suggesting that the relay understand the content of the note to 
determine urgency and priority--he was simply suggesting a situation 
where a sender might mark the message as high priority but low urgency.)


>> My argument remains that "Expires" is the most appropriate
>> header for this purpose.
> 
> 
> Right; I see I haven't convinced you yet :-)
> 
> - vijay




_______________________________________________
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