[rfc-i] Expanding acronyms in titles can be harmful (Fwd: [ipwave] Expertise on ND problems on OCB)
Carsten Bormann <cabo@tzi.org> Thu, 25 April 2019 19:48 UTC
Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7A5120319 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 25 Apr 2019 12:48:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.199
X-Spam-Level:
X-Spam-Status: No, score=-5.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vwRzdSNcyH8h for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Thu, 25 Apr 2019 12:48:16 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B064D120314 for <rfc-interest-archive-eekabaiReiB1@ietf.org>; Thu, 25 Apr 2019 12:48:16 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id ED1F4B81E79; Thu, 25 Apr 2019 12:48:07 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id CC61BB81E79 for <rfc-interest@rfc-editor.org>; Thu, 25 Apr 2019 12:48:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id It4gsqjw794B for <rfc-interest@rfc-editor.org>; Thu, 25 Apr 2019 12:48:04 -0700 (PDT)
Received: from smtp.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) by rfc-editor.org (Postfix) with ESMTPS id A2A6CB81E77 for <rfc-interest@rfc-editor.org>; Thu, 25 Apr 2019 12:48:03 -0700 (PDT)
Received: from [192.168.217.106] (p54A6CA34.dip0.t-ipconnect.de [84.166.202.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.uni-bremen.de (Postfix) with ESMTPSA id 44qnm92ZLyz12kH; Thu, 25 Apr 2019 21:48:09 +0200 (CEST)
From: Carsten Bormann <cabo@tzi.org>
X-Mao-Original-Outgoing-Id: 577914486.789803-3b7655d0dbb2905122ce7cb6ac3b0322
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Date: Thu, 25 Apr 2019 21:48:08 +0200
Message-Id: <4883ADB4-CDDF-4594-AADF-C1C3612408B0@tzi.org>
References: <B7639AFA-FDF3-400C-9AA0-6E48AD9ECF2A@tzi.org>
To: RFC Interest <rfc-interest@rfc-editor.org>
X-Mailer: Apple Mail (2.3445.9.1)
Subject: [rfc-i] Expanding acronyms in titles can be harmful (Fwd: [ipwave] Expertise on ND problems on OCB)
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============7775232616991335774=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
FYI (from a discussion the actual content of which is irrelevant here). It is interesting how a not-so-useful acronym expansion was repeatedly used to discount a document from consideration that actually is highly pertinent. (Note that this happens not only inside the IETF, where we see the misunderstanding and can correct it; the damage is actually with other SDOs not understanding what a document is about because the acronym expansions are getting in the way.) Grüße, Carsten > Begin forwarded message: > > From: Carsten Bormann <cabo@tzi.org <mailto:cabo@tzi.org>> > Subject: Re: [ipwave] Expertise on ND problems on OCB > Date: April 25, 2019 at 21:42:20 GMT+2 > To: "draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org <mailto:draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>" <draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org <mailto:draft-ietf-ipwave-ipv6-over-80211ocb.all@ietf.org>> > Cc: "ietf@ietf.org <mailto:ietf@ietf.org>" <ietf@ietf.org <mailto:ietf@ietf.org>>, "its@ietf.org <mailto:its@ietf.org>" <its@ietf.org <mailto:its@ietf.org>>, "int-dir@ietf.org <mailto:int-dir@ietf.org>" <int-dir@ietf.org <mailto:int-dir@ietf.org>> > > >>> • RFC 8505 isn't just about low power. >> The titles says that, so the authors said that and including the IETF WG that published and examined it under such use cases > > Actually, it doesn’t. > > The title is > > Registration Extensions for IPv6 over > 6LoWPAN Neighbor Discovery > > because 6LoWPAN Neighbor Discovery was invented for 6LoWPAN before we started applying it to the entirety of 6Lo. > > The RFC editor guidelines caused this to be expanded to: > > Registration Extensions for IPv6 over > Low-Power Wireless Personal Area Network (6LoWPAN) Neighbor Discovery > > which is indeed the expansion of “6LoWPAN”, but does not help at all — it just muddies the waters by polluting the title with terms that are no longer relevant to the document at hand. > > (I’m not going to go into the other parts of the current discussion; I have no idea how something like OCB can be discussed without acknowledging the hidden terminal problem, a.k.a. non-transitive connectivity, so it seems to me I won't have much to contribute.) > > Grüße, Carsten >
_______________________________________________ rfc-interest mailing list rfc-interest@rfc-editor.org https://www.rfc-editor.org/mailman/listinfo/rfc-interest
- [rfc-i] Expanding acronyms in titles can be harmf… Carsten Bormann