RE: Persistent or opportunistic IDs

["marcelo bagnulo" <mbagnulo@ing.uc3m.es>]

>
> Yes. In effect the application need to know and express to the "stack"
> whether there is a need to do "callbacks" on referrals, since this
> affects which source identifier to use for the communication.
> Would such a scheme be acceptable for the applications?

I wouldn't dare to answer that question considering my limited knowledge on
apps, but, perhaps it would be possible to distinguish the ephemeral ids
from the stable ids (IP addresses in this case) using a ephemeral/stable
(e/s) bit in the id itself.
So, when the app that will perfom a call back discovers its own identifiers,
the noid+wimp layer will show multiple addresses, some stable ids  and some
ephemeral ids. The app can, because of the (e/s) bit on the ids, identify
the ephemeral identifiers, so it can avoid sending them to the other end as
a call back information.
Perhaps, something similar can be done with refferals. I mean, the
application first discovers the ids available in its own endpoint, and then
selects one that fits its needs, (stable or ephemeral), and then it performs
a bind to the selected id.

But perhaps this is too complex and i don't know if it is worthy...

Regards, marcelo
>
>    Erik
>
>