Re: [dispatch] Securing Ancillary Data for Communicating with Devices in the Network (SADCDN)

Matt Joras <matt.joras@gmail.com> Thu, 02 November 2023 17:13 UTC

Return-Path: <matt.joras@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F619C151062 for <dispatch@ietfa.amsl.com>; Thu, 2 Nov 2023 10:13:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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=gmail.com
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 9RLnN0NDj4aE for <dispatch@ietfa.amsl.com>; Thu, 2 Nov 2023 10:13:25 -0700 (PDT)
Received: from mail-ej1-x62c.google.com (mail-ej1-x62c.google.com [IPv6:2a00:1450:4864:20::62c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 EC37DC14F74E for <dispatch@ietf.org>; Thu, 2 Nov 2023 10:13:25 -0700 (PDT)
Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-9d465d1c86bso187489766b.3 for <dispatch@ietf.org>; Thu, 02 Nov 2023 10:13:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698945204; x=1699550004; darn=ietf.org; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=9kkCZya4+DD5dRfmlcoO+JwEJp9occHUAHnFcpXHt00=; b=jKLIXSVJMX1Nw036zv4f+YDAcnAANxIjNysw9wm6XVzoPqM4Nwwp3j3AG/TYOqgaGj 0VvGpBD8QyqlFPeFgjAZjVNVBzX27qZ91uYqYZGki719BGpAD4fmE5kq+hLKBf0Nl2Md xcmDfmoReky93ZFDiFWNUdDvzjQx7KPAxgT/GUJo5E5AZ+0SxBUjKjBv1XMikdYJtV4W 3dUyDfKsjjcavgrdCiDATbeVhldfRmhc3HJQ0U9343idamvmdcVscHXsG3ZB0bTtdnYU SXUTmy3iVz9hsXubdcvlfIC2nWAMH81Qp61J/OWzq0va/MY5uG/CePiI2F7+wsEyQTbG NQxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698945204; x=1699550004; h=content-transfer-encoding:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=9kkCZya4+DD5dRfmlcoO+JwEJp9occHUAHnFcpXHt00=; b=lbFBz5FPLlvNrs8Td35mMwdZQtwy/gjRLAzS588Ti7hvRNcOJ4xUwS5KvMJk+wJJcw CZf3BmL4lTh/dEIr8cAE0cMnYwW3xUkBD3y4gJyMLojII81fz9hzMy7M801poH1N7MG6 FGvLaR8i8RwsFdrQP6UWXpRRZWGSvDlNtUnJl+XbAFuTyBWdvVvdW3arwwPuYTlobn4W 5ac8DTxpJ7NSnbm5ujEnIANbu213usTKw/IE/TrJWxLAbYIW7k3JLZj1dieIXnBjX3Tz YCU4QUdp7m/u9suOQCt30H75OpPPCsg1BqGr0LiFcU8jRep0ZgPJ16GHJ4t4tfCHjBjT yG7w==
X-Gm-Message-State: AOJu0YzalepubojyvENu2BfDpRwZDnzvMLTJ44ab3s+Ong4qg6Z8WrJH Ut0KDKJ3zBbkbxPWhOz/w/saqQ3DeNWoaOd1r0Ii9v1pXGM2Yg==
X-Google-Smtp-Source: AGHT+IEDTgtTc1XF7RMP0lKSWzMw5s5a73ioBhPfzWTQLXQ2qDBcH+Sh6S1zYxRo82Ljb3oILbBg4ZiHbKmDWGOeO2c=
X-Received: by 2002:a17:906:6a23:b0:9bf:2f84:5de7 with SMTP id qw35-20020a1709066a2300b009bf2f845de7mr5018039ejc.4.1698945203950; Thu, 02 Nov 2023 10:13:23 -0700 (PDT)
MIME-Version: 1.0
References: <027EF0D3-B55D-48C4-9456-18D061D272D8@gmail.com>
In-Reply-To: <027EF0D3-B55D-48C4-9456-18D061D272D8@gmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Thu, 02 Nov 2023 10:13:12 -0700
Message-ID: <CADdTf+gmKhwjiL0VnRvapdRNTfC1zGvjx7Yq6am9gFmi9Hhb+Q@mail.gmail.com>
To: dispatch@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/9K_evevDWkJL3xYDkmyguzuo6n4>
Subject: Re: [dispatch] Securing Ancillary Data for Communicating with Devices in the Network (SADCDN)
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Nov 2023 17:13:26 -0000

Hello all,

Just wanted to do a quick follow-up here: we will be having another
side meeting on the SADCDN topic (rather than any particular solution)
on Tuesday at 10:00 in Palmovka 1/2. As a reminder, SADCDN refers to
the concept of establishing an in-band encrypted communication channel
with a “network device” for the purposes of cooperative information
exchange about a given network flow. We will have the following
speakers speaking to use cases and potential implementation of this
_sort of thing_, not necessarily the SADCDN strawman draft:

Ian Swett from Google
Wonho Park from TikTok
Tiru Reddy from Nokia
Marcus Ilhar from Ericsson
Dan Druta from AT&T

If you are interested in this topic please feel free to attend or
reach out to me with questions.

Best,
Matt Joras


On Tue, Jul 11, 2023 at 11:16 AM Matt Joras <matt.joras@gmail.com> wrote:
>
> Hello all,
>
> (quic and tsvwg on bcc as interested parties)
>
> We will be presenting the SADCDN draft[1] during DISPATCH at IETF 117 and wanted to start some mailing list discussion prior. We have also scheduled a side meeting on Tuesday at 18:00 for anyone interested.
>
> The document primarily focuses on the problem space, but also has a sketch of what one solution might look like. That problem is, in brief, establishing a secure, entirely in-band, communication channel between devices in the network and content endpoints for exchanging certain limited classes of information. We are hoping to get dispatch feedback on how and if this should be worked on at the IETF. This work has similarities to previous and ongoing IETF work as is noted in the draft.
>
> Best,
> Matt Joras
>
> [1] https://datatracker.ietf.org/doc/draft-joras-sadcdn/01/