Re: WG Review: Effective Terminology in IETF Documents (term)
tom petch <daedulus@btconnect.com> Wed, 14 April 2021 11:39 UTC
Return-Path: <daedulus@btconnect.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA8C13A03FB for <ietf@ietfa.amsl.com>; Wed, 14 Apr 2021 04:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, MSGID_FROM_MTA_HEADER=0.001, NICE_REPLY_A=-0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=btconnect.onmicrosoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RDxL6pgKZgT0 for <ietf@ietfa.amsl.com>; Wed, 14 Apr 2021 04:39:09 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80118.outbound.protection.outlook.com [40.107.8.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EE1E3A03F6 for <ietf@ietf.org>; Wed, 14 Apr 2021 04:39:08 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mympmXl0OPCI5mq1wBWxF5y0VM1UfX+wmnpuIskRqR/fZNdt6auJd8QYnjZ47sicGw4vhjwrG7XANslEmYwJZ7r/IIoaWN98w0HbVb1hmNi8LLTpxnJ2ngs4g63vlHJxEv49Ss9zf8K7dgoy5hK7bjDMcNNpBmWGN1KRziCQCszIOaZEqwvoXPshGnbOFlXOlXVMWXgDfhkxVCQ2lMLW1VDufzNqW6dYLxtgno1x1iAutQAr99Qkm3OQsLEfbgtbV6OAwj/yHzHQ5XBynyPpoZjBBbyWU0VEbolrWF+1X/dyfGNwgUJl0mG7XbTFBTdRDLr/VXGtDViAL0BRY379Sg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xjEvX/lazi1ej55FB7F9JGClZmlDg+kqC4PpZe1CKkM=; b=f4262eNN2FWeYTFS7Y+K8zP7zMgbw8Xt+NnwbAgpWc+4UuHLSlx9HdjZ2D8ORhbz7Jf14y/JlsCBLDOGkqPdNNXCZFFxRn47nOiRB553dZuyDoXWuex+LrqBhSJk3I/l/cDE6QazvEaUj07NVzT3rlBM5OpFRdXykV21jboSFcoxbcXj4hL8g97dUtRf0XbLf8yVy/IwB3Kh3TA0Tg2+E8h/Xq4vm8DgzpwSe0x7LhpFDbk6u+7rJgrncpAwEZyGRq/koAtbkw9BOJgOcCmmBZmX6foP9c60EgjZ9gB7lW1owrA7h0c4KrY4JYgapxDjHZKzbduXUg2TsYzItFtpPw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=btconnect.com; dmarc=pass action=none header.from=btconnect.com; dkim=pass header.d=btconnect.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=btconnect.onmicrosoft.com; s=selector2-btconnect-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xjEvX/lazi1ej55FB7F9JGClZmlDg+kqC4PpZe1CKkM=; b=ZzPT+4riKAz6sg5uvvAwrLL0FzZGH6V9bTmhhSJELUIU42f9vDPCV0EGuQrZe8sGwC/2GgrU8n+GBlmR6G1HYTQw6XxjVJ7bLkZQpMF6ihbCxob7nRo8Ln6ledVZxzXTQNKPFXQsUgg+id6YOjsAAyGbtDjl1qhPuXR3T3m5rbo=
Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=btconnect.com;
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8) by VI1PR07MB5744.eurprd07.prod.outlook.com (2603:10a6:803:97::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.4042.6; Wed, 14 Apr 2021 11:39:06 +0000
Received: from VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877]) by VI1PR07MB6704.eurprd07.prod.outlook.com ([fe80::d461:48ec:82a3:1877%9]) with mapi id 15.20.4042.016; Wed, 14 Apr 2021 11:39:06 +0000
Subject: Re: WG Review: Effective Terminology in IETF Documents (term)
To: Jari Arkko <jari.arkko@piuha.net>, Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <6.2.5.6.2.20210401013907.0b3b7fe8@elandnews.com> <89383942-204e-a94e-3350-42bfb4165ba0@comcast.net> <792c4815-8c36-e5fa-9fbe-2e1cfa97239f@comcast.net> <D18D87D95723A68D8E75B6BC@PSB> <20210406152930.GR3828@localhost> <f52c46cf-03fb-6692-3a87-9b7db639f2e9@gmail.com> <DF5DCE5F-C1AA-4131-AC3F-56429ADC97CF@piuha.net>
Cc: IETF <ietf@ietf.org>
From: tom petch <daedulus@btconnect.com>
Message-ID: <6076D453.4050306@btconnect.com>
Date: Wed, 14 Apr 2021 12:38:59 +0100
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:38.0) Gecko/20100101 Thunderbird/38.5.0
In-Reply-To: <DF5DCE5F-C1AA-4131-AC3F-56429ADC97CF@piuha.net>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Originating-IP: [86.155.147.182]
X-ClientProxiedBy: LO4P123CA0106.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:191::21) To VI1PR07MB6704.eurprd07.prod.outlook.com (2603:10a6:800:18b::8)
MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from [192.168.1.65] (86.155.147.182) by LO4P123CA0106.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:191::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.20.4020.22 via Frontend Transport; Wed, 14 Apr 2021 11:39:05 +0000
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: 76520c11-987d-4954-c03c-08d8ff39e8f6
X-MS-TrafficTypeDiagnostic: VI1PR07MB5744:
X-Microsoft-Antispam-PRVS: <VI1PR07MB5744AFF6A99A7999A8F4FE2DC64E9@VI1PR07MB5744.eurprd07.prod.outlook.com>
X-MS-Oob-TLC-OOBClassifiers: OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 097v+8ggd0iYzti/T00CbqAVnaKw+V8la5fBu6PZk/14lR5FlDOz5jSycTCNXNZSdOfxWPjBML4N2IoRUAe9AGiHkfp7rKI2pMBxf7k9SfELItNVf3BJxtnpNMZRJ4UZwolvurtVgSTNkKeUnYx6JGcX8d2RSqXmNy977ks1QLRrQHRYs1Ju3tTsbETNC94/AA0ndQnx6QX17hr4UySe5GG60LZo5vdaqi6VB69rBhTmPTP5hV/X2Z8QrmiRevPxhcBMA30aN1dTuFMTFZmdRq3KscbqlJOnV7TNGLQqBYHcy0HCxFDb7lTKrn44FegD4TVJEXwE7NWcW1qM0sisoj1dT9tRX+jVk0Nuci2weS9A8NflHHHMklCPlRgBeI1/7c7QB1XYDHXp5pMnF69kFwj33w9L8GoVfJQk07cTaKzZE1FOg0G5kfze6lyBAJyi/1tVxbDtKeyqVVXhGllkUOgXOCDuDAi1Yyf+WJ46fN9qru/629h/bMHOS97rRm0TC6fHFm7wvUMNG32ZzLN3uW/80kympnnohs2Sg8HEhU/znWD4UETaVoWJpAbvwnt/N96Ruu4/QC+F2NJwmUfm7PdggftlTlnkcNqIYXhx2Y+4N6R0YaXgE9Mu0e+z4C0ZcQlf4Q9nSxlpsEdABctr7BKjL4x+OfPmSfJ7jRVFPf2RZ1IRdnalu2u2+4cxrpYMerkPzds3flZm/HED7mhj5SHSxAKy5PG6mmw7XHjJQFE=
X-Forefront-Antispam-Report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:VI1PR07MB6704.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(136003)(346002)(376002)(366004)(396003)(39860400002)(4326008)(2906002)(38100700002)(66946007)(6666004)(53546011)(66556008)(16526019)(16576012)(66476007)(478600001)(110136005)(38350700002)(316002)(8676002)(6486002)(956004)(2616005)(26005)(36756003)(87266011)(186003)(5660300002)(33656002)(52116002)(966005)(83380400001)(8936002)(86362001); DIR:OUT; SFP:1102;
X-MS-Exchange-AntiSpam-MessageData: rVNJCqac9wbg31QNXRNIJ+P/jwhI+QihU0t0tLuex/aMLjPWg/0gtyBlR+Y8t6w23lznPCiqaQMdjb/2B9H+RYYC5IKleMdeYn/ratA4VHF4YzSyBoJ5NPpyAKGjfypN+noFIgEy1vdvx7Wd7tS3T3cTSkd7olzHSli1Y7ELwCRi9GIwk1zwJt4W7e+sXBb/OUeDrrA64NxzQ8YlScj6qtMNAtY0tC3gFIzSGjGmmxB4y2o70J5vnA3Qk2OJphUFAx37ZPg6IaniyeqMyg3dHJ/em+2U+D76TcIdsKo+N4NKWjyHaTgiDvuWyscGiEchVYrQQG4QzjLf12fagcC74fEyFZ3QSTGUH7FD9VKeUG10Za/Y+BJ2RpI9LYAI6BB49U+ACm41HaafPRnfHoZI+RwQBnnv0CTj7LG0WYitJwQGI2UonJGK84A+s8F6Sb0Oc+jt+PnaEAyegZGbepy7yWNmUaMFa1TGbdxJ/H/Wsp7LyVshbrkndKk4mFTfd0xpb3RPGiytf1S2G3meFEKhsuSEXMgY6/vgw1AxbHgOh733zbQByaNfdkl7x6mDatdgpyw3idoychVTxcwf+KfAz8zEFOlitT9acoBA4sxMv3VsiueJtr+a+ZUdbeosv6dCKttr2g5h+ZUJ7j5CFvVp9uQJUskYz91zYMrNO/x6IObsGB07gHmSVMMx2z+9B1yK13+lAALr727JWex66Kmpv6ZrbDBa0gSvpO2DEs+jQ7NBBxAJO5jXfvPnih3EmpQYVo1tQlwM9EKIg3I1LG00PEdcVKUzzn9koQABg6lh6+wBcsTLnYZdWptqZ4JWd4A44gdhn5kEZRmQbSh64KQ6eKynl5solo54uPV92N5APs3sWmoko+U6PyYzfTO8mmSyDFWHLmSiyjXofqwyZK6NN6UB+G4Leny8DWEaDAl4tAlom4oBXD9cz8kztQOGcNdueyHxGtru00Xzrh7/ii8BtPQSoOVT+7OpdMsvMVmtXxBPYRi3xuJbnrWcgrE0ywFdITfBLxzY3NDxcWfZVZwhET3MHPAEtDzLKuM8Ks5zlopm26KVicVJ6cT9EZgp/AP5lW7FqTFnmGoTIbDmPjOPVTyFoe2eDv6wyA1+ruOOuM+I3h0NPZgWLZCSrB8kA3mWvzWbeb0MXXuZ3C6CdMU0kq76H2fzchySzbIaGUwMlzwkXQ1psdmwSmqW7anXI7LCn8a9THbc75a6XMZTQ1kFa5ddcpoRAliCszKJh0MEp5mWDzWu64BeVcCG4HZ2U+tTbpGXHy2mikMwkTm5omgd6WoSxn4UsXa5HK3qCBmOmIxKiMakfvrSFlP+YYHV7SjB
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 76520c11-987d-4954-c03c-08d8ff39e8f6
X-MS-Exchange-CrossTenant-AuthSource: VI1PR07MB6704.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Apr 2021 11:39:06.2048 (UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: cf8853ed-96e5-465b-9185-806bfe185e30
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: hU7tC0hlwrRBPeCYSEeuhKcxj4Jo/cBx0Es5p+aXzgR9xvLRPJ9yE5gUXzS25+of8Xg8FikJNh/IUgvSW8oezg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR07MB5744
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/iuNiC9JdRKAGOwm8C2b5vZyn0II>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Apr 2021 11:39:14 -0000
Jari At a tangent to the discussion on the role of the RFC Editor, I note that the style guide references TERMS, which is a Terms List for people to use, e.g IPsec and not IPSec. Calling a WG TERM but having it look at what is for me a very different aspect to terminology, inclusiveness, seems to me to be a good source of confusion in times to come. Tom Petch On 13/04/2021 17:44, Jari Arkko wrote: > Brian, > >> I believe that the charter is good enough as it is, but I also believe >> that the IESG should consider not only whether there is consensus on the >> charter text, but also the basic question whether this issue should be >> handled by the IETF at all, rather than by the RFC Editor. > > I think that’s a good question. > > I have a view on that, and interestingly I came to a different conclusion than you did. Perhaps it would be useful to talk about this a bit further. > > So, my reasoning is that the right place for most IETF decisions is at the working groups. (Subject to some common policies and full IETF review, of course, as discussed in the other thread…) > > I could imagine RFC Editor adjusting text in a security considerations section that talked about some filtering and used older versions of “denylist” in the text. But I’m not sure I’d want the RFC Editor to adjust a major term picked by a working group in their protocol, particularly when the change may cause differences between a new RFC and older RFCs to occur. I’d want the WG to make that determination. For an example, see https://tools.ietf.org/html/draft-ietf-tls-rfc8446bis-00#section-1.2 <https://tools.ietf.org/html/draft-ietf-tls-rfc8446bis-00#section-1.2> > > All this leads me to believe that the WGs are and should be in charge of the bigger modifications. This still leaves room for: > > - a new terminology working group to provide guidance & principles > - RFC editor to check and adjust text (and possibly highlight issues back to the authors)* > > Brian, what was your thought regarding the division of work and who would do what? And in your mind, what level of decisions would be required for actions similar the examples above? > > Jari > > *) Lars’ working group proposal does not involve the working group actually developing a list of terms. That too could possibly be a thing that the RFC Editor could do. But of course the community could do it also, as volunteers in some design-team like activity, or we could find an entirely external resource that is updated with information. > >
- WG Review: Effective Terminology in IETF Document… S Moonesamy
- Re: WG Review: Effective Terminology in IETF Docu… Lars Eggert
- Re: WG Review: Effective Terminology in IETF Docu… Nick Hilliard
- Re: WG Review: Effective Terminology in IETF Docu… Andrew G. Malis
- Re: WG Review: Effective Terminology in IETF Docu… S Moonesamy
- Re: WG Review: Effective Terminology in IETF Docu… Michael StJohns
- Re: WG Review: Effective Terminology in IETF Docu… Michael StJohns
- Re: WG Review: Effective Terminology in IETF Docu… Lucy Lynch
- Re: WG Review: Effective Terminology in IETF Docu… Adam Roach
- Re: WG Review: Effective Terminology in IETF Docu… Lloyd W
- Re: WG Review: Effective Terminology in IETF Docu… Adam Roach
- Re: WG Review: Effective Terminology in IETF Docu… Michael StJohns
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… Carsten Bormann
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… Jari Arkko
- Re: WG Review: Effective Terminology in IETF Docu… Brian E Carpenter
- Re: WG Review: Effective Terminology in IETF Docu… Joel M. Halpern
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… Joel M. Halpern
- Re: WG Review: Effective Terminology in IETF Docu… Keith Moore
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… Stewart Bryant
- Re: WG Review: Effective Terminology in IETF Docu… Masataka Ohta
- Re: WG Review: Effective Terminology in IETF Docu… Masataka Ohta
- Re: WG Review: Effective Terminology in IETF Docu… Leif Johansson
- Re: WG Review: Effective Terminology in IETF Docu… Sam Hartman
- Re: WG Review: Effective Terminology in IETF Docu… Leif Johansson
- Re: WG Review: Effective Terminology in IETF Docu… John Scudder
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… Brian E Carpenter
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… Brian E Carpenter
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… lloyd.wood@yahoo.co.uk
- Re: WG Review: Effective Terminology in IETF Docu… Jari Arkko
- Re: WG Review: Effective Terminology in IETF Docu… Salz, Rich
- Re: WG Review: Effective Terminology in IETF Docu… John Levine
- Re: WG Review: Effective Terminology in IETF Docu… Brian E Carpenter
- Re: WG Review: Effective Terminology in IETF Docu… Brian E Carpenter
- Re: WG Review: Effective Terminology in IETF Docu… Keith Moore
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… tom petch
- Re: WG Review: Effective Terminology in IETF Docu… Nico Williams
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… John C Klensin
- Re: WG Review: Effective Terminology in IETF Docu… Lloyd W