Re: [lisp] Draft-kouvelas-lisp-map-server-reliable-transport WG Adoption

Dino Farinacci <farinacci@gmail.com> Fri, 22 April 2022 20:41 UTC

Return-Path: <farinacci@gmail.com>
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 A86C33A1918; Fri, 22 Apr 2022 13:41:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level:
X-Spam-Status: No, score=-7.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 tSp3wQCGk47k; Fri, 22 Apr 2022 13:41:00 -0700 (PDT)
Received: from mail-pl1-x632.google.com (mail-pl1-x632.google.com [IPv6:2607:f8b0:4864:20::632]) (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 612013A1917; Fri, 22 Apr 2022 13:41:00 -0700 (PDT)
Received: by mail-pl1-x632.google.com with SMTP id c12so13322156plr.6; Fri, 22 Apr 2022 13:41:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uv8256VxX2GNuRuv4F+6oQ6Q4TLo0F0dasoMoHPC8NY=; b=YXXMruRliFRK49i0DzW1IickOt+r+ZCqe+RVX4A3rITBBEfHLoQmpaaLin/YBZiLqD qHfjtfbV2Fq3MlnvOeimOtBKILiLGc5bmq5X5i+PZm4TONig1StFeWAEOr5484SkpmEq BD/EEiVm2qZcMAiIkaKLj7+nyptG2lZZqSlefqtlsTvax77J/sZV3Upz6XD1MueiTnQv YcuAbrI3gKTDmjdDMY+nejNC8v0NnIVSQ9TMV2mKchxAHlrqoS60U7JHtAtfCmbUkYpP MnOmB2R6hxS19tGPTE6RW896LOXp4acOeUO/IFiU1JZ1CNjGuAVWLyXOpNfOiA2RYNzs B1XA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=uv8256VxX2GNuRuv4F+6oQ6Q4TLo0F0dasoMoHPC8NY=; b=zGI4AFUoLhRT9XgsfEak0WAXLV9p6/8fZ2DaSubfhytilgH5yXlbafUbjut0hgCcC2 aqdD5AB/Iz+rJY3qKm20oMlZQZGPh1EwoAisrpFdy6ZYnBriiX9FcLPKVb01M685crwN 2WonAJ0h3rQWh6RKW4lc1ixH/ubjTTp92fVD0Z+C+avIiVonWjEp5ZbU9S4SbPrLk4sg 0zLBQPoXx4e1qWsBUWdU/TSyNobWMRHHsoSOCZnzube52SexQVWN//+Y83/burnZb+Iv gpfkhwNuAPkj7PAjIL0YsXg8u/ckNzY4RdAcw0Ca8Mm3hBzOx/XO1la6KSPjbQZcesF1 p5TQ==
X-Gm-Message-State: AOAM532S3Wrgk3QqKsrh/9Q4/lMMJ86aVmmXklcWj0sk40SEomzTE4tf LgXHepB3aotkv6Td0mBnGrI=
X-Google-Smtp-Source: ABdhPJxgp3rKy2xMucSi5zHiPeB1N4lUp3d89UwwV8UFC1mc+VwtsxsFyIM5zZ0EgJilYZy2do8ukQ==
X-Received: by 2002:a17:902:70c1:b0:154:667f:e361 with SMTP id l1-20020a17090270c100b00154667fe361mr6447954plt.148.1650660059637; Fri, 22 Apr 2022 13:40:59 -0700 (PDT)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id l7-20020a17090a150700b001cd4989fec3sm6925853pja.15.2022.04.22.13.40.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Apr 2022 13:40:59 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <E54406EF-5CAF-4492-90C0-8E9A99BCC07B@gmail.com>
Date: Fri, 22 Apr 2022 13:40:57 -0700
Cc: Luigi Iannone <ggx@gigix.net>, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6D2655D8-DC32-4EC6-A946-AEC4CDCF00B7@gmail.com>
References: <1F470969-4ECE-437A-8E1A-C005679F9422@gigix.net> <CAOj+MMG2qnYhRXEeyOOjPuaAD4ZYcvP9wyUBiqGECrzUupLyew@mail.gmail.com> <73F7376E-B22B-488A-8503-B91F11D965AB@gmail.com> <CAOj+MMEVLzvuy2ZUS=5uzgVnj3xmF_C2LQSYOMUZ4E7xvy_GQw@mail.gmail.com> <CF1852EE-3684-4093-AA53-0F450C56CA18@gmail.com> <CAOj+MMG5XSSDB-z23fZwOPHFebntXYDcRtaDzgq6tespEHBMPA@mail.gmail.com> <E54406EF-5CAF-4492-90C0-8E9A99BCC07B@gmail.com>
To: Robert Raszuk <robert@raszuk.net>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/-HhuDuqE_4_eiIeRYSGJE5MDJ64>
Subject: Re: [lisp] Draft-kouvelas-lisp-map-server-reliable-transport WG Adoption
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Apr 2022 20:41:05 -0000

Actually there is, predictive-rlocs. No messaging is better than .5 RTT in control-plane. But might not be fair to compare since you have to send data to more places that may get dropped.

Dino

> On Apr 22, 2022, at 1:39 PM, Dino Farinacci <farinacci@GMAIL.COM> wrote:
> 
> Nothing is better than .5 RTT.  ;-)
> 
> Dino
> 
>> On Apr 22, 2022, at 1:18 PM, Robert Raszuk <robert@raszuk.net> wrote:
>> 
>> Hi Dino,
>> 
>>> If you use a transport layer that requires connection setup, it will slow down handoff time when EIDs are moving.
>> 
>> But quic connection setup is just 3 RTTs. Is that an issue ? 
>> 
>> Thx,
>> R.
>> 
>> On Fri, Apr 22, 2022 at 8:40 PM Dino Farinacci <farinacci@gmail.com> wrote:
>> The others know to add quic, it was part of a discussion on how to open sockets using QUIC and which port numbers to use. That text is coming. The drfat does intend to support multiple transports. Here is one excerpt that proves that:
>> 
>> <Screen Shot 2022-04-22 at 11.37.47 AM.png>
>> 
>> QUIC will be added to the list above.
>> 
>> To answer your second question. If you use a transport layer that requires connection setup, it will slow down handoff time when EIDs are moving. So in that case, a Map-Reqister should just be sent over UDP. And on the Map-Request side you will require an RTT before getting the map-cache populated.
>> 
>> Dino
>> 
>> 
>>> On Apr 22, 2022, at 11:11 AM, Robert Raszuk <robert@raszuk.net> wrote:
>>> 
>>> Hi Dino,
>>> 
>>> Before I hit sent I did search the draft and did not find any match on QUIC :( 
>>> 
>>> But to your question - yes. I see no reason why LISP control plane could not be running over QUIC. 
>>> 
>>> Best,
>>> R.
>>> 
>>> On Fri, Apr 22, 2022 at 7:59 PM Dino Farinacci <farinacci@gmail.com> wrote:
>>> The draft indicates QUIC can be used as a reliable transport. But are you saying QUIC should be used for all LISP messages?
>>> 
>>> Dino
>>> 
>>>> On Apr 22, 2022, at 6:35 AM, Robert Raszuk <robert@raszuk.net> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> May I ask for reasons not to use QUIC instead of home made UDP based transport followed by TCP ? 
>>>> 
>>>> Many thx,
>>>> Robert
>>>> 
>>>> On Wed, Apr 20, 2022 at 9:42 AM Luigi Iannone <ggx@gigix.net> wrote:
>>>> All,
>>>> 
>>>> During the last LISP WG meeting in Vienna/Meetecho the authors of the draft:
>>>> 
>>>> LISP Map Server Reliable Transport
>>>> https://datatracker.ietf.org/doc/draft-kouvelas-lisp-map-server-reliable-transport/
>>>> 
>>>> Asked for adoption as WG document.
>>>> Call for adoption during the meeting showed clear consensus.
>>>> This email is the usual procedure to confirm the consensus on the mailing list.
>>>> 
>>>> If anybody has concerns about adopting this document please state so on the mailing list before May 5th 2022. 
>>>> Please also argument the technical reason why you have concerns.
>>>> 
>>>> Ciao
>>>> 
>>>> Luigi & Joel
>>>> 
>>>> 
>>>> _______________________________________________
>>>> 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
>>> 
>> 
>