Re: Tel URI query

Iñaki Baz Castillo <[email protected]>
Newsgroups gmane.ietf.sip-implementors,gmane.ietf.sip
Message-ID <[email protected]>
2009/3/2 harbhanu <[email protected]>:
> I actually wanted to use +3314529!****! as example.
> But then as per your interpretation too it's not allowed.

Sure it's not allowed per RFC 3966 BNF syntax rules.


> TISPAN 182 025: [Section 6.1.2 Identification]
>             The wildcarded public user identity consists of a delimited
> regular expression located in the telephone-subscriber portion of a tel URI
> (e.g.         tel: +3314529!****!) or in the user portion of a SIP URI (e.g.
> sip:*@example.com).

This is annoying. It means that this specification violates the
grammar specified in RFC 3966. Theorically RFC 3966 is just updated by
RFC 5341. Sincerelly I can't understand how the above spec can
requiere such aberration in Tel URI.


> So do we have any parallel draft in IETF to apply these modification to Tel
> Uri ??
> How are we supposed to handle scenarios like this ?

Sorry, no idea, this is really confusing. Do people writting
specifications really want TEL URI to be usable??



-- 
Iñaki Baz Castillo
<[email protected]>

_______________________________________________
Sip-implementors mailing list
[email protected]
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.