IETF Logo Mail Archive

[ppsp] Call for WG consensus on Tracker Protocol encoding

Zongning <zongning@huawei.com> Thu, 13 November 2014 02:27 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 203301A1AD9 for <ppsp@ietfa.amsl.com>; Wed, 12 Nov 2014 18:27:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.794
X-Spam-Level:
X-Spam-Status: No, score=-104.794 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 KsoWwQFZawWs for <ppsp@ietfa.amsl.com>; Wed, 12 Nov 2014 18:27:52 -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 C544D1A1AD3 for <ppsp@ietf.org>; Wed, 12 Nov 2014 18:27:51 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml405-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BOS43245; Thu, 13 Nov 2014 02:27:49 +0000 (GMT)
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 13 Nov 2014 02:27:49 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.21]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Thu, 13 Nov 2014 10:27:43 +0800
From: Zongning <zongning@huawei.com>
To: "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: Call for WG consensus on Tracker Protocol encoding
Thread-Index: Ac/+6XHitTUE4yIXTIW0IaBSD9/HLg==
Date: Thu, 13 Nov 2014 02:27:42 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC666779661DB7CE@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.138.215]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC666779661DB7CEnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/u-zudCwl6aN4cK0A3D8WhXgsCs8
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 02:27:54 -0000

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.23.0 | Report a Bug | By Email