Re: [xrblock] xrblock status, no meeting at IETF 100
"Huangyihong (Rachel)" <rachel.huang@huawei.com> Mon, 25 September 2017 14:49 UTC
Return-Path: <rachel.huang@huawei.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 1D455134495 for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 07:49:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham 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 Iv003vAmV0MQ for <xrblock@ietfa.amsl.com>; Mon, 25 Sep 2017 07:49:25 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 523E6134496 for <xrblock@ietf.org>; Mon, 25 Sep 2017 07:49:18 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML713-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DWE70080; Mon, 25 Sep 2017 14:49:15 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.301.0; Mon, 25 Sep 2017 15:49:14 +0100
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.199]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Mon, 25 Sep 2017 22:49:07 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: Dan Romascanu <dromasca@gmail.com>, Varun Singh <varun@callstats.io>
CC: xrblock <xrblock@ietf.org>
Thread-Topic: [xrblock] xrblock status, no meeting at IETF 100
Thread-Index: AdM2DU0mhrFmG6wITL6mLPGXxZRkdQ==
Date: Mon, 25 Sep 2017 14:49:05 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB9C59647E@nkgeml513-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.200.65.80]
Content-Type: multipart/alternative; boundary="_000_51E6A56BD6A85142B9D172C87FC3ABBB9C59647Enkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020205.59C9176C.0183, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.199, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: ea92bfb9ff13204376b83dc4c2e50bac
Archived-At: <https://mailarchive.ietf.org/arch/msg/xrblock/9Q8zNEue2bBYN5KKUYqWYTH5_2M>
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:49:27 -0000
AVT is not expected to have a busy agenda if it’s as usual, so we can probably discuss there if necessary. BR, Rachel 发件人: xrblock [mailto:xrblock-bounces@ietf.org] 代表 Dan Romascanu 发送时间: 2017年9月25日 22:40 收件人: Varun Singh <varun@callstats.io> 抄送: xrblock <xrblock@ietf.org> 主题: Re: [xrblock] xrblock status, no meeting at IETF 100 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<mailto: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<mailto: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<mailto:xrblock@ietf.org> https://www.ietf.org/mailman/listinfo/xrblock
- [xrblock] xrblock status, no meeting at IETF 100 Dan Romascanu
- Re: [xrblock] xrblock status, no meeting at IETF … Varun Singh
- Re: [xrblock] xrblock status, no meeting at IETF … Dan Romascanu
- Re: [xrblock] xrblock status, no meeting at IETF … Huangyihong (Rachel)