[Pana] DiameterIdentity of new PAA in draft-ietf-pana-mobopts-01.txt

[Vijayarajan <[e-mail]>]

Hi Julien,
 
In draft-ietf-pana-mobopts-01.txt i.e. "PANA Mobility Optimizations", as
part of
Context transfer, an intermediate AAA-Key material is provided by
previous
PAA to new PAA. 
 
AAA-Key-int = The first N bits of
              HMAC-SHA1(AAA-Key, DiameterIdentity | Session-ID)
Where DiameterIdentity is the identifier of the current(new)
PAA
 
This computation is done at previous PAA. How does the previous
PAA know the DiameterIdentity of current(new) PAA?
This draft suggests "Context Transfer Protocol" RFC4067 as a
Possible way of transferring context. But RFC4067 message 
Context Transfer Request(CT-Req) does not have a field for
sending DiameterIdentity of new PAA. 
 
Is the method of determining DiameterIdentity of new PAA left
to implementations? One method I could think of is a reverse
DNS lookup on new PAA's source address(used in CxTP messages).
 
 
Regards,
Vijayarajan

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