Re: [lisp] Proposed WG Charter on GitHub

Padma Pillay-Esnault <padma.ietf@gmail.com> Thu, 12 October 2023 15:32 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 952FBC14CF0C; Thu, 12 Oct 2023 08:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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_DNSWL_BLOCKED=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 S5QOAvSa6jHH; Thu, 12 Oct 2023 08:32:19 -0700 (PDT)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450: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 0DF29C14F693; Thu, 12 Oct 2023 08:32:19 -0700 (PDT)
Received: by mail-lj1-x234.google.com with SMTP id 38308e7fff4ca-2c3c661f1a8so14018551fa.0; Thu, 12 Oct 2023 08:32:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1697124737; x=1697729537; 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=I8+qArm4s+M3jksnIRnfW3lmTsQtWUc7xFgBJpDUEiE=; b=jAcmlI4+fIi7njjIUzYYiYS2jXZboJniGvjBzYxGmIepfPjU2E8gj9Lq2M3A5/z4D2 RX5cBSHtiiNdpK84wpkhzF0fFIyXpAudgyy6NsBdXZggd6rDpxRHdVKlT84bLjO6YR2m I+mwWgTd8adpVLdhf2Z7J8e0M3jMvg4isdgq2N9Rws2Oi2Q3xnWit+Ws+RWTLFa+M/Pm rzbyPnbAKUH6PUbLtPVHfOYqwkt2vvr8UFQpunFOH1FJqem1ZNrsd+FeB/Z5scxAVk0O ovHugmakFvkakqa6rgwwJA6JgpAUitqq2RB9txmwWA128fklkDLNiWE2+ekcMbJmlSrL Jmdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697124737; x=1697729537; 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=I8+qArm4s+M3jksnIRnfW3lmTsQtWUc7xFgBJpDUEiE=; b=QohYMXx7a7rKYOqTN6k4NK7sZclIuV96tCMONdQKSnLiJGmQ79VoBff8cAWqPzunvt txvenQmIWu9Lrs69fRmzuKckceVgV1OWUQ9M8zZ8yp9HHJlnEl9QuZHAATZKU1++YSui eW0wgoVIV9oH8xxalg4ZSD5UBGuUbwoGVxrp1HCLIlVViMaQbsAtvMWH21fbpXB88640 gJknsmgrZkdsjVtOv0BCtYJH7rynxXgCiOltcGnEGaLGu2IVrNK+Bttdj2GyhBuM+Pwx T8n1T2cZVwGP1iLy99r3EocW623005F6mGgK0Lx/aBG/ZAgXKMYLa7fl+riXVYhzA1iR TSTg==
X-Gm-Message-State: AOJu0YwllcRVz3Tan3kNjGgmPWTqoxK5C9PSLE+PUlfnyNiro9gl23Qt VBmeDGiVnpgw3mV+HZ8sr6GSnx80J27Am+bzk8E=
X-Google-Smtp-Source: AGHT+IGJlLpS8NbMgH/ENFDRsm5DP00Ymq/RSjSQUUx7seBYtlEpeHenfg7jf9pfPYByZia+eKJj9q4rbVCU348zdQs=
X-Received: by 2002:a2e:bc21:0:b0:2c5:38d:f80b with SMTP id b33-20020a2ebc21000000b002c5038df80bmr127242ljf.6.1697124736908; Thu, 12 Oct 2023 08:32:16 -0700 (PDT)
MIME-Version: 1.0
References: <CAG-CQxqkFVNq_wOFZuK7D6hEz__2mjtZkuu3Z=S-vBKxoJwdfw@mail.gmail.com> <CAMMESsy46LBEmS539CM4BzHMVuX6TmrS1GQN3ssZkEs1jF60fg@mail.gmail.com> <C1FB78EB-EF2A-4956-92F3-D72548FD6309@gmail.com> <5471751F-D471-4E53-AC52-095B7B0923CA@gigix.net> <DM8PR11MB5622F5B7FF8BC9233AFD3D10CDCCA@DM8PR11MB5622.namprd11.prod.outlook.com>
In-Reply-To: <DM8PR11MB5622F5B7FF8BC9233AFD3D10CDCCA@DM8PR11MB5622.namprd11.prod.outlook.com>
From: Padma Pillay-Esnault <padma.ietf@gmail.com>
Date: Thu, 12 Oct 2023 08:32:05 -0700
Message-ID: <CAG-CQxqk6ONaYTnT6O9DVA3pVwGQkMj+JSv6fM+SW9Z60c5YCw@mail.gmail.com>
To: "Vengada Prasad Govindan (venggovi)" <venggovi@cisco.com>
Cc: Luigi Iannone <ggx@gigix.net>, Dino Farinacci <farinacci@gmail.com>, "lisp-chairs@ietf.org" <lisp-chairs@ietf.org>, LISP mailing list list <lisp@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001543fa060786a500"
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/L0PRvwPNn65yZawkFP0VB1b2vSk>
Subject: Re: [lisp] 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: Thu, 12 Oct 2023 15:32:23 -0000

Hi Prasad

Thanks for your comments

See PPE below

On Wed, Oct 11, 2023 at 9:08 AM Vengada Prasad Govindan (venggovi) <
venggovi@cisco.com> wrote:

> Hello Luigi/ Dino,
> A couple of minor comments inline with GVP1>
> >>    • Multicast Support: LISP support for multicast environments has a
> growing number of use cases. Support for multicast is needed in order to
> achieve scalability. The current documents [Ref to experimental multicast
> RFCs] should be merged and published as Standard Track.
> GVP1> Is it correct to understand that the scope of the above item
> includes RFC6831 and RFC8059 (and draft-ietf-pim-jp-extensions). Kindly
> clarify. We have many working implementations based on RFC6831 and hence it
> would be very useful to get them upgraded to Standards Track.
>
> PPE - Yes it does include RFC6831and RFC 8378. There was a discussion
about mechanisms needed and useful. See here
https://datatracker.ietf.org/doc/minutes-116-lisp/ .

>
> >>    • November 2024: Submit merged Multicast document to the IESG for
> >> consideration
> >
> > Note, from the previous email you referred to
> "underlay-multicast-trees". That document has changed its name to reflect
> what it really is designing, its titled draft-vdas-lisp-group-mapping-00.
>
> As for previous comments we better avoid “merged”, may be just use
> “multicast documentS”.
> GVP1> Agreed, this is another important document that we could complete.
>

PPE - ack

Thanks
Padma


> Thanks
> Prasad
>