IETF Logo Mail Archive

Re: [v6ops] Comments on draft-ietf-v6ops-ipv6-ehs-packet-drops-01: "can" vs "may" in English usage.

tom petch <ietfc@btconnect.com> Fri, 04 December 2020 17:09 UTC

Return-Path: <ietfc@btconnect.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D94F3A0E43; Fri, 4 Dec 2020 09:09:22 -0800 (PST)
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, 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 V3XNiTQCgRo8; Fri, 4 Dec 2020 09:09:20 -0800 (PST)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150134.outbound.protection.outlook.com [40.107.15.134]) (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 5DCE63A0E3B; Fri, 4 Dec 2020 09:09:14 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RJTYpFcBrJ21f6ECneO68eRU7D8CRdOWXQY5vM58ZNyeh/Wg0nUdf7SsyYrhqJQRxnhS8Pkw9Uqms9wPTnvBbduDdk2epKZH+dAKzNi0d3HkUMaKpiEnVGdOI8M0u0HkVPCwGxSxpc4r6lyzQsSgzGuHF96WVN4t4xOEpKYJiTXAvy3ScF/J5DV62JTdiHtfAJb9fRSOJKo0S+LF8NGsmbf7rT2KKgnJa50sASE7qCabumig4iek2lHC7GKWOdtKdCf6BteAHv0cXDTA2gpn0DAPnlrthBBaHsbjBzaZ3WI5vHvPTGJzU2iUu/vN3fty9mz9E7j8aK+U1AuacqukNA==
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=Sv84j2jjKij6B6xJAX/JYCYhWyWGf1rgcZHVlqU/gO4=; b=iKaoJ4rAYPO0kcMZzZCbCaBuXU2PeRF2aBWol4MinIZqxIxvRx2ZiyI0hNmqkA/S07SLwH+BJtKZbZGPpxgap2aOf3lknH2gKpDJFfhQJuzgDgeRXRk7yk8CNdYnxbJNgki6lLHLdXuT2FXxUkYVlDbu8XavihAaV5X0se/vk5TAi0k396jKPNg/9z2/lcpvrbC36WOydbIjTP07Fc4xMH97ruLCdoNVa5wOLgiSqbt+9FSRzgsdff6ekBnP0N5tNhRSRERqkC+AmK0yMDxX6AeQi3hurQRDTgvDQ56q1GZXbcFM7LZlzN/9tQjeREYEjN4nl847g6Z6Mu/ZcxqYsw==
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=Sv84j2jjKij6B6xJAX/JYCYhWyWGf1rgcZHVlqU/gO4=; b=iV4z3MpnkKWsbEnN26UGk2Lio6+CJ/sfvPTobcxGQ0Kz817V9tVX9qJUYc7+gTBCpK3MyILY2zfGPaXYBVGroGvn6nGLnY2yMLt4YO9wTvGD4j2Nei3E/pwg0yrJu+0kdr7pT/TDLSIdc0SB7YsfW4U5EYg+x2ycOUV6I+7d9PI=
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com (2603:10a6:20b:134::11) by AM7PR07MB6785.eurprd07.prod.outlook.com (2603:10a6:20b:1c2::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3632.9; Fri, 4 Dec 2020 17:09:10 +0000
Received: from AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::ad44:1086:3767:a804]) by AM7PR07MB6248.eurprd07.prod.outlook.com ([fe80::ad44:1086:3767:a804%7]) with mapi id 15.20.3632.018; Fri, 4 Dec 2020 17:09:10 +0000
From: tom petch <ietfc@btconnect.com>
To: Fernando Gont <fgont@si6networks.com>, Fred Baker <fredbaker.ietf@gmail.com>
CC: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IPv6 Operations <v6ops@ietf.org>, "draft-ietf-v6ops-ipv6-ehs-packet-drops.authors@ietf.org" <draft-ietf-v6ops-ipv6-ehs-packet-drops.authors@ietf.org>, Fernando Gont <fernando@gont.com.ar>
Thread-Topic: [v6ops] Comments on draft-ietf-v6ops-ipv6-ehs-packet-drops-01: "can" vs "may" in English usage.
Thread-Index: AQHWyZdmMR9RE2wt+UO2CzbqPBA7pqnlwh0AgAFplJ0=
Date: Fri, 04 Dec 2020 17:09:10 +0000
Message-ID: <AM7PR07MB62480C06B5F04AFA7EA5EFF2A0F10@AM7PR07MB6248.eurprd07.prod.outlook.com>
References: <d97ca0fd-776a-1525-50d1-3a62fd7edf5f@erg.abdn.ac.uk> <0c121812-44cf-119e-fd09-bb138ff789de@erg.abdn.ac.uk> <d1814cfd-d603-9cc0-f6ae-d37feafb62b8@si6networks.com> <2B7068A6-AB53-4685-AF47-9290A745BD13@gmail.com>, <fcd0a675-afe6-a487-cc8e-cbf453d2f556@si6networks.com>
In-Reply-To: <fcd0a675-afe6-a487-cc8e-cbf453d2f556@si6networks.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: si6networks.com; dkim=none (message not signed) header.d=none;si6networks.com; dmarc=none action=none header.from=btconnect.com;
x-originating-ip: [86.146.121.140]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0ce831a6-71d5-4195-f8ae-08d89877517a
x-ms-traffictypediagnostic: AM7PR07MB6785:
x-microsoft-antispam-prvs: <AM7PR07MB6785BE853B756A3FBE01D7B9A0F10@AM7PR07MB6785.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:6430;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /XfC2P15ft8zlP2yy0Z6t6iCaibLBEKxb7MRWWPXcbcXtgtOkfjIcDDAted3sPcMRuCLtDQggBDlXqcmZ/gevaq0WXghunjJlsokFdWjqbwRA3dxRWJN0DSiGGuoKFKEfN0PHi4tfNZgaxRUyiX/r0zxf8l7fwS9kufEQILDVLUFC6bZGuCvDY8ZyX6lP7moiApjpMrvk+zYxgMwgufAH87mjQgACW75PkHxM9f3LfuzTRj92y4IgxcGjvv7B5aesENbR8XFcwwtKTqAoXoU7JkQW0wrpvZiVhaYOdhE1wMcwaltHXA401Z5ZGJ3EBzze/ww/R4lY2JlBDgvMl9XbbIx9p6lumOEzfjLkkmKq4tiF/x0a4NMT+PonfroT9N1H7Ht3cDpqVlHBQF+k5bcgQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM7PR07MB6248.eurprd07.prod.outlook.com; PTR:; CAT:NONE; SFS:(376002)(346002)(366004)(39860400002)(136003)(396003)(8936002)(86362001)(8676002)(33656002)(966005)(478600001)(26005)(2906002)(6506007)(53546011)(83380400001)(186003)(110136005)(55016002)(9686003)(54906003)(316002)(71200400001)(4326008)(66446008)(64756008)(66556008)(66476007)(66946007)(7696005)(5660300002)(52536014)(76116006)(91956017); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: SBvI9GCirOJZzh7SkJseac8QJYBULPomiBETQ7pHGPhCQxja2BhbZojrKKkCmoTKtZQQ6ZQoN2bwNk9YeAO578CRenzt6PAGOxd+OulAMVwgCP5zNG6VWSCHV0LqdT/warbBxc5wz4Bz8mdBphCqxn/upiMq/0dVnVI6Pm8tQH9Qlwxi3yjfB7/sGNh6C0XgSatGm1upX2rj5sno/koJEXWPUgbTEYMdifHym2kaB8PpJk+tquQiD640MAtB9hgVYGpjE3K4Jm7O74zh9fblvD2IRKGTy+y5cUEAzyvLPs8DYaWkXgXliTM4nrcfIak8DH8aQZJp0WCU5toQS2Ijy05evqEtK4a1fe08b0pj6JRlcca9xIQU5vW9Oa9xcwUvszJflyNR6JbrlAKvevhDmdhQSN2pSW5436514Apczy2ilY2/hpLOSVeEnujxyIhWF4kG1gzQA+z79CXFlbF54O92oJcTy2/40CVlw0XTZtslwavzYqn7oJfcpofY/RKHaYxJRxVWpX3lKZwNllI4fofJ2sQ6kGe3xNolm9m1qv83H9/dkXa6o8KBEsuxQIbfJDeOHb2424zRl5qYrra0QyqYh0JSUMfEZrtA4sfI+5GxwNTP9PLDpBu1DKuE0T52Kx2GYr+e2YGAB/eJ15kl8gW3E4iah9AssHiWOBGjcYpD4WK7ULEDDwNx5FFU4OoeM/uH4MkHG3O5LiDByTPfLTkVjrI7BOq6OIIwqPZFncMyFWo77Rct7WGU6GxS8zJR/Nb9sLreIx80vgp0jRVuq5erWspOC3CmXKKWWSHSaT/TmgTOkLjyIAL1PoirkBWhRh6gjEuUWHmcbh3Cq2P/ZZVjE/h/oA4X396afx2vLntErrcAZ9JE3fX2vQcsc8qLywXdP5mhMFlNt/R20kRwCPH8L6sRD9fcxuXo98VZ1uKmylX1mJdEjC5zDr+qIbyxhu/diBmxouuTfct37zkebSnWoYI1woH96cOA+z8fcdQ=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: btconnect.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM7PR07MB6248.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0ce831a6-71d5-4195-f8ae-08d89877517a
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2020 17:09:10.7602 (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: Ex2ohU6WbyrHD0h5EUMEBNsBAytSPnSEo9GVnl5/uUAIpNwuDOq4oClANLIor4ts3CQPVDImQqjkXyCDW6rPaw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM7PR07MB6785
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/4NqML1B_sTTcQBNkozXKnkRX6P4>
Subject: Re: [v6ops] Comments on draft-ietf-v6ops-ipv6-ehs-packet-drops-01: "can" vs "may" in English usage.
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Dec 2020 17:09:22 -0000

From: v6ops <v6ops-bounces@ietf.org> on behalf of Fernando Gont <fgont@si6networks.com>
Sent: 03 December 2020 19:29

On 3/12/20 14:11, Fred Baker wrote:
>
>
>> On Dec 2, 2020, at 9:52 AM, Fernando Gont <fgont@si6networks.com> wrote:
>>
>> ("can" = ability, "may" = possibility)
>
> I tend to use "can" in the sense of capability, which may correspond to your word "ability". "May", however, is about permission. "You can get get hot water from the kitchen" indicates that hot water is to be found there, and that you have the capability of trotting off there - whether or not you're interested in hot water or have any desire to go to the kitchen. "You may get hot water from the kitchen" gives you permission to go to the kitchen for that purpose.
>
> Note that this differs from colloquial usage. "Can" is often used in the sense of "may" in common usage ("can I please have some candy?" with the meaning "may I please...?"), which can be very confusing. In written communications, I try to keep theses straight.

Thanks for the note! I will definitely go back to my grammar book and
try to save everyone's time -- I do remember that the last year I took
English lessons there was a unit about "need" vs "must" vs "have to" vs
"may" vs "can" vs "might". I also remember another on "that" vs "which".
Definitely need to check both of these, since I've been getting both of
them wrong lately :-(

<tp>

My pet hate is those who say something cannot be done when it patently can; they just do not want to say they will not do it.
You might want to add to your list 'e.g.' versus 'i.e.' a choice which does change the meaning and which I think is wrong in some I-D.  A statement that an option can be signalled by an IGP e.g. OSPF is very different to saying that an option can be signalled by an IGP i.e OSPF.   I came across one such earlier this week.

Tom Petch


Thanks for the help!

Regards,
--
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492




_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email