Re: [5gangip] BOF Description

[Alexandre Petrescu <[e-mail]>]

Le 06/02/2018 à 14:10, Dino Farinacci a écrit :
> And DNS doesn’t have pubsub.

Not sure about 'sub' but there is 'pub' in that DHCP clients can update 
DNS resource records.

Alex

  So that means caching DNS entries need to
> poll for changes. That will make handoffs as fast as the polling interval.
> 
> Dino
> 
> On Feb 6, 2018, at 6:48 PM, Saleem Bhatti <[e-mail] 
> <mailto:[e-mail]>> wrote:
> 
>> Lorenzo;
>>
>>> On 02 Feb 2018, at 05:56, Lorenzo Colitti <[e-mail] 
>>> <mailto:[e-mail]>> wrote:
>>>
>>> On Fri, Feb 2, 2018 at 4:34 AM, Behcet Sarikaya 
>>> <[e-mail] <mailto:[e-mail]>> wrote:
>>>
>>>     ·Most Id-Loc split solutions need mapping server to look up
>>>     efficiently for changes in locators of Identities. Scalability
>>>     and performance of such mapping systems is not in scope.
>>>
>>> This really doesn't make sense. The way I see it, the main downside 
>>> of ID-locator split solutions *is precisely* the fact that the 
>>> mapping system is hard to scale. Any scheme or solution that doesn't 
>>> also address this scaling problem is undeployable at scale and 
>>> therefore not useful to discuss in the context of any real deployment.
>>
>> Not all Id/Loc systems are the same. Not all need to map Id values to 
>> Locators.
>>
>> ILNP does not map Id values to Locator values.
>>
>> ILNP uses DNS lookups (as for IP today) so that DNS names map to an 
>> Id/Loc pair. Then, nodes use direct signalling with Locator Updates as 
>> they move, and update DNS with new Locator values.
>>
>> Updating DNS securely is possible today with, but deployed DNS 
>> engineering is not optimised for write operations. At the current 
>> time, at least, there is a significant performance hit with using DNS 
>> in this way.
>>
>> So, overall, for ILNP, the scaling issues with Locator updates are 
>> related to the performance of secure DNS write operations.
>>
>> Cheers,
>> --/Saleem
>>
>>
>>> _______________________________________________
>>> 5gangip mailing list
>>> [e-mail] <mailto:[e-mail]>
>>> https://www.ietf.org/mailman/listinfo/5gangip
>>
>> _______________________________________________
>> 5gangip mailing list
>> [e-mail] <mailto:[e-mail]>
>> https://www.ietf.org/mailman/listinfo/5gangip
> 
> 
> _______________________________________________
> 5gangip mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/5gangip
>