[icnrg] RFC 9510 on Alternative Delta Time Encoding for Content-Centric Networking (CCNx) Using Compact Floating-Point Arithmetic
rfc-editor@rfc-editor.org Thu, 22 February 2024 23:36 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5553EC15109A; Thu, 22 Feb 2024 15:36:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.657
X-Spam-Level:
X-Spam-Status: No, score=-6.657 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bpilo8cf6p-w; Thu, 22 Feb 2024 15:36:42 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91346C15171B; Thu, 22 Feb 2024 15:36:42 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 603EBEF28C; Thu, 22 Feb 2024 15:36:42 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, icnrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20240222233642.603EBEF28C@rfcpa.amsl.com>
Date: Thu, 22 Feb 2024 15:36:42 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/ZHxHaSPP7AnrqsR_YzIx8gDawp8>
Subject: [icnrg] RFC 9510 on Alternative Delta Time Encoding for Content-Centric Networking (CCNx) Using Compact Floating-Point Arithmetic
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://mailman.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://mailman.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Feb 2024 23:36:47 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9510
Title: Alternative Delta Time Encoding for
Content-Centric Networking (CCNx)
Using Compact Floating-Point Arithmetic
Author: C. Gündoğan,
T. Schmidt,
D. Oran,
M. Wählisch
Status: Experimental
Stream: IRTF
Date: February 2024
Mailbox: cenk.gundogan@huawei.com,
t.schmidt@haw-hamburg.de,
daveoran@orandom.net,
m.waehlisch@tu-dresden.de
Pages: 11
Updates: RFC 8609
I-D Tag: draft-irtf-icnrg-ccnx-timetlv-05.txt
URL: https://www.rfc-editor.org/info/rfc9510
DOI: 10.17487/RFC9510
Content-Centric Networking (CCNx) utilizes delta time for a number of
functions. When using CCNx in environments with constrained nodes or
bandwidth constrained networks, it is valuable to have a compressed
representation of delta time. In order to do so, either accuracy or
dynamic range has to be sacrificed. Since the current uses of delta
time do not require both simultaneously, one can consider a
logarithmic encoding. This document updates RFC 8609 ("CCNx messages
in TLV Format") to specify this alternative encoding.
This document is a product of the IRTF Information-Centric Networking
Research Group (ICNRG).
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
Distribution of this memo is unlimited.
This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
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