IETF Logo Mail Archive

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

邓灵莉/Lingli Deng <denglingli@chinamobile.com> Thu, 13 November 2014 23:41 UTC

Return-Path: <denglingli@chinamobile.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 CC9D71AE2EA for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 15:41:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.028
X-Spam-Level:
X-Spam-Status: No, score=0.028 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RELAY_IS_221=2.222, RP_MATCHES_RCVD=-0.594, SPF_PASS=-0.001] autolearn=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 BPnltI5CzyZS for <ppsp@ietfa.amsl.com>; Thu, 13 Nov 2014 15:41:44 -0800 (PST)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with SMTP id E86C91AE2EC for <ppsp@ietf.org>; Thu, 13 Nov 2014 15:41:43 -0800 (PST)
Received: from spf.mail.chinamobile.com (unknown[172.16.121.1]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee1546541b1ec3-4b2e2; Fri, 14 Nov 2014 07:41:41 +0800 (CST)
X-RM-TRANSID: 2ee1546541b1ec3-4b2e2
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[31.133.167.36]) by rmsmtp-syy-appsvr01-12001 (RichMail) with SMTP id 2ee1546541b1b3d-c241f; Fri, 14 Nov 2014 07:41:41 +0800 (CST)
X-RM-TRANSID: 2ee1546541b1b3d-c241f
From: 邓灵莉/Lingli Deng <denglingli@chinamobile.com>
To: 'Zongning' <zongning@huawei.com>, ppsp@ietf.org
References: <B0D29E0424F2DE47A0B36779EC666779661DB7CE@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B0D29E0424F2DE47A0B36779EC666779661DB7CE@nkgeml501-mbs.china.huawei.com>
Date: Fri, 14 Nov 2014 07:41:39 +0800
Message-ID: <00b001cfff9b$6109f510$231ddf30$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_00B1_01CFFFDE.6F2D3510"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Ac/+6XHitTUE4yIXTIW0IaBSD9/HLgAsWk8A
Content-Language: zh-cn
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/GZjaw9EwvsB3c9kruoj8gUaRavY
Subject: Re: [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:41:47 -0000

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

v2.14.0 | Report a Bug | By Email