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

Dan Romascanu <dromasca@gmail.com> Mon, 25 September 2017 14:40 UTC

Return-Path: <dromasca@gmail.com>
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 90786126BF3 for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 07:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 UYSiEOzyCHxo for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 07:40:46 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (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 3A11213447E for <xrblock@ietf.org>; Mon, 25 Sep 2017 07:40:14 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id s132so6872549qke.7 for <xrblock@ietf.org>; Mon, 25 Sep 2017 07:40:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JMFUC8ZI/VF+oDGchTdwGkByq5YiACkboTymvTo9BJo=; b=F/mBK1Kt45/oNX+XA8AydLvM0MAzfUkNkIFvZtg80A4c0+7Os5FmJ2l9Lk8ac7slkA mjF3zQquSEZl+lAvw7OEBaLXbJKbk4U2NvmQ8us4pAvGrAUKF5BVRObD5REef10Gc8qz w9NkMJOFD1RONKEadbLNWz1tIflg1zgAc1luZ+iOPn2/Zz7whvl6DIHogSf63oDH3VPo pkyvNAcC4b/xRxzX84TGEVv+k3gtLC388Eez5CLN72sYlp07jNkmR9f93pQkaQPdYgt4 EuG4qqR/CEV0GxBUAvqzNGoTbfCI61pJqIQf0zwc6XQ55V7igNGvXdROaNA0rFI/vrPv oHVw==
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:cc; bh=JMFUC8ZI/VF+oDGchTdwGkByq5YiACkboTymvTo9BJo=; b=B+uhb9bFMTceYBkdjYseQOo20pwlQlnNmdzraXTLicTazSke/naDJ4bVNTJx27b7Jz W+59EWFixfdsdXT36Veb8cYWzprf2s7LjEJn0005SOS/Y/JYgydnYxhRchN6tJWpcL15 eeLYdc6lVI/jqDpKccn7G1uPjpI7iVHinx4jj8hJiLdMKZOpqrytg5g28s9B8ofGUQv+ mlDfVsnDQTdpaepJ7BVIvalZczx8yHQ7yrUYeBoxvyN2IdZU4QbBUKaZmZjOSWrP5eMc uhn1fo6aSbbXCVYeUbfshub/7DYRwBTGvYpkGyXf2EbNftA5jWVfjkle9DiMy1Wsu3uk y1IA==
X-Gm-Message-State: AHPjjUj0CA15tp38gJ6p1TG6kHiRLQVlR2JnXB9iRuowCyqHu3R4jUHm KhTlNkNOeHCtZ7Ld3KnLktWKAytvICNPIHPz07Q=
X-Google-Smtp-Source: AOwi7QCsXxIPZvKGY4xNedaB+5Q9e9MMhwL2iDCFAkGWoGxn9xo2GpzTBsY2UHSYCxx6KND7crkM6Ggsy/X/NxZ1NbE=
X-Received: by 10.55.79.68 with SMTP id d65mr11008242qkb.110.1506350413194; Mon, 25 Sep 2017 07:40:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.35.242 with HTTP; Mon, 25 Sep 2017 07:40:12 -0700 (PDT)
In-Reply-To: <CACHXSv5d-oAiywjbGb2kS4z0-bdTVoA-eN3YtULfH66KsAgK-A@mail.gmail.com>
References: <CAFgnS4UahmZ6Yju0LR1y_WvL3X2Ti-wiJVqRCDr_9P_PUZ3P_w@mail.gmail.com> <CACHXSv5d-oAiywjbGb2kS4z0-bdTVoA-eN3YtULfH66KsAgK-A@mail.gmail.com>
From: Dan Romascanu <dromasca@gmail.com>
Date: Mon, 25 Sep 2017 17:40:12 +0300
Message-ID: <CAFgnS4XafQuBALwUATD4FMKKdbF4drt2UenSVKNsrGN5zAD72A@mail.gmail.com>
To: Varun Singh <varun@callstats.io>
Cc: xrblock <xrblock@ietf.org>
Content-Type: multipart/alternative; boundary="001a114a97f4492961055a048955"
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/uYIwOTxQILjc9fLs1h3nTgSpDYk>
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 14:40:49 -0000

AVT WG time, or if there is anything like or close to ART Area meeting,
would be fine.

FWIW - I do not plan to attend IETF 100.

Regards,

Dan


On Mon, Sep 25, 2017 at 3:47 PM, Varun Singh <varun@callstats.io> wrote:

> 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
>>
>