Re: [AVTCORE] Multi-party real-time text requiring new RTP payload type Wed, 06 May 2020 02:41 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BE4743A0CFD for <>; Tue, 5 May 2020 19:41:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.639
X-Spam-Status: No, score=-1.639 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id OroBxEoxdPpq for <>; Tue, 5 May 2020 19:41:09 -0700 (PDT)
Received: from ( [IPv6:2001:558:fe21:29:69:252:207:36]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 656873A0CB5 for <>; Tue, 5 May 2020 19:41:09 -0700 (PDT)
Received: from ([]) by with ESMTP id W9sfjG3toEK7sW9zgjHzck; Wed, 06 May 2020 02:41:08 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20180828_2048; t=1588732868; bh=GhMNpOl9GRuII7FK1oys0mXduxXhnGfh9ewX6w6MBM0=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID; b=WsBq5DfhgRes+j1kRZmfmj/BLHnS4sVphy2CQacWWH1pH1fSIU80FB9hDAXxvnOyR fTM2PVvjHlQHIvnub7WYvoa8YIhE8+Cfq3Ul6F1F4abNWnhQijJsQ0Xw8JQVLo6vjo +qI6g2Vcl6ZheEOoNdCIu2yDWhQHSrBhgORYfOYlRFna00i9Y+pefr443TEbbe3WA5 RpOr88WRNvCfkx+/lzzAwKApCO8AHKAPdd5twLunQcskNDjCrjrm9HzI4q8PeNV1D1 lt6/4BkzsrZhik6fI8WAbdS6R/wue/h/C4EbCRK8nlc/BeJ4TC1wBiVxGOYHlznOFy TkxwK109/E2Fw==
Received: from ([IPv6:2601:192:4a00:430:222:fbff:fe91:d396]) by with ESMTPA id W9zRjFj9v8WWMW9zejGkdw; Wed, 06 May 2020 02:41:07 +0000
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id 0462erkf014034; Tue, 5 May 2020 22:40:53 -0400
Received: (from worley@localhost) by (8.14.7/8.14.7/Submit) id 0462eqw2014019; Tue, 5 May 2020 22:40:52 -0400
X-Authentication-Warning: worley set sender to using -f
To: Gunnar Hellström <>
In-Reply-To: <> (
Date: Tue, 05 May 2020 22:40:51 -0400
Message-ID: <>
Archived-At: <>
Subject: Re: [AVTCORE] Multi-party real-time text requiring new RTP payload type
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Audio/Video Transport Core Maintenance <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 06 May 2020 02:41:11 -0000

Gunnar Hellstr\"om <> writes:
> I propose to add the following last in the introduction:
> -------
> 1.1.  Considered alternative
>     The mechanism specified in the present document makes use of the RTP
>     mixer model specified in [RFC3550].  From some points of view, use of
>     the RTP translator model specified in RFC 3550 would be more
>     efficient, because the text packets can pass the translator with only
>     minor modification.  However, there is no widely supported sdp
>     [RFC4566] specification for the translator model.

It doesn't seem to be that lack of an SDP specification for a
translatory would be needed, but I suspect that's due to my lack of
knowledge of the practical problems involved -- as far as I can tell,
such a connection could be negotiated in the ordinary way, and the fact
that the packets' SSRCs vary would identify that there were various
sources interleaved.

Though given that some protocol action will be necessary anyway (e.g.,
defining a new payload type), would it be difficult to invent an SDP
attribute that means "multiple sources will be interleaved, check the