[xrblock] FW: confused with "draft to RFC"
Qin Wu <bill.wu@huawei.com> Wed, 30 October 2013 01:28 UTC
Return-Path: <bill.wu@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 5C36821E80C4 for <xrblock@ietfa.amsl.com>; Tue, 29 Oct 2013 18:28:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.36
X-Spam-Level:
X-Spam-Status: No, score=-4.36 tagged_above=-999 required=5 tests=[AWL=-1.965, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qmv-BJ4OojFi for <xrblock@ietfa.amsl.com>; Tue, 29 Oct 2013 18:28:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id BE9E911E81CF for <xrblock@ietf.org>; Tue, 29 Oct 2013 18:28:25 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id AXI81646; Wed, 30 Oct 2013 01:28:24 +0000 (GMT)
Received: from LHREML401-HUB.china.huawei.com (10.201.5.240) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 30 Oct 2013 01:28:04 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml401-hub.china.huawei.com (10.201.5.240) with Microsoft SMTP Server (TLS) id 14.3.158.1; Wed, 30 Oct 2013 01:28:22 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.75]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Wed, 30 Oct 2013 09:28:14 +0800
From: Qin Wu <bill.wu@huawei.com>
To: xrblock <xrblock@ietf.org>
Thread-Topic: confused with "draft to RFC"
Thread-Index: AQHO1KUbZosyr6/ZHkmj5rTqAaL4TJoMcyGA
Date: Wed, 30 Oct 2013 01:28:14 +0000
Message-ID: <B8F9A780D330094D99AF023C5877DABA43C2C317@nkgeml501-mbs.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.138.41.149]
Content-Type: multipart/alternative; boundary="_000_B8F9A780D330094D99AF023C5877DABA43C2C317nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "fei_wang@bit.edu.cn" <fei_wang@bit.edu.cn>
Subject: [xrblock] FW: confused with "draft to RFC"
X-BeenThere: xrblock@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 30 Oct 2013 01:28:33 -0000
Hi, Wang Fei: The status of draft-ietf-xrblock-rtcp-xr-qoe-12 is work in progress and waiting for publication. Currently, the working group chair as shepherd has submitted publication request for this draft for 26 days. Area Director as sponsored AD will move this draft for IETF LC and IESG review after IETF 88 meeting. Hope this clarifies! Regards! -Qin From: 396399295@qq.com [mailto:396399295@qq.com] On Behalf Of 王飞 Sent: Tuesday, October 29, 2013 8:46 PM To: draft-ietf-xrblock-rtcp-xr-qoe Subject: confused with "draft to RFC" Dear IETF staff， I'm a PHD student interested in the IETF draft discussion but the status of draft-ietf-xrblock-rtcp-xr-qoe-12 is "Publication Requested (for 26 days) Submitted to IESG for Publication ". What does this mean？ The darft will be a RFC in 26 days? My appreciation for your generous help. WangFei Beijing Institue of Technology P.R.China 2013/10/29