[icnrg] ICNRG progress
"Dirk Kutscher" <ietf@dkutscher.net> Mon, 24 February 2020 18:19 UTC
Return-Path: <ietf@dkutscher.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 DC10C3A108B for <icnrg@ietfa.amsl.com>; Mon, 24 Feb 2020 10:19:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 hKi0YsWHNecv for <icnrg@ietfa.amsl.com>; Mon, 24 Feb 2020 10:19:44 -0800 (PST)
Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B91623A096F for <icnrg@irtf.org>; Mon, 24 Feb 2020 10:19:43 -0800 (PST)
Received: from [192.168.1.69] ([77.21.26.148]) by mrelayeu.kundenserver.de (mreue109 [212.227.15.183]) with ESMTPSA (Nemesis) id 1MsYzF-1jR8640zr1-00u0aH for <icnrg@irtf.org>; Mon, 24 Feb 2020 19:19:39 +0100
From: Dirk Kutscher <ietf@dkutscher.net>
To: ICNRG <icnrg@irtf.org>
Date: Mon, 24 Feb 2020 19:19:37 +0100
X-Mailer: MailMate (1.13.1r5671)
Message-ID: <9787A5A6-9B76-4091-8146-09C060ED7FBB@dkutscher.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"; format="flowed"; markup="markdown"
Content-Transfer-Encoding: 8bit
X-Provags-ID: V03:K1:Dm9ZkyQVwRtfmR++j0z7+hdbzj5HnORVqpWTLaYWukvbaxlEpiu js8DOwoHmksdgk6f5KfXNRT0UXuAMteNk6ZX6vNMeWrEhvabySatHyeLsD9+nXa/qeyImYg FKhS4LxI9GsqIs00vOC1QvsPTAKgBf8VWvuf2FlGo4XBrJm1skYAq2G4pNnCcqnXgFxh2OD nXOTolF/boehVSuGiVk6Q==
X-UI-Out-Filterresults: notjunk:1;V03:K0:Kmrgp1uBljQ=:2MWqyusaD3LkLxX+zbRzuT Go/LMkHdD6wgu6IBqgkPt1wWtMy0JM/BKF8mdV3nT9FC3NEvSijo/3mgVoTjxNRvt8NEINXyj 1pgdknSHelEKbJZEuo1vSZs5L4Lz/6vt8tmFbMNsTV8hinlvq08gQmyefyjdx9bHqDqa1p2zA Qolf1GktHjuA2WQB5o1hIhK4WpdcdL1BpaRNIQw5eqDZYoTOFReMRAxbIgvDLp4lhux/mxNDW 9SiUKwUtJD6TyCzzCwY/ECjSJuuIKbtyblNMEJAHEelRn3zwzE1eyWzWbfqE2spMBLI6MzkYr 1pTzlPPsvCmXPrH8ArrkTOMejUSGNde1mNFFiSO8ApyAydFQ2ykGucOb0kByg50Byy/FtQQPo bjBezOwWdaAhXwsA4FDWqngoRmv+OmG/+A27jm6nMRw34QpvcaIxN6veaHmPVB2wBhXWAO0IM ZBeJPGRmX9TLYOPsjNlg8BXnVgTQPjdYVZC6Nlsc7LmYDN/eaCfWeV7DS2wBfVK9fopc3AZJR 3eriTDmfOROihiXvyiK0OmcOrH3SDsEny6+xPPSuWLplzQ+GXaYYPpk2ha5ubNcj77zjTMaLe IIX/3Aj4LYmEhhuBtqcdrpBFNw/zl5nPbJkJtlRTozhpxRQuZzHCSKrX7XvUhcNDLxrxsWVyA +gDT7JjjPJ+KCFl8N441OUgXKnBjXESeRZzxOeZyhZsQrzGuFrR9Ko317+5reKC+5QVeE6t9u EyWBvKgRXkzlFGlCHpKlxjZphWSTUfLxHq9IetdHLlITb+5LyxG1o1J02nHS6NJ0SDJQosjlI qVIvSu7ZQpSin5uUpF6WTqhlj7ezOWuJdwOatGa32njExZpyU2Ca+LggZbAdLqQXYLAabCC
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/VhPrciCzH1ivxuJuBTIjZgZVtrU>
Subject: [icnrg] ICNRG progress
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.29
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: Mon, 24 Feb 2020 18:19:46 -0000
Hi ICNRG, ICNRG has been progressing nicely over the last months — with many useful submitted drafts and quite interesting and well-attended meetings. Recently, we have tried to last-call or to adopt a few documents, which evoked relatively limited activity, e.g., the Qos Architecture draft, the ICN Lowpan draft, ICN ping, ICN traceroute. We thought it might be good to remind us that we really do not have to wait until physical meetings to discuss these things. Instead, it’s often more productive to have an informed discussion on the mailing list and then just clarify unresolved issues at the meetings. Typically, our meetings are quite busy, hence, we would like to know whether there is any particular reason for the recent silence — and to encourage everyone to make use of the mailing list more, so that we can get things out of the door faster and turn towards new challenges. On that note, we would also like to remind everyone of our call for contributions to the upcoming ICNRG Interim and regular meetings at IETF-107. Especially for the Interim, we would need to see a few more suggestions for presentations & discussion that would justify having that meeting. Keep up the good work — your ever vigilant chairs, Börje, DaveO, and Dirk
- [icnrg] ICNRG progress Dirk Kutscher
- Re: [icnrg] ICNRG progress Ken Calvert
- Re: [icnrg] ICNRG progress Mosko, Marc <mmosko@parc.com>