IETF Logo Mail Archive

Re: Making RFC2119 key language easier to Protocol Readers

Mikael Abrahamsson <swmike@swm.pp.se> Sat, 05 January 2013 09:13 UTC

Return-Path: <swmike@swm.pp.se>
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 D541A21F8756 for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 01:13:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 sN7VKNTdJYAJ for <ietf@ietfa.amsl.com>; Sat, 5 Jan 2013 01:13:11 -0800 (PST)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) by ietfa.amsl.com (Postfix) with ESMTP id F00E821F8433 for <ietf@ietf.org>; Sat, 5 Jan 2013 01:13:04 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 08F1D9C; Sat, 5 Jan 2013 10:13:04 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 024F89A for <ietf@ietf.org>; Sat, 5 Jan 2013 10:13:04 +0100 (CET)
Date: Sat, 05 Jan 2013 10:13:03 +0100
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: ietf <ietf@ietf.org>
Subject: Re: Making RFC2119 key language easier to Protocol Readers
In-Reply-To: <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
Message-ID: <alpine.DEB.2.00.1301051010080.26235@uplift.swm.pp.se>
References: <CADnDZ8-yCxUbrD9oFyQKkJuTgDZbamnV8K4GU+sAN5SekpyHAA@mail.gmail.com> <CADnDZ88XgyNXiu1fdK3WB7jrZTmfuvAc5U1XyAxjprZf6=7P4Q@mail.gmail.com> <CADnDZ8_pd5ZrnucZAoK5WDXUgK9gQhHm+GJe7PihDQzx1uUsaw@mail.gmail.com>
User-Agent: Alpine 2.00 (DEB 1167 2008-08-23)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
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:13:12 -0000

On Sat, 5 Jan 2013, Abdussalam Baryun wrote:

> 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.

The problem here is that I want them to pay back some of the money (or 
take back the equipment totally and give back all money) for breach of 
contract, when I discover that they haven't correctly (as in intention and 
interop) implemented the RFC they said they said they were compliant in 
supporting.

Ianal, but it feels that it should easier to do this if there are MUST and 
SHOULD in there and I asked them to document all deviations from these.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email