Re: [Pce] WG Adoption of draft-li-pce-pcep-pmtu-05

Gyan Mishra <hayabusagsm@gmail.com> Sat, 23 April 2022 05:01 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D7E593A180B; Fri, 22 Apr 2022 22:01:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YNi1jY4ogBQ8; Fri, 22 Apr 2022 22:01:10 -0700 (PDT)
Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 564AD3A1809; Fri, 22 Apr 2022 22:01:10 -0700 (PDT)
Received: by mail-pl1-x631.google.com with SMTP id c12so15168127plr.6; Fri, 22 Apr 2022 22:01:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cXiaffUCzT1INo7G+4aiM03RwIto0peoUKtS85ig0pc=; b=Sdg4y+zluPz0Fw7qUcL7uVGtuClkfSY/qKIHKXFyKf4vxlCQPGdssyaAipmoA4t8D5 Car/dhF72r2Dqm5KQVqorCWL3i/6+d7h3jEbBHss8ZSz5JQZ4RlfRP2exiiZrOtBsYpE LVkLEYY/91k81FRunNT4NfsrqO6CPqZ5MeCb6ttojmTvZhI74aMjxDGjUK1DsNSrVhGs abIfMeYivVkD5pAHfNuItJ6YfaGNGLGu/diffcSdF8tn/MU0H6GofzviBxQngYM8n5Qh CrDTLa7/AyR44sePO54pEqLcxq1NAaG8eaqrzWRILrd8fBZh7dUC7O0mhUeFhijRqNAZ GGTA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cXiaffUCzT1INo7G+4aiM03RwIto0peoUKtS85ig0pc=; b=A++/boZTI8Y03jBxry+t0WKuj2mfc1IL4T3f7TSKQEcSz9doBpNI/cinyeedKiIB6+ HJGg/OYq3jDANVjq7ApCLd4w1UQH8UOrhFuY+QmDwMlj6IzHBxpM2Nn3wcdC+UbJ0aQ/ U2q9+y9M0YwK9yJrbziORI9npZoYFiC7yDGpxHT0YNF3sL1vDOUmiqBzvdqhzfWK+tVQ jXe4wxM9cECawM6FRKTlREyMvPYVbSknqaD8XR+uTHbY1D6sd28r7KO4ITzg736xU3r7 Bu23ETniVvf+8FwdkJgOjPlzBimJv4AzCIGGmOuFLjBaaHb966qauqqAGXjKEWeihA0m bmAQ==
X-Gm-Message-State: AOAM533r5AeWC0Ki6RrMBpBOx4eLOMk+IufH4sSviwq8qsxzuXmccGDQ 9AayrWIf9nNzGa+If4+YrINpk1VXxHeJ1KVv6BL8yvXS
X-Google-Smtp-Source: ABdhPJwxLlJQ6Tfm5qVU76GtCxgxJgpWz/JubKPgO148FykBAE5yX1zMxklf3GrX9I2++nREJsvIfh+rYT94CEi/Blc=
X-Received: by 2002:a17:902:7789:b0:156:8b5c:606f with SMTP id o9-20020a170902778900b001568b5c606fmr7636654pll.100.1650690069008; Fri, 22 Apr 2022 22:01:09 -0700 (PDT)
MIME-Version: 1.0
References: <CAP7zK5bC95SwqbPC-Fm1-bTyAmaVOb-O5Bg4CKqe3tSe=LUzZQ@mail.gmail.com>
In-Reply-To: <CAP7zK5bC95SwqbPC-Fm1-bTyAmaVOb-O5Bg4CKqe3tSe=LUzZQ@mail.gmail.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Sat, 23 Apr 2022 01:00:58 -0400
Message-ID: <CABNhwV26ZQXS4ET8Vdj907op0sL8Po2czTL_y49FX1Z8-PRJLw@mail.gmail.com>
To: Dhruv Dhody <dd@dhruvdhody.com>
Cc: SPRING WG <spring@ietf.org>, draft-li-pce-pcep-pmtu@ietf.org, pce@ietf.org
Content-Type: multipart/alternative; boundary="00000000000032968205dd4b3bd2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/YdTGaYKQnYaguQeA-iImfQ1POy4>
Subject: Re: [Pce] WG Adoption of draft-li-pce-pcep-pmtu-05
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Apr 2022 05:01:16 -0000

Dear PCE Chairs

After the discussion thread with Ketan we are now in sync and I have agreed
to work with the authors of the IDR and PCE draft in a collaborative effort
 on publishing a draft in SPRING WG that addresses PMTU in SR Policy and
Fragmentation in SR policy.

I have discussed with the PCE authors that I agree that PMTU in SR Policy
definition and SR Policy and fragmentation should be in a Spring Standards
Track draft from an implementation standpoint to avoid any interoperability
issues in proprietary vendor specific definitions of PMTU in SR Policy.

Anything SR architecture related which PMTU and fragmentation in SR policy
are part of the SR architecture which is why it belongs in Spring.

We have reached an agreement that the PCE draft can proceed for Adoption
and once it becomes a WG document we will ensure that protocol specific
encoding is only included in the PCE draft with informational reference to
the new Spring PMTU draft that has the detailed framework of PMTU in SR
Policy specification.

Ketan has offered to help in editing the new draft.

As well if anyone else in Spring or PCE would like to collaborate on the
draft please let us know.

Kind Regards

Gyan
On Mon, Mar 28, 2022 at 12:10 PM Dhruv Dhody <dd@dhruvdhody.com> wrote:

> Hi WG,
>
> This email begins the WG adoption poll for draft-li-pce-pcep-pmtu-05.
>
> https://datatracker.ietf.org/doc/draft-li-pce-pcep-pmtu/
>
> Should this draft be adopted by the PCE WG? Please state your reasons -
> Why / Why not? What needs to be fixed before or after adoption? Are you
> willing to work on this draft? Review comments should be posted to the list.
>
> Please respond by Monday 11th April 2022.
>
> Thanks!
> Dhruv & Julien
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email gyan.s.mishra@verizon.com <gyan.s.mishra@verizon.com>*



*M 301 502-1347*