Re: [lisp] Rechartering Thread 1: Promised work item: work items currently in the charter but not finished

Dino Farinacci <farinacci@gmail.com> Tue, 28 March 2023 01:56 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 5C60AC17B32A; Mon, 27 Mar 2023 18:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.098
X-Spam-Level:
X-Spam-Status: No, score=-7.098 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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id b-c4Hv0rN_02; Mon, 27 Mar 2023 18:56:19 -0700 (PDT)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FAFFC17B329; Mon, 27 Mar 2023 18:56:19 -0700 (PDT)
Received: by mail-pg1-x536.google.com with SMTP id d8so6319392pgm.3; Mon, 27 Mar 2023 18:56:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1679968578; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=b+3HmAoUMbhGQDRk5pBmoPVO8d3odU05i2QClY7F5R0=; b=j5yx2gy44X5aaUAxtIgNmaBp5KEVwEJO8LLhafzwz/MP2Jg+jHf5SkTxjpUoV1TFFE 0nUyVZ64mPe+fq8+3q2msGHDh+xhRMwXvwqSS/pOdRs+gacKrUTqEiW24J9g8FsnlfuO 88evEtCyU2op/wJjrJnBFU7PeCAxANQ+G9xI92eVQ0BcwnDUrOP+1rvUyWEdXJDJuSEp IWTM4U6GWOQ3g/ncW/4cKk8hXV1o9KhM/2yMxcntGI1UPpWlN9DNvq4Qc9k/vM8tKDT6 OFlCjyZPqAmxghbvuYbuwu4uoVaXzfDcojckFCxlQ8+LYDgNgVfP4FwQ8ukINPDrsuLq w8vA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1679968578; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=b+3HmAoUMbhGQDRk5pBmoPVO8d3odU05i2QClY7F5R0=; b=ePKrLJlYU+q9Xmm+UoA6DG4X502PX8zW1I4UrJmm76H9TVuxe8FL5yS9wjG4xykpyi d/50KBzcrxQtkSZJh6xVuTgpyCtOE/KHpN6Ln34bhB+/8ki6KeVmnORHN5v2OWwa3icb MEN9IsJ/Vv/ugBgZBG3VHlbyB1Pd3iHAemaQGv3yJLvWmtmDBiukGlWyPPLgxvFiOFMg L52qJuqAMolTug/3b8Ap9aEb8HUwrVEzByy2WY45mo2STjgKe6nR7Gb9kMLjStDlIsDv OeDrEdJnFtWb+R66L2wTPgOPAZ0l1dsU/PX/eFfKcDy5JosRPk9XAO+Ll8z5XeA43j5g Ffng==
X-Gm-Message-State: AAQBX9fnJg9MoSidvOWPozJWqKFQdKlMh45CmmlIflibzp4QM2JjpepI 8sNENi+e4mD5qYJmMtv/9qc=
X-Google-Smtp-Source: AKy350ZHgnnaBVjKGdWtw7JsVog0YNKuhu4NJKY6voIgm4FOEEeBhrVwHbEIvz2MevqhuZ+DCN/9bw==
X-Received: by 2002:a62:198a:0:b0:5a8:ba74:7a7b with SMTP id 132-20020a62198a000000b005a8ba747a7bmr11761760pfz.1.1679968578302; Mon, 27 Mar 2023 18:56:18 -0700 (PDT)
Received: from smtpclient.apple ([2001:67c:370:128:94eb:b6a4:bb3d:f2fc]) by smtp.gmail.com with ESMTPSA id v20-20020aa78094000000b006089fb79f1esm20206420pff.96.2023.03.27.18.56.16 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Mar 2023 18:56:17 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.400.51.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CF1C6CCB-183E-42B4-B8C5-19380CEB7066@cisco.com>
Date: Tue, 28 Mar 2023 10:56:04 +0900
Cc: Albert López <albert.lopez@upc.edu>, "lisp@ietf.org list" <lisp@ietf.org>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <08B1FF07-86B2-4318-8CA1-5E28FA996431@gmail.com>
References: <9D45B7AA-2534-4F12-93FA-3B461EA3829B@gigix.net> <f9a1cc3e-ddea-7116-1c14-542ac4a2f931@upc.edu> <595FB753-8CB2-4FEC-AA89-2A4FEE53999F@gmail.com> <CF1C6CCB-183E-42B4-B8C5-19380CEB7066@cisco.com>
To: Fabio Maino <fmaino@cisco.com>
X-Mailer: Apple Mail (2.3731.400.51.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/knRmUuyyJFlcu_DkASjY4Wd3Yr0>
Subject: Re: [lisp] Rechartering Thread 1: Promised work item: work items currently in the charter but not finished
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 28 Mar 2023 01:56:21 -0000

> Dino, 
> Back then Albert Lopez, Vina and others invested quite some time addressing in draft-ermagan-lisp-nat-traversal a lot of corner cases that were coming from mobiity. 
> 
> Before we move forward with a NAT document we should make sure we either explicitly leave out those use cases, or address them. 

Agree, just having basic LISP NAT-traversal standardized, or even just documented, should be our key goal. Or it limits LISP deployments to virually no where. Meaning, just within firewall/security domains.

Dino