[Sframe] Fwd: New Version Notification for draft-ietf-sframe-enc-04.txt

Richard Barnes <rlb@ipv.sx> Sun, 22 October 2023 18:32 UTC

Return-Path: <rlb@ipv.sx>
X-Original-To: sframe@ietfa.amsl.com
Delivered-To: sframe@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32C04C1524AC for <sframe@ietfa.amsl.com>; Sun, 22 Oct 2023 11:32:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.903
X-Spam-Level:
X-Spam-Status: No, score=-6.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=ipv-sx.20230601.gappssmtp.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 We4K0e35KLgB for <sframe@ietfa.amsl.com>; Sun, 22 Oct 2023 11:32:36 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 AE0DCC14F748 for <sframe@ietf.org>; Sun, 22 Oct 2023 11:32:21 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-99bdeae1d0aso380256266b.1 for <sframe@ietf.org>; Sun, 22 Oct 2023 11:32:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20230601.gappssmtp.com; s=20230601; t=1697999539; x=1698604339; darn=ietf.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=H/5C7395g0nr0zswHmtIjVVVRuGHyzZ+LM1NYKdZ1QA=; b=nDI6t0m4aSOYn2KpU3qOScObvGW6MKwtkcS9z9O4pLHEQzWZw9TnzxPv/Zlpz0uFpW 8Aa57FItReHjCqdWeaEK0nQpK64oOEiLVAK0NfDcH7FXtHpcb1aJNBrBmv6MmNzCkk2e NFhnbSvYlXZI6ScSU1SJOQ4+CE6GijpWMLQDeStBiweMwagkaSs5rqod9F5fDEC/EYe9 7laQlhxHJYY6cgnZnM4KeXb18hj12DbfwxGj2xeNC73wD64fRZkO5EuOqeiLpUzP9Uy+ +oKItOlGPez+x+3+Ks+UF0wvlXr1sst/GvqdTXRVYa1y39x2J3nsDnTableS2qGt/OtN +xGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1697999539; x=1698604339; h=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=H/5C7395g0nr0zswHmtIjVVVRuGHyzZ+LM1NYKdZ1QA=; b=UkwXzwdiHH5IqB3MiZAYzmOKts3ynZC0wFpkp5gHRTgn4bgVH1V0SH2W+wW4KBJTf5 2ZXqWOqU4DnWIdtzs/cT/dIXLjh6FzkHYQ96ISeXqkm9PgRu6uJZiWpkps34Db6GPVXg YKSxvOhjmi55VxIh4U1+qMzNm0JpOf2l9nAcqhJ0BvL2ue38d2avKZXwREDmgj+uVfRE yM/j4QjC/Fl0VFO2LhDLNR0dJYhangplNpfsAarq9nRJKMs7d3MuOh0DZ4QpwXukp5eh /EjUfzEAmOU4Md6m8D3LuTMQnPgVgnL1U5+8GJFQOywGJf5RZJ87KgGsScDkjlx1QlHq 5XqA==
X-Gm-Message-State: AOJu0YwLedteCmm39s+bTeuHaLkcnmFUxX4Dp3NhgsDG5RFcB6LK+YOe +WrLue2R/vqsCKx90SLBXuqmBQgVlgqg3VZKZavoIN4YrH5j0gZcgsw=
X-Google-Smtp-Source: AGHT+IGPXqp4gHxS7+DKDcl61/eQsypaQ1sLBS4LoRiXdu1I93P07NFphvmpUg1DmLtEuFoaQ8fJabL7VrMhTkJFT/g=
X-Received: by 2002:a17:907:9306:b0:9be:b43c:38db with SMTP id bu6-20020a170907930600b009beb43c38dbmr5262775ejc.5.1697999539205; Sun, 22 Oct 2023 11:32:19 -0700 (PDT)
MIME-Version: 1.0
References: <169799946855.5686.14155242659374594675@ietfa.amsl.com>
In-Reply-To: <169799946855.5686.14155242659374594675@ietfa.amsl.com>
From: Richard Barnes <rlb@ipv.sx>
Date: Sun, 22 Oct 2023 14:32:08 -0400
Message-ID: <CAL02cgTFmgaTaowdxUO02RU3789z-YQvoWSrJL3j8hnCnjqBfw@mail.gmail.com>
To: sframe@ietf.org
Content-Type: multipart/alternative; boundary="0000000000005d368506085253d1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/biRQXoT70ddqy_YCqPMHsIMNgKc>
Subject: [Sframe] Fwd: New Version Notification for draft-ietf-sframe-enc-04.txt
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Secure Media Frames <sframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sframe>, <mailto:sframe-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sframe/>
List-Post: <mailto:sframe@ietf.org>
List-Help: <mailto:sframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sframe>, <mailto:sframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Oct 2023 18:32:40 -0000

Dear SFrame WG,

This latest version reflects the discussion at the last interim, which
closed out all remaining issues.

Chairs: I believe this version is ready for WGLC.

Best,
--Richard

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Sun, Oct 22, 2023 at 2:31 PM
Subject: New Version Notification for draft-ietf-sframe-enc-04.txt
To: Richard L. Barnes <rlb@ipv.sx>, Emad Omara <eomara@apple.com>, Justin
Uberti <juberti@google.com>, Sergio Garcia Murillo <
sergio.garcia.murillo@cosmosoftware.io>, Youenn Fablet <youenn@apple.com>


A new version of Internet-Draft draft-ietf-sframe-enc-04.txt has been
successfully submitted by Richard Barnes and posted to the
IETF repository.

Name:     draft-ietf-sframe-enc
Revision: 04
Title:    Secure Frame (SFrame)
Date:     2023-10-22
Group:    sframe
Pages:    64
URL:      https://www.ietf.org/archive/id/draft-ietf-sframe-enc-04.txt
Status:   https://datatracker.ietf.org/doc/draft-ietf-sframe-enc/
HTML:     https://www.ietf.org/archive/id/draft-ietf-sframe-enc-04.html
HTMLized: https://datatracker.ietf.org/doc/html/draft-ietf-sframe-enc
Diff:     https://author-tools.ietf.org/iddiff?url2=draft-ietf-sframe-enc-04

Abstract:

   This document describes the Secure Frame (SFrame) end-to-end
   encryption and authentication mechanism for media frames in a
   multiparty conference call, in which central media servers (selective
   forwarding units or SFUs) can access the media metadata needed to
   make forwarding decisions without having access to the actual media.

   The proposed mechanism differs from the Secure Real-Time Protocol
   (SRTP) in that it is independent of RTP (thus compatible with non-RTP
   media transport) and can be applied to whole media frames in order to
   be more bandwidth efficient.



The IETF Secretariat