Re: [radext] Help with diameter considerations for draft-hartman-radext-bigger-packets

Hi Jouni,

RADIUS - Diameter interworking is important for fmc (fixed mobile
convergence), as you know the fixed network uses RADIUS and 3GPP uses
Diameter. So for example when authenticating UE when connected via Wi-Fi to
a fixed broadband network, this interworking is needed.

Regards,

Behcet

On Wed, Feb 12, 2014 at 2:58 PM, Jouni <jouni.nospam@gmail.com> wrote:

>
> One serious suggestion is just dropping the Diameter considerations
> unless you really insist doing one. We have not required one for some
> time already and that has not been an issue during the publication
> process.
>
> - Jouni
>
>
> On Feb 12, 2014, at 10:52 PM, Sam Hartman wrote:
>
> >
> >
> > Hi folks.  I could use some help with the diameter considerations
> > section for draft-hartman-radext-bigger-packets.
> >
> > First, what value should  a proxy forwarding from a diameter client to a
> > radius server include for the maximum-response-length attribute?
> >
> > When forwarding from radius towards a diameter server, what should
> > happen with regard to the maximum-response-length attribute:
> >
> > * Strip it as diameter doesn't expect it
> >
> > * Keep it if present.  Perhaps diameter will trim down its response
> >
> > * Insert it  if the transport in the radius direction is UDP--after all,
> >  might as well let diameter know what's going on.
> >
> > Another thing to consider here is interactions with
> > radius-diameter-radius situations.
> >
> > --Sam
> >
> > _______________________________________________
> > radext mailing list
> > radext@ietf.org
> > https://www.ietf.org/mailman/listinfo/radext
>
> _______________________________________________
> radext mailing list
> radext@ietf.org
> https://www.ietf.org/mailman/listinfo/radext
>