IETF Logo Mail Archive

Re: [lisp] WG work items list [WAS: Re: Proposed WG Charter on GitHub]

Dino Farinacci <farinacci@gmail.com> Mon, 16 October 2023 23: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 02465C14CF12; Mon, 16 Oct 2023 16:56:05 -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, FREEMAIL_FROM=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] 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 r2JXI_Ud1r1m; Mon, 16 Oct 2023 16:56:00 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 AC1CCC1516E0; Mon, 16 Oct 2023 16:56:00 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id 46e09a7af769-6c620883559so3420534a34.0; Mon, 16 Oct 2023 16:56:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697500559; x=1698105359; darn=ietf.org; 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=AqyoP+TdrCydCH9NNCkH9xpG7VEjWiFUFObYRImovx8=; b=Hs1Zv2rHMYVpPF2nJoe0moaOwFFF5kntDDMWSWd9qJGczAswzTPmu/f3mSaxO0bvFi ASPubFSlJdjm5WPGwVLKKy/IQoK6Tq4eyRGae+miW6N43nLuRC0c8EIXoOiaicmiDv6M rrmx6BlBverJIHH1YIjZcnQeHtOfgIrlmKlkEbq6dFRl513NX8bzwh70duiigNNSERIR QpV4rwvlSGqa757a/NDX2tnJV3nhdcucGfVwIuz9A2W0TzjoEYPZ6w7UJN6BInelo451 Jbzp2vKinaNqK93mFN3jX3GVhXrSiWgFus51S+6d8mF0ZibvHqOs2ty3bsJDq10TcdDV JRiA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697500559; x=1698105359; 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=AqyoP+TdrCydCH9NNCkH9xpG7VEjWiFUFObYRImovx8=; b=ZmNHacZopZHfliDblmLXbYd9abRwEpflFCrYYLvYlzBWCNRVOfURigAZfBWva8e7vu nxrGNMz1zi/QO+hm56co3GA6XH3TibzFflXYqkGhQe4pMly35Ke+LwygPuMMYqGk+Vdg 4It8ttF6DZ5S/42g81pxQt8QCX+FUfCZyW6xU/XuUpZTDKyYhwFeYXT/A2rzTtf9bPtL lvqoSbMR5MetVFJYuAcQ9pF16tYPP3Y1dqOIuXDe8qarXn1sSCFsQSzRFJcstMPNyVtQ j8IPKQ/8d2TnKp8DhVFxNYqlfwU0/mqk2fecMObCj3MjlhxV2USDMs8151raz0Kmxk8e wq2w==
X-Gm-Message-State: AOJu0YxgfCNo57ztQKUtCT/9yd5nZ6et6p5O7B9p3TKNaSc4NmqMva5e KX/HdqyuxI7cKsCubE5Kv54=
X-Google-Smtp-Source: AGHT+IH/j4X6IhCJJIKJ1/SvA329Ep/iRqRt/sUenrYpHduXp70La2YYVhVx4N8zM/3ERrbCYjpNNA==
X-Received: by 2002:a05:6870:9a99:b0:1e9:907b:1642 with SMTP id hp25-20020a0568709a9900b001e9907b1642mr703327oab.16.1697500559487; Mon, 16 Oct 2023 16:55:59 -0700 (PDT)
Received: from smtpclient.apple ([2600:381:4c0a:29ec:8e1:d90a:a4be:e5a]) by smtp.gmail.com with ESMTPSA id n21-20020a056870a45500b001e12bb81363sm49011oal.35.2023.10.16.16.55.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Oct 2023 16:55:59 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAG-CQxpctqd+kxyGXxBaCNd7bPfOEyYrkfrcaoSFNXHCcGGXdA@mail.gmail.com>
Date: Mon, 16 Oct 2023 16:55:47 -0700
Cc: Luigi Iannone <ggx@gigix.net>, LISP mailing list list <lisp@ietf.org>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C48EA7D9-BB89-42E2-92B7-3E9E2BF93BD3@gmail.com>
References: <CAG-CQxqkFVNq_wOFZuK7D6hEz__2mjtZkuu3Z=S-vBKxoJwdfw@mail.gmail.com> <BYAPR11MB359144DF24114292D527D35AB6CCA@BYAPR11MB3591.namprd11.prod.outlook.com> <7AA2F620-1223-4C17-A3D8-3F9D2AFEDBF5@gigix.net> <CAG-CQxpcLLQousw0qByP_nVYPSDe5j7g7E92J2HVA5d34TQ3EQ@mail.gmail.com> <CAG-CQxp9SkyHtiqXhDi=L16h2wGRBO4q+gLLW4xQAkHFnNLaZw@mail.gmail.com> <93890FA3-2C5B-4A3A-AC9D-8D704DA0DF87@gigix.net> <1474F61C-549B-4EFD-A6DE-BE407232C2DF@gmail.com> <CAG-CQxqz2LZ-KU7d4DyEoHrsbP+p8tJ7OM2m4M5g7nnGfqVQrg@mail.gmail.com> <E1B3025C-8D86-4634-9B0F-FA1F39BCA3BD@gmail.com> <CAG-CQxpctqd+kxyGXxBaCNd7bPfOEyYrkfrcaoSFNXHCcGGXdA@mail.gmail.com>
To: Padma Pillay-Esnault <padma.ietf@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/X5O8yHBrXx18f26RC61M-4pspW4>
Subject: Re: [lisp] WG work items list [WAS: Re: Proposed WG Charter on GitHub]
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: Mon, 16 Oct 2023 23:56:05 -0000

June 24 for both LCAF related and mobility sets? Fine with me.

Dino

> On Oct 16, 2023, at 4:46 PM, Padma Pillay-Esnault <padma.ietf@gmail.com> wrote:
> 
> Hi Dino 
> 
> The groupings look good!
> 
> Some dates look too aggressive Nov 2023:  draft-ietf-lisp-geo, draft-ietf-lisp-name-encoding, RFC 8060 and 9306 (Standards Track). We are already there ...
> As the dates proposed are target dates, i suggest we keep the date of June 2024 but if we can go faster it is all good. thoughts?
> 
> Similar comment for mobility. 
> 
> Thanks
> Padma
> 
> On Mon, Oct 16, 2023 at 4:35 PM Dino Farinacci <farinacci@gmail.com> wrote:
> > What do you think of putting some major milestones for mobility and security sections rather than per document?
> 
> I think security is further out compared to mobility. Just because other groups will have to peer-review the security documents. But good suggestion and will incldue below the set that go together (IMO).
> 
> So here is what I suggest:
> 
> For June 2024: Mobility documents as a set to IESG, which include:
> 
>   draft-ietf-lisp-eid-mobility, draft-ietf-lisp-mn, draft-ietf-lisp-predictive-rlocs, draft-ietf-lisp-vpn
> 
> And for June 2025: Security documents as a set to IESG, which include:
> 
>   draft-ietf-lisp-crypto (RFC8061 to Standards Track), draft-ietf-lisp-ecdsa-auth, draft-ietf-lisp-eid-anonymity
> 
> And then, not related to what you asked for, to put all LCAF related stuff in one set:
> 
> For Nov 2023:
> 
>   draft-ietf-lisp-geo, draft-ietf-lisp-name-encoding, RFC 8060 and 9306 (Standards Track)
> 
> What do you think?
> 
> Dino
> 
> 
> 
> 
> 
> 
>

v2.23.0 | Report a Bug | By Email