Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consensus call

John C Klensin <john-ietf@jck.com> Thu, 17 May 2007 16:17 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 1Hoifi-0006eT-7g; Thu, 17 May 2007 12:17:46 -0400
Received: from discuss by megatron.ietf.org with local (Exim 4.43) id 1Hoifh-0006eO-8Q for discuss-confirm+ok@megatron.ietf.org; Thu, 17 May 2007 12:17:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hoifg-0006eG-Us for discuss@apps.ietf.org; Thu, 17 May 2007 12:17:44 -0400
Received: from ns.jck.com ([209.187.148.211] helo=bs.jck.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hoiff-00043r-Ik for discuss@apps.ietf.org; Thu, 17 May 2007 12:17:44 -0400
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1HoifY-0005yk-HD; Thu, 17 May 2007 12:17:36 -0400
Date: Thu, 17 May 2007 12:17:35 -0400
From: John C Klensin <john-ietf@jck.com>
To: Dave Crocker <dcrocker@bbiw.net>, Harald Alvestrand <harald@alvestrand.no>
Subject: Re: [ietf-dkim] Re: Use of LWSP in ABNF -- consensus call
Message-ID: <1504A69099CF1B62F66FE576@p3.JCK.COM>
In-Reply-To: <4649FB9A.9000107@bbiw.net>
References: <BFE21101-5BC4-45FA-8905-89C2D4A1E593@osafoundation.org> <4648E8CB.3010502@dcrocker.net> <F5C06D62-639B-40CB-803F-6D9E50673768@osafoundation.org> <4649FA12.30909@alvestrand.no> <4649FB9A.9000107@bbiw.net>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: Apps Discuss <discuss@apps.ietf.org>, IETF General Discussion Mailing List <ietf@ietf.org>, ietf-dkim@mipassoc.org, 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


--On Tuesday, 15 May, 2007 11:27 -0700 Dave Crocker
<dcrocker@bbiw.net> wrote:

> Were we to deprecate every feature in IETF specifications that
> get mis-implemented a couple of times over 10 years, I suspect
> much of our technology would be deprecated...

IMO, and at the risk of again agreeing with Dave, this is the
issue for me.  

If we have inconsistent uses of terminology across documents
that are supposed to be using the same, standardized, term, then
that is a problem with our review process.  If the term is
explicitly standardized in one of the documents, that is the
definition; things that use the term incorrectly should be
candidates for fixing.

By contrast, if we consider "misused sometimes" or "ambiguous
with other uses" as a sufficient condition for deprecating the
term itself, then we have a long list of terms to deprecate in
front of us, almost certainly starting with "IP", which refers
to several different protocols, a protocol layer, and something
that often involves lawyers.

I think some warning language about safe and unsafe contexts may
be in order for this construction but I expect that everyone who
is arguing for deprecating it entirely (or inserting a strong
"don't use this" statement) will be making a case for similar
language the next time an IPv6 document comes up for review.

       john