Re: [dispatch] [Sframe] Dispatch of SFrame

Bernard Aboba <bernard.aboba@gmail.com> Wed, 17 June 2020 03:44 UTC

Return-Path: <bernard.aboba@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 B23D33A0E1A for <dispatch@ietfa.amsl.com>; Tue, 16 Jun 2020 20:44:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LD20DXKTGSsV for <dispatch@ietfa.amsl.com>; Tue, 16 Jun 2020 20:44:40 -0700 (PDT)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 2C1903A0E1D for <dispatch@ietf.org>; Tue, 16 Jun 2020 20:44:40 -0700 (PDT)
Received: by mail-pj1-x102f.google.com with SMTP id m2so388179pjv.2 for <dispatch@ietf.org>; Tue, 16 Jun 2020 20:44:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=t1nt5ThDIpq1r6aHWcBgHfHHL3CtHJ3D7lizEj+MMSk=; b=VN+Xyywi0fy5q1GNIGbuyjbm16yV7TnYv1kOGqNLjW4qdH2S+SsixjQz4mtCyLLZ4z 8K1T3Jd+RIeIYaf0+J1dqXn8iP8wsCoKqwiN6EZyopfQTj6Moaibkiy+9J0YDLjDCPGC aVMt2wPri3Xx+f9mBcpM+vrpkzUilLpXPliobV4RgEgLQNinRvOOL5JD5MQ7vY1HDEiQ 9MRt4TDg9rANCPs6vqy1Zd5aI8zkEKSdm3CLKlsAThSqV+h4V3dSdlq1++10yxvqTW3g LgkRE1stjpZMzR1M/8am5aXHP9+r1NUygrLRRd8b3CHFvmvJcQyXAhJOXhXL+Ko547mQ KZJg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=t1nt5ThDIpq1r6aHWcBgHfHHL3CtHJ3D7lizEj+MMSk=; b=Lt/svOTzuuI34wQxFRsmLPFYhCge+/0iLH4LYV3bC9zJkQXpN4rIGryKJVKjL8Sp5i C1nIBZLBN97gjpwgioZDK0WbjmGPhiWv+1RmyhmatH392C3qoH8Yt7foMITWUeap/xVH UjWDZmI8uor9IbEAisH58q/piJPLjMVPYrGOvnZxLP5UmLtzoYZxmMZ9e2s8UZdgYU45 1fq4ez/f8NShA5MbdwrU9sd6vANc9Dxt2nvNDUl1xH6OAWw58oQ9Zp7V3SEi66bFHNfi uN7+x5oPhtnGu76uF4vGPBLxCQzn1zoUPP4X5NdAvNu3MXQvqDDAxo+geiAlwOLWb0bw 16nQ==
X-Gm-Message-State: AOAM530Z0w738hujpNKJzHfWJLmbjLle7emcFULM+mCsrPzw9bzJHFDi EHzDc2o6rACsK9y7VdZkefI=
X-Google-Smtp-Source: ABdhPJzCCRiYXJFGwAG8S48wZ4kfTEMegtTZZC1xUEMDeX6cbPJFf0f0oi8Jr6AQch3EwOjnVQZN8Q==
X-Received: by 2002:a17:902:8304:: with SMTP id bd4mr4811099plb.8.1592365479351; Tue, 16 Jun 2020 20:44:39 -0700 (PDT)
Received: from [192.168.1.197] (c-71-227-236-207.hsd1.wa.comcast.net. [71.227.236.207]) by smtp.gmail.com with ESMTPSA id j17sm12223385pgn.87.2020.06.16.20.44.38 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 16 Jun 2020 20:44:38 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-45A5C78A-A27B-4E31-88E1-2ACEC2DA628A"
Content-Transfer-Encoding: 7bit
From: Bernard Aboba <bernard.aboba@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Tue, 16 Jun 2020 20:44:37 -0700
Message-Id: <8ACE39EA-BC17-4E8A-8D5C-1FF1247171C3@gmail.com>
References: <CAAZdMadu1HBRWLjZtZ5sj4zYXffmP9xNjLoZAVqq5Otk4PB-Og@mail.gmail.com>
Cc: Eric Rescorla <ekr@rtfm.com>, DISPATCH list <dispatch@ietf.org>
In-Reply-To: <CAAZdMadu1HBRWLjZtZ5sj4zYXffmP9xNjLoZAVqq5Otk4PB-Og@mail.gmail.com>
To: Victor Vasiliev <vasilvv@google.com>
X-Mailer: iPad Mail (17F80)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/jSMwf54IXhWaR62KHRYcmksn8Pc>
Subject: Re: [dispatch] [Sframe] Dispatch of SFrame
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 17 Jun 2020 03:44:42 -0000

For a key frame, SFrame can reduce the overhead of non-repudiation by two orders of magnitude. 

> On Jun 16, 2020, at 19:25, Victor Vasiliev <vasilvv@google.com> wrote:
> 
> I imagine that for high-bitrate traffic, the difference between encrypting every packet and encrypting an entire frame at once is substantial enough to make using asymmetric crypto feasible in practice.
> 
>> On Tue, Jun 16, 2020 at 10:53 AM Eric Rescorla <ekr@rtfm.com> wrote:
>> 
>> 
>>> On Tue, Jun 16, 2020 at 7:27 AM Bernard Aboba <bernard.aboba@gmail..com> wrote:
>>> On Jun 16, 2020, at 6:53 AM, Eric Rescorla <ekr@rtfm.com> wrote:
>>> > 
>>> > Yes, I understand that the wire encoding supports signatures, but in the discussions I've had (including with Emac) I don't think that people believe that the latency/bandwidth/computation tradeoff is viable.
>>> 
>>> [BA] Depends on the scenario.  We are in a pandemic where conferences are being used for all kinds of things that we haven’t seen before. For example, consider a situation in which participants are answering a binding poll and the responses (voice or data) need to be authenticated. SFrame can handle that. PERC cannot.
>> 
>> I don't really think framing this as "PERC vs. SFrame" is that helpful, but there's no in principle reason PERC couldn't have signatures, though of course one would need to define new algorithms.
>> 
>> -Ekr
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch