IETF Logo Mail Archive

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

Padma Pillay-Esnault <padma.ietf@gmail.com> Mon, 16 October 2023 23:46 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 B38D2C15198F; Mon, 16 Oct 2023 16:46:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 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, HTML_MESSAGE=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 Hl6TFBIfSFWa; Mon, 16 Oct 2023 16:46:23 -0700 (PDT)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::22a]) (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 47280C14CF12; Mon, 16 Oct 2023 16:46:23 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id 38308e7fff4ca-2c5087d19a6so44904171fa.0; Mon, 16 Oct 2023 16:46:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697499981; x=1698104781; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=4LhmFd+f/h3o3A/Qg+pQjLQr3kFMISy1ROkDh1F61uE=; b=dOimS1jj4v0RJEXDVjg2CBtmFebx+XrVYzn9RvyBgWEWs8WO1U5jdhyVi6QhUY9Tke yhHVqPzRgW2K2vlszZq6YYq/JeBnbtwOGihALYgxWl17ynGwoN86OJxVAcmCQvpkSixM 6ZV9AiGNZEmPQYrwPDayKE4hc95k5VPaZyLLEn/ygcMQv9NEdZnNdoSTeMRGa84M4E4b /BI+/Hpb4E0skoDNW1X3we9hwb5zfSv3WfgHu7FzJGytCmIqd+d2pcAONLOz9nUQZ7Z7 XDZI7FIeZd1Ubtr4NozH2pXNLcDJEfshC8LFeag+hSTnnhXq12V9ku/qhNhqlcZMUCLK Zv7g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697499981; x=1698104781; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=4LhmFd+f/h3o3A/Qg+pQjLQr3kFMISy1ROkDh1F61uE=; b=TM1+o8hOwNEyZXZcjVzO13enRiA0YM2vCy5CLbZHJx0s6LQ8VNPEEsWCvnbCBk3txd 6y8sxFoocYfjbUdXzoTWDz2Zb1/HhEppQurg7pyGal0ZsOrJZ8Ufr/oDk3G9yqJ3dZCZ J4d5VxQnOvPX02qTlafEU7pRQ8QYJrqWtipKzY8klssDjqMiH3F8rlsr+zr4Tsn6wUeD xHnosnb0U3KgYmPe5DgRqGm/Q+sEvLkB5V5x59sU1hdDAVzIXjDtZvREI3jVjqQ569p4 gLBJpifjLOx3UXO7WnY7dr7R4JfU3h8MqO1Opmtuu5zH58oqACdU/s+x9viXUEW0zBcN NFKA==
X-Gm-Message-State: AOJu0YyWlVG/sco1H/SykoJ4bDk1cbFN0PshnLd2b3FX305J+TW3sdNB kYrVOSMJo25LV9YZxyUN5tTBvXDMxYJNlivbGDE=
X-Google-Smtp-Source: AGHT+IHXfkgfEr6+RbRZb+KPLT2RUdRdSU/vzOsh0z0JYviRVMvbjhQswtHFZ6ERZop1Cs+2zSBhbnm0zRYtq95mG/w=
X-Received: by 2002:a05:651c:220a:b0:2bc:f2d7:f6ce with SMTP id y10-20020a05651c220a00b002bcf2d7f6cemr564450ljq.49.1697499981179; Mon, 16 Oct 2023 16:46:21 -0700 (PDT)
MIME-Version: 1.0
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>
In-Reply-To: <E1B3025C-8D86-4634-9B0F-FA1F39BCA3BD@gmail.com>
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Mon, 16 Oct 2023 16:46:10 -0700
Message-ID: <CAG-CQxpctqd+kxyGXxBaCNd7bPfOEyYrkfrcaoSFNXHCcGGXdA@mail.gmail.com>
To: Dino Farinacci <farinacci@gmail.com>
Cc: Luigi Iannone <ggx@gigix.net>, LISP mailing list list <lisp@ietf.org>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006270b30607de0350"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/fkKHtRaR6eME6aVtZ7YJaOdcVI0>
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:46:23 -0000

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