[Pce] Zaheduzzaman Sarker's No Objection on draft-ietf-pce-pcep-extension-native-ip-35: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Thu, 22 August 2024 12:11 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pce@ietf.org
Delivered-To: pce@ietfa.amsl.com
Received: from [10.244.2.52] (unknown [104.131.183.230]) by ietfa.amsl.com (Postfix) with ESMTP id 87E08C1D4A75; Thu, 22 Aug 2024 05:11:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.22.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <172432868221.2528543.4214302657052122349@dt-datatracker-6df4c9dcf5-t2x2k>
Date: Thu, 22 Aug 2024 05:11:22 -0700
Message-ID-Hash: DL7NFQWEIQRIM2LLTJ2CLBGSITJXNBNA
X-Message-ID-Hash: DL7NFQWEIQRIM2LLTJ2CLBGSITJXNBNA
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-pce-pcep-extension-native-ip@ietf.org, pce-chairs@ietf.org, pce@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Subject: [Pce] Zaheduzzaman Sarker's No Objection on draft-ietf-pce-pcep-extension-native-ip-35: (with COMMENT)
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/LbshDcRqcKd78taGQKfCjHNHrEo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-pce-pcep-extension-native-ip-35: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pce-pcep-extension-native-ip/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for working on this document. I have not comments from transport
protocol points of view.

I have following comment/question though -

 - In section 6.1 it says -

              "The PCInitiate message SHOULD be sent to PCC which is acting as
              BGP router and/or RR."

   In Section 6.2 it says -

              "The PCInitiate message SHOULD be sent to every router on the
              path."

   To me it seems like there is not way to bypass those SHOULDs and get the
   route and session establishment procedure done. If that understanding is
   correct then what are the exceptionsthiking about to let the implementers
   skip that part? Also, if this understand is not true, then I would expect
   this document to give warnings on the effects of skiping the PCInitiate
   messages.