IETF Logo Mail Archive

Re: Making RFC2119 key language easier to Protocol Readers

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 05 January 2013 09:08 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 E808A21F863F for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 01:08:33 -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 0pJTw3kao3xd for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 01:08:33 -0800 (PST)
Received: from mail-vb0-f52.google.com (mail-vb0-f52.google.com [209.85.212.52]) by ietfa.amsl.com (Postfix) with ESMTP id 3239721F8588 for <ietf@ietf.org>; Sat, 5 Jan 2013 01:08:33 -0800 (PST)
Received: by mail-vb0-f52.google.com with SMTP id ez10so17111363vbb.39 for <ietf@ietf.org>; Sat, 05 Jan 2013 01:08:32 -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=GpfWqwfijJrkBgW/f1lymN1Fq1aGwjKFPZOMmOSgKWk=; b=YxxnPnVf1koZnHs5tIAlOjMr/3GRbS2T0w/BdFuoEBHYquEQCWR1mdptb28eGVPJva sZtu0c2PLS9FDtyB8TfvcU908QxXFRINKZcLyRMzrwrwjDoojeW12L8XBPv0qRZhZAVU sdFQPjWJXBt71SBD/yKR7Qx4o+8pQIIdfGfPjcY338qH/SInfSkecxn4KcpE4nWSXg7C D4z88HQvSbhOTADUYrjQyVnOSZ0vFuEIEqUPFaL21bSUsusisSNDqFFjCg4oZleWKmEo L+TJrjoRQYYA8NKKFGUPpKcjZPmXcWqJpePU4BgdJnbWs2HAmfGPIA5PDZfk3yHpoM9M KN6g==
MIME-Version: 1.0
Received: by 10.52.21.179 with SMTP id w19mr69198079vde.55.1357376912674; Sat, 05 Jan 2013 01:08:32 -0800 (PST)
Received: by 10.220.145.5 with HTTP; Sat, 5 Jan 2013 01:08:32 -0800 (PST)
In-Reply-To: <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com>
Date: Sat, 05 Jan 2013 10:08:32 +0100
Message-ID: <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: swmike@swm.pp.se
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 09:08:34 -0000

Hi Mikael

>Also what it means following things in it that is not RFC2119 language.

It will mean, you should understand me/english/ietf/procedure even if
I don't have to explain, and you need to understand English well even
if you are a great implementor or great programming language speaker.

AB
===

On 1/5/13, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> I totally agree with you,
>
> AB
>
> +++
> As an operator, I purchase equipment and need to write RFQs. I would
> like to able to ask more than "does the product implement RFC
> <whatever>", I want to also ask "Please document all instances where
> you did not follow all MUST and SHOULD, and why".
>
> Otherwise I think there needs to be better definition of what it means
> to "implement" or "support" an RFC when it comes to completness and
> what this means as per following SHOULD and MAY.
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>

v2.23.0 | Report a Bug | By Email