I-D Action: draft-ietf-avtcore-rtp-scip-08.txt

internet-drafts@ietf.org Thu, 01 February 2024 21:18 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Cc: avt@ietf.org
Subject: I-D Action: draft-ietf-avtcore-rtp-scip-08.txt
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: avt@ietf.org
Message-ID: <170682233990.49986.5559828270084192366@ietfa.amsl.com>
Date: Thu, 01 Feb 2024 13:18:59 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/i-d-announce/a34_XdPpBRvqPyDrEkgZ9a218lQ>

Internet-Draft draft-ietf-avtcore-rtp-scip-08.txt is now available. It is a
work item of the Audio/Video Transport Core Maintenance (AVTCORE) WG of the
IETF.

   Title:   RTP Payload Format for the Secure Communication Interoperability Protocol (SCIP) Codec
   Authors: Daniel Hanson
            Michael Faller
            Keith Maver
   Name:    draft-ietf-avtcore-rtp-scip-08.txt
   Pages:   18
   Dates:   2024-02-01

Abstract:

   This document describes the RTP payload format of the Secure
   Communication Interoperability Protocol (SCIP).  SCIP is an
   application layer protocol that provides end-to-end capability
   exchange, packetization/de-packetization of media, reliable
   transport, and security services such as confidentiality and
   integrity protection.

   SCIP handles packetization/de-packetization of the encrypted media
   and acts as a tunneling protocol, treating SCIP payloads as opaque
   octets to be encapsulated within RTP payloads prior to transmission
   or decapsulated on reception.  SCIP payloads are sized to fit within
   the maximum transmission unit (MTU) when transported over RTP thereby
   avoiding fragmentation.

   SCIP provides confidentiality and integrity of the tunneled media,
   therefore the SCIP payload does not require the use of Secure RTP
   (SRTP) for payload protection.  SCIP also provides for reliable
   transport at the application layer, so it is not necessary to
   negotiate RTCP retransmission capabilities.

   To establish reliable communications using SCIP over RTP, it is
   important that middle boxes avoid parsing or modifying SCIP payloads.
   Because SCIP payloads are confidentiality and integrity protected and
   are only decipherable by the originating and receiving SCIP devices,
   modification of the payload by middle boxes would be detected as an
   integrity failure in SCIP devices, resulting in retransmission and/or
   communication failure.  Middle boxes do not need to parse the SCIP
   payloads to correctly transport them.  Not only is parsing
   unnecessary to tunnel/detunnel SCIP within RTP, but the parsing and
   filtering of SCIP payloads by middle boxes would likely lead to
   ossification of the evolving SCIP protocol.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-ietf-avtcore-rtp-scip/

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-avtcore-rtp-scip-08

A diff from the previous version is available at:
https://author-tools.ietf.org/iddiff?url2=draft-ietf-avtcore-rtp-scip-08

Internet-Drafts are also available by rsync at:
rsync.ietf.org::internet-drafts

I-D Action: draft-ietf-avtcore-rtp-scip-08.txt internet-drafts