I'd start by asking the author of 3265 if he thinks its a bug.
(That isn't definitive, but its a good start.)
If so, it might just be recorded as a bug and fixed the next time an
update is done to 3265.
If it is more controversial, then it will be a pain in the ass.
Thanks,
Paul
Klaus Darilion wrote:
>
> Paul Kyzivat schrieb:
>> Iñaki Baz Castillo wrote:
>>> 2008/10/22 Iñaki Baz Castillo <[EMAIL PROTECTED]>:
>>>> Hi, SIP Presence Event Package RFC( 3856 ) says that From and To of a
>>>> SUBSCRIBE cannot be a TEL URI:
>>>>
>>>> Section 5.
>>>>
>>>> SUBSCRIBE messages also contain logical identifiers that define the
>>>> originator and recipient of the subscription (the To and From header
>>>> fields). These headers can take either a pres or SIP URI.
>>>>
>>>>
>>>> Why? Why is valid a PRES URI but not a TEL?
>> I can think of no reason why a TEL should not be permitted. Presumably
>> it would be routed the same way an INVITE would. Eventually that should
>> lead to some UA, perhaps a GW, perhaps a native sip device. Either way
>> the SUBSCRIBE *might* be supported. If the subscribe isn't supported
>> then an error is reported.
>>
>> So I consider this a bug in the spec.
>
> So, what would be the next step to solve this issue? A new RFC?
>
> thanks
> Klaus
> _______________________________________________
> Sip-implementors mailing list
> Sip-implementors@lists.cs.columbia.edu
> https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
