mip6-5----Page:3
1 2 3 4 5
|
A new Service Selection mobility option.. RFC4283 could have been used but we wanted to avoid (again) overloading the NAI Use the NAI only to identify the user@operator Cleaner approach and also backwards compatible The Service Selection option is skipable -> ’legacy’ HAs just fall back to the default behavior Not coupled with with access authetication and AAA The Service Selection may affect the routing of the IP packets in the HA depending on the selected service. The Service Selection may affect the dynamic HoA allocation when e.g. used with the MN-NAI option Different HoA / prefix for the same MN-NAI depending on the identified service |