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

Albert López <alopez@ac.upc.edu> Fri, 03 November 2017 08:35 UTC

Return-Path: <alopez@ac.upc.edu>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE44A13FD01 for <lisp@ietfa.amsl.com>; Fri, 3 Nov 2017 01:35:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.801
X-Spam-Level:
X-Spam-Status: No, score=-2.801 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eBq8gbulY12H for <lisp@ietfa.amsl.com>; Fri, 3 Nov 2017 01:35:39 -0700 (PDT)
Received: from roura.ac.upc.es (roura.ac.upc.edu [147.83.33.10]) by ietfa.amsl.com (Postfix) with ESMTP id A4B3513FCFC for <lisp@ietf.org>; Fri, 3 Nov 2017 01:35:38 -0700 (PDT)
Received: from correu-1.ac.upc.es (correu-1.ac.upc.es [147.83.30.91]) by roura.ac.upc.es (8.13.8/8.13.8) with ESMTP id vA38ZaMN008834 for <lisp@ietf.org>; Fri, 3 Nov 2017 09:35:37 +0100
Received: from [192.168.1.135] (117.29.15.37.dynamic.jazztel.es [37.15.29.117]) by correu-1.ac.upc.es (Postfix) with ESMTPSA id BAF011A0 for <lisp@ietf.org>; Fri, 3 Nov 2017 09:35:31 +0100 (CET)
From: Albert López <alopez@ac.upc.edu>
To: lisp@ietf.org
Message-ID: <f574957a-e4fd-6984-99ef-185cd2c1bc15@ac.upc.edu>
Date: Fri, 03 Nov 2017 09:35:31 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/CVXWc36Ld8TcKeuE9O714cXsC3Y>
Subject: [lisp] draft-ermagan-lisp-nat-traversal question
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Nov 2017 08:35:46 -0000

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