Re: [icnrg] I-D Action: draft-irtf-icnrg-mapme-02.txt

Jordan Augé <jordan.auge@cisco.com> Tue, 23 October 2018 07:56 UTC

Return-Path: <jordan.auge@cisco.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16480130F80 for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2018 00:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.502
X-Spam-Level:
X-Spam-Status: No, score=-14.502 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ESNfcnqABwf0 for <icnrg@ietfa.amsl.com>; Tue, 23 Oct 2018 00:56:25 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF57F130F82 for <icnrg@irtf.org>; Tue, 23 Oct 2018 00:56:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1210; q=dns/txt; s=iport; t=1540281385; x=1541490985; h=from:to:subject:date:message-id:mime-version: content-transfer-encoding; bh=p1Fl/3zxlUCGeBXanRDKSTPjvyNTlugFY3QBqqKhE9A=; b=bBQd84RAHF+pdg++w57em/S4GfwIAvZ/5Zvt0HzHLxHC+ay8+K7DQihQ FbQ2QXc9Mx9dgR9Bh2znI9cYgqYOKx8hFbgpZMc0XA6vjOza4QGOvCoDI oDC/pEIW+FZdfwzNqv9dueoMH/2RXqFBMyTc60FqPT5H+6V6ga6LUE6MA s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AwAQCy0s5b/xbLJq1jHAEBAQQBAQcEAQGBVAQBAQsBgVqBLk8ShV2HN5BLim2JPIFmCwEBijE3Cg0BAwEBAgEBAm0ohXtaIQwJHwGGA6cliiSNeIERgxKEOQ4EARIBXg6FDQKeUAcCkQsJgUmOXokpjRsCBAYFAhSBWSJkcTM9gz2DOQEIjRY9i14PF4InAQE
X-IronPort-AV: E=Sophos;i="5.54,415,1534809600"; d="scan'208";a="7462679"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2018 07:56:22 +0000
Received: from adreena.localnet ([10.228.42.75]) (authenticated bits=0) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPSA id w9N7uMwJ023438 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <icnrg@irtf.org>; Tue, 23 Oct 2018 07:56:22 GMT
From: Jordan Augé <jordan.auge@cisco.com>
To: icnrg@irtf.org
Date: Tue, 23 Oct 2018 09:56:28 +0200
Message-ID: <1645375.1NsbAnTFpH@adreena>
Organization: Cisco Systems
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Authenticated-User: augjorda
X-Outbound-SMTP-Client: 10.228.42.75, [10.228.42.75]
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/82YFPY6SqwqpBcHB5PZLIUrc2Ko>
Subject: Re: [icnrg] I-D Action: draft-irtf-icnrg-mapme-02.txt
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2018 07:56:31 -0000

Hi everyone,

To follow up on the automated email sent yesterday following the update of the 
MAP-Me draft, we wanted to give you a quick overview of the changes.

Besides the usual tidying up of the document, the major change is a 
simplification of the retransmission mechanism ensuring the reliability of the 
update process. This consequently reduces the amount of information we store 
in the TFIB: we don't have anymore a timer per transmitted update but instead 
use a single timer to account for all FIB entries having pending updates.

This change is the result of the work we have been doing recently, to provide 
an efficient implemention of MAP-Me mechanisms in the VPP forwarder / hICN 
plugin.

We have also clarified the sections detailing face management in the 
forwarders, whose creation and deletion are the triggers for sending MAP-Me 
signaling. In particular, the previous version was only referring to 
synchronizing faces with Layer 2 changes, while the mechanism is in fact more 
generic when faces are built on top of IP adjacencies (as in hICN), tunnels 
(eg. UDP), etc.

As usual, we welcome any feedback you might have about the draft.

Cheers,
-- Jordan