Re: [Pce] Mahesh Jethanandani's No Objection on draft-ietf-pce-segment-routing-ipv6-23: (with COMMENT)

Dhruv Dhody <dd@dhruvdhody.com> Wed, 03 April 2024 09:43 UTC

Return-Path: <dd@dhruvdhody.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 0AE75C14CE29 for <pce@ietfa.amsl.com>; Wed, 3 Apr 2024 02:43:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.893
X-Spam-Level:
X-Spam-Status: No, score=-6.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dhruvdhody-com.20230601.gappssmtp.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 B0J2mMgvQNqq for <pce@ietfa.amsl.com>; Wed, 3 Apr 2024 02:43:34 -0700 (PDT)
Received: from mail-oo1-xc2c.google.com (mail-oo1-xc2c.google.com [IPv6:2607:f8b0:4864:20::c2c]) (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 045BFC14CE33 for <pce@ietf.org>; Wed, 3 Apr 2024 02:43:33 -0700 (PDT)
Received: by mail-oo1-xc2c.google.com with SMTP id 006d021491bc7-5a470320194so3565446eaf.3 for <pce@ietf.org>; Wed, 03 Apr 2024 02:43:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20230601.gappssmtp.com; s=20230601; t=1712137413; x=1712742213; 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=VzHoQ/mITMqUDRxMnZfGmU2xwniGI2YQvbMIe+PkCNY=; b=CqX7uVgE5A21mIynhoK6rKUTRHgy8mlTFMLo/dMToCKQL968+jn+z4ZMt9SI3yC/6l 0jO0Z3E0e4wE3TnZoRJQfOOz4OW6szoalIc8zCSxCKlNzIOXSb+LwgDqstgoEFQxHjr3 dBFAY1SaY4JRh2hUATKC8/5G1lqEvYaPwZZEQ25En2N3/X5+exYzXRdkcGXwp/ZErS7B TLtZ1LqhqiQqduaXI5Q1XqrIvqyFJF9ymp47UE4RX5dErIE7Jkcidf4CWIU97ARgGzAn SY+iqOw7ONUWoLuII37WuRxwFkuTjq2W9J2zf0VKGkoeD1g+F2xqHsHfOjGdgMgX65a4 /R8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712137413; x=1712742213; 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=VzHoQ/mITMqUDRxMnZfGmU2xwniGI2YQvbMIe+PkCNY=; b=CQZgSqADNtIN+YpYkuyhap2vOpf2A+z2pg4ClxTfkkXIqzlcOf90TS8otZGeM7P3IL 0mOUog5VeKLoltn6MBgJcN8Y8bsG+beIdrDE15DPiKToF8dU9XVYpfV0blnfkRO+WuKg Kfzi4BlM2OCw9ZTXpmwDKpa3C7cFKxq02xUBem7F0LN2zSpyY6jljABKpqqRoQ5eKJUs tm6+a6C8hRUjN2leeL71S7C7ugW3h2PMu9IwjDoeYix9NKwNYFvyyN5oxy106JOOziTI 9O8fEV12HnzzwqsuymvlN1HJoKcf48FmELOltCii8mFXqmw1KqdTSvCNTG3jV6wm7qDG KmZw==
X-Forwarded-Encrypted: i=1; AJvYcCVfxlxirk05YKvCYJ1CEvlcFJFjQQBT9ytB8TvTfjF8HQ8GIOniZ5Za08JRq1bUDmFPQz7j4lEEQktDJas=
X-Gm-Message-State: AOJu0YxYDK29bgiAX+3UHZNDkmlWusGlDadeeWFosSWYrZohWhI4mgzD 59B0/mpnbm3ple4pnBESL9H0/TRfoyN/zMWOsBxASSzSwGGGroQtpeXXYjjnPqjUodhCj6ynIkT /Qkajp4f4MKOhpCdOh49KgdCcwm0uWQlMXv1XEhiDpQmHToMyI7tqcA==
X-Google-Smtp-Source: AGHT+IFsHX7m66CZGnYxGnEsc99ray/Qp7g/t5nqjYVorFQPA2lTmXt4EtZZed1OqrmwB6nOmWAQAiYwZpIdNqJA3S4=
X-Received: by 2002:a05:6820:1f01:b0:5a5:2244:6b1c with SMTP id dl1-20020a0568201f0100b005a522446b1cmr15607339oob.9.1712137412971; Wed, 03 Apr 2024 02:43:32 -0700 (PDT)
MIME-Version: 1.0
References: <171209997983.16890.3582715394186815361@ietfa.amsl.com>
In-Reply-To: <171209997983.16890.3582715394186815361@ietfa.amsl.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Wed, 03 Apr 2024 15:12:56 +0530
Message-ID: <CAP7zK5aeer7ysXVuWM6zDPacrbb4xTrwuSe8aH2Wk6AhZ-bKvg@mail.gmail.com>
To: Mahesh Jethanandani <mjethanandani@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-segment-routing-ipv6@ietf.org, pce@ietf.org, pce-chairs@ietf.org
Content-Type: multipart/alternative; boundary="0000000000004ead5106152e0e48"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/AlMYzeWMlz03iKbZ3A0Oq3DnSF4>
Subject: Re: [Pce] Mahesh Jethanandani's No Objection on draft-ietf-pce-segment-routing-ipv6-23: (with COMMENT)
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: Wed, 03 Apr 2024 09:43:38 -0000

Hi Mahesh,

On Wed, Apr 3, 2024 at 4:50 AM Mahesh Jethanandani via Datatracker <
noreply@ietf.org> wrote:

> Mahesh Jethanandani has entered the following ballot position for
> draft-ietf-pce-segment-routing-ipv6-23: 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-segment-routing-ipv6/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for working on this document. I am not an expert in PCEP and its
> related
> drafts, but as I understand it, this document is defining an extension for
> SRv6
> and not SR-MPLS. Therefore, I am confused by this long paragraph in the
> Introduction section that delves into how SR-MPLS works. To quote:
>
>    [RFC8231] specifies extensions to PCEP that allow a stateful PCE to
>    compute and recommend network paths in compliance with [RFC4657] and
>    defines objects and TLVs for MPLS-TE LSPs.  Stateful PCEP extensions
>    provide synchronization of LSP state between a PCC and a PCE or
>    between a pair of PCEs, delegation of LSP control, reporting of LSP
>    state from a PCC to a PCE, controlling the setup and path routing of
>    an LSP from a PCE to a PCC.  Stateful PCEP extensions are intended
>    for an operational model in which LSPs are configured on the PCC, and
>    control over them is delegated to the PCE.
>
> If there is something this paragraph conveys applies to SRv6, it is not
> apparent in the next paragraph. In anything, the next paragraph on how this
> would work in SRv6 was clear in itself, without needing this paragraph.
>
>
>
Dhruv: The base PCEP specifications were specific to MPLS-TE and over time
they have been extended for SR-MPLS, GMPLS etc.  This and the previous
paragraph is setting the scene to highlight the existing specifications
(RFC 5440 and RFC 8231) that are extended to also support SRv6.

This might be a matter of style - the PCE WG documents do prefer longer
Introductions that references base specifications that are being extended.

Thanks!
Dhruv



>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce
>