Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix Issue 1: transport

Brian Rosen <br@brianrosen.net> Mon, 18 May 2020 15:35 UTC

Return-Path: <br@brianrosen.net>
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 0DB703A079A for <avt@ietfa.amsl.com>; Mon, 18 May 2020 08:35:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.012
X-Spam-Level:
X-Spam-Status: No, score=0.012 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=brianrosen-net.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 DqSrmpbLgQQM for <avt@ietfa.amsl.com>; Mon, 18 May 2020 08:35:12 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 CD0FF3A07E9 for <avt@ietf.org>; Mon, 18 May 2020 08:35:11 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id m11so10519307qka.4 for <avt@ietf.org>; Mon, 18 May 2020 08:35:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brianrosen-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XqYbyDGk+DAcVtPF6VeohBuUpfGL5WXbb1XkozcllSY=; b=SX4dDrFPa9PrmyWFwni4jEJdRaNLypvZTv7B8A6F4hkbK62XbjTSLT0Ub+akWI9GtI 05xKGk0pBAcH/jVOnOWmK4XPvOK0lyvLaHVPD3q6u5zYHU3SPXpCFDPKYSRGshA8vpkI LxT1I+sLCIO6IyU4h2TBJMVzfuBYRVceRALvHeZwoCSmg6oVdQWmqkObcLn/iKJLZyIZ bj7naUBqhgc2kDQHLHqimsfpEfLcNK6ES3gqQ/iY04C+xDUT+0nvLbhqv44wrjtiLAye 8ONvE/BCa/P0vo6Bw0CbKMssLEp13Wj1UKWIq+vR8tP5WP1yaBQK9XMSY6eAqhNbNgCN NAHA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=XqYbyDGk+DAcVtPF6VeohBuUpfGL5WXbb1XkozcllSY=; b=J8vL/3tVasVkFB9uNOWYbyspGXLvryVsLRfnQQLVHmvFVt4tWChATZSWR7gg7/Dg1Q sv5/gk1bdEC3SFfmaWhbeh+CEzouC08b3HVNE6xc/tGWnws2wtZcfoWt6ZzcKtEZGkWg KnQ69WnBSVKQimfne745LTzX694rLbK+5Xde7jNDtnnYzE5xUkxda9KGSKIsLsK2GnYG gGqLzBoCU5lOV1rZT9u769M3KocOVMtj/sbP64EXbY1HtokN0PJWMBg5XBOe3Y3U4ZJE /Aaq4w23jfSiPPx3gAXnA8+hV/ecBFKGv220+MPm4EMCDqrBHIApMt4/GZgdksDzKdJS RsRA==
X-Gm-Message-State: AOAM533wWzroy3/Ueuegj6CgKj90xS8NBkmwfcOqAfQkpLQWCe5DQQfU Eowia0PQ/nxr7uoD+GYL7ZTUchyuqmM=
X-Google-Smtp-Source: ABdhPJwol6cExuspQg1cC1Pyte4SGcHOQOgqqEXfn2DzEdK6pViT2DRmG5x21mziJjj07WNAj+3/fA==
X-Received: by 2002:a37:414f:: with SMTP id o76mr1919996qka.375.1589816110815; Mon, 18 May 2020 08:35:10 -0700 (PDT)
Received: from brians-mbp-2871.lan (dynamic-acs-24-154-119-158.zoominternet.net. [24.154.119.158]) by smtp.gmail.com with ESMTPSA id l133sm8571677qke.105.2020.05.18.08.35.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 May 2020 08:35:10 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
From: Brian Rosen <br@brianrosen.net>
In-Reply-To: <DC445046-4F9A-48AA-9192-6430B6FBEF4C@gmail.com>
Date: Mon, 18 May 2020 11:35:08 -0400
Cc: =?utf-8?Q?Gunnar_Hellstr=C3=B6m?= <gunnar.hellstrom@ghaccess.se>, avt@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <0112D996-221B-4B2F-9647-A6CCBF0F3B4C@brianrosen.net>
References: <46CB285F-C49A-4910-B9B1-667AB1AE4538@brianrosen.net> <DC445046-4F9A-48AA-9192-6430B6FBEF4C@gmail.com>
To: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/avt/2XiQJM6DyqcK5vQOG32pvrMumE4>
Subject: Re: [AVTCORE] draft-ietf-avtcore-multi-party-rtt-mix Issue 1: transport
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: Mon, 18 May 2020 15:35:14 -0000

I think this means we use the WebRTC data channel, which is HTTP based, right?  Totally bypasses the SBC.  Have to be careful to not cause the SBC to get confused with the SDP.

Middle box triumph, again.

Brian

> On May 18, 2020, at 11:24 AM, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> 
> lOn May 18, 2020, at 8:09 AM, Brian Rosen <br@brianrosen.net> wrote:
>> 
>> It occurs to me that the SBC may not pass text/red.  Depends on how picky they are.  Text/red is basic T.140.
> 
> [BA] Legacy SBCs are indeed an issue, and a basic obstacle to deployment of RTT. I am not aware of any SIP trunk providers that support text/red, because they would need to upgrade their SBCs to do so, which would be a large cost, with no corresponding revenue source.