Re: [Pce] Scoping Items from draft-koldychev-pce-operational

Siva Sivabalan <msiva282@gmail.com> Sun, 20 November 2022 00:06 UTC

Return-Path: <msiva282@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 70B75C1522C3 for <pce@ietfa.amsl.com>; Sat, 19 Nov 2022 16:06:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.843
X-Spam-Level:
X-Spam-Status: No, score=-1.843 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_ENVFROM_END_DIGIT=0.25, 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, 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 NArvNrdSMdd9 for <pce@ietfa.amsl.com>; Sat, 19 Nov 2022 16:06:14 -0800 (PST)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (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 AC52BC1522BE for <pce@ietf.org>; Sat, 19 Nov 2022 16:06:14 -0800 (PST)
Received: by mail-yb1-xb31.google.com with SMTP id z192so9828519yba.0 for <pce@ietf.org>; Sat, 19 Nov 2022 16:06:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=HAQTSV39YRWz4zm1aIc9z5pOFUF1Twx0BfEGOaoHeFY=; b=Cvjx95Xv/xd10zquIsAtkaU+1NzgrVoWF4IGj4DjmSEPlE4Wuk2PhMIoPOLkLoyKiK trsjtejerPsU7EcSgnz71A4XHSVJ3CsQsYNu37ULnydrbUuciAsBeLPIJcrg2AAA9xjq uKXH1Q7ik09fXVJOTKbsEbbh99V4LotEjZ1a0a6hO5ei2zVbGzY/2wYywqCfrEv6lJCp yrJwVXqq9LezmPSFS5EOMWLad52pzNeq2RaCKCnyNWjxWEMLQINXhLrmaH6ZeGPWZMz+ vykQ0XKfk1JfhVWuqHjJy6HG9bHLkBpZWKnajfoFlJLPg+z+JqWlPzsz0mdypElNpByt jE7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; 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=HAQTSV39YRWz4zm1aIc9z5pOFUF1Twx0BfEGOaoHeFY=; b=z1HYkZAqbaljHjPzjosA1ySgyKOsDGOb76bO6pYOPGpxNwR6NoTg8tZcCX5bAQrbwo hYt3wR/zKYcR/EPpudTTmeCYVRRvJJdYrR5P+v5wkBdV8v8u4/AOhnHoVbVG4vlCILyM FcQ1swoe/13VzcCo73qXWNq15LZyzhlcjA983JCAMJ+EaNvmpwvH6ZOi3qisr8RADL77 abLZ0gxc/BOuaSPRNZun6CkKzeOV2idncpUekcBt1UwR4s8uoNr63obRaQ3/fvzQhZSa 5ESmqoq8XCIXLAftLN2nKepfbJuF5hnT9yVab/aKwr1UkEqM/L+n6T4FC1186qICmnpT 3rVg==
X-Gm-Message-State: ANoB5plH0mxOlxB+RBcxbdyqhxz1l0+XgRXn2vLUl8lwHql6bqddY0kk OpxRVkrOiT3OkxG7NAOS+/y+rdUlfpQEhwYigb0=
X-Google-Smtp-Source: AA0mqf7FPF3T+7y6TO9k0cySJUfL8dD5tFHKj2sfYWVPw2QfRdnjh1+WeLE+kZOASI1qlYR9Iv1+UZujw+ox5OLcsjQ=
X-Received: by 2002:a25:5304:0:b0:6ea:2a2:f21a with SMTP id h4-20020a255304000000b006ea02a2f21amr3652324ybb.170.1668902773478; Sat, 19 Nov 2022 16:06:13 -0800 (PST)
MIME-Version: 1.0
References: <7c65cb43-7644-b241-fb3d-e26e948231d3@orange.com>
In-Reply-To: <7c65cb43-7644-b241-fb3d-e26e948231d3@orange.com>
From: Siva Sivabalan <msiva282@gmail.com>
Date: Sat, 19 Nov 2022 19:06:02 -0500
Message-ID: <CANJFx2S1jvx5L+xn+9avUSosQASUwP=BJXchzPG7wrdEU3ByfQ@mail.gmail.com>
To: julien.meuric@orange.com
Cc: "pce@ietf.org" <pce@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fa5a7905eddbb454"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/5GCL0C6pyozD0nNxBXvdbmtEW78>
Subject: Re: [Pce] Scoping Items from draft-koldychev-pce-operational
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 20 Nov 2022 00:06:18 -0000

Hi Dhruv, Julien:

The main motivation of this document is to have a single (in particular, a
brief)  document that sheds light on the inter-op issues encountered at
various multivendor public/private inter-op events. Even though PCEP is a
simple and a proven protocol, it is perceived to be complex due to large
number of RFCs/drafts. A single document of this sort would make developers
life easier. I am inclined towards option A.

Thanks,
Siva


On Thu, Sep 29, 2022 at 4:37 AM <julien.meuric@orange.com> wrote:

> Dear PCE WG,
>
> Let's follow up on the discussion started during IETF 114 about
> draft-koldychev-pce-operational [1]. The I-D currently tackles different
> issues about PCEP, some of them being informational, some other updating
> existing PCEP specifications. Among the options we discussed to proceed
> with this work, 2 remain:
> 1. Keep a single draft, but clearly separate the two types of content;
> 2. Break it up into 2 drafts.
>
> We'd like to hear the WG's opinion whether you prefer:
> a- a single standard track I-D, with both content types sharing fate
> until publication?
> b- a clarification I-D on informational track + an I-D updating PCEP on
> standard track (possibly progressing at different paces)?
>
> Please share your feedback using the PCE mailing list.
>
> Thanks,
>
> Dhruv & Julien
>
>
> [1] https://datatracker.ietf.org/doc/draft-koldychev-pce-operational/
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>