IETF Logo Mail Archive

Re: [core] RSSI in SenML

Cullen Jennings <fluffy@iii.ca> Wed, 22 March 2017 19:57 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ED95128BA2 for <core@ietfa.amsl.com>; Wed, 22 Mar 2017 12:57:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Xzu9lEFvZSJW for <core@ietfa.amsl.com>; Wed, 22 Mar 2017 12:57:12 -0700 (PDT)
Received: from smtp117.ord1c.emailsrvr.com (smtp117.ord1c.emailsrvr.com [108.166.43.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC14A1270A0 for <core@ietf.org>; Wed, 22 Mar 2017 12:57:12 -0700 (PDT)
Received: from smtp23.relay.ord1c.emailsrvr.com (localhost [127.0.0.1]) by smtp23.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 3DE094053E; Wed, 22 Mar 2017 15:57:12 -0400 (EDT)
X-Auth-ID: fluffy@iii.ca
Received: by smtp23.relay.ord1c.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id C9CA4404F0; Wed, 22 Mar 2017 15:57:11 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from [10.1.3.61] (S01065475d0f7dcd1.cg.shawcable.net [70.75.17.123]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:587 (trex/5.7.12); Wed, 22 Mar 2017 15:57:12 -0400
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Cullen Jennings <fluffy@iii.ca>
In-Reply-To: <41989F03-35A9-4C76-9626-696FE123AFBC@tzi.org>
Date: Wed, 22 Mar 2017 13:57:10 -0600
Cc: core <core@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E2DEAA22-A3FA-4C54-B950-5F5FD260F993@iii.ca>
References: <0A3A3346-9B5D-48B7-BB52-6DEE39A91200@iii.ca> <41989F03-35A9-4C76-9626-696FE123AFBC@tzi.org>
To: Carsten Bormann <cabo@tzi.org>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/4V06D2B2Jkoy9WEvUEP4Jis0GFE>
Subject: Re: [core] RSSI in SenML
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Mar 2017 19:57:14 -0000

> On Mar 22, 2017, at 12:52 PM, Carsten Bormann <cabo@tzi.org> wrote:
> 
> 
>> On 22 Mar 2017, at 19:47, Cullen Jennings <fluffy@iii.ca> wrote:
>> 
>> 
>> I got a request to add RSSI to the table in 12.1 of  of SenML 
>> 
>> Symbol: RSSI 
>> 
>> Description: Received signal strength indication
>> 
>> Type: float 
> 
> RSSI is a quantity (an ill defined one).
> 
> Table 12.1 is about units.
> 
> Is there a unit that RSSI tends to use?
> 
> (For certain Cisco devices, that would be “percent”.

Oh, despite what wikipedia claims, Cisco has different systems that implement pretty much every variant of this you can imagine :-) When you get down to it RSSI is really more or less defined by device and software that is loaded on it. I've seen, uh, grade inflation on RSSI on some devices because a competitors device reported better RSSI in same conditions. But  it is still one of the primary metrics to understand what is going on with radios. 


> Other devices try to express their signal strength indications in dBm (typically a negative value approximately from -30 to -120).
> But I don’t think there is any industry-wide way to do this.)
> 
> Grüße, Carsten
>

v2.23.0 | Report a Bug | By Email