From nobody Thu Feb 4 07:46:00 2021 Return-Path: X-Original-To: rtcweb@ietfa.amsl.com Delivered-To: rtcweb@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E18CB3A15D9 for ; Thu, 4 Feb 2021 07:45:57 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.097 X-Spam-Level: X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Dlz6DY-rnCly for ; Thu, 4 Feb 2021 07:45:56 -0800 (PST) Received: from mail-vk1-xa2d.google.com (mail-vk1-xa2d.google.com [IPv6:2607:f8b0:4864:20::a2d]) (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 D022E3A15D3 for ; Thu, 4 Feb 2021 07:45:56 -0800 (PST) Received: by mail-vk1-xa2d.google.com with SMTP id y8so773149vky.4 for ; Thu, 04 Feb 2021 07:45:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JcpAdxqBdLNF30zFE11Yqv2im8aoVUw8Ng+iV3DHGAw=; b=hmgw95qx4E1F/dQHAZPbHIL6XtmgwQYCH6AspvMfnPnDQ4VNwp/byr1Rm47Rq0g1ZF /byx1TMb2aRkGHS6amcavofpUNkP//SWmQcwwfXNzXezLJROaJ+E7GKYLenOl9RD00F7 1MxU4voy79rP939CvxZfcnr9napEb0giEbfWLomRZpuyiXBDYuZM7aefo7yehE8t39aI HkJANijOpki1AxVVlCGMYyvi831pxcB5/j8OrP8Pj2WUV0Cc4KCELpRwaQENPDBylCEd tRy+4jRL6utnwfZR0XTcSL1oDWx2oI6IrCj4im3x2LHo9wc58dFEZ6hHsNZxOPhbzJEU WRWQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JcpAdxqBdLNF30zFE11Yqv2im8aoVUw8Ng+iV3DHGAw=; b=YYeCUrl8acMHnMVrdftAQmIqZB4avwCo9AFSoyd0RmqnNvDfyLVtrBjbPSKXA+PXLn +exxM45WLTybcGdjP5WHFBtqSizfFe6PY+hL77/iiWFB/L+1IzAMpmF7euN5tv/1mU0H COcBD87BMYw9h+8aacpF6ucjtmmZ2CfaQMFm31v7+D9KqqKJ+XVs1uvku8jwg/I76iPc Fyd8iz1y5xHOdCnW57jK/X+5P0LO7se02L94kMygQ/alm9xMh9m8lDuBLc8HzkBSNhFz f3dGksHw1rjJBkIhrnumAy1lp9/vGIyVn5s7aerfoEzYCQdTTb2X2SGs4mG6IECQrsZG E4Rw== X-Gm-Message-State: AOAM530Zy3F+eUut4JvEGXBrK19LK0B43ATv67P0zjeJBzmZsMw4Ht4q pREVrIm6BqQgpwfPvAaH62YGyc9gWah0oNzNJbHJQEQ6iKQ= X-Google-Smtp-Source: ABdhPJyPdlxnMD1w2aC3mwgXvr30L58nTVuReLhbHpkTWOuuGbuoC43fwPcF5wrWiMoWTqv8fCr/x12vfTc0Q+hS+zs= X-Received: by 2002:a1f:9855:: with SMTP id a82mr5906939vke.13.1612453555794; Thu, 04 Feb 2021 07:45:55 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: "Murray S. Kucherawy" Date: Thu, 4 Feb 2021 07:45:44 -0800 Message-ID: To: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= Cc: Christer Holmberg , RTCWeb IETF Content-Type: multipart/alternative; boundary="00000000000068f6c505ba84997f" Archived-At: Subject: Re: [rtcweb] RFC 8855 registries X-BeenThere: rtcweb@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Real-Time Communication in WEB-browsers working group list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Feb 2021 15:45:58 -0000 --00000000000068f6c505ba84997f Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Feb 4, 2021 at 7:42 AM I=C3=B1aki Baz Castillo wrot= e: > May I ask how is BFCP related to WebRTC at all? > The chairs of that working group, when closing it, made that proposal. I didn't think it sounded like a crazy idea given both contributed to C238, but if that was wrong, I'm happy to look for volunteers elsewhere. -MSK --00000000000068f6c505ba84997f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Thu, Feb 4, 2021 at 7:42 AM I=C3=B1aki= Baz Castillo <ibc@aliax.net> wr= ote:
May I ask how is BFCP related to WebRTC at all?

The chairs of that working group, when closi= ng it, made that proposal.=C2=A0 I didn't think it sounded like a crazy= idea given both contributed to C238, but if that was wrong, I'm happy = to look for volunteers elsewhere.

-MSK
--00000000000068f6c505ba84997f--