nemo-4----Page:2
1 2 3
|
Issues on the mailing list since the last IETF Last IETF conclusion (discussion based on draft-ng-nemo-aaa-use) Requirements on the draft looks generic for AAA AAA is orthogonal issue to NEMO basic solution It is premature to discuss before we get requirements document However, discussion about AAA on NEMO goes... “Migration transparency” and AAA policy transparency When NEMO changes its point of attachment, NEMO SHOULD NOT require re-auth/authz of MNN However, NEMO may want to change billing policy for MNN if billing policy of NEMO’s new access network differs from one of old access network Does this require notification to MNN? If yes, is existing AAA tools capable of doing so? |