Re: [Lwip] WGLC for lwig-terminology

"Dijk, Esko" <esko.dijk@philips.com> Mon, 22 April 2013 08:41 UTC

Return-Path: <esko.dijk@philips.com>
X-Original-To: lwip@ietfa.amsl.com
Delivered-To: lwip@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D83921F8EB1 for <lwip@ietfa.amsl.com>; Mon, 22 Apr 2013 01:41:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 Km9+ovqJ6iqi for <lwip@ietfa.amsl.com>; Mon, 22 Apr 2013 01:41:04 -0700 (PDT)
Received: from va3outboundpool.messaging.microsoft.com (va3ehsobe003.messaging.microsoft.com [216.32.180.13]) by ietfa.amsl.com (Postfix) with ESMTP id 6189021F8EAC for <lwip@ietf.org>; Mon, 22 Apr 2013 01:41:02 -0700 (PDT)
Received: from mail50-va3-R.bigfish.com (10.7.14.250) by VA3EHSOBE004.bigfish.com (10.7.40.24) with Microsoft SMTP Server id 14.1.225.23; Mon, 22 Apr 2013 08:41:01 +0000
Received: from mail50-va3 (localhost [127.0.0.1]) by mail50-va3-R.bigfish.com (Postfix) with ESMTP id 5DCD930025B; Mon, 22 Apr 2013 08:41:01 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.55.7.222; KIP:(null); UIP:(null); IPV:NLI; H:mail.philips.com; RD:none; EFVD:NLI
X-SpamScore: -31
X-BigFish: VPS-31(zz15d6O9251Jc89bh542I217bIzz1f42h1fc6h1ee6h1de0h1fdah1202h1e76h1d1ah1d2ahzz8275dh1033ILz2dh2a8h668h839h947hd25hf0ah1288h12a5h12a9h12bdh137ah13b6h1441h1504h1537h153bh15d0h162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1155h)
Received: from mail50-va3 (localhost.localdomain [127.0.0.1]) by mail50-va3 (MessageSwitch) id 1366620059206124_14632; Mon, 22 Apr 2013 08:40:59 +0000 (UTC)
Received: from VA3EHSMHS013.bigfish.com (unknown [10.7.14.245]) by mail50-va3.bigfish.com (Postfix) with ESMTP id 24C202E024E; Mon, 22 Apr 2013 08:40:59 +0000 (UTC)
Received: from mail.philips.com (157.55.7.222) by VA3EHSMHS013.bigfish.com (10.7.99.23) with Microsoft SMTP Server (TLS) id 14.1.225.23; Mon, 22 Apr 2013 08:40:58 +0000
Received: from 011-DB3MMR1-014.MGDPHG.emi.philips.com (10.128.28.98) by 011-DB3MMR1-011.MGDPHG.emi.philips.com (10.128.28.50) with Microsoft SMTP Server (TLS) id 14.2.328.11; Mon, 22 Apr 2013 08:40:28 +0000
Received: from 011-DB3MPN2-083.MGDPHG.emi.philips.com ([169.254.3.176]) by 011-DB3MMR1-014.MGDPHG.emi.philips.com ([10.128.28.98]) with mapi id 14.02.0328.011; Mon, 22 Apr 2013 08:40:28 +0000
From: "Dijk, Esko" <esko.dijk@philips.com>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: [Lwip] WGLC for lwig-terminology
Thread-Index: Ac4zYMPX/q/pzk/ARPipDrdU0yerAQIreMQQAA5YRoAAuwR28A==
Date: Mon, 22 Apr 2013 08:40:27 +0000
Message-ID: <031DD135F9160444ABBE3B0C36CED618C14907@011-DB3MPN2-083.MGDPHG.emi.philips.com>
References: <014001ce3369$1794bf50$46be3df0$@chinamobile.com> <031DD135F9160444ABBE3B0C36CED618C11457@011-DB3MPN2-083.MGDPHG.emi.philips.com> <C98A44D1-6E3E-418D-A3BE-DF5B1F67D317@tzi.org>
In-Reply-To: <C98A44D1-6E3E-418D-A3BE-DF5B1F67D317@tzi.org>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [194.171.252.103]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: philips.com
Cc: "lwip@ietf.org" <lwip@ietf.org>
Subject: Re: [Lwip] WGLC for lwig-terminology
X-BeenThere: lwip@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Lightweight IP stack <lwip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lwip>, <mailto:lwip-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lwip>
List-Post: <mailto:lwip@ietf.org>
List-Help: <mailto:lwip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lwip>, <mailto:lwip-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2013 08:41:07 -0000

> Well, just tell them that you want to communicate with an S0-class device.
Ok, that's better, instead of questioning my sanity they will now question their own knowledge level ;)
 I understand the concerns as the terms 'sleepy' and 'sleeping' are already widely used.

thanks,
Esko

-----Original Message-----
From: Carsten Bormann [mailto:cabo@tzi.org]
Sent: Thursday, April 18, 2013 17:19
To: Dijk, Esko
Cc: lwip@ietf.org
Subject: Re: [Lwip] WGLC for lwig-terminology

> section 2.1 " and available power." -> should it be "and available power/energy." ?

Yes.  Changed it to "available power and energy".

> section 2.2.1. ; term "MSL" -> perhaps write it out in full here. Similar as done with the DTN term in the same section.

Indeed (I already had done that based on another editorial comment).

> section 4.3: could we mention here the term "sleepy device" as being equivalent, or an alternative for, the "Always-off" class?
>        I've seen the term "sleepy" more often used than the term "Always-off". The latter term may be confusing (try explaining to a colleague that you want to communicate with an always-off device...)

Well, just tell them that you want to communicate with an S0-class device.

The problem I have with "sleepy" is that it is not clear whether S0 or S1 is meant.
Trying to assign a specific meaning to an existing overloaded term is nearly impossible, inventing  a new term is much better.  Of course, "always-off" is a bit provocative...  Good that we have the numeric classes, too.

Grüße, Carsten


________________________________
The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.