[core] RFC 8798 on Additional Units for Sensor Measurement Lists (SenML)

rfc-editor@rfc-editor.org Thu, 25 June 2020 18:18 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 D48DC3A0E8A; Thu, 25 Jun 2020 11:18:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=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 OxbNRAnPga-d; Thu, 25 Jun 2020 11:18:24 -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 9188C3A0E92; Thu, 25 Jun 2020 11:18:24 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1E1DEF4070D; Thu, 25 Jun 2020 11:18:11 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, core@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20200625181811.1E1DEF4070D@rfc-editor.org>
Date: Thu, 25 Jun 2020 11:18:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/MyhcFv78gIec7Ypz2U72ghE0U48>
Subject: [core] RFC 8798 on Additional Units for Sensor Measurement Lists (SenML)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 25 Jun 2020 18:18:38 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8798

        Title:      Additional Units for Sensor Measurement 
                    Lists (SenML) 
        Author:     C. Bormann
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2020
        Mailbox:    cabo@tzi.org
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-core-senml-more-units-06.txt

        URL:        https://www.rfc-editor.org/info/rfc8798

        DOI:        10.17487/RFC8798

The Sensor Measurement Lists (SenML) media type supports the
indication of units for a quantity represented.  This short document
registers a number of additional unit names in the IANA registry for
units in SenML.  It also defines a registry for secondary units that
cannot be in SenML's main registry, as they are derived by linear
transformation from units already in that registry.

This document is a product of the Constrained RESTful Environments Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC