Re: [Pce] Murray Kucherawy's No Objection on draft-ietf-pce-pceps-tls13-03: (with COMMENT)

Dhruv Dhody <dhruv.ietf@gmail.com> Thu, 04 January 2024 06:12 UTC

Return-Path: <dhruv.ietf@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 B7DC6C151083; Wed, 3 Jan 2024 22:12:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 STneOz3gv1cr; Wed, 3 Jan 2024 22:12:39 -0800 (PST)
Received: from mail-vs1-xe30.google.com (mail-vs1-xe30.google.com [IPv6:2607:f8b0:4864:20::e30]) (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 BC8B6C15155C; Wed, 3 Jan 2024 22:12:39 -0800 (PST)
Received: by mail-vs1-xe30.google.com with SMTP id ada2fe7eead31-467a18fc0fcso48761137.3; Wed, 03 Jan 2024 22:12:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704348758; x=1704953558; 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=DWFTcvm4dH0KCVxiLiaUKcCvOK0djKJIWqhGqvDXbL0=; b=ZcfTQPxnpKOF+jA0kRG0tq/xo+XwWMZtJPghLVTVKnwDa36msFHct0CzqW2bcSXvCK pdxZsEf0BjPQAkmQqhRNlR31+uXhepd/IpSUTyEpyRnYGW6fdi2uTGw3NQrNCXSfB94t DqptJyw0s0gePuf2fPnh21iGlvwz/zOiFvS4tWGloIFKmNCq0Aya9zLjwnCJfnzepfUG NsabPjWPsmvAkCVCRl7tc7xek0VhY2FxWNgDPGUb4l3lej/xrWQNnXyoU4+HMSaIMPz/ qvXhEu7Lbq0PWW+Bbrd2b4ACnTjQUk5pU/TOsGUkUGrLdnmxVfFT6ccfL+X9Rv5gIe8/ txJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704348758; x=1704953558; 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=DWFTcvm4dH0KCVxiLiaUKcCvOK0djKJIWqhGqvDXbL0=; b=B8jUz4hX8yymyamJ76aiDLE+PaBT2lTh2CIjT7otWc9M7ZbLymUmtdqjK+SpzwP11o CkP5mKYyegJyThe+9j8ZfDsBOASKRILFpIv5Cpi52h8tXnCs7hqAtxXCHqPCDIuJky4C 9IQSd/xn94ZbcALBGYfJhUSaIxYFfWlXn6RWzuy9gbmnyz54nfz5nAlzBy5ISaM7c9+Z tj7W1ItrMIX5KyZOe22YYYyPUbMN2+RuT6geXf/dwNNNQNus4bB5ktkrGtjk0o8k9QdI sYqjuZ7NY2KCh5qSs+lfmn8Rkxi8/W0rLgsjfwfnWOi1ZrOLrwOKCbUhczpMgbGe1U13 2vSQ==
X-Gm-Message-State: AOJu0Yw5VMCK2e9QWzqEVmDLnGpHtJWnnpENKRe1x5GAmDQcdwUDlv4P nGoiCC+AJC8wKQPnXBCsXSg2o0g5pib1KlkzIj4=
X-Google-Smtp-Source: AGHT+IGbrXhvYTopBqaoSJi1yy6XkRlwa5ZdUtBODH6+KxXspfDnkU23We9dd4eNuDOn+CQVbtt7B1ptp4dbSpIB3Xs=
X-Received: by 2002:a67:c10e:0:b0:466:fc2c:3cac with SMTP id d14-20020a67c10e000000b00466fc2c3cacmr47722vsj.67.1704348758156; Wed, 03 Jan 2024 22:12:38 -0800 (PST)
MIME-Version: 1.0
References: <170434804500.35593.6503947237738879936@ietfa.amsl.com>
In-Reply-To: <170434804500.35593.6503947237738879936@ietfa.amsl.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Thu, 04 Jan 2024 11:42:01 +0530
Message-ID: <CAB75xn444UCMOKaEFWAhhnuw0w74AWPVExVg0pg3XTyY6xAMZg@mail.gmail.com>
To: Murray Kucherawy <superuser@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-pce-pceps-tls13@ietf.org, pce-chairs@ietf.org, pce@ietf.org, andrew.stone@nokia.com
Content-Type: multipart/alternative; boundary="0000000000004dace2060e189e1e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/h0wjVjterq6PGjOUbrxiBP0mebY>
Subject: Re: [Pce] Murray Kucherawy's No Objection on draft-ietf-pce-pceps-tls13-03: (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: Thu, 04 Jan 2024 06:12:43 -0000

Hi Murray,

On Thu, Jan 4, 2024 at 11:30 AM Murray Kucherawy via Datatracker <
noreply@ietf.org> wrote:

> Murray Kucherawy has entered the following ballot position for
> draft-ietf-pce-pceps-tls13-03: 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-pceps-tls13/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Further to Eric's comment, I'm completely confused by question #4 of the
> shepherd writeup.  While the document claims there are no implementations
> known, the shepherd writeup says there's at least one (and it was easy),
> and
> makes another "Yes" remark that I don't understand.
>
>
>
Dhruv: The shepherd writeup mentions this email response on the mailing
list -
https://mailarchive.ietf.org/arch/msg/pce/dLdcUan2psssBUgzCtXPluEr_ok/ that
mentions some implementation experience. When we asked to include that
information in the implementation section we did not get a confirmation
back. Soo that's that :)

We could update the implementation section to say -

OLD:
   At the time of posting the -02 version of this document, there are no
   known implementations of this mechanism.
NEW:
   At the time of posting the -04 version of this document, there are no
   known implementations of this mechanism. It is believed that one
   vendor has implementation, but these plans are too vague to make
   any further assertions.
END

Thanks!
Dhruv