Issue: redir_cnt not included as method of redirection removal

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

redir_cnt not included as method of redirection removal
Submitter name: Paul Congdon
Submitter email address: paul.congdon@hp.com
Date first submitted: 08-10-2005
Reference: N/A
Document: draft-ietf-radext-ieee802-00.txt
Comment type: T
Priority: S
Section: A.2.3, Pg 27, last paragraph
Rationale/Explanation of issue:
This section talks about how the redirection process can be disabled.
Since we added the redir_cnt parameter to the rule we should include it
as a mechanism for disabling redirection.  Also it isn't clear if a new
session is created when the redir_cnt value becomes zero.  If a new
session is created, then the accounting records should also be sent.  I
will propose that we insert a paragraph before the last paragraph in
this clause so the accounting scheme will remain intact.
Requested change:
Insert a paragraph before the last paragraph that describes the
redir_cnt scheme.  Suggest something like the following words: "When
HTTP redirection is established via a NAS-Filter-Rule (TBD) it also
possible to have HTTP redirection automatically removed by including a
redir_cnt parameter along with the rule.  The rule will be removed from
the active rule set when the rule matches redir_cnt number of times.
When the rule is removed, HTTP redirection will also be removed."


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