[ppsp] 答复: Call for WG consensus on Tracker Protocol encoding

Zongning <zongning@huawei.com> Thu, 13 November 2014 23:58 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ADD61A1B28 for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 15:58:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.494
X-Spam-Level:
X-Spam-Status: No, score=-104.494 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 YMowV724faXR for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 15:58:38 -0800 (PST)
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 4B9CF1AE35A for <ppsp@ietf.org>; Thu, 13 Nov 2014 15:57:48 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOT54297; Thu, 13 Nov 2014 23:57:46 +0000 (GMT)
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Nov 2014 23:57:46 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 14 Nov 2014 07:57:40 +0800
From: Zongning <zongning@huawei.com>
To: 邓灵莉/Lingli Deng <denglingli@chinamobile.com>, "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: [ppsp] Call for WG consensus on Tracker Protocol encoding
Thread-Index: Ac/+6XHitTUE4yIXTIW0IaBSD9/HLgAsWk8AAACf08A=
Date: Thu, 13 Nov 2014 23:57:39 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC666779661DBBB1@nkgeml501-mbs.china.huawei.com>
References: <B0D29E0424F2DE47A0B36779EC666779661DB7CE@nkgeml501-mbs.china.huawei.com> <00b001cfff9b$6109f510$231ddf30$@com>
In-Reply-To: <00b001cfff9b$6109f510$231ddf30$@com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.151.167]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC666779661DBBB1nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/_x1OU9tgJJArivE-qNVEsbZogpY
Subject: [ppsp] 答复: Call for WG consensus on Tracker Protocol encoding
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp/>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Nov 2014 23:58:42 -0000

Hi, Lingli,

Yunfei and I are working on roadmap of all I-Ds in PPSP, and will post on the list soon.

The poll for encoding will be open till the *end of next week*.

Thanks.

-Ning

发件人: 邓灵莉/Lingli Deng [mailto:denglingli@chinamobile.com]
发送时间: 2014年11月13日 13:42
收件人: Zongning; ppsp@ietf.org
主题: RE: [ppsp] Call for WG consensus on Tracker Protocol encoding

Dear Chairs,

Speaking as one of the co-authors for the base tracker protocol, we are happy to take whatever the group feels right.
But would you mind setting a clear time limit for this poll?

Thanks,
Lingli

From: ppsp [mailto:ppsp-bounces@ietf.org] On Behalf Of Zongning
Sent: Thursday, November 13, 2014 10:28 AM
To: ppsp@ietf.org<mailto:ppsp@ietf.org>
Subject: [ppsp] Call for WG consensus on Tracker Protocol encoding

Hi, all,

Firstly, thanks to the co-authors of Base Tracker Protocol for persistently moving the draft forward.

Now the outstanding issue is that as a Standard Track document, we really NEED to agree on a mandatory encoding for the interoperable on-the-wire Tracker Protocol. As discussed in the PPSP session today, we will start WGLC for the draft, provided that we can reach a rough consensus on the encoding option and the co-authors revise the draft accordingly.

Currently we have two options mentioned in the draft – they are text based and binary based. For an exemplary comparison, please see Section 3.1 in the draft. Could folks in the group give their opinions on which encoding option is preferred for Tracker Protocol, and why? People are welcome to give other options beyond text and binary, but please do show us the reason for choosing them.

The during of this call will not last too long, before the co-chairs will make a decision. So, please do contribute your technical expertise in this perspective, to enlight the group.

Thanks.

-Yunfei & Ning