RE: review of draft-ietf-radext-ieee802-01.txt

["Congdon, Paul T (ProCurve)" <paul.congdon@hp.com>]

Sounds good to me...  We'll put it in the next draft.

> -----Original Message-----
> From: jouni.korhonen@teliasonera.com 
> [mailto:jouni.korhonen@teliasonera.com] 
> Sent: Tuesday, January 31, 2006 4:39 AM
> To: Congdon, Paul T (ProCurve); radiusext@ops.ietf.org
> Subject: RE: review of draft-ietf-radext-ieee802-01.txt
> 
> > Good point.  The redir-cnt approach is somewhat different 
> because it 
> > is set-up at the beginning of the session rather than removing the 
> > redirection explicitly mid-stream.  We should say something about 
> > redir-cnt here though...  How about the followign text?
> > 
> > 
> >  A.2.3  HTTP Redirection Removal
> > 
> >       HTTP Redirection rules can be automatically removed 
> when using 
> > the
> >       redir-cnt parameter or explicitly removed from the RADIUS 
> > server.
> > 
> >       The RADIUS server can explicitly turn HTTP redirection off 
> >       mid-session in two ways. It can push new redirection rules 
> > within a
> >       NAS-Filter-Rule(TBD) attribute using a CoA message or it can 
> > send the
> >       NAS a CoA message requesting it to re-authorize.  
> 
> This is much better. How about mentioning the mid-session for 
> redir-cnt as well? Something like:
> 
>      "HTTP Redirection rules can be automatically removed mid-session
>       from the NAS when using the redir-cnt parameter or explicitly
>       removed from the RADIUS server.
> 
>       ..."
> 
> /Jouni
> 
> > Paul
> 
> 

--
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/>