RFC 8272 on TinyIPFIX for Smart Meters in Constrained Networks
rfc-editor@rfc-editor.org Tue, 14 November 2017 03:45 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B876126C2F for <ietf-announce@ietfa.amsl.com>; Mon, 13 Nov 2017 19:45:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 0x1mnBTGN3G4 for <ietf-announce@ietfa.amsl.com>; Mon, 13 Nov 2017 19:45:30 -0800 (PST)
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 926DA127005 for <ietf-announce@ietf.org>; Mon, 13 Nov 2017 19:45:30 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 690D9B8154D; Mon, 13 Nov 2017 19:45:11 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8272 on TinyIPFIX for Smart Meters in Constrained Networks
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20171114034511.690D9B8154D@rfc-editor.org>
Date: Mon, 13 Nov 2017 19:45:11 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/_N6cYlJTk32wl_RW_Mb_5S1bOLM>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Nov 2017 03:45:34 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8272
Title: TinyIPFIX for Smart Meters in
Constrained Networks
Author: C. Schmitt,
B. Stiller,
B. Trammell
Status: Informational
Stream: Independent
Date: November 2017
Mailbox: schmitt@ifi.uzh.ch,
stiller@ifi.uzh.ch,
ietf@trammell.ch
Pages: 30
Characters: 66447
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-schmitt-ipfix-tiny-04.txt
URL: https://www.rfc-editor.org/info/rfc8272
DOI: 10.17487/RFC8272
This document specifies the TinyIPFIX protocol that is used for
transmitting smart-metering data in constrained networks such as IPv6
over Low-Power Wireless Personal Area Networks (6LoWPAN, RFC 4944).
TinyIPFIX is derived from IP Flow Information Export (RFC 7011) and
adopted to the needs of constrained networks. This document
specifies how the TinyIPFIX Data and Template Records are transmitted
in constrained networks such as 6LoWPAN and how TinyIPFIX data can be
converted into data that is not TinyIPFIX in a proxy device.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. 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