Re: Making RFC2119 key language easier to Protocol Readers

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 05 January 2013 08:36 UTC

Return-Path: <abdussalambaryun@gmail.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 0693821F8464 for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 00:36:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ln2qZMM+9q3u for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 00:36:56 -0800 (PST)
Received: from mail-vb0-f51.google.com (mail-vb0-f51.google.com [209.85.212.51]) by ietfa.amsl.com (Postfix) with ESMTP id E794421F8450 for <ietf@ietf.org>; Sat, 5 Jan 2013 00:36:55 -0800 (PST)
Received: by mail-vb0-f51.google.com with SMTP id fq11so17523083vbb.10 for <ietf@ietf.org>; Sat, 05 Jan 2013 00:36:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WWFKDeMO1i34H4dv24WmXy8kKOTbC4hUfEiIiHdkITY=; b=V0sLh1xu2b8pmi/2Rl47caSWZ0nMJ4/I/ja2DRDsoOxmbey916rrBw0gNfYBWvLyba XGq5LjPAOkBnljVsbOR/pCo5ZWhm1kMOrC1L46lVJBvB+96KRhHRFwqSb4yl/DQYuquC UV+Jzn44Ue7Aapvh4UfzAtEUYY6E9v9zot/XJZMefXGAH58SNYuBrd/tOHfO/1KoZNPD YQMN2ERLOOgyTNlXiIpu8BnPOvH4HJ9Iem1WCesS3b/p7j2oQTPoex4q3j7QLOiG/w0n Rpbg9n+vHgGHAwG6ogczIE1SwYd7R22F8NZdyy0F8Yq9z8R7uqNHyPkuN0etLg9aa+KT IJCA==
MIME-Version: 1.0
Received: by 10.52.70.46 with SMTP id j14mr67766923vdu.99.1357375015406; Sat, 05 Jan 2013 00:36:55 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 00:36:55 -0800 (PST)
In-Reply-To: <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ8_a8cRSKrHzE4fZSrMNO6pGLa9vCcHzKUmHsVtCWRCf6g@mail.gmail.com>
Date: Sat, 05 Jan 2013 09:36:55 +0100
Message-ID: <CADnDZ8_p-Ako98uwnQvq_hm4OOBXS1hSMFxkZvaPXgfXirFOdg@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: narten@us.ibm.com
Content-Type: text/plain; charset="ISO-8859-1"
Cc: ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Sat, 05 Jan 2013 08:36:57 -0000

>IMO, too many specs seriously overuse/misuse 2119 language, to the
detriment of readability, common sense, and reserving the terms to
bring attention to those cases where it really is important to
highlight an important point that may not be obvious to a casual
reader/implementor.

also to highlight an important point that may not be obvious to
imlementors which are non-English speakers/writers.

AB