IETF Logo Mail Archive

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

Padma Pillay-Esnault <padma.ietf@gmail.com> Wed, 15 March 2023 12:11 UTC

Return-Path: <padma.ietf@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 1D723C15152D; Wed, 15 Mar 2023 05:11:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.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_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 FWRPkPX18TEB; Wed, 15 Mar 2023 05:11:24 -0700 (PDT)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 5C117C14CE3F; Wed, 15 Mar 2023 05:11:24 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id nv15so16175879qvb.7; Wed, 15 Mar 2023 05:11:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678882283; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=GsYed2/97bYn6uLFmIxKQlIxPkOewf96wwALwdn+8io=; b=brRSUBa95kvR4ZtrkbCturfB6ALtxDJX8J/WtrjKWpv3GAYVwlKlvxPlxMfjUrQ5sp A/2gbaxhM9x3iTNROoFMw6/H6K3HoxuUmeE6Ej9t421y4rBFCAHLQsi1wxwCqBw1WY9m /83zG3u/1jzpegMGom4kqz/LlRRensj3T4IYCcCfKYyucHh6hwmOUHIuBrzFA1NJ5tsk S/ddilCrt7aKuA40uw66jIJ818NKzukysFrn9F4IQNKq7qbaXHBqYtieGSKAUrHTOhx3 t8H86AOiqgFStHs7GLKauHdriuB4EO9LuBKe4OUeh6iiFHzL6YQhbnqbzK3HgthhdfK2 VJ7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678882283; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=GsYed2/97bYn6uLFmIxKQlIxPkOewf96wwALwdn+8io=; b=XgRzghXFRRWRwubUTnsBj3zhlhX0R0tjflRvUqBFgPlytHuX4OW4hnyTiZAyyKNzct 05FSDgCzKgxGUjzWPqEJx5PMgbaxSQOvgpYnFPHoIXiUTa6AwYccf7VNNtwPuShBonBT ficdaMkF4hCmgH2htH5uryj2OyALmmgw7aKKevxLu8YPQNY3CUi7qee9miJ3ygkONQro +7yc+7sMIOloKC1RXbVIccl5Aj+DBr2KGAKL42YpoOyA6AEdxtFj5urD7dta9hPdoi6D qSoyByTKsPQ2Zzne9IGJ50CGCVzpR5y5LhFS5s8gY/imBq797qF8McrgchPzCFmdebAt mMGA==
X-Gm-Message-State: AO0yUKXd0PohrNFz8J6aUZiH62kM6gJ1WiexmkQzKyWrrVJCGaF1S31n te20KGRiKuTOLrzy/N4ZHh9++82SIW4=
X-Google-Smtp-Source: AK7set8i3KVVJHwKaORSeT8EDMWWua4q7hD9j2y2iRBRf0V+25xVU0a9NdMDuTHUy7EJphGfCzSZEw==
X-Received: by 2002:ac8:7d12:0:b0:3bf:da83:f8d6 with SMTP id g18-20020ac87d12000000b003bfda83f8d6mr72779121qtb.28.1678882283219; Wed, 15 Mar 2023 05:11:23 -0700 (PDT)
Received: from smtpclient.apple ([50.234.228.35]) by smtp.gmail.com with ESMTPSA id bs37-20020a05620a472500b00738e8e81dc9sm3655148qkb.75.2023.03.15.05.11.22 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 15 Mar 2023 05:11:22 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 15 Mar 2023 05:11:11 -0700
Message-Id: <09DC0539-EFAE-4DE5-8F34-0F0CBFBDAB29@gmail.com>
References: <38D80C3E-80B8-4F45-A70C-4298F2944EC6@gigix.net>
Cc: Dino Farinacci <farinacci@gmail.com>, "lisp@ietf.org list" <lisp@ietf.org>, lisp-chairs@ietf.org
In-Reply-To: <38D80C3E-80B8-4F45-A70C-4298F2944EC6@gigix.net>
To: Luigi Iannone <ggx@gigix.net>
X-Mailer: iPhone Mail (20D67)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/UJsUC77ocjA49XCfsF_bd4NIImo>
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: Wed, 15 Mar 2023 12:11:26 -0000

Hi Luigi, Dino

See below PPE

Thanks
Padma

> On Mar 15, 2023, at 02:03, Luigi Iannone <ggx@gigix.net> wrote:
> 
> Hi Dino,
> 
>>> On 14 Mar 2023, at 20:35, Dino Farinacci <farinacci@gmail.com> wrote:
>>> 
>>> LISP Mobility: candidate document LISP-MN but does not solve everything should we enlarge the scope?
>> 
>> draft-ietf-lisp-eid-mobility as well. 
> 
> Right. We can have a general discussion about mobility and what kind of documents we need.
> Would lisp-mn and lisp-end-mobility be sufficient? Are there any other use cases? 

PPE- should we consider predictive rlocs draft as well? It covers predictive mobility.

>> 
>>> LISP Yang Model: We are pretty close to finish this one
>>> LISP NAT Traversal: we have a candidate document
>> 
>> And VPNs are in charter and used quite a lot in LISP deployments, so draft-ietf-lisp-vpn.
> 
> Good point.
> 
>> 
>> Alternative Mapping System Design is part of the charter and the only draft that is pending is draft-farinacci-lisp-decent but not sure this needs to be standardized.
>> 
>> And we need to decide the outcome of draft-ietf-lisp-te and control-plane security such as draft-ietf-lisp-ecdsa-auth and draft-ietf-eid-anonymity. I'm not sure they need to be standards track. 
>> 
> 
> They can still be experimental if WG is willing to publishing them. The charter may include a security/privacy work item and these documents would be covered.
> 
> Ciao
> 
> L.
> 
> 
> 
>> Dino
>> 
>

v2.23.0 | Report a Bug | By Email