Re: [Mip6] mip6-aaa frameworks

["Mohan Parthasarathy" <[e-mail]>]

Alper,

Thanks for summarizing this.  A few comments below.

> 
> Framework 1:
> ------------
> Using network access AAA to deliver MIP6 configuration parameters from
> the AAA server to the MN. 
> 
> MIP6 configuration is directly delivered from the AAA server to the MN
> during network access AAA, in-band with the authentication (e.g.,
> transported by EAP or EAP methods).
> 
> Related I-Ds:
> 
> draft-giaretta-mip6-authorization-eap-01
> draft-le-aaa-mipv6-requirements-03
> draft-ohnishi-mip6-aaa-problem-statement-00
> 
> Discussion:
> 
> The end2end transport between the AAA and the MN is the key. Use of EAP
> for this somewhat network access unrelated "configuration" is not
> recommended as far as I understand. One can design his own EAP method to
> do that, yet that would have limited applicability.
> 
Perhaps, you don't need a new method. But something like EAP-TLV (there was
a draft around sometime back) is sufficient i guess. Anyway, the key issue
is using EAP for configuration.

 
> Framework 3:
> ------------
> Piggybacking MIP6 signaling (BU) with network access AAA. In-band with
> the network access authentication execution, the MN delivers
> (piggybacks) a BU to the AAA server. The AAA server may have to relay
> the BU to the HA (unless collocated).  
> 
> Related I-D:
> 
> draft-le-aaa-mipv6-requirements-03
> 
> Discussion:
> 
> While the performance benefits are clear, limited applicability (not
> always the network access and mobility services are bundled) and
> complexity are concerning.
> 
Can you elaborate on the complexity issue ?

> 
> Framework 4:
> ------------
> A backend AAA protocol is executed between the HA and the AAA server in
> response to the MIP6 signaling between the MN and the HA. Similar to the
> use of AAA protocols with MIPv4 co-located care-of address case.
> 
> Related I-Ds:
> 
> draft-giaretta-mip6-aaa-ha-goals-00.txt
> draft-yegin-mip6-aaa-fwk-00.txt
> 
> Discussion:
> This one appears to be the most needed framework. It is assumed that MN
> already knows the HA address. 
> 
Agreed.  We can always use a simpler mechanism e.g. DNS to discover the
HA address i suppose. 

-mohan

> 
> Are there other frameworks to add?
> 
> I am sure I have missed some references, please let us know which ones.
> 
> Alper
> 
> 
> 
> 
> _______________________________________________
> Mip6 mailing list
> [e-mail]
> https://www1.ietf.org/mailman/listinfo/mip6

_______________________________________________
Mip6 mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/mip6