IETF Logo Mail Archive

[icnrg] Re: Post IETF 125 ICNRG Meeting

Hitoshi Asaeda <asaeda@ieee.org> Wed, 25 March 2026 14:35 UTC

Return-Path: <asaeda@ieee.org>
X-Original-To: icnrg@mail2.ietf.org
Delivered-To: icnrg@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 5030AD13F94E for <icnrg@mail2.ietf.org>; Wed, 25 Mar 2026 07:35:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (1024-bit key) header.d=ieee.org
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rI68DLhDvIb1 for <icnrg@mail2.ietf.org>; Wed, 25 Mar 2026 07:35:26 -0700 (PDT)
Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 5ACF8D13F887 for <icnrg@irtf.org>; Wed, 25 Mar 2026 07:34:51 -0700 (PDT)
Received: by mail-pf1-x434.google.com with SMTP id d2e1a72fcca58-82c20b9fb16so1205919b3a.0 for <icnrg@irtf.org>; Wed, 25 Mar 2026 07:34:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; t=1774449290; x=1775054090; darn=irtf.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=fnLXFk6Kp/HmHZFCxj2nep44omZ5WDcIuQ6OH3Lq7Zg=; b=bjswT6nzbQHkzsTfdt60D30et03pOJk7A8XeGVJViTlQaPzPxsCrGspkLvb8WHhuZB 1+AEkN9Buae44JMGnYrjcXUlp35qMVm14IbB6APaIgQ/X9EP1JtBBXClnh8eJKpotZBx 1hfOacDtKr13dqD7/01u8YxGPWbb0vnMOFyqs=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1774449290; x=1775054090; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-gg:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=fnLXFk6Kp/HmHZFCxj2nep44omZ5WDcIuQ6OH3Lq7Zg=; b=rAwUQMMK7tFyHhHTykvHtOw5ioGLVZkjNDLigql1TEAxG46+r8/uVBWAK8OhjuRDfM o4MqzekIvCOHnfSaHIJsbY4NM9yHEbKYYLrkZsmfFw7hgbSW8VByHPXUbyd2TvF8Jep+ dnUcjHBRmcot3GYkhZc1d2fEVRTR88j+uIO1pgBNL1OUgjvbciJvpsTbl2FoIpjspeEn 0eIAHiMi+UagArFEXCNGIq07yZRKdbN1wgshUc9ItngDPrNRjK+md6uLKG+xHKhxyu6+ al1ty8+CdVD1Xrs3cbD6fyqr/sT5BBQkkESpO69nZuDA1iPDGgr3r7SxfLdbkNctIkr0 Yo1A==
X-Forwarded-Encrypted: i=1; AJvYcCUJIN4j0BuqWD7Wzfmtr/uTpFNLe+Nxs0W/vk2xV3+ImZWw0Xf+fxm9DOsa8JQCSNeqH2kTHA==@irtf.org
X-Gm-Message-State: AOJu0YyY5NT2Ijpe5QWHFTxTlYfMZocydE6ddYNva6YIAe7Tdac2h0/h c5xGEl/AF+gLgmHGr3V3D6SeaK6RGXFKE9lm856beDllergM7yrHhLe8Fhsslf8BRA==
X-Gm-Gg: ATEYQzyZRxUr/BfXflfmtXMiPVF+Gp47oOg7kDIoJNL0rAclVoy91Qo998u6fA3d2tY O7V0jvuzJDi3ZJzQjhAyTaiQ2R+PLkFgoSx0Wj114VBu3rOeXQUhoKQIPzU+/YKVG7clJeEylUe ohggsM/R6tozhxYxEwxfokdDoq/sr1kUq+zDZoYggP3b4G+IkhpED6PJc/KyoS6qwTy3cZTXq9p QPdMEOp2BES8jEc3X+hKU3XozKbe5cKk/pOEyWFnoRdm6owGG0EF9/1HUK4A9anmVNE4oReeA+/ ROzaRl+AragDlnedNtrRAHOQqxNorrlbJ2uAK5JfiFhIKNCbim5rrAkZCRTwna7EqXZQlMY2cON uRQmhEcJC1+szgZiFDfB3oUHwRSfeva59MXl+UfhFCKYjeHx6AmFRA93kKUM2MFTtRxMMbgZr/j S9N6f0JusByI0HKhUdjcQB7L5J6sJAiFnYvwhRb0u8Eeh2UAIddT04bJopfXnQJnSiPoa+YC2ya b6Oog5dUmfN
X-Received: by 2002:a05:6a00:94f1:b0:82a:8163:4c00 with SMTP id d2e1a72fcca58-82c6de73d4fmr3561625b3a.2.1774449290390; Wed, 25 Mar 2026 07:34:50 -0700 (PDT)
Received: from smtpclient.apple (zz20164245726F66C1A1.userreverse.dion.ne.jp. [111.102.193.161]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-82b03aa5aa7sm15763319b3a.1.2026.03.25.07.34.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 25 Mar 2026 07:34:50 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51\))
From: Hitoshi Asaeda <asaeda@ieee.org>
In-Reply-To: <b9a7d7a4-b8d3-48e0-b457-e7461d78d31a@gmail.com>
Date: Wed, 25 Mar 2026 23:34:46 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <40082E61-DA4F-4D82-A6F1-AE6DBFD04792@ieee.org>
References: <288365C7-5076-4DDD-9BA7-F29C578CCF16@htonl.net> <b9a7d7a4-b8d3-48e0-b457-e7461d78d31a@gmail.com>
To: Michael Toomim <toomim@gmail.com>
X-Mailer: Apple Mail (2.3776.700.51)
Message-ID-Hash: 3MQXQS5WE2CRW2OITN5CT37BTV7545GM
X-Message-ID-Hash: 3MQXQS5WE2CRW2OITN5CT37BTV7545GM
X-MailFrom: asaeda@ieee.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-icnrg.irtf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ryo Yanagida <ryo@htonl.net>, icnrg@irtf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [icnrg] Re: Post IETF 125 ICNRG Meeting
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/KgYuMFC75zbr5uprc6fUHKgzXIo>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Owner: <mailto:icnrg-owner@irtf.org>
List-Post: <mailto:icnrg@irtf.org>
List-Subscribe: <mailto:icnrg-join@irtf.org>
List-Unsubscribe: <mailto:icnrg-leave@irtf.org>

