Re: Minimum Implementation Requirements (Was: 2119bis)
Hector <sant9442@gmail.com> Fri, 02 September 2011 05:01 UTC
Return-Path: <sant9442@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 B841D21F9422 for <ietf@ietfa.amsl.com>; Thu, 1 Sep 2011 22:01:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.241
X-Spam-Level:
X-Spam-Status: No, score=-3.241 tagged_above=-999 required=5 tests=[AWL=0.358, 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 E+VDfCKYEQGr for <ietf@ietfa.amsl.com>; Thu, 1 Sep 2011 22:01:56 -0700 (PDT)
Received: from mail-gy0-f172.google.com (mail-gy0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 21D6F21F93A7 for <ietf@ietf.org>; Thu, 1 Sep 2011 22:01:53 -0700 (PDT)
Received: by gyf3 with SMTP id 3so2187388gyf.31 for <ietf@ietf.org>; Thu, 01 Sep 2011 22:03:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ACMGdPPImDBOh2y7zQbWio1Q1V6J8lDWj6hj3vAJ5V8=; b=fpXeSztgqFxy6IYCJD9XVUiHH86KlyePPx4EZs0Az6JoqyXmSSs7aIEvnFf6kyQx16 vk1lIT6qvqBxd0L9ZmI7X6k+7f+4vGFtOeyYLZoySf7u/9XLAZh2KogQVrK6BjTzAEhY LTUw3DBvJ9E2BLy8ZA3K22qw6FA6FH2gX4XYs=
Received: by 10.150.114.12 with SMTP id m12mr737667ybc.287.1314939806257; Thu, 01 Sep 2011 22:03:26 -0700 (PDT)
Received: from adsl-215-50-126.mia.bellsouth.net (99-3-147-93.lightspeed.miamfl.sbcglobal.net [99.3.147.93]) by mx.google.com with ESMTPS id s15sm721190ank.8.2011.09.01.22.03.25 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 01 Sep 2011 22:03:25 -0700 (PDT)
Message-ID: <4E6063CB.3030402@gmail.com>
Date: Fri, 02 Sep 2011 01:04:11 -0400
From: Hector <sant9442@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Spencer Dawkins <spencer@wonderhamster.org>
Subject: Re: Minimum Implementation Requirements (Was: 2119bis)
References: <4E5C067A.9080400@stpeter.im> <201108292150.p7TLoIXh031665@cichlid.raleigh.ibm.com> <41696E7A-3EC7-4775-804B-BE9AC8D4042D@standardstrack.com> <003401cc66b1$d35af5a0$6801a8c0@oemcomputer> <01O5FL6TFAY8014O5Z@mauve.mrochek.com> <5A0F4E88-9D47-40F5-93FA-8249CEAE70AD@standardstrack.com> <4E5D30CC.4000009@nostrum.com> <2ABF7A30-EDF5-47B7-8972-4377AB4798AD@standardstrack.com> <4E5D3546.3020109@winserver.com> <BEF48D17-5233-4D0C-AB6C-1C69CDD6232D@standardstrack.com> <4E5FA04A.4040900@qualcomm.com><4E5FDC24.8080101@gmail.com> <4E5FE0C0.2040405@gmail.com> <3A997FFB4F2B4D3F9499D0C7B7ACA5CB@china.huawei.com>
In-Reply-To: <3A997FFB4F2B4D3F9499D0C7B7ACA5CB@china.huawei.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: Pete Resnick <presnick@qualcomm.com>, IETF General Discussion Mailing List <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: Fri, 02 Sep 2011 05:01:56 -0000
I'm just winging this. What do you think about having a Conformance Level model ? Conformance Level 1 (CL1) - MUST [NOT] - minimum requirement Conformance Level 2 (CL2) - CL1, SHOULD [NOT] Conformance Level 3 (CL3) - CL1, CL2, MAY [NOT] It allows author to declare in the RFC (abstract, intro perhaps) the level of conformance he expects, i.e. "This Protocol only works best with CL2 implementators." When an implementator sees that, it might help in its decision making process on how much is supported. This is also help remove the stigma of existing implementations being labeled non-compliant, which quite frankly, those are "fighting words!" :) Of course, out of the gate, all protocols must be a Conformance Level 1 protocol :) Spencer Dawkins wrote: > Hi, Melinda, > >> Can anybody point to an incident in which lack of clarity around >> 2119 language caused problems, and it was determined that 2119 >> itself was the problem and not authors or editors being careless? >> >> Melinda > > My recollection is that, at least since the early 2000s, most "problems" > were encountered with Last Call/Gen-ART (and probably other review team) > comments taking forms like > > "Why is this SHOULD not a MUST?", or the ever-popular > "Why is this Informational draft using 2119 language?? > > There are probably variants I don't remember (I stopped being an active > Gen-ART reviewer when I began serving on the IAB, and I've slept since > then). > > In my comments on 2119bis > (http://www.ietf.org/mail-archive/web/ietf/current/msg68885.html), I was > suggesting that clarifications might head off some of these recurring > conversations. > > At this point, I would be fine with a draft (of any flavor - obsoleting, > updating, or just an IESG statement) that addresses whether these > questions are reasonable questions. I don't have a deep need to add the > (mostly reasonable) suggestions that have been made for new terms. > > If the IESG thinks that's a reasonable thing to do, they can make a call > about the particular flavor, just fine ... > > Spencer > _______________________________________________ > Ietf mailing list > Ietf@ietf.org > https://www.ietf.org/mailman/listinfo/ietf
- Re: 2119bis Donald Eastlake
- Re: 2119bis Dave CROCKER
- 2119bis Peter Saint-Andre
- Re: 2119bis Thomas Narten
- Re: 2119bis Eric Burger
- Re: 2119bis Eric Burger
- Re: 2119bis Frank Ellermann
- Re: 2119bis Brian E Carpenter
- Re: 2119bis John C Klensin
- Re: 2119bis Spencer Dawkins
- Re: 2119bis Mark Nottingham
- Re: 2119bis Randy Presuhn
- Re: 2119bis Keith Moore
- Re: 2119bis ned+ietf
- Re: 2119bis Eric Burger
- Re: 2119bis Mark Nottingham
- Re: 2119bis Keith Moore
- Re: 2119bis HLS
- Re: 2119bis HLS
- RE: 2119bis Murray S. Kucherawy
- RE: 2119bis Thomson, Martin
- Re: 2119bis HLS
- Re: 2119bis Eliot Lear
- Re: 2119bis Mykyta Yevstifeyev
- Re: 2119bis Mykyta Yevstifeyev
- Re: 2119bis Eric Burger
- Re: 2119bis Marshall Eubanks
- Re: 2119bis Eric Burger
- Re: 2119bis Eric Burger
- Re: 2119bis Eric Burger
- Re: 2119bis Keith Moore
- Re: 2119bis Keith Moore
- Re: 2119bis Eric Burger
- Re: 2119bis Keith Moore
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis HLS
- Re: 2119bis Keith Moore
- Re: 2119bis Keith Moore
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis Keith Moore
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis Keith Moore
- Re: 2119bis Eric Burger
- Re: 2119bis Keith Moore
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis Bill McQuillan
- Re: 2119bis Keith Moore
- Re: 2119bis Martin Sustrik
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis Keith Moore
- Re: 2119bis Eric Burger
- Re: 2119bis Spencer Dawkins
- Re: 2119bis HLS
- Re: 2119bis Keith Moore
- Re: 2119bis Keith Moore
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Eric Burger
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Marc Petit-Huguenin
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Keith Moore
- Re: 2119bis Eric Burger
- Re: 2119bis hector
- Re: 2119bis Adam Roach
- Re: 2119bis Eric Burger
- Re: 2119bis -- Tying our hands? Adam Roach
- Re: 2119bis hector
- Re: 2119bis Adam Roach
- Re: 2119bis Keith Moore
- Re: 2119bis Marc Petit-Huguenin
- Re: 2119bis Hector Santos
- Re: 2119bis ned+ietf
- Re: 2119bis Brian E Carpenter
- Re: 2119bis Barry Leiba
- Re: 2119bis Richard Barnes
- Re: 2119bis -- Tying our hands? Dean Willis
- RE: 2119bis -- Tying our hands? Thomson, Martin
- Re: 2119bis Eric Burger
- Re: 2119bis Eric Burger
- Re: 2119bis Mark Nottingham
- Re: 2119bis Hector
- Re: 2119bis Keith Moore
- Re: 2119bis Hector
- Re: 2119bis Keith Moore
- Re: 2119bis Scott O. Bradner
- Re: 2119bis hector
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Keith Moore
- Re: 2119bis Keith Moore
- non-2119 Tony Hansen
- Re: 2119bis Jari Arkko
- Re: 2119bis Jari Arkko
- Re: 2119bis Peter Saint-Andre
- Re: 2119bis Keith Moore
- Re: 2119bis Peter Saint-Andre
- Re: 2119bis Hector
- Re: 2119bis Keith Moore
- Re: non-2119 Mykyta Yevstifeyev
- Re: 2119bis - SHOULD Classifications Hector Santos
- Re: 2119bis Michael Richardson
- Re: 2119bis Jari Arkko
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Hector
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Randy Presuhn
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Hector
- RE: 2119bis Christer Holmberg
- Re: 2119bis Hector
- Re: 2119bis Keith Moore
- Re: 2119bis Melinda Shore
- Re: 2119bis Hector
- Re: you can't force people to write well, was 211… John Levine
- Re: 2119bis Keith Moore
- Pachyderm in the parlor (Was: 2119bis) Pete Resnick
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Tony Hansen
- Re: 2119bis Melinda Shore
- Re: 2119bis Hector
- Re: 2119bis Mark Nottingham
- Re: 2119bis Eric Burger
- Re: 2119bis Hector
- Re: 2119bis Keith Moore
- Re: 2119bis George Willingmyre
- Re: 2119bis George Willingmyre
- Re: 2119bis Mykyta Yevstifeyev
- Re: 2119bis George Willingmyre
- Re: 2119bis Barry Leiba
- Re: 2119bis Mykyta Yevstifeyev
- Re: Pachyderm in the parlor (Was: 2119bis) John C Klensin
- Re: Last Call: <draft-housley-two-maturity-levels… John C Klensin
- Re: Pachyderm in the parlor (Was: 2119bis) SM
- Minimum Implementation Requirements (Was: 2119bis) hector
- Minimum Implementation Requirements (Was: 2119bis) Hector
- Re: 2119bis hector
- Re: Minimum Implementation Requirements (Was: 211… Melinda Shore
- Re: Minimum Implementation Requirements (Was: 211… Brian E Carpenter
- Re: Minimum Implementation Requirements (Was: 211… Spencer Dawkins
- Re: 2119bis Hector
- RE: Minimum Implementation Requirements (Was: 211… Murray S. Kucherawy
- Re: 2119bis Bob Hinden
- Re: Minimum Implementation Requirements (Was: 211… Hector
- RE: Minimum Implementation Requirements (Was: 211… ned+ietf
- Re: 2119bis Frank Ellermann
- Re: 2119bis Frank Ellermann
- Re: Minimum Implementation Requirements (Was: 211… Hector
- Re: Minimum Implementation Requirements (Was: 211… Melinda Shore
- Re: Minimum Implementation Requirements (Was: 211… Hector
- Re: 2119bis Michael StJohns
- Re: 2119bis Hector
- Re: Minimum Implementation Requirements (Was: 211… Hector
- Re: Minimum Implementation Requirements (Was: 211… t.petch
- Re: 2119bis t.petch
- RE: 2119bis Murray S. Kucherawy
- Re: 2119bis Hector
- Re: 2119bis Sam Hartman
- Re: 2119bis Alan Barrett
- Re: 2119bis Hector
- Re: 2119bis Hector
- Re: 2119bis John C Klensin
- Re: 2119bis Noel Chiappa
- Re: 2119bis Hector
- Re: 2119bis Randy Presuhn
- RE: 2119bis Murray S. Kucherawy
- RE: 2119bis Murray S. Kucherawy
- RE: 2119bis Yaakov Stein
- Re: 2119bis Hector
- Re: 2119bis Hector
- Re: 2119bis Martin Rex
- Re: 2119bis SM
- Re: 2119bis Peter Saint-Andre
- Re: 2119bis Mykyta Yevstifeyev
- Re: 2119bis John C Klensin
- Re: 2119bis Hector
- Re: 2119bis Brian E Carpenter
- Re: 2119bis John C Klensin
- Re: 2119bis Joe Touch
- Re: 2119bis Hector
- Re: 2119bis Martin Rex