[spring] Re: spring WG Adoption Call for draft-peng-spring-pmtu-sr-policy

Gyan Mishra <hayabusagsm@gmail.com> Wed, 03 July 2024 03:35 UTC

Return-Path: <hayabusagsm@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 CD661C14F748; Tue, 2 Jul 2024 20:35:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.844
X-Spam-Level:
X-Spam-Status: No, score=-1.844 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, HTML_OBFUSCATE_05_10=0.26, 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 hZs08f3fZYhm; Tue, 2 Jul 2024 20:35:34 -0700 (PDT)
Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 DE043C151070; Tue, 2 Jul 2024 20:35:34 -0700 (PDT)
Received: by mail-oi1-x232.google.com with SMTP id 5614622812f47-3d561d685e7so3429632b6e.1; Tue, 02 Jul 2024 20:35:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1719977733; x=1720582533; 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=mFiYYx1oqVgzvnS8Q28eVOn42gG8oa6Rwp3leWEAJdU=; b=btcRRzoX1uV9MLA/WQ8tY0sgYXOMMZDYSksbp61SxbPWnAuxQN4fcUatMOs5xy5GrB TREoYfuwu15koOH50gavNnLUxg8F+RLD1NNrbRfr5Twc/Hd5ab5TlUiGi3ii8w2jkQxD zxEYcC74T91qbg7miXv6dA7eBpFcg4LFTHnShLCK1eVw0UAA/m9KU1Knu8Qnd7eWfU5p I3fmTJMmVZsBHOVyegwv8rVvNBb5D846gPB5hRklP4BezCnbUJ3+I2XBW1TB3jVgh40r zTiCqpgUMCYJKLYkoUKJAaYB/D0cy8usC4s4TDYURMJYzjRLili7SVX1ScyI6UlXSViP V2/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1719977733; x=1720582533; 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=mFiYYx1oqVgzvnS8Q28eVOn42gG8oa6Rwp3leWEAJdU=; b=NEVO99NkfqlK1862UE96uhg6hvHZgtqnNIoCSipLkvD4LjJrig6Iuahw0ioM+A+ouw DHjAsZVWgikbIGvlTeToTAXL+d5gjQbzL1vTULHBDiyMz4y7EibNW5nkxIWI5tCAHF21 CVNzw7H+Ncz2qZKc0Vl9GNVCi1ncQ/fMnK28w4dclvSyNGbrsRGu7cNlCekWKKQPyUwk /CSC86xomtB6igQ9CZB/xUxBXgHPUSNAW/B9yOZilmUp/7ImSGaqvE0NpWP5KhBTLDNv NcbloGLazT0/4o/2oYqmfTolDLivFeaifEGkRWvueGMV3aGW9Baw07FfW2YfTTnwO/2M EnXQ==
X-Forwarded-Encrypted: i=1; AJvYcCVXMT3PmQYbn5boDiwMxB5O1GvEsPJXt9c6euoXKmlerghVJ/GFaFI8OBLfPel6jVFBq8WVU6nRHB8UwDaQfaQ9W6QAdahHeD/r5UU3BDJu4bRtY7sFFLfKfyld1cf4GspMJHygUcyDSrBXd3oFBBpgrg==
X-Gm-Message-State: AOJu0YzHlZa9y4Zy9rbJm8pEG262Z9YnHaPHXUFpqepa6mahzs8WVbB/ W8/XPrVlUclfeLxNClvsm/CC0QMGMzVOQ+y+eZ8kVQ56HNcawKZtzsTL7Amssir4EfBrMTHhw2Q rN2/A5vC9vkjrrj20dR0xmb2w9PoOUg==
X-Google-Smtp-Source: AGHT+IEzRVLJsptL3lP9inpolAiLiH0be0ZRscoRjEF+NSCpZIheD9NGNdXZ/RpL7cqWW6uwV//FhHkP4OvMXhJIzss=
X-Received: by 2002:a05:6808:1387:b0:3d6:2b5f:b6c9 with SMTP id 5614622812f47-3d6b30f5354mr13326240b6e.23.1719977733425; Tue, 02 Jul 2024 20:35:33 -0700 (PDT)
MIME-Version: 1.0
References: <CAMMESsyObenev5KUG2WnSz9yq-ed3gbgPjcGYNcseJ6GHZibpA@mail.gmail.com>
In-Reply-To: <CAMMESsyObenev5KUG2WnSz9yq-ed3gbgPjcGYNcseJ6GHZibpA@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 02 Jul 2024 23:35:22 -0400
Message-ID: <CABNhwV2UfhFEpYskwdNS8NwenVPj34GNXrsKRrx_ZT-LMZZCAg@mail.gmail.com>
To: Alvaro Retana <aretana.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d28f2e061c4f85b1"
Message-ID-Hash: KTJPDUZO2ASNZBBSHM332C5RNMGVOHGG
X-Message-ID-Hash: KTJPDUZO2ASNZBBSHM332C5RNMGVOHGG
X-MailFrom: hayabusagsm@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 WG <spring@ietf.org>, draft-peng-spring-pmtu-sr-policy@ietf.org, spring Chairs <spring-chairs@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [spring] Re: spring WG Adoption Call for draft-peng-spring-pmtu-sr-policy
List-Id: "Source Packet Routing in NetworkinG (SPRING)" <spring.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spring/JMKL13bVmUT_EvAyXIGflzvOVTM>
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>

