[radext] Gathering opinions on draft-xue-radext-key-management

[Xueli <[e-mail]>]

Hello all

As you know, we presented the draft-xue-radext-key-management (new version http://tools.ietf.org/id/draft-xue-radext-key-management-03.txt  )
 Which defines the Radius extensions for key delivery between BNG and AC in some specific scenario.

In practice, operators prefer to deploy BNG as Authenticator while AC is as much as simple for AP management.
In this scenario, an standard approach is required to help the WTP to obtain the PMK, especially, when AC and BNG are deployed by different vendors.. 
This work tries to discuss the issues related with this topic and proposes a RADIUS extension to address the problem.
As before we discussed in the meeting, the scenario is already clear and reasonable. 

Now the argument is that whether this item is the genuine Radius/RADEXT problem? 
Radius packet is proposed to resolve this issue because of following reasons:
1 transmit session authorization attributes
(Key, which is produced during authentication and delivered by Radius from Server to NAS)
2 unsolicited messages 
3 It is not the issue of Radius, it may be the issue of EAP over Radius..

At this stage, the authors appreciate your opinions very much for the next step of this draft.
Can it be solved in RADEXT? If not, which WG could be the place?

Thanks in advance

Li On co-authors' behalf