[spring] Re: spring Charter Update (charter-ietf-spring)

Alvaro Retana <aretana.ietf@gmail.com> Thu, 05 September 2024 18:51 UTC

Return-Path: <aretana.ietf@gmail.com>
X-Original-To: spring@ietfa.amsl.com
Delivered-To: spring@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6220C14F610; Thu, 5 Sep 2024 11:51:43 -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 OJXG7dViMeFt; Thu, 5 Sep 2024 11:51:43 -0700 (PDT)
Received: from mail-pg1-x535.google.com (mail-pg1-x535.google.com [IPv6:2607:f8b0:4864:20::535]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F57DC14F60D; Thu, 5 Sep 2024 11:51:38 -0700 (PDT)
Received: by mail-pg1-x535.google.com with SMTP id 41be03b00d2f7-7d4f8a1626cso926156a12.3; Thu, 05 Sep 2024 11:51:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1725562297; x=1726167097; darn=ietf.org; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date :message-id:reply-to; bh=FjS8MASkhu84d36rNbFVXq/IWtQ0OMfupsTzb2G2lHU=; b=BzeonWD5Ey3Oc8RGdmNl5znp6fR+OqYfCOtNjANbYGY5BS+PehvwSTwoKDu/RKLWeV 5CJ+Gjy6rMzlvA7EQhB7oEGCDlNgnSaD307dWO2Xz0y/SiQrOvPCOftiNR3BcDPpNKZo ZGEU/72q4hJkHBeMMEHdv/uZaVLlS0YAkgwbP8ch8kITsQojlAtOfgShdiezCxlmvhK4 5HUtqm8pdAFy+fPMmYtLHYAFSZ/WOxFCmqM19gOZFzmshoSbWN7Gv0oU2/Su7d3vTeYY mEbqxPb9e8iK+YIYL3a2KnnKI/7758MsbT0jcBvwY0+h7EgHYe2uN3CDUp3ofIsPSfPZ W0Xw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1725562297; x=1726167097; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=FjS8MASkhu84d36rNbFVXq/IWtQ0OMfupsTzb2G2lHU=; b=XpnM4Uzx23cBVd1nBpX+LI23Ep2FQMjsroExz5DNvauW0+/c+Ve3fQbAcoFjx/teu3 5EMv5B395gp/rzJAQk5MnhGOZzcA9HltZqKjbBM9O7LORo1Y92iExXe+NhTraf+IbV6I SFEoXd26GQP1T2fDC09aiFrrKiV6pN3tIOJuPlpFZO4e1JUXzlX487K1OgeAziuGLlBY SlcnLYg2Q6dHpRerhrTFmubhXr4PoJP8lJMxMqiUQCrWJsMwWI7qbsHzBL1aKS/1JwQN vcO5IK3DuaGqblcdUNnrjjNsTGwtZkjkiOdcY8R730muofO+nDih//S1xZFM8cYICzqE 1HSQ==
X-Forwarded-Encrypted: i=1; AJvYcCUxOie2Jxvq+0kRFreP1ZE2jSgw4QL72p5Z2j3phjGG6oey/cRxUikQarUflWz++ZcNMQB0rfI=@ietf.org
X-Gm-Message-State: AOJu0YzCQyBplSBJ/qZXguxoU8Ei5BKzgf72Y2D3EmKmjzrTAic+0nSJ uEXnzpq6ZtYO2lTm0m9lR6BxUNzsw9rvHKLNpeO99PzJg1IK+Um4qkT2CBFdNRZmqZexToCGbaf HlKR/5T+4vGWnoFrcoHN+L6JzID0=
X-Google-Smtp-Source: AGHT+IH/9BBjDPndg6UNpGY123c+RlDssRciNk92fHnhUjRXkWu38uXJSy5zMbxeM2Sja6em95n+cGb8esHiNOnP+so=
X-Received: by 2002:a17:903:188:b0:205:4e22:ccfc with SMTP id d9443c01a7336-20584222d0bmr177152895ad.50.1725562297264; Thu, 05 Sep 2024 11:51:37 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 5 Sep 2024 11:51:35 -0700
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <CA+RyBmWK5Kxjr5omM9MXXwnQfP1v4xR8LOgB=z-nO0uN8Bh2wQ@mail.gmail.com>
References: <CAMMESsyWWKqLaN2Cfzer-efT3gmTQ4ANLAP34k1ZsLEhKJEZyQ@mail.gmail.com> <CA+RyBmWK5Kxjr5omM9MXXwnQfP1v4xR8LOgB=z-nO0uN8Bh2wQ@mail.gmail.com>
MIME-Version: 1.0
Date: Thu, 05 Sep 2024 11:51:35 -0700
Message-ID: <CAMMESsxbySEDUtgQBmLODt1aHW8TX8sVwsYdxv0xKDzkwKLEjA@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: OABHDRAPIQD3AT75B7Y3OJ4KEDDJWQLC
X-Message-ID-Hash: OABHDRAPIQD3AT75B7Y3OJ4KEDDJWQLC
X-MailFrom: aretana.ietf@gmail.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-spring.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: "spring-chairs@ietf.org" <spring-chairs@ietf.org>, SPRING WG <spring@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [spring] Re: spring Charter Update (charter-ietf-spring)
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/HCZ98IVaIWNawtw8KYDNu-EwxTI>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spring>
List-Help: <mailto:spring-request@ietf.org?subject=help>
List-Owner: <mailto:spring-owner@ietf.org>
List-Post: <mailto:spring@ietf.org>
List-Subscribe: <mailto:spring-join@ietf.org>
List-Unsubscribe: <mailto:spring-leave@ietf.org>

On September 5, 2024 at 10:57:33 AM, Greg Mirsky wrote:

Hi Greg!

> thank you for sharing the proposed updates to the SPRING charter. It all
> looks good to me. I have a minor proposal to the extend the list of the
> topics on which SPRING collaborates and coordinates adding the following:
> IPPM on performance measurement methods and metrics

After thinking about this, I'm inclined to cut the list instead of expanding it.

Yes, you're right, the WG does interact with ippm.  It also interacts
with pim (on p2mp segments); rift (for example) is in the process of
rechartering to include (among other things) SR extensions -- so maybe
we should include them too.  I'm sure there are others -- and I'm also
sure we will forget someone.

Instead of trying to be exhaustive, we should list the *required*
groups we have to coordinate with.  Here's the proposed text:


OLD>
   The SPRING WG will coordinate and collaborate with other WGs as
   needed. Specific expected interactions include (but may not be
   limited to):

   mpls on the MPLS data plane and associated extensions
   6man on the IPv6 data plane and associated extensions
   lsr on OSPF and IS-IS extensions
   idr on BGP extensions
   bess on VPN control plane
   pce on extensions for centralized solutions
   teas on traffic engineering architecture
   rtgwg on fast-reroute technologies
   srv6ops on SRv6 operations


NEW>
   The SPRING WG is expected to coordinate and collaborate closely
   with the following WGs:

   mpls on the MPLS data plane and associated extensions
   6man on the IPv6 data plane and associated extensions
   srv6ops on SRv6 operations

   As needed, the WG will also collaborate with other WGs to develop
   extensions and other SR-related solutions.


Thoughts?

Thanks!

Alvaro.