IETF Logo Mail Archive

Re: [ppsp] ***SPAM*** 8.616 (5) Re: =?utf-8?Q?=E7=AD=94=E5=A4=8D=3A__?=Call for WG consensus on Tracker Protocol encoding

Dave Cottlehuber <dch@skunkwerks.at> Fri, 21 November 2014 13:33 UTC

Return-Path: <dch@skunkwerks.at>
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 B48491AD40E for <ppsp@ietfa.amsl.com>; Fri, 21 Nov 2014 05:33:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.299
X-Spam-Level:
X-Spam-Status: No, score=0.299 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] 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 IklFWiZzhUMM for <ppsp@ietfa.amsl.com>; Fri, 21 Nov 2014 05:33:28 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DE0D41AD48F for <ppsp@ietf.org>; Fri, 21 Nov 2014 05:31:32 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 329F6207DD for <ppsp@ietf.org>; Fri, 21 Nov 2014 08:31:32 -0500 (EST)
Received: from frontend2 ([10.202.2.161]) by compute3.internal (MEProxy); Fri, 21 Nov 2014 08:31:32 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=skunkwerks.at; h= x-sasl-enc:date:from:to:message-id:in-reply-to:references :subject:mime-version:content-type:content-transfer-encoding; s= mesmtp; bh=WXsqJwS1/M7shJAu28nbIqn0CMQ=; b=UfLBfcRxT6budxwtcWt4x gaynyZCSH8kqGKhxMIZ8PmGPEzWx5cljapqQR/Dcqp9FM3aQ+ezF/wVO8dK0ua06 zHL72V32eq4pKk4VMXJC1QpojAOoqUBt72kyEgNDKHgWaLDhJPokOqm4RLlbZo9Y Yn/CTXhgksc2+LvU1AF4o4=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=x-sasl-enc:date:from:to:message-id :in-reply-to:references:subject:mime-version:content-type :content-transfer-encoding; s=smtpout; bh=WXsqJwS1/M7shJAu28nbIq n0CMQ=; b=sbHBBcba+TBAQCr5kCw2kRB1FoYBBcd7ctoyv7QK0Gyzv2u5xhqxLv 8AsXOXpU+jOiV3okRYPyPOItc1Ew3GC4LGIEyMYD8SY2yYTamOhU/KEA3p3EMo4U qdM9o6jM3oVfw9286lIFrYkJKbVgNVgFkC8LttPVGlnSOj1TQL/kU=
X-Sasl-enc: jWyhB92z6xdjZkui0uethcGj4L91VdbdBk+zxtEXN84g 1416576691
Received: from akai.skunkwerks.at (unknown [94.136.7.161]) by mail.messagingengine.com (Postfix) with ESMTPA id AF44F6800A2 for <ppsp@ietf.org>; Fri, 21 Nov 2014 08:31:31 -0500 (EST)
Date: Fri, 21 Nov 2014 14:31:30 +0100
From: Dave Cottlehuber <dch@skunkwerks.at>
To: "ppsp@ietf.org" <ppsp@ietf.org>
Message-ID: <etPan.546f3eb2.6b8b4567.bc5b@akai.skunkwerks.at>
In-Reply-To: <201411200912520787195@bjtu.edu.cn>
References: <B0D29E0424F2DE47A0B36779EC666779661DB7CE@nkgeml501-mbs.china.huawei.com> <00b001cfff9b$6109f510$231ddf30$@com> <B0D29E0424F2DE47A0B36779EC666779661DBBB1@nkgeml501-mbs.china.huawei.com> <201411200912520787195@bjtu.edu.cn>
X-Mailer: Airmail Beta (278)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/t2_Orwdq224nB2_7AsoGgl_UZpE
Subject: Re: [ppsp] ***SPAM*** 8.616 (5) Re: 答复: 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: Fri, 21 Nov 2014 13:33:31 -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

Given we are writing a *transport* protocol and not an http server, I would opt for binary encoding as mandatory. Optional text encoding if necessary.

The more fat we mix into the the tracker protocol, the less useful it becomes.

—
Dave Cottlehuber
dch@skunkwerks.at
+43 688 60 56 21 44
Sent from the Cloud

v2.14.0 | Report a Bug | By Email