Re: [xrblock] xrblock status, no meeting at IETF 100

Varun Singh <varun@callstats.io> Mon, 25 September 2017 12:47 UTC

Return-Path: <varun@callstats.io>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC9251342F5 for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 05:47:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=callstats.io
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 9vx0Pb8_BLYf for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 05:47:35 -0700 (PDT)
Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (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 CEE731342E6 for <xrblock@ietf.org>; Mon, 25 Sep 2017 05:47:34 -0700 (PDT)
Received: by mail-wr0-x231.google.com with SMTP id c23so7515732wrg.9 for <xrblock@ietf.org>; Mon, 25 Sep 2017 05:47:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=callstats.io; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=+m+3ak8uPMJ54pz0cX3xeKIzmKMbHKK7nwhqDShhXXY=; b=EYiC3A0OgNxNr93y9/kBk9Cf8O49Ev/2q5rysmg6T69/ctDO6nEyhVdqF+yqoTjk7K XkuDp31/NA5eF+TEj735COgTK3ejATWzPaO4HzYMJ+RqvvrQzXMJw0ZBVLodSzaY7gAs 83a0CNipQK6cy22wLfaqSpP/9tRd/2PCt7QTc=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=+m+3ak8uPMJ54pz0cX3xeKIzmKMbHKK7nwhqDShhXXY=; b=jtjXnCTS3aL2tJcbZkbfhWyV/NcDC0849nOAQn0c6luM2ePPrDO0FEWtuvdpzINMe/ Wda7knrE55KHYauKoHB5wGKK1PxV2aR/pe8XQ9rkAuVp3Bg3tkrkDbCd/mKToLjavV2X ubICNgMSZ1WO1LcdFaqEuf6lrd9uJHP0DdU+nQcbLOkYSEMCjREacDApjqh9WKUyH7iw +TzstKW07PLa9NZig5FyGhl35I8ghgZr9xdFbR4fh7qiQIAwKY5dEKUb0R3eO8aR3d2Y W59CZCbIuCKivMWk8Hld2CsF58FqxwWjew4gb98aoAzd1M+5YfuQw4xBQHVmalgYLjpt rWeg==
X-Gm-Message-State: AHPjjUiRcVtSNff0yo2sJmToB7FjSdgENvDe6oLZXkBss/YOE+liBsdm QYgbkc2mE6MnGISYVMxlGWql7fWwKDWdRC+Qi98jJQ==
X-Google-Smtp-Source: AOwi7QCoSqPhTgsfgXnFlG/yFJWu0eILdWtgFFlkE1evKGQ0wVzGk8ibmtt8y4q9D/uUHpBZrDxNw1aXwmCquNZfSjA=
X-Received: by 10.25.208.137 with SMTP id h131mr2297188lfg.101.1506343653090; Mon, 25 Sep 2017 05:47:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.159.149 with HTTP; Mon, 25 Sep 2017 05:47:12 -0700 (PDT)
In-Reply-To: <CAFgnS4UahmZ6Yju0LR1y_WvL3X2Ti-wiJVqRCDr_9P_PUZ3P_w@mail.gmail.com>
References: <CAFgnS4UahmZ6Yju0LR1y_WvL3X2Ti-wiJVqRCDr_9P_PUZ3P_w@mail.gmail.com>
From: Varun Singh <varun@callstats.io>
Date: Mon, 25 Sep 2017 05:47:12 -0700
Message-ID: <CACHXSv5d-oAiywjbGb2kS4z0-bdTVoA-eN3YtULfH66KsAgK-A@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>, xrblock <xrblock@ietf.org>
Content-Type: multipart/alternative; boundary="001a11412da85a409a055a02f60a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/wQ2rzy4_LS7ozePOcqMoRHEsEX8>
Subject: Re: [xrblock] xrblock status, no meeting at IETF 100
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Metric Blocks for use with RTCP's Extended Report Framework working group discussion list <xrblock.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/xrblock>, <mailto:xrblock-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/xrblock/>
List-Post: <mailto:xrblock@ietf.org>
List-Help: <mailto:xrblock-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/xrblock>, <mailto:xrblock-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Sep 2017 12:47:37 -0000

Currently, I have no concerns. I'm most likely not attending the Singapore
meeting in person.

However, what would be the course of action, If there are comments raised
in the IESG that requires group discussion? use agenda time from avt-
group?

Thanks,
Varun.
On Sat, 23 Sep 2017 at 12.34, Dan Romascanu <dromasca@gmail.com> wrote:

> Hi,
>
> The publication request for draft-ietf-xrblock-rtcweb-rtcp-xr-metrics-06
> was sent by Shida. This is the last deliverable in our current charter.
> With almost all our chartered work done, and no proposals or discussions on
> the list about new work, it looks like there is no need for the WG to meet
> at IETF 100. Does anybody have any concern about pushing the 'the WG will
> not meet' button at the IETF 100 request tool?
>
> Regards,
>
> Dan
>
> _______________________________________________
> xrblock mailing list
> xrblock@ietf.org
> https://www.ietf.org/mailman/listinfo/xrblock
>