[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HOKEY] Review of draft-gaonkar-radext-erp-attrs-02.txt
When the peer, the local domain and the AAA-Home also
support ERP, a DSRK (DSRK1) may be requested by the local ER server A at
the time of the EAP exchange.
1. Is the "Local ER server" always a RADIUS client? The ERX document
indicate that this might not always be the case.
2. How is the request for the DSRK made by the "local ER server"? Is the
request authenticated with user credentials? How does the RADIUS server
determine if the Request is valid?
3. How does the RADIUS server know how to reach the "Local ER server"?
The ERX document talks about a "Domain Identity". How does the RADIUS
use the "Domain Identity" to determine what RADIUS client to send a packet
Is there an assumption that the "Local ER server" is one hop away from the
home RADIUS server? What attributes need to be placed within an
to ensure that the packet is routed to the "local server"?
4. In Figure 1, the ERX document shows the following flow:
[<-- EAP-Request/ ------
[<-- EAP Initiate/ ------
Is this a typo? The figure shows that the EAP-Request/Identity isn't being
to by the peer. If the peer implements RFC 3748, won't it send an
which will be passed to the RADIUS server, which will then initiate EAP?
seems to show the EAP peer ignoring the EAP-Request, which
implies that it needs to wait for some period of time for another message,
might or might not arrive. How long should it wait?
If the peer doesn't respond to the EAP-Request/Identity, according to RFC
and RFC 4137, the NAS will retransmit. So we'll have two EAP conversations
going on at once?
5. In Figure 2, the peer is initiating what would appear to be a standard
RADIUS/EAP conversation via the EAP-Response/Identity. However, it
would appear that the EAP Response/Identity is being "augmented" by
the local server. It's hard for me to tell from the figure whether the
[DSRK Req, Domain Identity] is being inserted within the
or whether it represents separate RADIUS attributes. Can you clarify?
6. If the "local 'server" isn't on the path between the NAS and the home
(as it might not be, because of failover), what happens? Does each proxy
also need to host a "local server" to make sure that doesn't occur?
If the "local server" is not on the path, then it seems like two distinct
would be required. Is there an expectation that the RADIUS Access-Accept
will be multicast, or that two distinct RADIUS Access-Accept packets will
to unsubscribe send a message to email@example.com with
the word 'unsubscribe' in a single line as the message text body.