[Detnet] detnet chairs: github, pls.

Toerless Eckert <tte@cs.fau.de> Tue, 20 January 2026 11:02 UTC

Return-Path: <eckert@i4.informatik.uni-erlangen.de>
X-Original-To: detnet@mail2.ietf.org
Delivered-To: detnet@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 2875DAA54125; Tue, 20 Jan 2026 03:02:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.981
X-Spam-Level:
X-Spam-Status: No, score=-1.981 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.017, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=cs.fau.de
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 d0oZ0US1Oafk; Tue, 20 Jan 2026 03:02:21 -0800 (PST)
Received: from faui40.informatik.uni-erlangen.de (faui40.informatik.uni-erlangen.de [131.188.34.40]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 8B0E7AA5411E; Tue, 20 Jan 2026 03:02:21 -0800 (PST)
Received: from faui48e.informatik.uni-erlangen.de (faui48e.informatik.uni-erlangen.de [IPv6:2001:638:a000:4134::ffff:51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by faui40.informatik.uni-erlangen.de (Postfix) with ESMTPS id 4dwPXz62fTz1RBtW; Tue, 20 Jan 2026 12:02:11 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cs.fau.de; s=r20250630-faui40; t=1768906933; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type; bh=BQqM3jS91SSLNBFwcxG65FNJk2c0KQ5a4zmE1XepxJs=; b=MC/fz3SNVVRZSMxBrAZEgoHaw3itN/WmtEeYSw0Y1SwNagLcoWl/zIJzkF7g2lO78+gG/t Lwa/C80ngio5C2hS22aGUASTOX7Jogjtd3Eq0GiWnar50yRdtG+HkmvPRAFLXoO0J6509N V6wCvKrbeVrCOPasxSgi2tZTS1d+U7r+f9jqiBXvdNyQHkduJmXHaTyZM+MXlMRrYjbSbu 68HNtmQHIqwmnToA/5AtLc0roQ9PfcMQeOWtNN2wLhxd05SG9cAdH6nWR6DVi+X2swY69P II+CPVqAKlr8oqegIDyIvdZ8WzaaM3yYDnZd++l9QqORchoJ5FnLiXN/NTldvw==
Received: by faui48e.informatik.uni-erlangen.de (Postfix, from userid 10463) id 4dwPXz5QwSzl2r0; Tue, 20 Jan 2026 12:02:11 +0100 (CET)
Date: Tue, 20 Jan 2026 12:02:11 +0100
From: Toerless Eckert <tte@cs.fau.de>
To: detnet-chairs@ietf.org
Message-ID: <aW9gs8GHZ8ymmvC0@faui48e.informatik.uni-erlangen.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Message-ID-Hash: XP35QXQN32MKCWS7GBLT22U6CJQZELAD
X-Message-ID-Hash: XP35QXQN32MKCWS7GBLT22U6CJQZELAD
X-MailFrom: eckert@i4.informatik.uni-erlangen.de
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-detnet.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: detnet@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Detnet] detnet chairs: github, pls.
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/dzawdUwVuKHVRdXp1K8fOtE7004>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Owner: <mailto:detnet-owner@ietf.org>
List-Post: <mailto:detnet@ietf.org>
List-Subscribe: <mailto:detnet-join@ietf.org>
List-Unsubscribe: <mailto:detnet-leave@ietf.org>

Dear DetNet chairs

Could you please tkae the necessary steps so we can use the detnet github for the
just adopted draft ? I would certainly prefer a separate repository for each
draft just because it's then so much easier to not get confused about which draft
is being discussed, e.g. in the issues part. 

Also: please renev the invitation to the scaling requirements draft, hopefully
us co-authors can get towards also using that github repo (sorry, i missed the
invite, forgot about github earlier on, when it was created).

Thanks!
    Toerless