Hi Michael,

> Do you wish to support cases where multiple peers can mutate state at the same time?  If so, you will want to allow branching and forking.

We currently assume that a content owner sets the version of the content and that they will increase the version number sequentially. Intermediate nodes/forwarders do not change the version number.

Regards,

Hitoshi


> On Mar 25, 2026, at 21:25, Michael Toomim <toomim@gmail.com> wrote:
> 
> Hello Ryo and Dave!  Congrats on the new draft!
> 
> I am new to CCNx, but I happen to be authoring a "Resource Versioning" draft for HTTP, and I couldn't help but check out the similarities and differences in CCNx.
> 
> One thing I notice is that the CCNx version identifiers are defined to be a linear sequence.  Do you wish to support cases where multiple peers can mutate state at the same time?  If so, you will want to allow branching and forking.
> 
> Michael
> 
> On 3/25/26 6:23 PM, Ryo Yanagida wrote:
>> Hi all,
>> Thank you very much for a very successful ICNRG meeting at IETF 125.
>> It has been our pleasure to chair the session with the help of Dirk who kindly sat in the room onsite as the onsite delegate.
>> First, we’d like to thank all the speakers who gave a wonderful set of talks.
>> Second, we are looking for reviewers for the *CCNx Content Versioning draft: draft-irtf-icnrg-ccnxversioning-00 <https://datatracker.ietf.org/ doc/draft-irtf-icnrg-ccnxversioning/>*
>> If any of you can contribute, it would be great. Even those who are quite new, if you can take a look to see if anything is confusing or spotting the typos are also useful. (Just send a quick email to the group)
>> Third, we have a draft on *Flie-Like ICN Collections (FLIC) (draft-irtf- icnrg-flic-07 <https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/  >)*, and it would be great to get it over the line.
>> And last but not least, we should start thinking about agenda for the next IETF 126 meeting in Vienna.
>> Please send a quick email to the groups with ideas around themes/topics as well as specific talks.
>> Best,
>> Ryo and Dave
>> _______________________________________________
>> icnrg mailing list -- icnrg@irtf.org
>> To unsubscribe send an email to icnrg-leave@irtf.org
> 
> _______________________________________________
> icnrg mailing list -- icnrg@irtf.org
> To unsubscribe send an email to icnrg-leave@irtf.org

v2.46.0 | Report a Bug | By Email | System Status