Re: [icnrg] IRTF Chair review of draft-irtf-icnrg-ccnx-timetlv-01

Cenk Gündoğan <mail+ietf@gundogan.net> Sun, 08 January 2023 11:43 UTC

Return-Path: <mail+ietf@gundogan.net>
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 58959C14F738 for <icnrg@ietfa.amsl.com>; Sun, 8 Jan 2023 03:43:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.694
X-Spam-Level:
X-Spam-Status: No, score=-1.694 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_FAIL=0.001, SPF_HELO_NONE=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (bad RSA signature)" header.d=gundogan.net
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 Guf33Q-sH0kR for <icnrg@ietfa.amsl.com>; Sun, 8 Jan 2023 03:43:39 -0800 (PST)
Received: from mail.localdomain (trantor.gundogan.net [37.120.167.193]) (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 53180C14F72C for <icnrg@irtf.org>; Sun, 8 Jan 2023 03:43:39 -0800 (PST)
Received: from localhost (ip5f5ac3fc.dynamic.kabel-deutschland.de [95.90.195.252]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by mail.localdomain (Postfix) with ESMTPSA id BBE4A50CA3; Sun, 8 Jan 2023 12:43:36 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gundogan.net; s=201712; t=1673178216; bh=x+rCpwiYeozqfUsNXcPEL3wl9vqlBBve4mfOVXJQJBc=; h=References:From:To:Cc:Subject:Date:In-reply-to:From; b=X8IE/cR63b41ZO1ltBXtaI3tzrHKwIBBgxcYr1dechQ/V9ZEVN2bz0fcurn9/x38A LF0ramBeruncUWdL0ioRpZl1YJdPBAN9TEU6cthQJhcUdQX9/RdYFZpo4n0EzTnPLY 2aG25kkSlnwLFGsL2kIbrsi08kiWqy7A/Z7qT+Etnz3+SLg505E3KSTrjmCG1SHcPm Hf1Omj6yxBbJPyEDI6H7M4MDbqb8BaPI4afEU6U49KJJTeD43VMCvgqHIOlmGJU6Bv S/jK+dWKza29ImoG+9NaNxwXkaVKKPv6osfq23sL2zTTLiI8lV8YD+wr6rkBggi6r6 wdrApkofaOFlA==
References: <68FDE7B4-B03E-4540-BA57-60BA8D361D93@csperkins.org> <2EB2137C-1C21-4BC5-BA3E-D6AD399D0244@orandom.net> <alpine.WNT.2.00.2212081926150.13544@mw-x1> <CD48A385-5F31-4442-A254-A777430BFC66@csperkins.org> <c3ce3966008b43e487b90770918d7033@huawei.com> <13701880-B95B-4937-A58E-6D0CE8412B23@csperkins.org>
User-agent: mu4e 1.8.13; emacs 30.0.50
From: Cenk Gündoğan <mail+ietf@gundogan.net>
To: Colin Perkins <csp@csperkins.org>
Cc: draft-irtf-icnrg-ccnx-timetlv@ietf.org, icnrg-chairs@ietf.org, icnrg@irtf.org
Date: Sun, 08 Jan 2023 12:15:27 +0100
Message-ID: <87pmbp5ku2.fsf@gundogan.net>
In-reply-to: <13701880-B95B-4937-A58E-6D0CE8412B23@csperkins.org>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="===-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/0bBUXiDnbPiGI7nwThFUBVld7Uc>
Subject: Re: [icnrg] IRTF Chair review of draft-irtf-icnrg-ccnx-timetlv-01
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://www.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://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sun, 08 Jan 2023 11:43:44 -0000

Hello Colin,

sorry for the delay; there is a new version of the document now 
(-02).  Changes include:

1. Mentioning the experiment deployments in the Introduction.
2. Removing alternative solutions, as we do not mention them 
anywhere else.
3. Moving the CCNx RFCs to normative.
4. Stating in the IANA considerations that we re-use “CCNx 
Hop-by-Hop Types”
   T_INTLIFE (0x0001) and T_CACHETIME (0x0002).
5. Minor affiliation updates

Cheers,
 Cenk

Colin Perkins <csp@csperkins.org> writes:

> On 9 Dec 2022, at 8:08, Cenk Gundogan wrote:
>
>> Hello Colin,
>>
>> On 8 Dec 2022, at 18:27, Matthias Waehlisch wrote:
>>> On Thu, 8 Dec 2022, David R. Oran wrote:
>>>
>>>>       Authors, please can you also respond to this message to 
>>>>       confirm
>>>>       that all necessary IPR disclosures, as described on
>>>>   <https://irtf.org/policies/ipr>, have been made?
>>>>
>>>> None from me.
>>>>
>>>   same for me.
>>
>> Also none from me.
>>
>> We will update and upload a new version of the document in the 
>> next few days to address your comments.
>
> Thanks!
>
> Colin
>
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> <https://www.irtf.org/mailman/listinfo/icnrg>

—
Cenk Gündoğan
--- Begin Message ---
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Information-Centric Networking RG of the IRTF.

        Title           : Alternative Delta Time Encoding for CCNx Using Compact Floating-Point Arithmetic
        Authors         : Cenk Gündoğan
                          Thomas C. Schmidt
                          Dave Oran
                          Matthias Waehlisch
  Filename        : draft-irtf-icnrg-ccnx-timetlv-02.txt
  Pages           : 12
  Date            : 2023-01-08

Abstract:
   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 such as that
   specified in [RFC5497] and [IEEE.754.2019].  This document updates
   _CCNx messages in TLV Format_ [RFC8609] to specify this alternative
   encoding.

   This document is a product of the IRTF Information-Centric Networking
   Research Group (ICNRG).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-irtf-icnrg-ccnx-timetlv/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-ccnx-timetlv-02

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-irtf-icnrg-ccnx-timetlv-02


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts


_______________________________________________
icnrg mailing list
icnrg@irtf.org
https://www.irtf.org/mailman/listinfo/icnrg
--- End Message ---