This is not to say that the IETF could play a useful and essential role. We can certainly develop and define the requirements, use cases etc.
In addition the IETF can architect a solution but experience tells me that deployment and implementation issues surrounding e164 issues will need the cooperation of "other bodies" which is where the problem lies. It's not really the ITU, in fact the ITU is a much easier place to get things done these days. The complications arise with the ITU member states, who jealously guard their diplomatic and political prerogatives. This was the conclusion that we drew when the Infrastructure ENUM issues first arose. We essentially said ..."Here is this problem, this is what we (IETF) think, the solution is in your court. Have a nice day." > -----Original Message----- > From: Hannes Tschofenig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, February 19, 2008 10:49 AM > To: Richard Shockey > Cc: 'IETF SIP List'; [EMAIL PROTECTED] > Subject: Re: Infrastructure issues involving e164 numbers > > > > If there is going to be a solution to the SIP identity problem > involving > > e164 numbers, it will not IMHO be solved in the IETF. > > > > > Interesting view. I obviously does not appear to be an easy thing; > in the draft I called this "There is non-neglectable deployment > incentive challenge." _______________________________________________ Sip mailing list http://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
