[Sipping] Do we have a problem with History-Info and tel: URI?

[Dean Willis <[e-mail]>]

This item from the thread on retargeting and Reason header usage just  
caught my eye:

On Oct 11, 2005, at 10:59 AM, Elwell, John wrote:

> Paul said:
>>
>> One issue with the uri parameter approach is: what if the new
>> target is
>> not a sip-uri? It could easily be a tel: uri - there are quite
>> reasonable use cases for that. It could also potentially be an IM: or
>> PRES: uri. And in the case of 3xx responses it can be any
>> kind of URI -
>> even http. At best the rules for affixing parameters can vary by URI
>> scheme, and at worst some schemes may not allow it.
>>
> URI excepted, this limitation applies also to the Reason header
> approach, since that relies on the header being placed in a History- 
> Info
> header in the retargeted or recursed SIP request. But your point  
> about the
> tel: URI is valid.


I'm thinking that the generalized usage of the History-Info header  
for telephone services (like some of the TISPAN discussion usage)  
depends on using tel: URIs in requests.

But if I read this right, we really can't put the Reason header into  
a History-Info which uses a tel: URI.

Do we have a major problem here? Or am I just missing something?

Thanks,

--
Dean 

_______________________________________________
Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [e-mail] for questions on current sip
Use [e-mail] for new developments of core SIP