Hi, thanks for the reply, inline text below:
From: Tony Li [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 26, 2008 12:22 PM To: 'Damian Lezama'; [email protected] Subject: RE: [rrg] Questions about ILNP Hi Damian, ----- "Identifiers are unique within the context of a given Locator; in many cases, Identifiers might happen to be globally unique, but that is not a functional requirement for this proposal." I don't understand how this works. If you can have duplicated IDs then what happens if you have a conflict? (i.e. You move to another network where the ID is in use by another host?). As IDs are also used to identify sessions I also imagine trouble there. ----- Presumably if you move to another network, you'll need to get another identifier. One could imagine that this could be based on DHCP, or by manual configuration. Isn't this what we are trying to avoid? If I move my site to another provider my locators change right? If they do change, can't my IDs collide with someone else's ones? Note that if a network uses particular ID allocation policies (e.g., your MAC address is your identifier), this is very unlikely. Well, the ID identifies the host not the interface in this proposal, it says something about generating the ID with your set of MACs, if you do this or even if you random choose it a collision is very unlikely I agree, but the possibility exists. "There are no standardised mechanisms to update most transport protocols with new IP addresses in use for the session. [NB: There is IETF work in progress to add this capability into the Stream Control Transport Protocol (SCTP).]" Isn't this RFC5061 and therefore a standard more than a work in progress? 5061 appears to be a proposed standard at this point. OK ----- Is this proposal suggesting that DNS should be responsible for finding the hosts locators? Is a DNS update fast enough for that to work (i.e. with mobility) or cached entries make it too slow? DNS is only responsible for the mapping function from FQDN to a set of locators. I read you get two things from DNS: "L" and "I" records. I assume those are Locators and Identifiers (I don't understand why ID's in plural). My doubt is: is DNS fast enough for solving this? To move a site to a new provider what do I have to do? How long are invalid locators (new site to where I still didn't move or old site after moving) in some DNS server's cache and what is the impact of that? In previous discussions, I believe that we came to the consensus that RRG is not trying to solve the full-blown mobility problem. The rate of dynamism is higher than what we'd really like to support in any mapping function. Well, I'm new around here, I'll take that into account, thanks. But the draft says that ILNP treats mobility as a special case of multihoming and solves it. Tony Regards, Damian
_______________________________________________ rrg mailing list [email protected] https://www.irtf.org/mailman/listinfo/rrg
