IETF Logo Mail Archive

Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt

SM <sm@resistor.net> Wed, 01 August 2012 20:23 UTC

Return-Path: <sm@resistor.net>
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 DB52B11E8235 for <ietf@ietfa.amsl.com>; Wed, 1 Aug 2012 13:23:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.569
X-Spam-Level:
X-Spam-Status: No, score=-102.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, 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 N5qCNHYtIPNQ for <ietf@ietfa.amsl.com>; Wed, 1 Aug 2012 13:23:20 -0700 (PDT)
Received: from mx.ipv6.elandsys.com (mx.ipv6.elandsys.com [IPv6:2001:470:f329:1::1]) by ietfa.amsl.com (Postfix) with ESMTP id DA72B11E820D for <ietf@ietf.org>; Wed, 1 Aug 2012 13:23:20 -0700 (PDT)
Received: from sm-THINK.resistor.net (IDENT:sm@localhost [127.0.0.1]) (authenticated bits=0) by mx.elandsys.com (8.14.5/8.14.5) with ESMTP id q71KN93I001882; Wed, 1 Aug 2012 13:23:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=opendkim.org; s=mail2010; t=1343852597; bh=43L2W7PlvjQb+tGtS/SSsiYM6ffw5hgwzcMmDIi6WGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=WM/+4rxPUyczoUN8kOAdnIeSVw80FBrZAq//NNGMniMMZ37BVOQGdbfBFAU2M9Z+m BdZ7fmi8Wds3HmcvMWme4v1DqmMmdDbwBmpJpnca9XisRPdLXmezmYLeP7WEUyWsO6 aG1CrLx+IDQadHiKc7V5a/2MBaW/UZpLT7dMpZYY=
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=resistor.net; s=mail; t=1343852597; i=@resistor.net; bh=43L2W7PlvjQb+tGtS/SSsiYM6ffw5hgwzcMmDIi6WGY=; h=Date:To:From:Subject:Cc:In-Reply-To:References; b=zTzF7q12rdej7wKcvV00zt6XE8mnJ1Oc8oLuuI9LFm0h3ZkDFwrMYa+IJ7WExrzGG Sgl/fLFjqRoFnaH/voZANK/qwJmmm0SQcDMER6CSQ8zzQ5XfMZabJF3/F0wWN0ORyG akV2/T32LFaOWa6xoPtuRfxs5hVfXX4Vc54Ws2ZI=
Message-Id: <6.2.5.6.2.20120801125000.04c23488@resistor.net>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.5.6
Date: Wed, 01 Aug 2012 13:21:38 -0700
To: Abdussalam Baryun <abdussalambaryun@gmail.com>
From: SM <sm@resistor.net>
Subject: Re: New Version Notification for: draft-baryun-rfc2119-update-00.txt
In-Reply-To: <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.g mail.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> <CADnDZ892BCo7Vb87eTKGNmpHGxQi5RK6khT8curBL8iFkUjqcw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Wed, 01 Aug 2012 20:23:25 -0000

At 11:19 AM 8/1/2012, Abdussalam Baryun wrote:
>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?

You are probably receiving feedback on your draft because the WG 
sessions this week are boring. :-)  The is a thread about "all caps" 
at http://www.ietf.org/mail-archive/web/ietf/current/msg73338.html  I 
suggest reading RFC 1122 and RFC 1123 to get a view of how some 
specifications were written and why they were written in such a way.

Melinda Shore provided some good advice ( 
http://www.ietf.org/mail-archive/web/ietf/current/msg74191.html ).  I 
would not say that your draft is not helpful.  It is up to you to 
assess whether draft-baryun-rfc2119-update-00 can gain IETF Consensus.

Regards,
-sm

v2.23.0 | Report a Bug | By Email