IETF Logo Mail Archive

Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below

"Cullen Jennings (fluffy)" <fluffy@cisco.com> Wed, 19 February 2020 15:57 UTC

Return-Path: <fluffy@cisco.com>
X-Original-To: v3@ietfa.amsl.com
Delivered-To: v3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF26A12021D for <v3@ietfa.amsl.com>; Wed, 19 Feb 2020 07:57:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=FPohWijZ; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=CGrtYebH
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 dq9Gsk5e0HzC for <v3@ietfa.amsl.com>; Wed, 19 Feb 2020 07:57:25 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C9AD120820 for <v3@ietf.org>; Wed, 19 Feb 2020 07:57:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1992; q=dns/txt; s=iport; t=1582127845; x=1583337445; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=HIUKgMiS+Rl2oCNHYIsqrSrXgZvhpFd+VCpQ+gQnHME=; b=FPohWijZAQ9HP0nbnxJly/G3Pk0RHzTdt4cykzfpLSpnHOvcfPi9tNJh Cka74v+jPD8YtWA4Q69R6Ml7mfB5FJ0PTEeS5Qa/w92lG3w0bECqWrxGK icYFRNI2nHZVvWsX0opbP4rLoI70K7Jl6l4yZ6hY87gi8arrhLPivkN9L c=;
IronPort-PHdr: 9a23:bKhRtRK4EqLJUftDPdmcpTVXNCE6p7X5OBIU4ZM7irVIN76u5InmIFeCtKd2lFGcW4Ld5roEkOfQv636EU04qZea+DFnEtRXUgMdz8AfngguGsmAXEP/MfDkfgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CgBQA3Wk1e/5hdJa1mHAEBAQEBBwEBEQEEBAEBgXuBVCQFJwWBRCAECyoKhAqDRgOKcYI6JZgRglIDVAkBAQEMAQEtAgQBAYRAAheBbSQ4EwIDDQEBBQEBAQIBBQRthTcMhWYBAQEBAgESEREMAQE3AQQLAgEIGAICJgICAjAVEAEBBA4FIoMEgksDDiABonUCgTmIYnWBMoJ/AQEFhTsYggwJgQ4qjCQaggCBEScMFIIeLj6BBINGAYMQMoIskGOfMgqCO5ZgHJsrhEaiPIMyAgQCBAUCDgEBBYFpIoFYcBVlAYJBPhIYDY4dGIEPAQmCQopTdIEpjFoBgQ8BAQ
X-IronPort-AV: E=Sophos;i="5.70,461,1574121600"; d="scan'208";a="727570367"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rcdn-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 19 Feb 2020 15:57:24 +0000
Received: from XCH-ALN-003.cisco.com (xch-aln-003.cisco.com [173.36.7.13]) by rcdn-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 01JFvN5O024207 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 19 Feb 2020 15:57:24 GMT
Received: from xhs-aln-003.cisco.com (173.37.135.120) by XCH-ALN-003.cisco.com (173.36.7.13) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:57:23 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 19 Feb 2020 09:57:22 -0600
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 19 Feb 2020 09:57:22 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DYInEZO0C9sR10QuQbjL+8AVbA8qGfqOju6OvdNW6lA+5AZBvuCFhjrIYcWS3GLIesVtS92KXdcGk47UvqU8IdYa8C0jaInO0ozP/2QG+KJJhXWuFTfvfXuB8jPhWvV/GWe7RuRb2LTcpSMXBPHy6K4JrPPiEOADJM5dHzcBWwtr1ebYxmGuvGWtsVhm8QUsPVtKSO/rE5FPLo5Wj82t1y5gFMCnPFyNlEA0zCiTK9jS0GNKzWyKuFXy9hmd/oEwQOSLsoneI1e0/QYAhtdhwB3O850Dss2g0vv2Zi1jMwgLvGRqecMKKUCaofcwa9xF/qpGcqDNTxdx5Fc7tZ6ALA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HIUKgMiS+Rl2oCNHYIsqrSrXgZvhpFd+VCpQ+gQnHME=; b=SCedzlZeQE6RStCNWLDP4M5JU2QSjrQ+ybcndq9Pxe7Nwm7ciGyjgLeDdaTJsabEXfAScucFZHt50WCeNT81w5OLkgwzsyelObSOT7sx5CR3qMBOUANdek6KN8TrQ3PQRIeHmMGuFWN3/SLzxOS+rAsQ2qYbUISonctZDzh54VGJQtxTjL9tAcSrm33gJIQYfuVB0jutyzYUPg4lQywcfUN4pxjJPmG82GrkHL7ka4og0+YyKxqlfMfhNrucwRP7aNg1gk2Lysnud15L0l6WgZT0laZ+z+bCJ4DD+s8gbtNSsYa1yQuMrT89FrbfkstrHH40q4VhdcPPfOnLCsmcbw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=HIUKgMiS+Rl2oCNHYIsqrSrXgZvhpFd+VCpQ+gQnHME=; b=CGrtYebH/Un0baemeudLNXltzFptohoYWEi5eaXqbcYwAnUEVL3xU50MX27ZcfJ1hhpdfN7wV/2TBkCd/hNVnMgWeUa+VKzNqAyOxOd823VAX+gWm7YW4shQbZoQFgLCGJMRUBk0Rn4ga68NdpwnGVvcEiT+3/Koz95e+KREW94=
Received: from CY4PR11MB0056.namprd11.prod.outlook.com (10.165.88.30) by CY4PR11MB1925.namprd11.prod.outlook.com (10.175.82.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.17; Wed, 19 Feb 2020 15:57:21 +0000
Received: from CY4PR11MB0056.namprd11.prod.outlook.com ([fe80::f9f2:aca9:b3a7:4c7e]) by CY4PR11MB0056.namprd11.prod.outlook.com ([fe80::f9f2:aca9:b3a7:4c7e%7]) with mapi id 15.20.2729.032; Wed, 19 Feb 2020 15:57:21 +0000
From: "Cullen Jennings (fluffy)" <fluffy@cisco.com>
To: Ross Finlayson <finlayson@live555.com>
CC: "v3@ietf.org" <v3@ietf.org>, Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Jonathan Rosenberg <jdrosen@five9.com>, Jonathan Rosenberg <jdrosen@jdrosen.net>
Thread-Topic: [V3] RIPT BoF approved for IETF 107 - Draft charter below
Thread-Index: AdXjgeGz8imU79X0QTWjBiq5oM7qsgAEGIgAAACwSIAADAjQAADeBrEA
Date: Wed, 19 Feb 2020 15:57:21 +0000
Message-ID: <DF3A5713-AF43-4399-B464-76E48AABF6E7@cisco.com>
References: <BYAPR06MB43914433BF91CE216E6123A6FB150@BYAPR06MB4391.namprd06.prod.outlook.com> <CAKKJt-eKB4wxqK8Xiho2tYaqpM3_fjQYsjJh5-cf_RWd6iR8sQ@mail.gmail.com> <CA+23+fGNO86ii6q0hd3aiSdib2AT-iu3O+DmgGJXTFbFkGxLnQ@mail.gmail.com> <F72DFB60-1BA3-4CD3-9DB2-DF986F3729DE@live555.com>
In-Reply-To: <F72DFB60-1BA3-4CD3-9DB2-DF986F3729DE@live555.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=fluffy@cisco.com;
x-originating-ip: [128.107.241.172]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: d7c663b3-d803-4651-7322-08d7b5546788
x-ms-traffictypediagnostic: CY4PR11MB1925:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <CY4PR11MB1925A622FF99E268A813068FC6100@CY4PR11MB1925.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0318501FAE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(39860400002)(346002)(366004)(396003)(136003)(376002)(189003)(199004)(478600001)(66556008)(33656002)(2906002)(86362001)(5660300002)(64756008)(66946007)(66476007)(66446008)(53546011)(6506007)(91956017)(186003)(76116006)(2616005)(26005)(6486002)(71200400001)(8676002)(8936002)(6916009)(81166006)(36756003)(81156014)(6512007)(316002)(4326008)(54906003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1925; H:CY4PR11MB0056.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: //4U3lKoEu+runo6g60IRC++3vXvIMbVPPrM+UVQbL1SngGo0BcW8pIsSzga0+NS/DtZ2pcfr7MkuX8cLvrHJ5f86Fgml8X4uGqXOFwiaDyHQCPUU5q2E1pyF2GpOeM/hGIkFs/92T6FYvmvwArIubaoOODF3Z3ln/pRrijLDTLO0j9N3bg6F5yX/5/MG/v7xgpMcIIVVJb0S3qAewt0aUUPWhT4RMj9+SlvOWYI5PE28owfOvp3F9ItxT0n0LSjrubF3xZkicsho5xISBmOUSHmEIdd08HuSYmS56SO8safLdomlZU6cw770l3Aj2oOvCdYjcYIbfIZk7mJ0ziSehKh704YHSdwqsgIsvZbZy1l0Tfr+3LwV4pEdZvhPuFEqkc17oV1y61/iSveKsMKCTKLc70qncGZEiS5tPoCKf8Ga006uD9Mi5jd7OycgZwz
x-ms-exchange-antispam-messagedata: GYPLAnvZric0GaJXikMnIPk/pMZ12e2PjaTCQcqGqWZuYo++bXrleV/UwXY2+7PPWMZUZX4y+EzmnbuwQWYCaUsmVuNN7nr1+itiYzxEJZrm3Okot9mRRMLxWR2gid2sRdAotTQUopsQPqSKmJEHpA==
Content-Type: text/plain; charset="utf-8"
Content-ID: <4F81F01914127F4ABAE8E8A8E386D147@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: d7c663b3-d803-4651-7322-08d7b5546788
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Feb 2020 15:57:21.3651 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: HbckmNN/w+KBUF3tJmMZ/rXoTqoYWfZd/oQc7jeFwY08A84ZXctw8ududmMwMCBZndenZ/6OpcMgDlQoMeypFg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1925
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.13, xch-aln-003.cisco.com
X-Outbound-Node: rcdn-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v3/f7KqC4KnGjtIT34kpiFTIEnrInU>
Subject: Re: [V3] RIPT BoF approved for IETF 107 - Draft charter below
X-BeenThere: v3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <v3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v3>, <mailto:v3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v3/>
List-Post: <mailto:v3@ietf.org>
List-Help: <mailto:v3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v3>, <mailto:v3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Feb 2020 15:57:34 -0000


> On Feb 14, 2020, at 10:00 PM, Ross Finlayson <finlayson@live555.com> wrote:
> 
> If we want to get something standardized/working quickly, then this is a ’no brainer’, IMHO.  First, define a way to carry RTP/RTCP packets directly in QUIC datagrams - in such a way that the existing RTP payload format defined for each media type could map directly (i.e., with no more media-specific IETF standardization work required).  Even if this means that there's some duplication of functionality between RTP and QUIC (datagrams).  (Ditto for RTP over QUIC (reliable) streams.)
> 
> While - at some point in the future - it may be worthwhile defining a new version (v3?) of RTP that works more efficiently with QUIC, this should not be something that we require before we define/standardize a replacement for SIP.  Otherwise it’ll be years before we’re done.  (RTP is starting to show its age, but it’s not broken, and has lots of existing deployment that could, ideally, be leveraged quickly within a SIP replacement.

Almost no modern RTP implementation actually does the full RTP spec so at the very least we need some serious subsetting of what part of RTP would be mapped to QUIC. The RTP extension mechanism is badly broken particularly for low bandwidth satellite links. And if you look at what RTP clients do with the RTCP sent to them, well, I think there is some house cleaning needed here to be able to actually use RTP /RTCP.

v2.23.0 | Report a Bug | By Email