IETF Logo Mail Archive

Re: [5gangip] BOF Description

Saleem Bhatti <saleem@st-andrews.ac.uk> Tue, 06 February 2018 14:30 UTC

Return-Path: <saleem@st-andrews.ac.uk>
X-Original-To: 5gangip@ietfa.amsl.com
Delivered-To: 5gangip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 692D512D7EE for <5gangip@ietfa.amsl.com>; Tue, 6 Feb 2018 06:30:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.23
X-Spam-Level:
X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=universityofstandrews907.onmicrosoft.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 cbmI9uMwBXs2 for <5gangip@ietfa.amsl.com>; Tue, 6 Feb 2018 06:30:33 -0800 (PST)
Received: from mcgraw.st-andrews.ac.uk (mcgraw.st-andrews.ac.uk [138.251.8.95]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 44AE912D7EA for <5gangip@ietf.org>; Tue, 6 Feb 2018 06:30:33 -0800 (PST)
X-StAndrews-MailScanner-From: saleem@st-andrews.ac.uk
X-StAndrews-MailScanner-ID: w16EUOPH006974
X-StAndrews-MailScanner-Information: Please contact the ISP for more information
Received: from wallace.st-andrews.ac.uk (wallace.st-andrews.ac.uk [138.251.9.23]) by mcgraw.st-andrews.ac.uk (8.14.9/8.14.9/Debian-4~bpo0+uos) with ESMTP id w16EUOPH006974 (version=TLSv1/SSLv3 cipher=ADH-AES256-SHA bits=256 verify=NOT); Tue, 6 Feb 2018 14:30:25 GMT
X-StAndrews-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-1.9, required 5, autolearn=not spam, BAYES_00 -1.90, T_DKIM_INVALID 0.01, T_RP_MATCHES_RCVD -0.01), not spam (whitelisted), SpamAssassin (not cached, score=-4.2, required 5, autolearn=not spam, BAYES_00 -1.90, RCVD_IN_DNSWL_MED -2.30, T_DKIM_INVALID 0.01, T_RP_MATCHES_RCVD -0.01)
X-StAndrews-MailScanner: No virus detected, No virus detected
Received: from unimail.st-andrews.ac.uk (exch13-srv04.st-andrews.ac.uk [138.251.9.21]) by wallace.st-andrews.ac.uk (8.14.9/8.14.9/Debian-4~bpo0+uos) with ESMTP id w16ETloX031201 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Tue, 6 Feb 2018 14:29:48 GMT
Received: from exch13-srv01.st-andrews.ac.uk (138.251.8.22) by exch13-srv04.st-andrews.ac.uk (138.251.9.21) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 6 Feb 2018 14:29:47 +0000
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (213.199.154.211) by exch13-srv01.st-andrews.ac.uk (138.251.8.22) with Microsoft SMTP Server (TLS) id 15.0.1210.3 via Frontend Transport; Tue, 6 Feb 2018 14:29:46 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=UniversityofStAndrews907.onmicrosoft.com; s=selector1-standrews-ac-uk0e; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=KkgG4MiFNJ67TbXDAIFauA4pqYptZm5q36KQzHKrLwk=; b=d/XkoG29cTNl7974eacCf1hezmJFf9tLLtUzB0ztVwbY4Ued2weBjvUTz59UAgtRhF4ng2A8JEPtq566aON01ErxEbp95iYOiBu4F/j9OoZOm0gps11wtDEqnd65cpVrFhfFRkjXgUCeDLkb+nmjSbwiOB+nV/bJMXNOM2Fre+s=
Received: from DB6PR0601MB2469.eurprd06.prod.outlook.com (10.169.213.151) by DB6PR0601MB2533.eurprd06.prod.outlook.com (10.168.81.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.464.11; Tue, 6 Feb 2018 14:29:46 +0000
Received: from DB6PR0601MB2469.eurprd06.prod.outlook.com ([fe80::c0e1:6d41:9279:47ad]) by DB6PR0601MB2469.eurprd06.prod.outlook.com ([fe80::c0e1:6d41:9279:47ad%18]) with mapi id 15.20.0464.016; Tue, 6 Feb 2018 14:29:45 +0000
From: Saleem Bhatti <saleem@st-andrews.ac.uk>
To: Dino Farinacci <farinacci@gmail.com>
CC: Lorenzo Colitti <lorenzo@google.com>, 5GANGIP <5gangip@ietf.org>, Behcet Sarikaya <sarikaya@ieee.org>, "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>
Thread-Topic: [5gangip] BOF Description
Thread-Index: AQHTm5PIwoiwqB6UFUexDQxmCEVQY6OQndyAgAaKR4CAADhlAIAAEtuAgAABAwCAAAJPAA==
Date: Tue, 06 Feb 2018 14:29:45 +0000
Message-ID: <859A4E8E-DFF8-482C-9A46-525EB1ABC227@st-andrews.ac.uk>
References: <CAC8QAcdEgP1Lbfm64QJVONzDOXTLALXOkihyz2MV4Euo6avSHg@mail.gmail.com> <CAKD1Yr1iFGGec_6zsvbpx2-8-eTq+EMcwZWaHV9PwWqdEVBiaQ@mail.gmail.com> <91A70D5E-0893-417F-A98E-8E2C48003362@st-andrews.ac.uk> <F7A4CBF0-A7D8-476C-B832-5949723671D4@gmail.com> <8B7DC9A0-DE8C-48C4-98AC-EF3950D096B0@st-andrews.ac.uk> <917F62FB-1874-421D-8B9E-A6266638F9CB@gmail.com>
In-Reply-To: <917F62FB-1874-421D-8B9E-A6266638F9CB@gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=saleem@st-andrews.ac.uk;
x-originating-ip: [2001:8b0:d3:1:5181:c7f:75e9:d126]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0601MB2533; 7:pKu+zadgEpmagaBzO2HF473wmuEJbKCMzykBrVR0r4GuY2tH5loOaX1wLrfnmyDYzzU5Pz8r8hxWyHQ89mh3GH1tjV1zXN6nu8/2AhZzzrDD44DmfznqaFGRm8FLmS0KdrL3e5QWg2ryv6hWKvPD47THzDhy3hjpa4WGEG+dGkTsLqvRMm9mnpJBLzwb2XctQEHmTu+Xr5a51vVk2uERp2fBoPQH2YBavIYveH38yXG99B/E/UqWJk+tnaWiCtiR
x-ms-exchange-antispam-srfa-diagnostics: SSOS;SSOR;
x-forefront-antispam-report: SFV:SKI; SCL:-1; SFV:NSPM; SFS:(10019020)(346002)(366004)(39380400002)(396003)(39860400002)(376002)(199004)(189003)(5250100002)(83716003)(478600001)(3660700001)(786003)(3280700002)(93886005)(4326008)(99286004)(186003)(36756003)(102836004)(229853002)(59450400001)(966005)(76176011)(53546011)(6506007)(68736007)(39060400002)(1411001)(6486002)(6436002)(106356001)(33656002)(81156014)(105586002)(86362001)(6246003)(6306002)(6116002)(25786009)(82746002)(6512007)(97736004)(14454004)(42882006)(8936002)(6916009)(53936002)(316002)(8676002)(2950100002)(305945005)(7736002)(2900100001)(74482002)(81166006)(54906003)(11609785009)(2906002)(5660300001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0601MB2533; H:DB6PR0601MB2469.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
x-ms-office365-filtering-correlation-id: ba500d85-d9e0-4c1e-2b7d-08d56d6e11eb
x-microsoft-antispam: UriScan:(36968037445663); BCL:0; PCL:0; RULEID:(7020095)(4652020)(8989060)(5600026)(4604075)(3008032)(4534165)(4627221)(201703031133081)(201702281549075)(8990040)(2017052603307)(7153060)(7193020); SRVR:DB6PR0601MB2533;
x-ms-traffictypediagnostic: DB6PR0601MB2533:
x-microsoft-antispam-prvs: <DB6PR0601MB25338EAD49082BA4047A8461A7FD0@DB6PR0601MB2533.eurprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(76576733993138)(165104125076784)(158342451672863)(85827821059158)(36968037445663)(148501403981450)(211936372134217)(153496737603132);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040501)(2401047)(8121501046)(5005006)(10201501046)(3002001)(93006095)(93001095)(3231101)(2400082)(944501161)(6041288)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(6072148)(201708071742011); SRVR:DB6PR0601MB2533; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0601MB2533;
x-forefront-prvs: 0575F81B58
received-spf: None (protection.outlook.com: st-andrews.ac.uk does not designate permitted sender hosts)
x-microsoft-antispam-message-info: OIvLaEJHbcnHa1W344CrzGOifdAjtFnWSs5qTSqld+nmDGfd+i4RRlGI1KeleAXdCs6dw0Tw5IXYe8jf3s1twA==
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <D4433E0FEE854148B621D697BDA8FE0F@eurprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: ba500d85-d9e0-4c1e-2b7d-08d56d6e11eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Feb 2018 14:29:45.5529 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: f85626cb-0da8-49d3-aa58-64ef678ef01a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2533
Archived-At: <https://mailarchive.ietf.org/arch/msg/5gangip/CR7i_CXm78feUgZF_z9ve_QCbio>
Subject: Re: [5gangip] BOF Description
X-BeenThere: 5gangip@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Discussion of implications of the upcoming 5th Generation \(fixed and\) Mobile communication systems on IP protocols." <5gangip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/5gangip>, <mailto:5gangip-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/5gangip/>
List-Post: <mailto:5gangip@ietf.org>
List-Help: <mailto:5gangip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/5gangip>, <mailto:5gangip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Feb 2018 14:30:36 -0000

Dino;

> On 06 Feb 2018, at 14:21, Dino Farinacci <farinacci@gmail.com> wrote:
> 
>> 
>> Why not just set a low TTL value for the DNS RRs (e.g. 1s or 0s)?
> 
> Then that increases request load when there are no locator changes. 

a) Only need to change / set low TTL for DNS RRs that move.

b) Even if that is all the nodes, then the additional load in DNS is not significant - please see:

    Reducing DNS Caching.
    14th IEEE Global Internet Symposium (GI2011), Shanghai, China. 15 April 2011.
    http://dx.doi.org/10.1109/INFCOMW.2011.5928919
    https://goo.gl/z31vAF    

Cheers,
--/Saleem


> 
> Dino
> 
>> 
>> Cheers,
>> --/Saleem
>> 
>> 
>>> 
>>> Dino
>>> 
>>> On Feb 6, 2018, at 6:48 PM, Saleem Bhatti <saleem@st-andrews.ac.uk> wrote:
>>> 
>>>> Lorenzo;
>>>> 
>>>>> On 02 Feb 2018, at 05:56, Lorenzo Colitti <lorenzo@google.com> wrote:
>>>>> 
>>>>> On Fri, Feb 2, 2018 at 4:34 AM, Behcet Sarikaya <sarikaya2012@gmail.com> 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
>>>>> 5gangip@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/5gangip
>>>> 
>>>> _______________________________________________
>>>> 5gangip mailing list
>>>> 5gangip@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/5gangip
>>

v2.45.0 | Report a Bug | By Email | System Status