[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency

To: "Beck01, Wolfgang" <BeckW@t-systems.com>
Subject: Re: AW: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
From: Bernard Aboba <aboba@internaut.com>
Date: Wed, 23 Mar 2005 04:54:29 -0800 (PST)
Cc: Miguel.An.Garcia@nokia.com, radiusext@ops.ietf.org
In-reply-to: <76C27E1CE3FFC847B4D51C645D6F42AA15FE91@E9JDF.mgb01.telekom.de>
References: <76C27E1CE3FFC847B4D51C645D6F42AA15FE91@E9JDF.mgb01.telekom.de>

> I don't think it is a big problem. If you have a RADIUS client and
> Diamter server, configure the RADIUS client to obtain the nonces
> from the server. If you have a Diameter client and a RADIUS server,
> configure your server to provide nonces.

In practice, this won't work because Diameter and RADIUS are inter-domain
protocols.  If a SIP proxy *somewhere* in the system is generating nonces,
it may not be possible to force it to reconfigure.

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>

Follow-Ups:
- Re: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
  - From: Jari Arkko <jari.arkko@piuha.net>

References:
- AW: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
  - From: "Beck01, Wolfgang" <BeckW@t-systems.com>

Prev by Date: Re: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.txt, Diameter dependency
Next by Date: Re: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
Previous by thread: AW: AW: AW: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
Next by thread: Re: [Issue] Review of draft-ietf-radext-digest-auth-01.tx t, Diameter dependency
Index(es):
- Date
- Thread