Re: Updating RFC2119
Scott Brim <scott.brim@gmail.com> Sun, 22 July 2012 15:49 UTC
Return-Path: <scott.brim@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 669B221F865C for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:49:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9J1eRgz0tLWH for <ietf@ietfa.amsl.com>; Sun, 22 Jul 2012 08:49:44 -0700 (PDT)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id CF84821F8659 for <ietf@ietf.org>; Sun, 22 Jul 2012 08:49:44 -0700 (PDT)
Received: by pbcwy7 with SMTP id wy7so9693032pbc.31 for <ietf@ietf.org>; Sun, 22 Jul 2012 08:50:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=P9KVyEN2p+2Q3cE3iCMuQom4x8KZRuzf0c8v5RR9pvs=; b=FB8Q/TROH3GZ/p7/81ZLTAthbyT89D9dyT0oq18tleYXdZVM3gdgptXi6nq2gNuX9/ wCGmsRZIDjABFRqv/uTVJW8SDCw2A5bBQu5NxdBxcFfcuGmcnmAay4AXkYlfnaDb2qvK bcQXgdaGUPaXMu2HV4L0vv39MC2JYvP3Al8aIHuHWtp/gl09bpaWvfjARPnrI77jVijW TT10fclyfz8hLcquB3jj7hgFsQ8+lgW7tpudGBC1j3eZ4EE32zEb6CjQm+ZNosifWvkm FDgfytC2DJnOKjgtKZlzFdaHUQEXvnL3H17quy7XGV5Vmq1V4IO1mL93vpL+lQq4up+x duSQ==
Received: by 10.68.218.133 with SMTP id pg5mr28555648pbc.140.1342972246766; Sun, 22 Jul 2012 08:50:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.220.132 with HTTP; Sun, 22 Jul 2012 08:50:26 -0700 (PDT)
In-Reply-To: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
References: <CADnDZ89tHLL5OsLwcT4P76w=W-jShM55HfVm+FSW2ubBerWiCQ@mail.gmail.com>
From: Scott Brim <scott.brim@gmail.com>
Date: Sun, 22 Jul 2012 11:50:26 -0400
Message-ID: <CAPv4CP95Rhma3reOvrWfrWQE_mqsyY8bL2EvkZq5hD6gbyf_ow@mail.gmail.com>
Subject: Re: Updating RFC2119
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: 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: Sun, 22 Jul 2012 15:49:45 -0000
On Sun, Jul 22, 2012 at 7:17 AM, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote: > Hi All, > > I am working on an I-D which is intended as proposed standard but need > some addition requirement language. Therefore, I want to propose to > write a draft to update RFC2119 to add some other language requirement > as below: > > IF x, THEN y: > > ELSE: > > ELSE IF: > > Please send your comments or advise, thanking you, That doesn't have to be in 2119. Lots of RFCs have pseudocode at various levels of rigor. Just look around at some protocol specs for examples.
- Updating RFC2119 Abdussalam Baryun
- Re: Updating RFC2119 Scott Brim
- Re: Updating RFC2119 Melinda Shore
- Re: Updating RFC2119 Stewart Bryant
- Re: Updating RFC2119 Abdussalam Baryun
- Re: Updating RFC2119 Stephen Farrell
- Re: Updating RFC2119 Abdussalam Baryun
- Re: Updating RFC2119 Dave Crocker