Dear WG

 As an co-author, I support the adoption of this draft.

As Shuping mentioned some background on this draft:

During the adoption of the related PCEP draft“draf-ietf-pce-pcep-pmtu-02”,
a need for a document in SPRING was requested and confirmed by both PCE &
SPRING WG chairs.  As well  during the IDR document “draft-ietf-idr-sr-
policy-path-mtu-05” adoption call, a discussion was brought up that the
concept of “Path MTU” for SR Policy and its applicability should be first
defined in SPRING WG before we introduce signaling aspects into BGP.

Following these discussions and needs, this draft was created and being
developed in the SPRING WG.

As a result the overall goal was that the PCE PMTU extension adoption call,
the draft “draf-ietf-pce-pcep-pmtu-02” was to maintain only protocol
extension specific details, while the SR Policy PMTU definition & framework
was to be developed in SPRING WG as a Standards Track document to ensure
vendor interoperability related to SR-PMTU concepts and computation details.

Please review the latest draft as well as I presented this draft in 2022
IETF 114 and 115.

https://datatracker.ietf.org/meeting/114/proceedings

https://datatracker.ietf.org/meeting/115/proceedings


Kind Regards

Gyan
On Tue, Jun 18, 2024 at 11:44 AM Alvaro Retana <aretana.ietf@gmail.com>
wrote:

> Dear WG:
>
> This message starts a two-week adoption call for
> draft-peng-spring-pmtu-sr-policy, ending on July/2nd. From the
> Abstract:
>
>    This document defines the Path MTU (PMTU) for Segment Routing (SR)
>    Policy (called SR-PMTU). It applies to both Segment Routing over IPv6
>    (SRv6) and SR-MPLS. This document specifies the framework of SR-PMTU
>    for SR Policy including the link MTU collection, the SR-PMTU
>    computation, the SR-PMTU enforcement, and the handling behaviours on
>    the headend.
>
>
>    https://datatracker.ietf.org/doc/draft-peng-spring-pmtu-sr-policy/
>
>
> Please review the draft and consider whether you support its adoption
> by the WG. Please share any thoughts with the list to indicate support
> or opposition -- this is not a vote.
>
> If you are willing to provide a more in-depth review, please state it
> explicitly to give the chairs an indication of the energy level in the
> working group willing to work on the document.
>
> WG adoption is the start of the process. The fundamental question is
> whether you agree the proposal is worth the WG's time to work on and
> whether this draft represents a good starting point. The chairs are
> particularly interested in hearing the opinions of people who are not
> authors of the document.
>
> Note that draft-ietf-pce-pcep-pmtu ("Support for Path MTU (PMTU) in
> the Path Computation Element (PCE) Communication Protocol (PCEP)")
> Normatively references this document. It may be helpful to look at
> that document too.
>
> Thanks!
>
> Alvaro (for the Chairs)
>
> _______________________________________________
> spring mailing list -- spring@ietf.org
> To unsubscribe send an email to spring-leave@ietf.org
>