[xrblock] Request followup of <draft-ietf-xrblock-rtcp-xr-synchronization>

Qin Wu <bill.wu@huawei.com> Tue, 19 November 2013 01:57 UTC

Return-Path: <bill.wu@huawei.com>
X-Original-To: xrblock@ietfa.amsl.com
Delivered-To: xrblock@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 508A91AE9E6 for <xrblock@ietfa.amsl.com>; Mon, 18 Nov 2013 17:57:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.726
X-Spam-Status: No, score=-4.726 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.525, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id Xz_-NOgKt2tF for <xrblock@ietfa.amsl.com>; Mon, 18 Nov 2013 17:57:12 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) by ietfa.amsl.com (Postfix) with ESMTP id 47F5A1AE9EB for <xrblock@ietf.org>; Mon, 18 Nov 2013 17:57:02 -0800 (PST)
Received: from (EHLO lhreml204-edg.china.huawei.com) ([]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AYB16055; Tue, 19 Nov 2013 01:56:55 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com ( by lhreml204-edg.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Tue, 19 Nov 2013 01:56:48 +0000
Received: from nkgeml407-hub.china.huawei.com ( by lhreml402-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Tue, 19 Nov 2013 01:56:53 +0000
Received: from NKGEML501-MBS.china.huawei.com ([]) by nkgeml407-hub.china.huawei.com ([]) with mapi id 14.03.0158.001; Tue, 19 Nov 2013 09:56:47 +0800
From: Qin Wu <bill.wu@huawei.com>
To: "xrblock@ietf.org" <xrblock@ietf.org>
Thread-Topic: Request followup of <draft-ietf-xrblock-rtcp-xr-synchronization>
Thread-Index: AQHO5Mqa4NIx1TN8U0e8+QE+bsWKWg==
Date: Tue, 19 Nov 2013 01:56:46 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C55EEB@nkgeml501-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "xrblock-chairs@tools.ietf.org" <xrblock-chairs@tools.ietf.org>
Subject: [xrblock] Request followup of <draft-ietf-xrblock-rtcp-xr-synchronization>
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Tue, 19 Nov 2013 01:57:14 -0000

Here is one minor update to draft-ietf-xrblock-rtcp-xr-synchronization. 
The only change is version number from (-06) to (-07). 

Chairs, would you like to follow up? We believe this draft is ready to go for publication.

-----Original Message-----
From: IETF Secretariat [mailto:ietf-secretariat-reply@ietf.org] 
Sent: Monday, November 18, 2013 8:42 PM
To: Hitoshi Asaeda; Huangyihong (Rachel); Qin Wu
Cc: Dan Romascanu; Shida Schubert
Subject: Expiration impending: <draft-ietf-xrblock-rtcp-xr-synchronization-06.txt>

The following draft will expire soon:

Name:     draft-ietf-xrblock-rtcp-xr-synchronization
Title:    RTP Control Protocol (RTCP) Extended Report (XR) Blocks for Synchronization Delay and Offset Metrics Reporting
State:    I-D Exists
Expires:  2013-11-29 (in 1 week, 3 days)