[AVTCORE] RFC 8088 and draft-ietf-avtcore-rtp-sframe

Bernard Aboba <bernard.aboba@gmail.com> Tue, 14 November 2023 04:34 UTC

Return-Path: <bernard.aboba@gmail.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 97419C15108C for <avt@ietfa.amsl.com>; Mon, 13 Nov 2023 20:34:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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, 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 uN_eRUuKszhB for <avt@ietfa.amsl.com>; Mon, 13 Nov 2023 20:33:59 -0800 (PST)
Received: from mail-pf1-x42b.google.com (mail-pf1-x42b.google.com [IPv6:2607:f8b0:4864:20::42b]) (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 C26B3C14F748 for <avt@ietf.org>; Mon, 13 Nov 2023 20:33:59 -0800 (PST)
Received: by mail-pf1-x42b.google.com with SMTP id d2e1a72fcca58-6c431ca7826so4429051b3a.0 for <avt@ietf.org>; Mon, 13 Nov 2023 20:33:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699936439; x=1700541239; darn=ietf.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=RchcymwgUGLbAbtf6I42PgDacvGvIwA3NqB2KqNsXBs=; b=hDk464/QBpYK3OTjbVQswUUQQoNBEJoRvBsK9YDDA//LHRRX5G4pqlpJpC9De4gmb9 nAQpy45jo7yMGkR7Ec216orYa6eBZPIIFtvMPz3bbXGT2t22uTX9aroSYpldm8HFAtGD 6qPRkNEU9vM3eUfGADz4u0OBWUmhvhaOlafOp6MJjbUC4VuGOCV2s0/6z7DhDeJW3BtU 0ShK6GcBSV079YI4n/yobB0Ma6ZBX5SYy0ppdoaJv3af73U9jaQui+ZHJ8CWSiYFg7Ax MxvS5+sKEuBCmJHkUEGFE/C8oP2OwCLKQ/FskNuXeWrIMDCZ+QeKnXFFGSl4KAdgXqNn upqQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699936439; x=1700541239; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=RchcymwgUGLbAbtf6I42PgDacvGvIwA3NqB2KqNsXBs=; b=ioBGoX25xKCszuAPTaB66/+Kqn6rq0RR8ql61HroaGR5dlRPXwvgGUBzSY1rJguF8o bseFdSm5/NzBksfo90Vpz3sPaas782FSqoAAoNrtW+hbBIUP8hWySeSIEPbcHZkJlXQu P/9p15KCPVzhAKmrSzplEaqPXIlQLEKexOmBfiRSSYfwlGnJXVgoxLdUl1JcH6MQ9BCW zR8t6707pqLtbc7VUNOsxCVyghJgJszhRR/s+t6k8HKowQmB0CZPkX5DVFQst5MmUBIo f/3sCmr+SdG1mE3bWejhtceG6YxZo8AHnhdupn43Gty5nvlclaZ0QzIt5ktG2bLWe69L TVNw==
X-Gm-Message-State: AOJu0YzTJC5XhsGQiwaJ+6erKXAg+YOL8wd9NsO4qocsO5w/1CGu5QCF fOlC717aU4oy1fhLDaCjRJS1tMSGPO876+SVWmo1ZDRPB/m5cQ==
X-Google-Smtp-Source: AGHT+IF+hK4ozKc2mBRlDeEEzZ6OBIfF5cQDx7zi5/EJuasqeOgWj87Klg1Um7VFyhprsNO+1NrQR5yCbKrUUTiRWNM=
X-Received: by 2002:a05:6a20:441f:b0:186:7509:7f62 with SMTP id ce31-20020a056a20441f00b0018675097f62mr4706049pzb.28.1699936438851; Mon, 13 Nov 2023 20:33:58 -0800 (PST)
MIME-Version: 1.0
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Mon, 13 Nov 2023 20:33:48 -0800
Message-ID: <CAOW+2dux-9hHr6eNTxOUgSfXr_Lca-sZoRRK=i_8XxTNA8rRpA@mail.gmail.com>
To: IETF AVTCore WG <avt@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000941b8c060a154b97"
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/dqlKqyLbo36L16-B0-k7l4e_G0U>
Subject: [AVTCORE] RFC 8088 and draft-ietf-avtcore-rtp-sframe
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 14 Nov 2023 04:34:03 -0000

This draft is attempting to provide an RTP payload format for SFrame, which
provides for E2E encryption of RTP payloads.  As such, readers (including
the IESG) will expect it to conform to RFC 8088 "How to Write an RTP
Payload Format".

https://imgflip.com/i/85y9ko

So you should expect the IESG to ask many of the same questions asked of
the SCIP RTP payload format, and to expect them to be answered in the
document. Some of the questions you might expect include:

Packetization/depacketization

Details of the packetization/depacketization process, answering questions
like:
a. Does the SFrame packetizer or depacketizer need to parse SFrame? If so,
will the packetizer/depacketizer need to be revised if the SFrame format
changes?
b.Does the packetizer/depacketizer need to keep track of the state of
SFrame key negotiation?

SDP
How is Sframe negotiated in SDP? What profiles are used?  What are the
associated SDP parameters? What are the requirements for SBCs to pass Frame
over RTP through without causing problems?

Transport
Can SFrame be negotiated along with RTP/RTCP mux and BUNDLE?

Security Considerations

What are the SFrame security services provided for RTP and RTCP?

What attacks are prevented by using SRTP (e.g. SAVP and SAVPF profiles) and
cryptex in addition to SFrame?