From nobody Thu Feb 4 07:42:51 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 5EB6A3A15D3 for ; Thu, 4 Feb 2021 07:42:50 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.899 X-Spam-Level: X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=aliax-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 acrrKI_mrp5j for ; Thu, 4 Feb 2021 07:42:48 -0800 (PST) Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 E52243A15D2 for ; Thu, 4 Feb 2021 07:42:47 -0800 (PST) Received: by mail-ot1-x334.google.com with SMTP id k10so1444806otl.2 for ; Thu, 04 Feb 2021 07:42:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aliax-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=+pUCHl5k99f1PmmrT0aweG5AB5ZYrzlUqtCmYcNJipQ=; b=z8JUQN7cRYwENKH2I+zXY3sgv0qx3MafI9kmtr/SeUcXOXNouSqt9VfFIpVs89a8tx 14N9+e3ZVCaKxMwU98Sq+0gzMkjOvbRFiokRC86WiopJtpGxlu1vLHN6r0iCqz6FpxQj DiVfJL5NvJk9bO5LHOF3BsAVLsz0Af6A+zc728SGbqm2GlpJwWzIYXQup8T5qBeynZZU z8gIT7VisngrceOur9Ac3k+MD4RZeHh5FTO4tT+v9w80UFSHBekxRC/4Tm9gdak3Eo3e FbI4/RYHGy9J3puPy59gJZ+Lf4joSVHnX9/tKgaKA+g8MTkLpjwBXUzIiNZG4pSawjx/ pvhg== 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:content-transfer-encoding; bh=+pUCHl5k99f1PmmrT0aweG5AB5ZYrzlUqtCmYcNJipQ=; b=unHhuBmqIemIwD4iZ4910tijh9QDvDuMrP+8SVUDXfKehwHTjma7dkETQMLr+DZEsm 1c+8yKvPmc8maA0ztIkChl7FnUvCn3czgdYCYB2n5wu3SDqWfwlBHdv2JcgPIHGyxCe/ clcMikpBITsY2gDnhfchoi+DdQCGOhKsAQZzLNFenkDuhXdLMZ6037yKOmNbdf2e2jNx UOcCkianfjMlmN6229zY9nSzvOKtDmlZicPGovZS2nQtzTmoTCYxr8EHODwZPT5aAA/W O2uuRJu7kH6BSYgBxb2kgG827TUPwZCNfsLlnaSzEwFn5PGTOHnd4cADACzbOn/V8/rl 2lZg== X-Gm-Message-State: AOAM531KMPQH7aMN4UyBeZ+9wqv1V/DxISICW1wWFXW003qmbTO9nGh8 9VUjMJOGSMwjiuOtl7Mzh/hZoSAy5sGINLYaU68OGw== X-Google-Smtp-Source: ABdhPJwhzjDN5oUgBF8ngwhCF8Nqz50IwoGk66gCWrk24wPbEpSxGPxzA201xbSgB7Jj9QbHSSrrT2qHvyQWf6o4epM= X-Received: by 2002:a05:6830:150a:: with SMTP id k10mr5114432otp.144.1612453366803; Thu, 04 Feb 2021 07:42:46 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: =?UTF-8?Q?I=C3=B1aki_Baz_Castillo?= Date: Thu, 4 Feb 2021 16:42:35 +0100 Message-ID: To: "Murray S. Kucherawy" Cc: Christer Holmberg , RTCWeb IETF Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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:42:50 -0000 May I ask how is BFCP related to WebRTC at all? On Thu, 4 Feb 2021 at 16:41, Murray S. Kucherawy wrot= e: > > Yep, that's where this message went. > > -MSK > > On Thu, Feb 4, 2021 at 7:32 AM Christer Holmberg wrote: >> >> Hi, >> >> >> >> BFCP related discussions redirected to RTCWEB? >> >> >> >> Regards, >> >> >> >> Christer >> >> >> >> From: rtcweb On Behalf Of Murray S. Kucherawy >> Sent: torstai 4. helmikuuta 2021 17.28 >> To: RTCWeb IETF >> Subject: [rtcweb] RFC 8855 registries >> >> >> >> Greetings, >> >> >> >> RFC 8855 ("The Binary Floor Control Protocol (BFCP)") created an IANA re= gistry with four sub-registries. They are all written up to follow Specifi= cation Required rules, which requires appointment of a designated expert. = The BFCPBIS working group is closed, and future discussion was redirected h= ere, which brings me to this audience to seek volunteers or nominations for= designated experts for these registries. >> >> >> >> Any takers? >> >> >> >> -MSK > > _______________________________________________ > rtcweb mailing list > rtcweb@ietf.org > https://www.ietf.org/mailman/listinfo/rtcweb --=20 I=C3=B1aki Baz Castillo