Re: FYI: RADIUS & SIP

Hmmm -- I thought my insight could be still useful :-)
In fact, my email client has chosen to send out some unsent
historicla emails after crash and reindexing. Sorry for
this quite late email :-)

-jiri

[email protected] wrote:
> Jiri,
> 
> I don't understand what is the message of your e-mail. I wrote this
> e-mail 2003. It's 6 years ago...
> 
> Laura
> 
> 
> 
> 
>> -----Original Message-----
>> From: [email protected] 
>> [mailto:[email protected]] On Behalf Of Jiri Kuthan
>> Sent: Sunday, July 19, 2009 10:19 PM
>> To: Liess, Laura
>> Cc: Dumler, Alexander; [email protected]; [email protected]; 
>> Wolff, Christian
>> Subject: Re: [Sipping] FYI: RADIUS & SIP
>>
>> to my best knowledge, iptel.org SIP Express Router's radius 
>> implementation
>> is quite widely used. We don't trace the use though.
>>
>> -jiri
>>
>> Liess, Laura wrote:
>>> I think most carriers currently use some kind of RADIUS 
>> platform to do 
>>> user authentication and they would like to reuse it in the 
>> future to 
>>> authenticate their SIP customers. My colleagues who are 
>> responsible for 
>>> the RADIUS Platform of the Deutsche Telekom (CC)are currently on 
>>> vacation so I could not check with them now about how to 
>> answer this 
>>> mail, but we already talked about this issue a number of 
>> times and my 
>>> strong opinion is that "yes, Deutsche Telekom cares a lot 
>> about SIP and 
>>> RADIUS". Reusing the existing RADIUS platform for SIP 
>> authentication is 
>>> a strong requirement for the development of SIP services within the 
>>> Deutsche Telekom. 
>>> Laura (T-Systems/Deutsche Telekom Group) 
>>>
>>>> -----Ursprungliche Nachricht-----
>>>> Von: Henning Schulzrinne [mailto:[email protected]]
>>>> Gesendet: Freitag, 18. Juli 2003 09:45
>>>> An: [email protected]
>>>> Betreff: [Sipping] FYI: RADIUS & SIP
>>>>
>>>>
>>>> Bernard Aboba <[email protected]> would like to know 
>> about people 
>>>> and companies that care about SIP and RADIUS (for authentication). 
>>>> There is an attempt afoot to rationalize RADIUS-related 
>> efforts within 
>>>> the IETF, but there seems to be a lack of representation from SIP 
>>>> folks, as per the note to the radius-authors mailing list:
>>>>
>>>> "I was not clear about the need for SIP/RADIUS work. 
>> Apparently there is
>>>> ongoing deployment of I-Ds (e.g. the Sterman draft on 
>> RADIUS attributes
>>>> for HTTP Digest Authentication), so perhaps 
>> standardization would be
>>>> valuable in documenting what is in use. On the other hand, I also 
>>>> heard that "there
>>>> isn't much commercial interest." Note sure what to make of 
>> this, perhaps
>>>> someone can clarify."
>>>>
>>>> Henning
>>>>
>>>>
>>>> _______________________________________________
>>>> Sipping mailing list  
>> https://www1.ietf.org/mailman/listinfo/sipping
>>>> This list is for NEW development of the application of SIP
>>>> Use [email protected] for questions on current sip
>>>> Use [email protected] for new developments of core SIP
>>>>
>>> _______________________________________________
>>> Sipping mailing list  https://www1.ietf.org/mailman/listinfo/sipping
>>> This list is for NEW development of the application of SIP
>>> Use [email protected] for questions on current sip
>>> Use [email protected] for new developments of core SIP
>> _______________________________________________
>> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
>> This list is for NEW development of the application of SIP
>> Use [email protected] for questions on current sip
>> Use [email protected] for new developments of core SIP
>>
> 
_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP