[Pce] Re: WG Last Call for draft-ietf-pce-iana-update

Dhruv Dhody <dd@dhruvdhody.com> Wed, 18 September 2024 09:18 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 D6BB8C16942A for <pce@ietfa.amsl.com>; Wed, 18 Sep 2024 02:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.903
X-Spam-Level:
X-Spam-Status: No, score=-1.903 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_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=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 VKuxydcge2yE for <pce@ietfa.amsl.com>; Wed, 18 Sep 2024 02:18:54 -0700 (PDT)
Received: from mail-oo1-xc31.google.com (mail-oo1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A25AFC16940E for <pce@ietf.org>; Wed, 18 Sep 2024 02:18:54 -0700 (PDT)
Received: by mail-oo1-xc31.google.com with SMTP id 006d021491bc7-5e1c425b52fso132852eaf.2 for <pce@ietf.org>; Wed, 18 Sep 2024 02:18:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dhruvdhody-com.20230601.gappssmtp.com; s=20230601; t=1726651134; x=1727255934; 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=WhfE03LltSQxlBTvAiautin1RDs5BoIofNpe0xNJEPk=; b=B1l5wgWF8xfY8HVu8PdNM3h59CmmaepRHx7HNIy28nHz3eSp0nWaJl664aO2AsOIMG Fjsvnh6lke3YjR6fbk+vN0H7McSskssldw8j16PERLCRUN3Ms72mWkarNTkN/h+Z3Kfu mZ6rR//9iib2lLMlWqmShZBoF5nFheGlU0Xu0TUFd+MkktDKgMzKs+Dk7If5lC7PG3qY dn09DPmMuUUheGQ0yQsU5UgBqcc9aISPTV8NxsYHEU8Q4+5GeEIUBqs5fj2SrnKBh4x3 Ey0UDLlUFI2PB3K1VMzTtPyOA0xpVGVqXJD+rcn9UZrRe7qZIZXEkmMdaAjNuqMmNDd3 DRnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726651134; x=1727255934; 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=WhfE03LltSQxlBTvAiautin1RDs5BoIofNpe0xNJEPk=; b=f2J+Pg4Cta880R4f4TtC9RqVAmqi6ERzj+rfYwueEwPqeQxnKVCVdcwj3vxIsZUrtN YNTO2FC1VrJ3soPI/8nHGyxdbkHrtqKxkY+p8WuI0xD6Tau4lC8uqo06nLHS/PolQTHh tMBPJZOqR3syOkbuCcAozVSTlTZvxWCCQWpDGv4qm9vsZHlwazm2cFobIqgD0yhVCX8w kLrYsU8yRKe71X+7z+Cz12MN3n45TlE/7BJwEBvIStwgzc5fHYGZ64LLYSb70odj1CeX vN2RKNE0pBlteBbyhRacd1O8AJHwgBXLnryWEGlFoRWvCKS5Rx2I6o4uoC0C6I5aFrgf X3nA==
X-Gm-Message-State: AOJu0YzloTItmGbbFD1WM4RI9tIwQNB4awwBFe6oYo1UJxA1ahYNcQ4n gPMHo+2Prz7oc0pMcZODUSTyEoAJuWRpj211CIppkJ1jEpq+yeQEgTrvuf/TF8Q+/1467X+qVKb 9p2I+yS5v1Q5DdVaNmyKKrO7B0CMIMLOin5AIaw==
X-Google-Smtp-Source: AGHT+IHQANQbSRtKeBgPzw8fKFmpvJxMLgpoBJgFxz1cfWo+dzO4FVhjLlknQibo6Wqw0lmWflehowRedgN7je55E0c=
X-Received: by 2002:a05:6870:1693:b0:27b:56b1:9ded with SMTP id 586e51a60fabf-27c3f2c3893mr4031720fac.5.1726651133729; Wed, 18 Sep 2024 02:18:53 -0700 (PDT)
MIME-Version: 1.0
References: <e522052c-3693-42cb-9b7b-c4cf0af0bbc1@orange.com> <IA0PR11MB77925E3F68F1E903FF3D47BED0612@IA0PR11MB7792.namprd11.prod.outlook.com>
In-Reply-To: <IA0PR11MB77925E3F68F1E903FF3D47BED0612@IA0PR11MB7792.namprd11.prod.outlook.com>
From: Dhruv Dhody <dd@dhruvdhody.com>
Date: Wed, 18 Sep 2024 14:48:17 +0530
Message-ID: <CAP7zK5YqRC4t8ecGvZXMZ0Z=B3-nMz1ZCjuBfCBD7TmjOZf5gA@mail.gmail.com>
To: "Samuel Sidor (ssidor)" <ssidor=40cisco.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007a373c0622614b78"
Message-ID-Hash: V4J6RCGN4YUCIHBR37B6R5QG4OSRURIH
X-Message-ID-Hash: V4J6RCGN4YUCIHBR37B6R5QG4OSRURIH
X-MailFrom: dd@dhruvdhody.com
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: "pce@ietf.org" <pce@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] Re: WG Last Call for draft-ietf-pce-iana-update
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/GB-iodoVlZNFIQkuEFPVWQ2365E>
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>

