Re: call for discussion on draft-heinanen-radius-pe-discovery-03.txt

Bernard Aboba writes:

 > My issues were with other parts of the proposal, such as
 > modifying RFC 2486, using Interim Accounting as a failure detection
 > mechanism, and attempting to do dynamic re-authorization in a manner not
 > supported within draft-chiba-radius-dynamic-authorization-20.txt.  

i'm not proposing any modifications to the protocols described in RFC
2486 and RFC 2866.  all packets and procedures remain as it.  i'm simply
describing how those protocols are used in a pe discovery application.
neither is this application requiring any dynamic changes to user
sessions as covered by draft-chiba-radius-dynamic-authorization-20.txt.
in particular, the pe discovery application described in my draft does
not require or need the radius server to send any unsolicited messages
for any purpose to the pes.

 > hope that discussion in this forum will focus on figuring out how to
 > meet the requirements given existing facilities (RFC 2865-2869 + 3162,
 > 2869bis, draft-congdon and draft-chiba).

i don't see any conflict with my draft and rfc 2486 and rfc 2866.  if
you do, please describe what that are.  in particular, those rfcs do
allow the ras to send re-authentication and interim accounting requests
at any time.

-- juha