IETF Logo Mail Archive

Re: [Coin] Use case draft: next (and final) steps

Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk> Thu, 24 November 2022 09:18 UTC

Return-Path: <Jon.Crowcroft@cl.cam.ac.uk>
X-Original-To: coin@ietfa.amsl.com
Delivered-To: coin@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7247CC14CF03 for <coin@ietfa.amsl.com>; Thu, 24 Nov 2022 01:18:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.997
X-Spam-Level:
X-Spam-Status: No, score=-6.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=cl.cam.ac.uk
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 9iAL60Fabw7N for <coin@ietfa.amsl.com>; Thu, 24 Nov 2022 01:18:01 -0800 (PST)
Received: from mta1.cl.cam.ac.uk (mta1.cl.cam.ac.uk [128.232.0.57]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B4F99C14F6E7 for <coin@irtf.org>; Thu, 24 Nov 2022 01:18:01 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=cl.cam.ac.uk; s=mta3; h=Message-Id:Date:Content-Transfer-Encoding: Content-ID:Content-Type:MIME-Version:References:In-reply-to:Subject:to:From: Sender:Reply-To:Cc:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=+hupaP7i3v+6w6HonXdRut8HO+WXpqdv5lrp+mDQFqc=; t=1669281481; x=1670145481; b=GQq0w9/zIRbOK+XYAnqFENO5mLhro4YaiMph2jkMrfDVyVjPqv4BBdRgdEztKYNpvSH/CqUkge6 4YGvhkS3zccZY5sPnyr3/367II9h6UyxuroDzHILicrXDm0EJ9H8YtehXDdnLBYY1qfZannf11R+X u3MV7tLAVD3Z2j5jmLNYTq6YmB2WrLGOAuXb2aJt8p1iPoHw7YnAdmp6x16CUDmbNNIufRGq8lKWN 5eRzFzcE3UsF8qS8nj2A3Oj11ksiZlcqi39FrIBwQllDdK+uyfOasAwR6KwAoP+WIIC/lOkXQEjj6 ee1S9h5frvM4fLW/IiJT39tIVCSLU+Z8FQtw==;
Received: from svr-ssh-1.cl.cam.ac.uk ([128.232.102.11]:57434) (dnseec=no) by mta1.cl.cam.ac.uk:587 [128.232.0.57] with esmtp (Exim 4.95) id 1oy8Kg-00HOqG-Re (envelope-from <Jon.Crowcroft@cl.cam.ac.uk>); Thu, 24 Nov 2022 09:15:46 +0000
From: Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
to: coin <coin@irtf.org>, Jon Crowcroft <Jon.Crowcroft@cl.cam.ac.uk>
In-reply-to: <0603435C-6EF0-4FEF-9216-69FD0BD03CDF@comsys.rwth-aachen.de>
References: <0603435C-6EF0-4FEF-9216-69FD0BD03CDF@comsys.rwth-aachen.de>
Comments: In-reply-to Ike Kunze <Ike.Kunze@comsys.rwth-aachen.de> message dated "Thu, 24 Nov 2022 07:47:42 +0000."
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-ID: <2298895.1669281346.1@svr-ssh-1.cl.cam.ac.uk>
Content-Transfer-Encoding: quoted-printable
Date: Thu, 24 Nov 2022 09:15:46 +0000
Message-Id: <E1oy8Kg-00HOqG-Re@mta1.cl.cam.ac.uk>
Archived-At: <https://mailarchive.ietf.org/arch/msg/coin/tqWthuvx6kmpiRE89hHeezA_53Q>
Subject: Re: [Coin] Use case draft: next (and final) steps
X-BeenThere: coin@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "COIN: Computing in the Network" <coin.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/coin>, <mailto:coin-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/coin/>
List-Post: <mailto:coin@irtf.org>
List-Help: <mailto:coin-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/coin>, <mailto:coin-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Nov 2022 09:18:06 -0000

random thoughts:-
https://paravirtualization.blogspot.com/2022/11/in-network-compute-and-end-to-end.html

> Hi all,
> 
> As parts of the ongoing "E2E transport discussions” directly relate to 
> originally envisioned content of the use case draft and as we could not 
> give an update at IETF 115, I would like to take the time and briefly lay 
> out the next steps for the use case draft.
> You can also have a look at our slides for London [1] for an overview of 
> the current draft structure.
> 
> Overall, we will move towards closing off the document as we have not 
> received any new notes regarding possible new use cases that could be 
> added.
> For this, we will first finish aligning the use cases according to our 
> tightened taxonomy.
> Afterwards, we will move out the terminology and analysis sections into 
> separate drafts.
> The terminology draft will most likely directly have some sensible 
> content that could be discussed in the RG while the analysis draft will 
> only have a fundamental structure, nothing more.
> 
> While we will be happy to set up these documents, we will need more/other 
> contributors to actively contribute to and pursue these drafts.
> This is especially true for the analysis of the use cases as this will 
> require some effort.
> Please respond to this mail if you are interested in contributing!
> 
> Once we have the mentioned updates ready, we will submit a first 
> “final” version from our perspective and move to an RG last call.
> 
> If you have any additional thoughts on our plans that you think we should 
> consider, please let me know soon.
> We are hopeful to finish these changes before Christmas.
> 
> Thanks.
> 
> Cheers,
> Ike
> 
> [1] 
> https://datatracker.ietf.org/meeting/115/materials/slides-115-coinrg-draft-irtf-coinrg-use-cases
> 
> --
> Coin mailing list
> Coin@irtf.org
> https://www.irtf.org/mailman/listinfo/coin
>

v2.23.0 | Report a Bug | By Email