Re: [6lowpan] [ADs] AUTH48 [MF]: RFC 6282 <draft-ietf-6lowpan-hc-15.txt>

"Timothy J. Salo" <salo@saloits.com> Sat, 23 July 2011 19:10 UTC

Return-Path: <salo@saloits.com>
X-Original-To: 6lowpan@ietfa.amsl.com
Delivered-To: 6lowpan@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4067921F8ABB for <6lowpan@ietfa.amsl.com>; Sat, 23 Jul 2011 12:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.307
X-Spam-Level:
X-Spam-Status: No, score=-1.307 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MISSING_HEADERS=1.292]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k4goB0cPuG8n for <6lowpan@ietfa.amsl.com>; Sat, 23 Jul 2011 12:10:49 -0700 (PDT)
Received: from server.saloits.com (saloits.com [208.42.140.127]) by ietfa.amsl.com (Postfix) with ESMTP id 5B05921F8A66 for <6lowpan@ietf.org>; Sat, 23 Jul 2011 12:10:25 -0700 (PDT)
Received: from [192.168.255.119] (thinkpad2.saloits.com [192.168.255.119]) by server.saloits.com (8.14.4/8.14.3) with ESMTP id p6NJAMC2004959; Sat, 23 Jul 2011 14:10:23 -0500
Message-ID: <4E2B1CA2.2080505@saloits.com>
Date: Sat, 23 Jul 2011 14:10:26 -0500
From: "Timothy J. Salo" <salo@saloits.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
References: <6A2A459175DABE4BB11DE2026AA50A5D05228480@XMB-AMS-107.cisco.com> <DE69914A-2813-4044-AEA7-A716FE2157CE@tzi.org>
In-Reply-To: <DE69914A-2813-4044-AEA7-A716FE2157CE@tzi.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 6lowpan <6lowpan@ietf.org>, 6lowpan-chairs@tools.ietf.org, 6lowpan-ads@tools.ietf.org
Subject: Re: [6lowpan] [ADs] AUTH48 [MF]: RFC 6282 <draft-ietf-6lowpan-hc-15.txt>
X-BeenThere: 6lowpan@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Working group discussion for IPv6 over LowPan networks <6lowpan.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/6lowpan>
List-Post: <mailto:6lowpan@ietf.org>
List-Help: <mailto:6lowpan-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/6lowpan>, <mailto:6lowpan-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2011 19:10:50 -0000

> It is a bit hard to diagnose a consensus here, except that
> the clear WG consensus seems to be that nobody cares much :-)
>
> It is indeed pretty clear from the extended WG discussion that
>
> 	Compression Format for IPv6 Datagrams over IEEE 802.15.4-based Networks
>
> or
>
> 	Compression Format for IPv6 Datagrams over IEEE 802.15.4-based Networks
>
> is the important part of the title.

I think that the name should speak to a large audience (not just the
working group or even just the IETF) and should make sense for many
years.

The "-based" part of the name seems something between subtle and
extraneous.  If you want to emphasize that this RFC doesn't require
or use a full implementation of IEEE 802.15.4, this should be
highlighted in the text, not in the title.

> We don't seem to have full consensus on whether 6LoWPAN should be part of the title.
> Jonathan would like to keep it out, others have indicated that they think it should
> be part of the title (as it was during WGLC and IETF last call).

"6lowpan", I believe, fails the test of speaking to a broader audience
and having longevity.  Today, few people know what 6lowpan means, and
in the future it will be merely an interesting (or not-so-interesting)
historical footnote.  Using "6lowpan" feels sort of like using a
development code name for a marketing name.

> Megan has indicated that 6LoWPAN would be expanded as in RFC 4919:
>
>      IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs):

I think that the term "personal area networks" is, well, archaic.
That is not how IEEE 802.15.4 is being used and not how these
specifications are being used.  Rather, I think we all hope that
this technology will be used for much more than personal area
networks.

Carsten made essentially this argument in his original e-mail.

This reasoning suggests that "6lowpan" doesn't add any value to the
title, since it embeds an acronym that we don't really believe.

RFC 4944, "Transmission of IPv6 Packets over IEEE 802.15.4 Networks",
contains neither "based", "6lowpan", nor "personal area networks" in
its title.

> I think the best of both worlds would be
>
> 	Compression Format for IPv6 Datagrams over IEEE 802.15.4-based Networks (6LoWPANs)
>
> but I'd need input from the RFC editor whether that can be done without
> falling into the expansion trap.

Again, I think that "6lowpan" is, or soon will be, historical trivia.
It's a title that, while we as a working group might have some affection
for, we don't really believe it.

-tjs