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

Dino Farinacci <farinacci@gmail.com> Mon, 16 October 2023 23:36 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 E0EC9C1519BE; Mon, 16 Oct 2023 16:36:00 -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_DNSWL_NONE=-0.0001, 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 RhKdJQKRE7Ir; Mon, 16 Oct 2023 16:35:58 -0700 (PDT)
Received: from mail-oi1-x234.google.com (mail-oi1-x234.google.com [IPv6:2607:f8b0:4864:20::234]) (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 BDA0AC15198F; Mon, 16 Oct 2023 16:35:53 -0700 (PDT)
Received: by mail-oi1-x234.google.com with SMTP id 5614622812f47-3ae388eb437so3194058b6e.0; Mon, 16 Oct 2023 16:35:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697499352; x=1698104152; 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=iubEObZGkSDguBJgvp5OjHA9NScqb2kRDiwGji2UIn8=; b=EmsW+l0rBXzUYj9pZ/orMhJDfMvXGeTjruJKItuSqcXT4ureCFwonA/KtFJJQTyYVY hEXKDvFzeOxH8QH296NcXBvHcKe11pEblW4P56A1jEhZG+WTJ+284M4HIz/rWLBJSiUr +olHqwm1cXlLan+6qZBysHRYuzM2QiC//iXzXNEMKh2zMXzFMW88l9UJhVg05kpx87Xk KTR7r7z0m+vFEb9NVfj/C1fBC8JgsjUlxH95nPPuYJAU1ClIsrK+ijQvEnkZRyxiwFiu 0TRmNZQb3DhrMITTnstk5Os941XD/asUxP4ONfE1fn2eueH3TE7/qXh8zcWKvojTi/QS Stpw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697499352; x=1698104152; 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=iubEObZGkSDguBJgvp5OjHA9NScqb2kRDiwGji2UIn8=; b=VRFG+hVWKMokEWv815i5XBGJQhnSzahbhpnDFpKwJ4VqzTUhrgy+J1ifLlDu7EZmGL N7OVU5IZLW3MTbVU2JJkHGynkXGyt9TfpzyhDMA3JCP5vwKsAPwbs1jekQRO56K0KEpx gRri3lKX0Q5Rc/iTLyktpa+u1Iq5GjmyhjmRmKjMEQsFdYc9PGQAqfh9xg4U3lK54dDL ALXh2t+Sp+ixKkwvIMCToIrtgwrjDBkkobk5+d176Ip60uoYXfDijmqWGj73Z4G6tWmY gZg7gDVGgVgBIKEyBPVA89qg9PjtCZgZtetd2uZRJHL7zuxwr+BP1kpybnsWZxyvxasT f4Mg==
X-Gm-Message-State: AOJu0Yw6sPWvIAzzgTXuvdjCV61hlaToQpmnv3nBHFy1equTQU1bVuNU PeiiTze0MO++XtUUUgGvMa8=
X-Google-Smtp-Source: AGHT+IGGLzCckFpRi6DByLXhdEiFO48kzkoW2INnSZfVHEvZn4o97cS7MQi0Qef8aHt77Byu1D5HoQ==
X-Received: by 2002:a54:4516:0:b0:3ad:d577:c64a with SMTP id l22-20020a544516000000b003add577c64amr134689oil.15.1697499352413; Mon, 16 Oct 2023 16:35:52 -0700 (PDT)
Received: from smtpclient.apple ([2600:381:4c0a:29ec:8e1:d90a:a4be:e5a]) by smtp.gmail.com with ESMTPSA id x3-20020a4ac583000000b0057346742d82sm49463oop.6.2023.10.16.16.35.51 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 16 Oct 2023 16:35:52 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <CAG-CQxqz2LZ-KU7d4DyEoHrsbP+p8tJ7OM2m4M5g7nnGfqVQrg@mail.gmail.com>
Date: Mon, 16 Oct 2023 16:35:40 -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: <E1B3025C-8D86-4634-9B0F-FA1F39BCA3BD@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>
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/UDIo-Uc3jX_fZKnb3S7-MexkU_s>
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:36:01 -0000

> 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