[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: draft-chiba compatibility with Diameter review of Chiba 19
Yes!
> -----Original Message-----
> From: Murtaza S. Chiba [mailto:mchiba@cisco.com]
> Sent: May 13, 2003 4:42 PM
> To: Bernard Aboba
> Cc: Avi Lior; 'aaa-wg@ietf.org'; 'gdommety@cisco.com';
> 'meklund@cisco.com'; 'david@mitton.com'; 'iesg@ietf.org';
> 'jari.arkko@piuha.net'
> Subject: Re: draft-chiba compatibility with Diameter review
> of Chiba 19
>
>
>
> Hi ALl,
> If I understand this correctly the Authorize-Only
> triggers the NAS to
> send an Access-Request (after the NAK). Since, username contains
> domain, this is not enough as a domain could have multiple
> servers for
> redundancy and this request needs to go back to a particular
> server(?)
> and hence we need the State attribute?
>
> Thanks,
> Murtaza
>
> Bernard Aboba wrote:
> > The draft has been revised to support the State attribute as Avi
> > indicates below. -19 has now been submitted to the IETF
> archive. Until
> > it shows up, it is available at it:
> >
> >
> http://www.drizzle.com/~aboba/IEEE/draft-> chiba-radius-dynamic-authoriz
> > ation-19.txt
> >
> > On Tue, 13 May 2003, Avi Lior wrote:
> >
> >
> >>Hi All,
> >>
> >>I reviewed Chiba 19 and have one issue relating to routing. The
> >>originator, the entity that wants to make the change may not be the
> >>same entity that would receive the Authorize only message. State
> >>could be used to help the RADIUS route the message to the
> destination.
> >>
> >>Otherwise, all looks okay.
> >
> >
>
>
Bridgewater Systems Hosts a 4-city Wi-Fi Forum for Service Providers May 7-14, 2003
To learn more about the event and to register please visit: http://www.bridgewatersystems.com/forum