Re: Question re HIP dependency & some architectural considerations

Hi Pekka,

I agree with most of your comments, just a clarification question 
here....
>

> To me, it remains an interesting question how to support API evolution.
> One architectural possibility would be to use HIP as an example:
>  - convert AIDs into EIDs at the API level
>  - use EIDs to establish the end-to-end context
>  - map EIDs to IP addresses when sending packets out
>

This is how hip works today, right?
i mean in the HIP case:
AID==HIT
EID==HI

I guess that what it seems that we need is to support routable AIDs, 
and provide the means to securely bind them to the corresponding EID, 
right?

regards, marcelo