Re: [lisp] draft-ermagan-lisp-nat-traversal question

Hi Vina,

It make sense for me.

Thank you very much.

Albert

El 08/11/17 a les 21:33, Vina Ermagan (vermagan) ha escrit:
> Hi Albert,
>
> ³Map Register TTL² in the referenced paragraph is indeed the TTL for which
> a Map Register stays valid in a Map Server. Suggested time in the RFC for
> periodic Map Registers is 1 minute. And MS will expire the registration
> after 3 minutes if it does not receive a renewal. So this TTL in RTR
> should be set no larger than 3 minutes, and no smaller than 1 minute.
> Unfortunately NAPT devices don¹t have a standard TTL for expiring their
> address associations; some use 2 minutes as the threshold. So the 3 minute
> recommendation for expiring a Map Register seems suitable here.
>
> Hope this clarifies it.
>
> Best,
> Vina
>
>
> On 11/6/17, 1:01 AM, "lisp on behalf of Albert López"
> <lisp-bounces@ietf.org on behalf of alopez@ac.upc.edu> wrote:
>
>> In that case, I think that It would be better if the validation time /
>> expiration time of the locator associated with the ECM-ed Map Register &
>> ECM-ed Map Notify is related with the periodic time of sending ECM-ed
>> Map Registers.
>> Usually a hole in the nat box is less than two minutes so we send
>> periodic ECM Mag register to maintain this hole opened apart from
>> maintaining the status in the Map Server. If we use the TTL of the
>> record to maintain an entry in the Map Cacahe of the RTR, it is possible
>> we maintain an entry which is no longer valid or send packets to an
>> invalid rloc.  What do you think?
>>
>> Regards
>>
>> Albert
>>
>> El 03/11/17 a les 18:38, Dino Farinacci ha escrit:
>>> The TTL in the Map-Register is the TTL returned in Map-Replies. So it
>>> is the expiry time for a map-cache entry. Note it is the ³Record TTL² in
>>> the EID-record which both appear in Map-Register and Map-Reply messages.
>>>
>>> Dino
>>>
>>>> On Nov 3, 2017, at 1:35 AM, Albert López <alopez@ac.upc.edu> wrote:
>>>>
>>>> Dear all,
>>>>
>>>> In section 5.3 of the draft  draft-ermagan-lisp-nat-traversal which
>>>> describe the RTR processing, it says that when the RTR receive and
>>>> ECM-ed Map Notify, once it is validated, it changes the state of the
>>>> associated map-cache entry to verified for the duration of the Map
>>>> Register TTL.  What does it mean by Map Register TTL?  it means the TTL
>>>> of the record of the Map Register or it is the same concept of the Map
>>>> Register TTL of the Map Server which is 3 minutes? If I understand
>>>> correctly, if we don't receive more Encap Map Register / Map Notify to
>>>> renew this verified period, the map-cache entry of the RTR expires, at
>>>> least the locator of the map-cache entry associated with the Encap Map
>>>> register.
>>>>
>>>>     "Once the authenticity of the message is verified,
>>>>     RTR can confirm that the Map-Register message for the ETR with the
>>>>     matching xTR-ID was accepted by the Map-Server.  At this point the
>>>>     RTR can change the state of the associated map-cache entry to
>>>>     verified for the duration of the Map-Register TTL"
>>>>
>>>> Thank you in advance.
>>>>
>>>> Albert López
>>>>
>>>>
>>>> _______________________________________________
>>>> lisp mailing list
>>>> lisp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/lisp
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp