Re: [rmcat] How to handle remaining milestones

Colin Perkins <csp@csperkins.org> Thu, 21 November 2019 02:34 UTC

Return-Path: <csp@csperkins.org>
X-Original-To: rmcat@ietfa.amsl.com
Delivered-To: rmcat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C108E120077 for <rmcat@ietfa.amsl.com>; Wed, 20 Nov 2019 18:34:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 IceanLgXVj8k for <rmcat@ietfa.amsl.com>; Wed, 20 Nov 2019 18:34:53 -0800 (PST)
Received: from haggis.mythic-beasts.com (haggis.mythic-beasts.com [IPv6:2a00:1098:0:86:1000:0:2:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 532D41208AA for <rmcat@ietf.org>; Wed, 20 Nov 2019 18:34:53 -0800 (PST)
Received: from [31.133.155.18] (port=65430 helo=dhcp-9b12.meeting.ietf.org) by haggis.mythic-beasts.com with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92.3) (envelope-from <csp@csperkins.org>) id 1iXcJ0-0007Fm-4v; Thu, 21 Nov 2019 02:34:51 +0000
From: Colin Perkins <csp@csperkins.org>
Message-Id: <5D04B388-51DD-408B-9584-537CB5E0CF74@csperkins.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_6365D876-3CBA-472C-BDA8-1DB5D9D3F11A"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Thu, 21 Nov 2019 10:34:44 +0800
In-Reply-To: <HE1PR07MB442519D024F9D01153ED790EC24F0@HE1PR07MB4425.eurprd07.prod.outlook.com>
Cc: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>, "rmcat@ietf.org" <rmcat@ietf.org>, Anna Brunstrom <anna.brunstrom@kau.se>
To: Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>
References: <cde7bae8743b4637b0cc0ae6fba3cd35@kau.se> <HE1PR07MB4425D9B9C9E14278E687748FC24C0@HE1PR07MB4425.eurprd07.prod.outlook.com> <259ECB6E-3C46-44BE-9E1F-6865DE4C31BC@csperkins.org> <HE1PR07MB442519D024F9D01153ED790EC24F0@HE1PR07MB4425.eurprd07.prod.outlook.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-BlackCat-Spam-Score: 14
Archived-At: <https://mailarchive.ietf.org/arch/msg/rmcat/IO7IaBXYZ1iXrG1e1ztAQN2XjdI>
Subject: Re: [rmcat] How to handle remaining milestones
X-BeenThere: rmcat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "RTP Media Congestion Avoidance Techniques \(RMCAT\) Working Group discussion list." <rmcat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmcat>, <mailto:rmcat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rmcat/>
List-Post: <mailto:rmcat@ietf.org>
List-Help: <mailto:rmcat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmcat>, <mailto:rmcat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Nov 2019 02:34:56 -0000

Hi Ingemar,

We’re looking for experience with use of these protocols over the Internet. This doesn’t necessarily have to be in browsers.

Colin



> On 20 Nov 2019, at 18:56, Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org> wrote:
> 
> OK  
>  
> Listened in on the RMCAT session, not sure that I get it fully.
>  
> I find it unlikely that SCReAM will find its way to web browser implementations. 
>  
> Will experience from remote control use cases be a sufficient toll gate to advance SCReAM to proposed standard?. I understand that remote control was not the initial intention in RMCAT.
>  
> /Ingemar
>  
> From: Colin Perkins <csp@csperkins.org> 
> Sent: den 20 november 2019 06:05
> To: Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
> Cc: Anna Brunstrom <anna.brunstrom@kau.se>se>; rmcat@ietf.org; Ingemar Johansson S <ingemar.s.johansson@ericsson.com>
> Subject: Re: [rmcat] How to handle remaining milestones
>  
> Hi Ingemar,
>  
> As we discussed in the meeting, I think we’re looking for some deployment experience before we progress candidate algorithms to proposed standard.
>  
> Colin
>  
> 
> 
> On 19 Nov 2019, at 18:39, Ingemar Johansson S <ingemar.s.johansson=40ericsson.com@dmarc.ietf.org <mailto:ingemar.s.johansson=40ericsson.com@dmarc.ietf.org>> wrote:
>  
> Hi
>  
> My plan is to drive an update of RFC8298 towards proposed standard status if that is seen as important enough.
> That update would also specify the L4S support either as implemented in the example running code or some improved version of it. 
> Still I would like to see more real life deployment experience, to get an understanding of the possible outstanding issues that need to be fixed.
> The problem is that SCReAM has not been deployed/experimented with other than in a use case with remote controlled vehicles  and I don’t foresee any wider deployment in other contexts for the moment. 
>  
> Question is if this is sufficient for a proposed standard status ?
>  
> /Ingemar
>  
> From: Anna Brunström <anna.brunstrom@kau.se <mailto:anna.brunstrom@kau.se>> 
> Sent: den 18 november 2019 15:47
> To: rmcat@ietf.org <mailto:rmcat@ietf.org>
> Subject: [rmcat] How to handle remaining milestones
>  
> Dear all,
>  
> As part of the WG status overview in tomorrow’s rmcat meeting at IETF106 we want to bring up how to handle our remaining milestones:
>  
> Jul 2019            Publish first draft of evaluation results
> Jul 2019            Publish first draft of Standards Track congestion control algorithm                                                                                                                          
> Nov 2019          Submit interactions between applications and RTP flows to IESG as Informational
> Nov 2019          Submit congestion control to IESG for Proposed Standard 
>  
> One approach for how to move forward could be to gather evaluation results and experiences for the next 12 months or so (with meetings only if there are results to report) and then evaluate the status and whether to pursue further work. But the way forward of course depends on the interest of the working group and the intentions of the algorithm authors. 
>  
> We just wanted to give a heads up for this discussion point so you all have a chance to think about it beforehand, also as it is not directly visible in the agenda as it is part of the WG status review. Any comment on the mailing list is of course also welcome!
>  
> Best Regards,
> Anna (for the chairs)
> 
>  
> ---------------------------------------------------------------------
> Professor Anna Brunstrom
> Department of Mathematics and Computer Science
> Karlstad University
> 651 88 Karlstad, Sweden
> Phone:   +46 54 7001795
> E-mail:  anna.brunstrom@kau.se <mailto:anna.brunstrom@kau.se>
> ---------------------------------------------------------------------



-- 
Colin Perkins
https://csperkins.org/