I'm not sure about that. It's not because it's mandatory that people implement it (TLS, TCP, SIPS, to name a few). I think we need instead to explain it is necessary, and what doest it mean to various components (i.e., UACs, UASs, and Proxies).
For example: - UACs MUST support Tel URIs (and use whatever proxy they have available to route requests to Tel URIs). Example, recurse on 302. - UAs (not sure there are many problems here). - Proxies. Need to be able to route on Tel URI. If they don't recurse, need to pass 302 with Tel Contact. If they recurse, need to act on it. Also, we need to warn people on improper usages of Tel URI (stupid UA pet tricks). For example, don't use Tel URIs in Contacts other than 3XX. In other words, this is not just as simple adding "must support Tel URI" in RFC 3261. > -----Original Message----- > From: Juha Heinanen [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 15, 2008 09:39 > To: Dean Willis > Cc: Audet, Francois (SC100:3055); SIP IETF; Paul Kyzivat; Dan WING > Subject: Re: [Sip] E.164 - who owns it > > Dean Willis writes: > > > > I have no problem with us recommending Tel URI usage for > this, and > > hoping that implementations will catch-up. > > > > Same here. > > "recommending" is not enough. support for tel uris must be > made mandatory. as i said, if there is a somewhere an > rfc3261 bug list, this belongs there. > > -- juha > _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use [EMAIL PROTECTED] for questions on current sip Use [EMAIL PROTECTED] for new developments on the application of sip
