Re: Use of LWSP in ABNF -- consensus call
Harald Alvestrand <harald@alvestrand.no> Tue, 15 May 2007 18:21 UTC
Return-path: <discuss-bounces@apps.ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
by megatron.ietf.org with esmtp (Exim 4.43)
id 1Ho1eB-0007jF-0i; Tue, 15 May 2007 14:21:19 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43)
id 1Ho1e8-0007j4-V0 for discuss-confirm+ok@megatron.ietf.org;
Tue, 15 May 2007 14:21:16 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
by megatron.ietf.org with esmtp (Exim 4.43) id 1Ho1e8-0007iq-L5
for discuss@apps.ietf.org; Tue, 15 May 2007 14:21:16 -0400
Received: from eikenes.alvestrand.no ([158.38.152.233])
by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ho1e7-0003wF-B1
for discuss@apps.ietf.org; Tue, 15 May 2007 14:21:16 -0400
Received: from localhost (eikenes.alvestrand.no [127.0.0.1])
by eikenes.alvestrand.no (Postfix) with ESMTP id 6914A25970D;
Tue, 15 May 2007 20:21:14 +0200 (CEST)
Received: from eikenes.alvestrand.no ([127.0.0.1])
by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new,
port 10024)
with ESMTP id 00447-02; Tue, 15 May 2007 20:21:09 +0200 (CEST)
Received: from [192.168.1.54] (162.80-203-220.nextgentel.com [80.203.220.162])
by eikenes.alvestrand.no (Postfix) with ESMTP id 4041F25817F;
Tue, 15 May 2007 20:21:09 +0200 (CEST)
Message-ID: <4649FA12.30909@alvestrand.no>
Date: Tue, 15 May 2007 20:21:06 +0200
From: Harald Alvestrand <harald@alvestrand.no>
User-Agent: Thunderbird 1.5.0.7 (X11/20060921)
MIME-Version: 1.0
To: Lisa Dusseault <lisa@osafoundation.org>
Subject: Re: Use of LWSP in ABNF -- consensus call
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org> <4648E8CB.3010502@dcrocker.net>
<F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org>
In-Reply-To: <F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: ietf-dkim@mipassoc.org, Apps Discuss <discuss@apps.ietf.org>,
IETF General Discussion Mailing List <ietf@ietf.org>,
dcrocker@bbiw.net, Paul Overell <paul.overell@thus.net>
X-BeenThere: discuss@apps.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: general discussion of application-layer protocols
<discuss.apps.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
<mailto:discuss-request@apps.ietf.org?subject=unsubscribe>
List-Post: <mailto:discuss@apps.ietf.org>
List-Help: <mailto:discuss-request@apps.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/discuss>,
<mailto:discuss-request@apps.ietf.org?subject=subscribe>
Errors-To: discuss-bounces@apps.ietf.org
Lisa Dusseault wrote: > >> >> 2. The ABNF is a candidate for moving from Draft to Full. Will >> removing a >> rule (that is already in use?) or otherwise changing the semantics of >> the >> specification, at this point, still permit the document to advance? I >> had the >> impression that moving to Full was based on some serious beliefs about a >> specification's being quite stable. Making this kind of change, this >> late in >> the game, would seem to run counter to that. > > Moving to Internet Standard is indeed something we do carefully, and > of course that means investigating proposed changes to make sure > they're appropriate, and setting a high bar for accepting them. I > believe that's what we're doing here, investigating carefully. > > I share your concerns about removing rules that are already in use -- > that would generally be a bad thing. However I'm interested in the > consensus around whether a warning or a deprecation statement would be > a good thing. Removing features that have proved to be a Bad Idea has always been listed as one of the possible changes from Proposed to Draft - Draft to Full happens so rarely that I would be hesitant to claim that there's tradition for such changes there. Despite this, I agree with the people who think that a warning comment, rather than removal of the rule, is the Right Way. Harald
- Use of LWSP in ABNF -- consensus call Lisa Dusseault
- Re: Use of LWSP in ABNF -- consensus call Julian Reschke
- Re: Use of LWSP in ABNF -- consensus call Frank Ellermann
- Re: Use of LWSP in ABNF -- consensus call Lisa Dusseault
- Re: Use of LWSP in ABNF -- consensus call Paul Hoffman
- Re: Use of LWSP in ABNF -- consensus call Tony Hansen
- Re: Use of LWSP in ABNF -- consensus call Tony Finch
- Re: Use of LWSP in ABNF -- consensus call Clive D.W. Feather
- Re: Use of LWSP in ABNF -- consensus call Keith Moore
- Re: Use of LWSP in ABNF -- consensus call Harald Alvestrand
- Re: Use of LWSP in ABNF -- consensus call Frank Ellermann
- Re: Use of LWSP in ABNF -- consensus call Ned Freed
- Re: Use of LWSP in ABNF -- consensus call John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Tony Finch
- Re: Use of LWSP in ABNF -- consensus call Dave Crocker
- Re: Use of LWSP in ABNF -- consensus call Eric Allman
- Re: Use of LWSP in ABNF -- consensus call Philip Guenther
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Dave Crocker
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Dave Crocker
- Re: Use of LWSP in ABNF -- consensus call Douglas Otis
- Re: Use of LWSP in ABNF -- consensus call Alexey Melnikov
- RE: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Bill.Oxley
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Tony Finch
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Harald Tveit Alvestrand
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Dave Crocker
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… todd glassey
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Sam Hartman
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Sam Hartman
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Dave Crocker
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Tony Finch
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Keith Moore
- Re: Use of LWSP in ABNF -- consensus call Frank Ellermann
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Tony Finch
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Sam Hartman
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Sam Hartman
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… John C Klensin
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Tony Finch
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Sam Hartman
- Re: Use of LWSP in ABNF -- consensus call Lisa Dusseault
- Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consen… Clive D.W. Feather
- Re: Use of LWSP in ABNF -- consensus call Lisa Dusseault
- Re: Use of LWSP in ABNF -- consensus call Dave Crocker
- Re: Use of LWSP in ABNF -- consensus call Keith Moore
- Re: Use of LWSP in ABNF -- consensus call Frank Ellermann
- Re: Use of LWSP in ABNF -- consensus call John C Klensin
- Re: Use of LWSP in ABNF -- consensus call Alexey Melnikov
- Re: Use of LWSP in ABNF -- consensus call Clive D.W. Feather
- Re: Use of LWSP in ABNF -- consensus call Dave Crocker