Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
Abdussalam Baryun <abdussalambaryun@gmail.com> Wed, 01 August 2012 18:20 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 3F93021F8821 for <ietf@ietfa.amsl.com>; Wed, 1 Aug 2012 11:20:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.481
X-Spam-Level:
X-Spam-Status: No, score=-3.481 tagged_above=-999 required=5 tests=[AWL=0.118, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 Tm4ATGWbH784 for <ietf@ietfa.amsl.com>; Wed, 1 Aug 2012 11:20:00 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 737D211E82CA for <ietf@ietf.org>; Wed, 1 Aug 2012 11:19:59 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so7955931vbb.31 for <ietf@ietf.org>; Wed, 01 Aug 2012 11:19:50 -0700 (PDT)
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=WsM+kkhpOQMc/AmwnSo8StF8PZkZGrpdN7Ejo8Xn/wM=; b=j8AfD2ibbKIblH+s385txSfeTaKNOiuoOqa8xmQm95dOltGQw7vG4zM90cOZiK5/GE 5OuN3FjLlWZLNV9cnO4EvtdAK3BheMNcpEktbwe7FaOhf5LaAnA53mQqEHImaRZnKYAy NEB5rZSiP98+DWfpTs0FMl9K3+WNb+qUK9q5lEfxvQhIsXAylEbm7gBAuaXDv7KHZvY5 u+baKxrCy1kUXRZcf+LNiruL8JXxe7N1MsALI3LMeYZj5gANc/A+qqluANy0ExhZnoG2 tQaSveI/arzE03Yum6Ih/KMJQE8lLbsA19cDMI2E40nWcDH7yByqwTiHE3wdHQEhJQ5X 6O3g==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr15799915vdb.10.1343845190581; Wed, 01 Aug 2012 11:19:50 -0700 (PDT)
Received: by 10.220.141.200 with HTTP; Wed, 1 Aug 2012 11:19:50 -0700 (PDT)
In-Reply-To: <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
References: <CADnDZ8-zqjf=e1RHp+pr_Jh4x=u5T_pY95U8i_ORRMLXtWLm_A@mail.gmail.com> <CAC4RtVDwx9JxGK=kRZV=-BiJNXmzJJuH7212QPKrv8t8GmdFnA@mail.gmail.com> <CADnDZ8-6iTjav+utqDOXriKc3FUVesHAy0CD5FtFQjrWDMvuWA@mail.gmail.com> <CAPv4CP-LBGVPn9O5N1HmbUqw8H7dpK66q7JEcrYA_Sd395giCA@mail.gmail.com>
Date: Wed, 01 Aug 2012 20:19:50 +0200
Message-ID: <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.gmail.com>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: Barry Leiba <barryleiba@computer.org>, 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: Wed, 01 Aug 2012 18:20:03 -0000
> Yes but that's an editing issue. Go look at how process documentation > and state machines are handled in serious protocol RFCs. Some do use > if/then in a formal way, but some are just informative. The purpose > of 2119 is clarity of terminology. That is good when they use, I seen thoes, but how can we use terminology so that don't collide, some people use 2119 terms that are not condition, to describe conditions. > Everyone knows what "if" and > "then" mean - your concern is how they are used. Yes my concern is how/when use terms not meaning of terms. Ok, What about "MUST" (every one know it), wasn't it clear as "if then", please explain why capital? > The way to fix that > is in the particular drafts you have an issue with. > I did put that in one draft already as you say and one participant before suggest. but I am thinking for the future works and to make the authors document the specification they implemented more efficiently without using 2119 terms in conditional and I thank you for your comments, your email will be more concsidered, AB
- Fwd: New Version Notification for: draft-baryun-r… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… Paul Hoffman
- Re: New Version Notification for: draft-baryun-rf… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… Melinda Shore
- Re: New Version Notification for: draft-baryun-rf… Barry Leiba
- Re: New Version Notification for: draft-baryun-rf… Paul Hoffman
- Re: New Version Notification for: draft-baryun-rf… Mark Nottingham
- RE: New Version Notification for: draft-baryun-rf… Adrian Farrel
- Re: New Version Notification for: draft-baryun-rf… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… Melinda Shore
- Re: New Version Notification for: draft-baryun-rf… Yoav Nir
- Re: New Version Notification for: draft-baryun-rf… Eggert, Lars
- RE: New Version Notification for: draft-baryun-rf… Adrian Farrel
- Re: New Version Notification for: draft-baryun-rf… James Polk
- Re: New Version Notification for: draft-baryun-rf… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… Scott Brim
- Re: New Version Notification for: draft-baryun-rf… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… SM
- Re: New Version Notification for: draft-baryun-rf… Hector Santos
- Re: New Version Notification for: draft-baryun-rf… Abdussalam Baryun
- Re: New Version Notification for: draft-baryun-rf… joel jaeggli
- Re: New Version Notification for: draft-baryun-rf… Randy Bush
- Re: New Version Notification for: draft-baryun-rf… Murray S. Kucherawy
- RE: New Version Notification for: draft-baryun-rf… Adrian Farrel