From nobody Mon Apr 2 20:55:49 2018 Return-Path: X-Original-To: ila@ietfa.amsl.com Delivered-To: ila@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 958E0127010 for ; Mon, 2 Apr 2018 20:55:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=verizon.com header.b=iJfQrZow; dkim=pass (1024-bit key) header.d=verizon.com header.b=VovShnCY; dkim=pass (1024-bit key) header.d=verizon.com header.b=cun1AkP4 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 bRi_m2Zax_qY for ; Mon, 2 Apr 2018 20:55:46 -0700 (PDT) Received: from omzsmtpe02.verizonbusiness.com (omzsmtpe02.verizonbusiness.com [199.249.25.209]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A6EC0126DD9 for ; Mon, 2 Apr 2018 20:55:46 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1522727746; x=1554263746; h=from:to:subject:date:message-id:mime-version; bh=NdRZFCHaIOU/DPv4aueLzTAlAxbhnjyRbc5wfSHO33A=; b=iJfQrZowOxH5vWHZBPOM9jmdYTXTXIsWvxrInG+//PpxZCH1X5JHSfxl EIdYI+4fR4nR+kJqOD/TtHUofBNFAPjuDiNFW4u4G1LTRS3Q77fne6I8v YNxjYxMtHOLJqq/6kO7oZQF9Y0o6hJMNwc0uapAClHw++82Dw9LByV2CU M=; Received: from unknown (HELO fldsmtpi03.verizon.com) ([166.68.71.145]) by omzsmtpe02.verizonbusiness.com with ESMTP; 03 Apr 2018 03:55:45 +0000 Received: from rogue-10-255-192-101.rogue.vzwcorp.com (HELO atlantis.verizonwireless.com) ([10.255.192.101]) by fldsmtpi03.verizon.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 03 Apr 2018 03:55:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1522727708; x=1554263708; h=from:to:subject:date:message-id:mime-version; bh=NdRZFCHaIOU/DPv4aueLzTAlAxbhnjyRbc5wfSHO33A=; b=VovShnCYDKL1rqL/bvxi6VtoBAR7Z5yWQcw+bv+nuqsDen6d3lkcEBTY V7Q1NNzS40gMP7RpFI+7DS9TjyN+TC3LbyCQKVTPiCoZWNIV7kBk+GVC0 X5P8X+ERaKYA0y08izA/Cfz/HG4WvZOw11O+fQVPNSgowGqqHyq8ue69H U=; Received: from pioneer.tdc.vzwcorp.com (HELO eris.verizonwireless.com) ([10.254.88.34]) by atlantis.verizonwireless.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 02 Apr 2018 23:53:47 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=verizon.com; i=@verizon.com; q=dns/txt; s=corp; t=1522727627; x=1554263627; h=to:subject:date:message-id:mime-version:from; bh=NdRZFCHaIOU/DPv4aueLzTAlAxbhnjyRbc5wfSHO33A=; b=cun1AkP4ADgrs8JjCmsHGP84Vv8eAmJ8aa8jCNtSHdaBBUN2qI6X2I/K IY/MhLBAnqmRZ6T7f9IiGos16vHjEmyoD46mc03gPDL3UbgyH+xz+AxZV YfoQni4NTHHLTkn1PrtelDJB0I8pXQ6nW/HLi7TLTkszwYTOYeJXS5fVm 8=; From: samita.chakrabarti@verizon.com X-Host: pioneer.tdc.vzwcorp.com Received: from ohtwi1exh003.uswin.ad.vzwcorp.com ([10.144.218.45]) by eris.verizonwireless.com with ESMTP/TLS/AES128-SHA256; 03 Apr 2018 03:53:47 +0000 Received: from tbwexch17apd.uswin.ad.vzwcorp.com (153.114.162.41) by OHTWI1EXH003.uswin.ad.vzwcorp.com (10.144.218.45) with Microsoft SMTP Server (TLS) id 14.3.248.2; Mon, 2 Apr 2018 23:53:47 -0400 Received: from tbwexch18apd.uswin.ad.vzwcorp.com (153.114.162.42) by tbwexch17apd.uswin.ad.vzwcorp.com (153.114.162.41) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 2 Apr 2018 23:53:46 -0400 Received: from tbwexch18apd.uswin.ad.vzwcorp.com ([153.114.162.42]) by tbwexch18apd.uswin.ad.vzwcorp.com ([153.114.162.42]) with mapi id 15.00.1320.000; Mon, 2 Apr 2018 23:53:46 -0400 To: "ila@ietf.org" Thread-Topic: IETF 101 ILA BOF minutes uploaded Thread-Index: AdPK/rYHH80ijt/aTbKkAXf35MXBkw== Date: Tue, 3 Apr 2018 03:53:46 +0000 Message-ID: <0ede3f760f6d41ee82b70c3fe2317b79@tbwexch18apd.uswin.ad.vzwcorp.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader: Hosted x-originating-ip: [10.144.60.250] Content-Type: multipart/alternative; boundary="_000_0ede3f760f6d41ee82b70c3fe2317b79tbwexch18apduswinadvzwc_" MIME-Version: 1.0 Archived-At: Subject: [Ila] IETF 101 ILA BOF minutes uploaded X-BeenThere: ila@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Identifier Locator Addressing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Apr 2018 03:55:49 -0000 --_000_0ede3f760f6d41ee82b70c3fe2317b79tbwexch18apduswinadvzwc_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello: The BOF minutes are uploaded. https://datatracker.ietf.org/meeting/101/mate= rials/minutes-101-ila-00 Thanks to Uma and Alberto for taking the minutes and Evangelos for being th= e jabber scribe. Please take a look on the minutes, please let Joel and me know if any chan= ges are needed. The WG can use the minutes for further clarification and follow-up discussi= on. Thanks, -Samita and Joel --_000_0ede3f760f6d41ee82b70c3fe2317b79tbwexch18apduswinadvzwc_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello:

 

The BOF minutes are uploaded. https://datatracker.ietf.org/meeting/101/materials/minutes-101-ila-00

 

Thanks to Uma and Alberto for taking the minutes and= Evangelos for being the jabber scribe.

 

Please take a look on the minutes, please let Joel a= nd me know if  any changes are needed.

The WG can use the minutes for further clarification= and follow-up discussion.

 

Thanks,

-Samita and Joel

--_000_0ede3f760f6d41ee82b70c3fe2317b79tbwexch18apduswinadvzwc_-- From nobody Fri Apr 27 11:37:20 2018 Return-Path: X-Original-To: ila@ietfa.amsl.com Delivered-To: ila@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFE3B1200C5 for ; Fri, 27 Apr 2018 11:37:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.91 X-Spam-Level: X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 pbznUqcGau9A for ; Fri, 27 Apr 2018 11:37:11 -0700 (PDT) Received: from mail-wr0-x233.google.com (mail-wr0-x233.google.com [IPv6:2a00:1450:400c:c0c::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 735C2124205 for ; Fri, 27 Apr 2018 11:37:11 -0700 (PDT) Received: by mail-wr0-x233.google.com with SMTP id g21-v6so2637455wrb.8 for ; Fri, 27 Apr 2018 11:37:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/mc0DPZcuGibmiulwjf4yk9yXZQOcToy7YiWFn8mQKY=; b=qx0tjFLeZHUcMlatuEdrsSHyNSiWjTOtjXHZP99FRCNBjP53nHR8Wt+8XrvueWGAW8 5WzFxbf7uI0FF189x1pfevhE06EY/rxMBTAyFN2jK7PJrOi7NM7S6d+pPQjRqj+CR4hk zNEK8t5viTD7Xwg0CMrTzXkp42kDCPJ4u6Hmlbj4CkQmJqlEOoCPo+9g9EtwPdLbn5+Q FUErNhUuYE7PWb6x08TW26bmbIIVEj/gqAjJWxPZ7BVcRo8xS4Rz/0/CKhzGlmQwyIK/ KRcqPJY6Dvo+TVUvNfvXhte4V8eVfbIzbvvJ1THfzhn8OqRxOEUwZeiE/3OsLIj2WoV1 iomw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/mc0DPZcuGibmiulwjf4yk9yXZQOcToy7YiWFn8mQKY=; b=i2evQTlffrmKftgZvE2T4x+gOG2YXmK3USfbCzyhTvl0R0HPzJyD5MwaNTmFeFL57/ v0tj1+SQ2IgAY+W/iKq2dvuNVXA9xwCvZkOR2Qhiftm2LlKxgc0Urt0MSYa54vIDIQMj q5gbg3kwFcAC/5HeEoRXguUZuze+9FFxKcj072V5Uy2jVj/Lvu/VveronkeGqclx2DqM cdx0P9S6UsGqqW8ql3mojblAHQtPzSae8JQzG7wk7bmnMcwsqBGoEMUIfW8Ai3TaqnnD DmwaIBljvRDkpHfcbF9tGzBSX9462223F2LvuFJMZd6xA2rNsoBzYXxVnVrwFCUDjQyd Ul+w== X-Gm-Message-State: ALQs6tDePBYQjU3ut6rURkWFlexvUUc9vM8klOzsY5fenP2a6cNJ6aOr FYmeMn0pEo8bghozP8HZY4R4B5xpZBPmEogNDhSIsw== X-Google-Smtp-Source: AB8JxZqyLVZ9zsC/3AFsDZXVaebIwB3JTBRmHBaAKr1urox4uYD0dgUae5T7Y3DHXOEU2fd+nROkhh3EZ06pycSbCAo= X-Received: by 2002:adf:e181:: with SMTP id k1-v6mr2704791wri.111.1524854229813; Fri, 27 Apr 2018 11:37:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.128.227 with HTTP; Fri, 27 Apr 2018 11:37:09 -0700 (PDT) In-Reply-To: <9C0497E2-017A-471B-8B73-70CD335A7CFD@gmail.com> References: <347F486D-0F7B-45D9-92B6-3AFE10B0550E@gmail.com> <9C0497E2-017A-471B-8B73-70CD335A7CFD@gmail.com> From: Tom Herbert Date: Fri, 27 Apr 2018 11:37:09 -0700 Message-ID: To: Dino Farinacci Cc: Tom Herbert , 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya , Christian Huitema , Dirk.von-Hugo@telekom.de, ila@ietf.org Content-Type: text/plain; charset="UTF-8" Archived-At: Subject: Re: [Ila] [5gangip] Problem Statement X-BeenThere: ila@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Identifier Locator Addressing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 18:37:14 -0000 On Fri, Apr 27, 2018 at 11:21 AM, Dino Farinacci wrote: >> >> Yes,you can differentiate them. ILA never drops of blocks packets >> becasue of cache miss; LISP allows that at least in certain >> configurations. So the worst DOS attack in ILA results in sub-optimal >> routing, worst case in LISP is indefinitely blocking packets. > > What does an ILA router (one that maintains a cache) do when there there is a map-cache miss? > ILA routers (ILA-R) are not caches. They contain their shard of the mapping system. ILA forwarding nodes (ILA-N) may have a cache. In the case of a cache miss the packet is forwarded. It will go to an ILA router that can perform ILA transformation. The ILA router may also send back an ILA redirect to the forwarding node to populate the cache so that it can perform the transformation on subsequent packets. ILA forwarding nodes never drop or block packets because of a cache miss. Tom > Dino From nobody Fri Apr 27 12:01:41 2018 Return-Path: X-Original-To: ila@ietfa.amsl.com Delivered-To: ila@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9751200C5; Fri, 27 Apr 2018 12:01:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 X5GBN4XDpto8; Fri, 27 Apr 2018 12:01:33 -0700 (PDT) Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9648E126D85; Fri, 27 Apr 2018 12:01:33 -0700 (PDT) Received: by mail-pg0-x231.google.com with SMTP id b9-v6so2213991pgf.6; Fri, 27 Apr 2018 12:01:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=q8It5hJANTOmLtsOv/aipp4VVknhFdhEUt8vm4ALGHw=; b=tqKvq949C2chq7dk5UraLBhD9VwROKL/zigyvl6BRx8OTjsGYqZkYjbCc7F4hL6/wM k79qAjBoOEH0AHH/yobmQ2grmN7qoxsCbqK0tbyrQdXAdx9Cpi7jRGAb5UnS+PRja5fn IcIxwH0r0ubwE1YF8OSC/HkNWlCScxm49xLrdb57VsbAj/0A3HLyb+uyrUs+YcU9WDlh HdIGkCB8vqftBB6UYPLT4C7zr+pNCQ3dhD18SEg5Cfi4NliACCZq7Iyost24/ymFaRCi h7t3xQIYNBsZsQAqC+e3Szv3TZ2jgiPvgwjFErSqrNlmSv+Jvnze4m2qs3DLTmRXA+Zy 90Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=q8It5hJANTOmLtsOv/aipp4VVknhFdhEUt8vm4ALGHw=; b=fqhCQoYN2GEHwLNrApAd48ZCEDt/HfAhEZCiEDj1pZpH1A1aN7uM6E8K89x32zM6gV CpmcPBrj85ZtFme24pcBwC6UZuxBegmal2jF+Y1TxVpmLd23Z1HOwnGuVj/9jBwt9oxx mMMkuHKjO6ZG1a2ZBBNiBi9Dvoqx8yy+BMzQID6i7a6nzwG/Mywb1QZqDPOLRuPAVZ+q kU7T+EQ7hiFa4kqz9bFNdW0w4CVCcd+jaeLUSYCvtRxwF/6zPEbNKcZ/laHEVqq7IADn 1c5MRIp6026QpHf/j9rfl1IIDmj0AGG4d9A7jKFd3ypRiqezDdUWFx5G8LCknRF74VRv D6rA== X-Gm-Message-State: ALQs6tBNB2aVEnVKdVeQZXUy6XnBfku0r6HgKX7/On++kZIPvbYhEb1F hI/lPkWb97de5S68QS6k+PA= X-Google-Smtp-Source: AB8JxZoqK6/oaE30OVber8+dEdNBL7IUZIx0HZwt4aJeom4zuSZgXV+U/POq7pkoyNciiSbuZj+vEQ== X-Received: by 2002:a17:902:3281:: with SMTP id z1-v6mr3263539plb.226.1524855693239; Fri, 27 Apr 2018 12:01:33 -0700 (PDT) Received: from [10.31.79.152] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id 204-v6sm4543847pgb.67.2018.04.27.12.01.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Apr 2018 12:01:32 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Dino Farinacci In-Reply-To: Date: Fri, 27 Apr 2018 12:01:30 -0700 Cc: Tom Herbert , 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya , Christian Huitema , Dirk.von-Hugo@telekom.de, ila@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <6535548C-B60C-47CB-8D5E-4175C4D49B07@gmail.com> References: <347F486D-0F7B-45D9-92B6-3AFE10B0550E@gmail.com> <9C0497E2-017A-471B-8B73-70CD335A7CFD@gmail.com> To: Tom Herbert X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [Ila] [5gangip] Problem Statement X-BeenThere: ila@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Identifier Locator Addressing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 19:01:35 -0000 > ILA forwarding nodes (ILA-N) may have a cache. In the case of a cache > miss the packet is forwarded. It will go to an ILA router that can > perform ILA transformation. The ILA router may also send back an ILA And how does the ILA router get the locator? > redirect to the forwarding node to populate the cache so that it can Yes, but it has to know what the destination locator is. You keep = leaving this information out whenever I ask you > perform the transformation on subsequent packets. ILA forwarding nodes > never drop or block packets because of a cache miss. But then they don=E2=80=99t have a locator to transform or redirect.=20 Dino= From nobody Fri Apr 27 12:11:41 2018 Return-Path: X-Original-To: ila@ietfa.amsl.com Delivered-To: ila@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA9DC12778D for ; Fri, 27 Apr 2018 12:11:35 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.61 X-Spam-Level: X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=quantonium-net.20150623.gappssmtp.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 CnX3TeY3Gveg for ; Fri, 27 Apr 2018 12:11:33 -0700 (PDT) Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com [IPv6:2a00:1450:400c:c09::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 118AC1200C5 for ; Fri, 27 Apr 2018 12:11:33 -0700 (PDT) Received: by mail-wm0-x236.google.com with SMTP id m70so3881790wma.2 for ; Fri, 27 Apr 2018 12:11:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=quantonium-net.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=2fnekvb2gsuVi7vXE1TSm8HVLIzOCEYxMNtHJcma91I=; b=ulef4RDtrUHKIzkGe27DCs4h9BITEwz/3sOoP/eRM5RWRmnuMtp21/8vSoejrfXSMl DhwFQnuxXS9vffoGXX4R70LwXg8zvfxnkbcUoWDDG/y0wRAPdH2Mrp8nK6YfjUEmOgR+ uavWo5oJklhrsxRGia1qszwmQBFRXov9fa0WukrYuFu/eSq6nmTX9PQc1w+cBCsp7LFC IO9hLwv/b0akaUO8DZzmUbnhHOzp5tRh3U9iFxMHFe8T4ieuEw2v6csZviEZPL29Lj3M bjBhJnMW2IngGPLNtmfy2x+ZLZvt5YYfLojlGEGaosCc11yHM3M/hvZQlPklkfJCB5aq NNTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=2fnekvb2gsuVi7vXE1TSm8HVLIzOCEYxMNtHJcma91I=; b=CPJx0hHgLsVFDAoYeSnSKg8rlus0kKnu9jFD11tA4ncLasvNyFBEd/E7VNes0k700P rv+BGz8xhBxIF50nEsQJ+AVSbUyX6WwLdnR1TtEgFd6T8Chxozu6rGLbAVQreTOt87RA R61hOT06B2A/4cvb21Y7ZiUKDUb1ijGrJV2dCI4dKwzGPrXOX5AHuLSxioWAKP1QXS+F 4S00NA2fAmqtEAtiM/w5lGc3wf7qOg+sgK0dqOM9k10mK1tpd60e/TeM/B4XiozR2gSj 8JXs2o0ccO5GbfP1RVmsNr8sfjMNYbhYaH3yKawr6ruTlf2+62qClBZfdBLfQnJkE1gM fG/g== X-Gm-Message-State: ALQs6tDdwRr1vxr5TQo1x7I/eM4eVMiJIIJfaQ2K4TkTVZlpV6trsVw9 KuKzDpbr4AuIjT/5o36bcIDEo6zuhBnfa//Ft250FA== X-Google-Smtp-Source: AB8JxZoyX8i8NzrGgDbHIuNr2gPjAcxfdVpEopCZzs7JfoSmKtgZACp3gctTzqllSKzKCxTJlGTrMSS9ckWnHokXKxI= X-Received: by 10.28.124.10 with SMTP id x10mr2014893wmc.59.1524856291388; Fri, 27 Apr 2018 12:11:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.128.227 with HTTP; Fri, 27 Apr 2018 12:11:30 -0700 (PDT) In-Reply-To: <6535548C-B60C-47CB-8D5E-4175C4D49B07@gmail.com> References: <347F486D-0F7B-45D9-92B6-3AFE10B0550E@gmail.com> <9C0497E2-017A-471B-8B73-70CD335A7CFD@gmail.com> <6535548C-B60C-47CB-8D5E-4175C4D49B07@gmail.com> From: Tom Herbert Date: Fri, 27 Apr 2018 12:11:30 -0700 Message-ID: To: Dino Farinacci Cc: Tom Herbert , 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya , Christian Huitema , Dirk.von-Hugo@telekom.de, ila@ietf.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Archived-At: Subject: Re: [Ila] [5gangip] Problem Statement X-BeenThere: ila@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Identifier Locator Addressing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 19:11:36 -0000 On Fri, Apr 27, 2018 at 12:01 PM, Dino Farinacci wrot= e: >> ILA forwarding nodes (ILA-N) may have a cache. In the case of a cache >> miss the packet is forwarded. It will go to an ILA router that can >> perform ILA transformation. The ILA router may also send back an ILA > > And how does the ILA router get the locator? > >> redirect to the forwarding node to populate the cache so that it can > > Yes, but it has to know what the destination locator is. You keep leaving= this information out whenever I ask you > We are currently using a distributed key value store for that (redis DB). ILA-Rs read the monitor their shard. Code is in github.com/quantonium/ila if you want to take a look. IMO, using a KV store for this as opposed to developing a new protocol is a good direction. This way were leveraging all the recent development for security, availability, reliability, replication, etc. ILAMP defines the protocol between ILA-Rs and ILA-Ns primarily for managing ILA-N caches. >> perform the transformation on subsequent packets. ILA forwarding nodes >> never drop or block packets because of a cache miss. > > But then they don=E2=80=99t have a locator to transform or redirect. > The router can send them a redirect if it chooses. On a cache miss the packet is forwarded like normal. > Dino From nobody Fri Apr 27 12:26:20 2018 Return-Path: X-Original-To: ila@ietfa.amsl.com Delivered-To: ila@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CE321200C5; Fri, 27 Apr 2018 12:26:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2 X-Spam-Level: X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 cWCCE1l6GOpp; Fri, 27 Apr 2018 12:26:17 -0700 (PDT) Received: from mail-pf0-x229.google.com (mail-pf0-x229.google.com [IPv6:2607:f8b0:400e:c00::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38AA5127863; Fri, 27 Apr 2018 12:26:17 -0700 (PDT) Received: by mail-pf0-x229.google.com with SMTP id f189so2154198pfa.7; Fri, 27 Apr 2018 12:26:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EMFrYWtspm9MlBv30EFCJ20XOW82H6rA0szDR7ohdc8=; b=VpILktZz9wXMK/xvjLCM6/OspuFzyTw3hkDiVmj+H06Picqc8Ifp+o52DNg13wZ6vD yFHCBPRFDOGLDUTZBsUdRkBPl/Wz3IRb9L+fnQ53DMagq6vITu3yb0eQcbRNc9Ma+TZl yw881Y5fa8D2/CMgYqjq5P3XY3z68e4tZoaxzISIH4bNqtRmtXTGALnI1T70Yg4V6a5w v2wTsjJsa3Y27Z2cI0HbOL4qgxP5yBsACU/Ikzu/DhHwAwWaDYe+PJyLXtrx7b6RciA9 3s+rl+FHtr5G0Md8k6aF7N7v2Aisnhg0Iob4w6vrloIqm1mmwYRpSfEa+4jBOiSxYon2 uMmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=EMFrYWtspm9MlBv30EFCJ20XOW82H6rA0szDR7ohdc8=; b=uWNP1juE7oIrxwvxfJfSZw18wrxmhmjR83nnUSazfUB/tEW9XUsdEiQr9DbV1D5hET xed0eQuOgGgDq8w+1cTaIJs19qYFll+8ZYm1C0pqqXN7MNgf82RCJ88NkgH2Lgmqq7G5 BjIEcGGamy/RSIabr5IFrftutTxqyjj7NxwwdM/H/SfY5AayLac/3fLe7JGyvkkAwMQe FWWhUENQrAPKHIWRRBodI6R5GnPrPhTfHmSS+OfHL7YFsKnHBFvgs4LVZTQOegBjQ9/B cbfxf6WfU4fJpY2ZKnlovIFmoGfCBD/xb4H/x02g5ZZUYPGKAgiNTgAi366et56+fhjT vmFg== X-Gm-Message-State: ALQs6tB0tajZjK1Ed+VzIN3KNCBX0NeJPMrxkUuPtpCE6nSmDQad+edD JJ4dPN4eKKiTEwvQZrlfsQI= X-Google-Smtp-Source: AB8JxZrcur5IiZaT4vNx8q5EeHIiQeviDA7kjVUy8z8Be8u6Aaj4WajERnpXnw3103xpiHjAcGAsqA== X-Received: by 2002:a63:6dc3:: with SMTP id i186-v6mr3040890pgc.403.1524857176903; Fri, 27 Apr 2018 12:26:16 -0700 (PDT) Received: from [10.31.79.152] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id e126sm3773359pfh.5.2018.04.27.12.26.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 27 Apr 2018 12:26:15 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.2 \(3445.5.20\)) From: Dino Farinacci In-Reply-To: Date: Fri, 27 Apr 2018 12:26:14 -0700 Cc: Tom Herbert , 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya , Christian Huitema , Dirk.von-Hugo@telekom.de, ila@ietf.org Content-Transfer-Encoding: quoted-printable Message-Id: <45F4FCDE-A056-4C24-914D-4B032B5E26CD@gmail.com> References: <347F486D-0F7B-45D9-92B6-3AFE10B0550E@gmail.com> <9C0497E2-017A-471B-8B73-70CD335A7CFD@gmail.com> <6535548C-B60C-47CB-8D5E-4175C4D49B07@gmail.com> To: Tom Herbert X-Mailer: Apple Mail (2.3445.5.20) Archived-At: Subject: Re: [Ila] [5gangip] Problem Statement X-BeenThere: ila@ietf.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Identifier Locator Addressing List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Apr 2018 19:26:19 -0000 >=20 > We are currently using a distributed key value store for that (redis > DB). ILA-Rs read the monitor their shard. Code is in So does LISP. > github.com/quantonium/ila if you want to take a look. IMO, using a KV > store for this as opposed to developing a new protocol is a good I don=E2=80=99t want to look at code. I want you to explain clearly how = a cache misser gets the RLOC. What if the identifier is not in its = shard? > direction. This way were leveraging all the recent development for > security, availability, reliability, replication, etc. >=20 > ILAMP defines the protocol between ILA-Rs and ILA-Ns primarily for > managing ILA-N caches. I know that. You are not answering the key questions. >> perform the transformation on subsequent packets. ILA forwarding = nodes >>> never drop or block packets because of a cache miss. >>=20 >> But then they don=E2=80=99t have a locator to transform or redirect. >>=20 > The router can send them a redirect if it chooses. On a cache miss the > packet is forwarded like normal. You are missing the point. Forward to where? How? Dino