Re: [Pce] Lars Eggert's No Objection on charter-ietf-pce-07-04: (with COMMENT) Thu, 14 December 2023 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 33477C14F680; Thu, 14 Dec 2023 07:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.105
X-Spam-Status: No, score=-7.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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WoY263oB5_tG; Thu, 14 Dec 2023 07:31:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 46BF3C14F60C; Thu, 14 Dec 2023 07:31:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;;; q=dns/txt; s=orange002; t=1702567878; x=1734103878; h=message-id:date:mime-version:subject:to:cc:references: in-reply-to:content-transfer-encoding:from; bh=PNEh3kcjfuhX3qW7Sn+o5gfvBAuYRjcDoueANp6BIK0=; b=Vasse6J5koecYG7TMHweZn4Pf0yac5fxKa1JITwOn1XAdqtAOtNEjnuO 2MOo7n4z2yf4DVnM9lBwc3jGEcYpl1V3x1V0BG4PHTmbYpoKBLDngGQ5P tPXvd3GUPd+wzu+21RbeHR/fvanqJ5w2Haf7rDicpnm3YDyzfAkicG5tE 4X0EoAOiOPumegXSYCupZqJIbWOM+c2D/6cX8LeFXSMAMJICb0f9bxI7l 2Pu8n6U8DmVZjGKzJH+WIyYBNNXRK4bsi+zMUqdQFbk+9pxhYiP+8ornS 1TU/YxBXIEziDtXmwEnyMgi50OROhsvqpeGYPxyz5jHL7BiDJRKg8xfdq w==;
Received: from unknown (HELO ([x.x.x.x]) by with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Dec 2023 16:31:16 +0100
Received: from unknown (HELO OPE16NORMBX407.corporate.adroot.infra.ftgroup) ([x.x.x.x]) by with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 14 Dec 2023 16:31:16 +0100
Received: from [x.x.x.x] [x.x.x.x] by OPE16NORMBX407.corporate.adroot.infra.ftgroup [x.x.x.x] with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.35; Thu, 14 Dec 2023 16:31:15 +0100
X-IronPort-AV: E=Sophos;i="6.04,275,1695679200"; d="scan'208";a="80080213"
Message-ID: <>
Date: Thu, 14 Dec 2023 16:31:13 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US, fr
To: John Scudder <>, Lars Eggert <>
CC: The IESG <>, "" <>, "" <>
References: <> <>
Organization: Orange
In-Reply-To: <>
X-Originating-IP: []
X-ClientProxiedBy: OPE16NORMBX603.corporate.adroot.infra.ftgroup ( To OPE16NORMBX407.corporate.adroot.infra.ftgroup (
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <>
Subject: Re: [Pce] Lars Eggert's No Objection on charter-ietf-pce-07-04: (with COMMENT)
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Path Computation Element <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 14 Dec 2023 15:31:23 -0000

Hi John,

I guess Lars points "native" out because it appears in the milestones. 
It's there because it's reusing the title of the associated draft, which 
is a reference to the title of RFC 8821...

As I'm not a "native" English speaker, I can't really evaluate how much 
offensive the term is. I also see that the NIST table [1] is rather 
pragmatic and includes an example of "language taken directly from that 
external specification" (on terms that should clearly be precluded). So 
I wonder how much effort should be put on that change...




On 14/12/2023 15:46, John Scudder wrote:
> I don't see the word "native" in the charter text?
> John
>> On Dec 14, 2023, at 8:02 AM, Lars Eggert via Datatracker <> wrote:
>> Lars Eggert has entered the following ballot position for
>> charter-ietf-pce-07-04: 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.)
>> The document, along with other ballot positions, can be found here:
>> ----------------------------------------------------------------------
>> ----------------------------------------------------------------------
>> # GEN AD review of charter-ietf-pce-07-04
>> CC @larseggert
>> ## Comments
>> ### Inclusive language
>> Found terminology that should be reviewed for inclusivity; see
>>*inclusive_language__;Iw!!NEt6yMaO-gk!CS86MpyLAch3FBrrIHUnybIAvaSiSxNIJnzru9PIKMOslJrRBg6FT0ZuyRO_PbZq2Fn3e8cFfj-W$  for background and more
>> guidance:
>> * Term `native`; alternatives might be `built-in`, `fundamental`, `ingrained`,
>>    `intrinsic`, `original`
>> ## Notes
>> This review is in the ["IETF Comments" Markdown format][ICMF], You can use the
>> [`ietf-comments` tool][ICT] to automatically convert this review into
>> individual GitHub issues. Review generated by the [`ietf-reviewtool`][IRT].
>> [ICMF]:;!!NEt6yMaO-gk!CS86MpyLAch3FBrrIHUnybIAvaSiSxNIJnzru9PIKMOslJrRBg6FT0ZuyRO_PbZq2Fn3e6kYFONU$
>> [ICT]:;!!NEt6yMaO-gk!CS86MpyLAch3FBrrIHUnybIAvaSiSxNIJnzru9PIKMOslJrRBg6FT0ZuyRO_PbZq2Fn3e7EYScuX$
>> [IRT]:;!!NEt6yMaO-gk!CS86MpyLAch3FBrrIHUnybIAvaSiSxNIJnzru9PIKMOslJrRBg6FT0ZuyRO_PbZq2Fn3e-z1ASAx$

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.