[Sframe] Proposal: SFrame && SPacket && !SIDU

Richard Barnes <rlb@ipv.sx> Thu, 02 September 2021 20:20 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 24B053A0A8E for <sframe@ietfa.amsl.com>; Thu, 2 Sep 2021 13:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ipv-sx.20150623.gappssmtp.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 Y2RYbiCnGjD9 for <sframe@ietfa.amsl.com>; Thu, 2 Sep 2021 13:20:33 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (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 8D0F43A0A71 for <sframe@ietf.org>; Thu, 2 Sep 2021 13:20:33 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id p17so1941408qvo.8 for <sframe@ietf.org>; Thu, 02 Sep 2021 13:20:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ipv-sx.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=lnnS5yGUKzoU/5F8J05FNLQcemUqz7gTkXqyNqAxv/0=; b=NUc4vcPRaT1T8JBwTom74hq5XusxzBvo5/ROW/utU+UVeSD2QD1+QtHPGmHUP/RewJ dRRLO06i/4pl/AWmQ8YqIDCBBYrc9CbUM8+L42Qfz1gHYEW+57TJtEYpk+uqfp9YdVo5 nYM+UykGXrTLWPOukvUh8uFJwpBx7aNyDYfyT3tT+pac+xjrevYiaNmLCrOlF0raLkiW adfjViBFg+Rx9tdBiAYbapIY+bGlWD6GLkChT59q/eW6z832tWxQl35VexrG6kUdTRsA EiaQ6ygrTMigsq5wvKc1ItR3QmfcAybCJOOsS21bv0hi48LN96sKKAP9u+VliZbrJDDr /PnQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lnnS5yGUKzoU/5F8J05FNLQcemUqz7gTkXqyNqAxv/0=; b=KfeRC+25P2xS1ZqPQV0bEhK7ER0AKKdANZSb6YfXBKw/Qu884CbVoAV9YcmcAGqGly L3JtjuUL3JMfnVRoCKOH6ru7xshDE27wJN7ymyi4RtLjN2dl00LnAWFbBxp2Zg8Ybf5h eyPA5/Vu77UPDT7IBfqxBCROhf35abqpnDU6yQrd59aVf1lapA+Xl7gWbF1TDj5gv8R9 h14TcLA7vEteFPcYeQwAOLywSzgYfuM4wfJW2Rp5DfgOtxj3Tgv7nCi1XJ2ROGLwJtma iFruBGTEwJjcT1vv0JGRmmVy8I3Tt+ysgw88dJfHfVRnl+6bh095imUrjyOyNiQ2jWBR +KdQ==
X-Gm-Message-State: AOAM533pBe9tIBRIebfU3rL8H9m3Pv8fNVyogrnnQOFgKgdkDYyRarEW ixu5+XTzwSnf1aS/KNPfHobQ0aMyAEq5lPYjfRVp+ZXYumOUbg==
X-Google-Smtp-Source: ABdhPJzMprxG7+jSk1pHCHMzwxhGoShJQrklXg0QmzyLYV/m+VeOrYCdJHD4ajl21xEjlnZ3uhQYnvuEExzFyVNxFQ8=
X-Received: by 2002:ad4:46f0:: with SMTP id h16mr118467qvw.0.1630614030627; Thu, 02 Sep 2021 13:20:30 -0700 (PDT)
MIME-Version: 1.0
From: Richard Barnes <rlb@ipv.sx>
Date: Thu, 02 Sep 2021 16:20:18 -0400
Message-ID: <CAL02cgSytJSLPziTzTOAQZFke47YrhdS381b4OmqcMPM1=Nzbw@mail.gmail.com>
To: sframe@ietf.org
Content-Type: multipart/alternative; boundary="0000000000000fc44205cb08ea53"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sframe/vlVBbep8UiWV4t7SBuDOeCeDDDI>
Subject: [Sframe] Proposal: SFrame && SPacket && !SIDU
X-BeenThere: sframe@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 02 Sep 2021 20:20:35 -0000

Hi folks,

I'd like to see if we can agree to limit our scope a bit.  There has been
discussion of multiple levels at which SFrame could be applied:

* "SFrame" - Whole media frames
* "SPacket" - Individual RTP media payloads
* "SIDU" - Some codec-specific "independently decodeable units"

I'd like to propose that we take "SIDU" off of the table, but keep the
other two.

It seems like SFrame and SPacket both have strengths in certain scenarios
(depending on how you want to trade off bandwidth vs. complexity), but
they're both pretty straightforward in terms of how they integrate with the
media processing pipeline.  In particular, they don't have any
codec-dependence.  SIDU, by contrast, seems like a world of pain.  It
requires that the encryption scheme be entangled with the codec, which
requires special per-codec integration logic in the specifications.  And
the bandwidth gains for all that complexity are not that large.

Is there anyone here who feels that SIDU is something this group needs to
spend time specifying?

--Richard