Hi Samuel,

Thanks for your review.

On Tue, Sep 17, 2024 at 7:21 PM Samuel Sidor (ssidor) <ssidor=
40cisco.com@dmarc.ietf.org> wrote:

> Hi Julien and PCE WG,
>
> I support progress of this document.
>
> 3 minor (non-blocking) comments:
> 1. Do we need to expand "PCEP" in document title? (It seems to be expanded
> in most of PCEP RFCs)
>

Dhruv: Fixed as "Update to the IANA PCE Communication Protocol (PCEP)
Registration Procedures and Allowing Experimental Error Codes"; PCE is
marked as well-known by RFC-Editor
https://www.rfc-editor.org/rpc/wiki/doku.php?id=abbrev_list


> 2. In section 3.1, shouldn't we use normative SHOULD/MUST when specifying
> what an "experiment" should/will do? (I understand that the whole section
> is even called as "Advice ...", so it seems that it is not really
> specifying requirements. However, in reality, it seems to be defining
> required behavior for anyone using experimental error types/values.


Dhruv: I personally prefer to not use normative keywords when they do not
apply to protocols or their implementations :)


> 3. Just a note: If I haven't missed anything, American English is used in
> most of PCEP drafts. I can see a few words from British English
> ("recognise", "synchronised",..) in this draft. That should be fine as long
> as we are not mixing American and British English in a single document (I
> don't see a specific example of some a word that would be specific to
> American English. I'm just raising this because there is a chance that
> could happen during merge of 2 drafts into current one).
>
>
Dhruv: Thanks. Fixed.

Commit ->
https://github.com/ietf-wg-pce/draft-ietf-pce-iana-update/commit/493c08e19c56fc3a72d6c4102e230173de01d2e0

Diff ->
https://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-pce-iana-update&url_2=https://ietf-wg-pce.github.io/draft-ietf-pce-iana-update/draft-ietf-pce-iana-update.txt

Thanks!
Dhruv



> Thanks a lot,
> Samuel
>
> -----Original Message-----
> From: julien.meuric@orange.com <julien.meuric@orange.com>
> Sent: Friday, September 6, 2024 2:24 PM
> To: pce@ietf.org
> Subject: [Pce] WG Last Call for draft-ietf-pce-iana-update
>
> Hi all,
>
> Since we have consensus, let's move forward with this simple fix to [1],
> as agreed with the IESG. This message starts a 2-week WG last call for
> draft-ietf-pce-iana-update-01 [2]. Please share your support or comments
> on the PCE mailing list by Friday September 20.
>
> Thank you,
>
> Julien
>
>
> [1] https://www.rfc-editor.org/cluster_info.php?cid=C519
> [2] https://datatracker.ietf.org/doc/html/draft-ietf-pce-iana-update-01
>
> _______________________________________________
> Pce mailing list -- pce@ietf.org
> To unsubscribe send an email to pce-leave@ietf.org
>