IETF Logo Mail Archive

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

Robert Raszuk <robert@raszuk.net> Fri, 22 April 2022 20:17 UTC

Return-Path: <robert@raszuk.net>
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 A647F3A15D7 for <lisp@ietfa.amsl.com>; Fri, 22 Apr 2022 13:17:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.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, HTML_MESSAGE=0.001, 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=raszuk.net
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 bQCQ2lncA3ov for <lisp@ietfa.amsl.com>; Fri, 22 Apr 2022 13:17:40 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 5BB0D3A15DA for <lisp@ietf.org>; Fri, 22 Apr 2022 13:17:39 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id w1so16172438lfa.4 for <lisp@ietf.org>; Fri, 22 Apr 2022 13:17:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=raszuk.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sEwifm9U4BRLtZOt19aWsLsMzPMlWzCpQytzuvulOBA=; b=QfmLb4thqngzIbbSUfj3AEqtQpuHBWJcya+/fgAjUj8d54UlW/VD3yUtB0XM7UbRsL 1UWISL9TdGgi37uxrYs5HSuOvfQIY5X6sbReQfo3xbbjBnvo3VmzokPNA9G7l2r3N6kW IfDVFhCK2Ix8lvfO658VVl3F/gapyAnTbPoHJe6j7JUqqyc91ooniN8POxGRoMU6zzx2 DsRR0AVyqg7kB4TV5mzZFQWkHWIdpv/bb8FmERottlIH3RXzgojEuYy22iBWc7kYkNjj Mv1iYdTgxYgCXWDmhy1Mb0BPj4893t2ioB2dEJnuU8kn5iKLVznGk6RTrlEWIzrQFp4M YJCg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sEwifm9U4BRLtZOt19aWsLsMzPMlWzCpQytzuvulOBA=; b=ThoLcgGkAf4iHjSD+8qNr/hUyCEZ+a2WPDgDFOOfvzhfl2Ateo59WaHCrkfusT8X7p jWJ0zAksymPyBhPMz7Zm44V3PYC8P97MOz8D/O89buHnoL3HMYjpd2jsaRXjUhysyPrf tZSsTebe4zddp0U8avTcdrgCG2saR6lqtvaxA1L/KTE20Dznmdg06L4jg2Nlr/X1j0gC 1uu/XDNhkOSRIaahhqEdhNUYcOiq4sfI3QtmUt3QteTLKOrPyu2hFB4f+KSzgwbOtrjs KpU+7CHuWsNVtzbGmk08qC0SN8dPjAO0zTSHbBykZok6ILJglufx9C+Kvj9iEdcmcVG5 ba5w==
X-Gm-Message-State: AOAM533pGm+HvxhperPBxX6ffCp5YcIiVErJgjpSZbs+TydVuJcOgajf 9/BhkpUmnTb1NpQurUrWiUgQX6hw+XhnEaqnhS+SVTMgLLeFcw==
X-Google-Smtp-Source: ABdhPJySn8RyQp6uxnPO8kA2xaCve5NcUfCSPSUbVkDWaTAHIg3VCbilcLxHyyc2I5bO7WOI+qUeXLrJ1RUzwscm4SM=
X-Received: by 2002:a05:6512:318a:b0:471:8f3b:e2bd with SMTP id i10-20020a056512318a00b004718f3be2bdmr4250424lfe.129.1650658656437; Fri, 22 Apr 2022 13:17:36 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <CF1852EE-3684-4093-AA53-0F450C56CA18@gmail.com>
From: Robert Raszuk <robert@raszuk.net>
Date: Fri, 22 Apr 2022 22:18:56 +0200
Message-ID: <CAOj+MMG5XSSDB-z23fZwOPHFebntXYDcRtaDzgq6tespEHBMPA@mail.gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Cc: Luigi Iannone <ggx@gigix.net>, lisp-chairs@ietf.org, "lisp@ietf.org list" <lisp@ietf.org>
Content-Type: multipart/related; boundary="000000000000dd08ae05dd43eace"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/7T2BaqIimNwkAc3OpK__tKF_a04>
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:17:45 -0000

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:
>
>
> 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
>
>
>

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