[AVTCORE] RTP Header Encryption
Justin Uberti <juberti@google.com> Thu, 30 July 2020 06:12 UTC
Return-Path: <juberti@google.com>
X-Original-To: avt@ietfa.amsl.com
Delivered-To: avt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DF1F3A0E5B for <avt@ietfa.amsl.com>; Wed, 29 Jul 2020 23:12:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.6
X-Spam-Level:
X-Spam-Status: No, score=-17.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 zm164QY-F_4E for <avt@ietfa.amsl.com>; Wed, 29 Jul 2020 23:12:31 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 1ED183A0E5D for <avt@ietf.org>; Wed, 29 Jul 2020 23:12:30 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id l1so27074094ioh.5 for <avt@ietf.org>; Wed, 29 Jul 2020 23:12:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=xNGldhDD0t0CqxyNgXK78b5iBDmxoseMcpq06QKYmrA=; b=HWWkLdSvrBwP3v+zU81ObSes8bMjk6IPzYNqkCslBwgkF0yzuND4WGJ1F9pT6yXrrs tgkrRDnQCm+4tn6nIHXpP+3oFQ9ltJ9VZHUto9oGAP4un+l+tCELUvdCXMm7HMhL2w4q 9gPEfFc98RiZ27Jb5gV92gQF4PREOxLxfLrdbDiAbiMGuDhvatZFF+umRsyCH9XHOBN2 s9rP7C5XdFzsfaYvI3POpeaYoSDhahp4uot3pd/fHfRpnHmoqI6JsoFrDcri7U1coffK SZigsP2mYOpbBNeYFkDhtU4oLiTBuCR2yj+AaokIc+yPi1ot3SavRlOqOFE4Kvm8q857 SqmQ==
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=xNGldhDD0t0CqxyNgXK78b5iBDmxoseMcpq06QKYmrA=; b=NoWqNlg1wd1YNIfpExafnNoBIWTiEcIIh8pDpStWxRPGebYll71Efe9xoVM2jgmgPR msbMqAgB97n1ClZ+2hHEDQNu+h4IJe760mCJBS0AUJBdWWVEbUoHYyPnQoOna+0YUbe6 t8EZ2qUOS3v8Jyl2GBTL+TlsLzSRRNBgrRiBJTd1KlJWV2Ura6fRdS5K5Vp2myHmINCo FKAGSMoOCu58orNE0f380tnHbUXCQa57Oj5opPMBImxZg4uWplPZH9g/IU8KJg3Hx99d 9FO7HEWCgJ1ewCnqRdPAVjw9B+x0ytLRF6rA3086LRJCfETS0FrxMhYRjQJwyndySjrc 1bJA==
X-Gm-Message-State: AOAM532cTbqwFRaIHfXOlzOmnyq1+wSc/ZVtZOLXKuwNQI36HKFdNtkv KrZZJsIhO6UB4mJFd+bgfIrYR6Kv77oX2hM4/Qwbpn5nOks3gA==
X-Google-Smtp-Source: ABdhPJwAlQqySjsMat+6NtFLhbf1wk0AcRFDi81ii48O3BIpQA9GStBVfvB8ADyaY+HmwToAYzyWNaKJga/mkWvaxN0=
X-Received: by 2002:a5d:8552:: with SMTP id b18mr37239307ios.28.1596089549596; Wed, 29 Jul 2020 23:12:29 -0700 (PDT)
MIME-Version: 1.0
From: Justin Uberti <juberti@google.com>
Date: Wed, 29 Jul 2020 23:12:18 -0700
Message-ID: <CAOJ7v-1sY_xS3GkY4MtyYvfJbi=XZWVhz+ZywXeEV8o5w-ZjYw@mail.gmail.com>
To: avt@ietf.org
Content-Type: multipart/alternative; boundary="000000000000a2995905aba28eaa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/M-WyBlSBxupL38H32ULobq7Iebc>
Subject: [AVTCORE] RTP Header Encryption
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/avt/>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Jul 2020 06:12:33 -0000
While investigating some issues with libwebrtc's implementation of RFC 6904 header encryption, I noted it is a fairly complex mechanism, which perhaps partially explains why it hasn't yet seen widespread adoption. I do think encrypting RTP header extensions in modern communications apps would be a Good Thing, and a few of us have put together some ideas on how we could improve things here. We'll discuss briefly in Thursday's AVTCORE meeting, but if you're interested in this topic, please join us at 1600 UTC for a longer discussion at https://meet.google.com/awy-bndk-pgi. For more details, see the slides <https://drive.google.com/file/d/1VtOLrBsoFvmJCuBXaXGQKyzBzWqna3sk/view?usp=sharing> for the discussion. Justin
- [AVTCORE] RTP Header Encryption Justin Uberti