IETF Logo Mail Archive

Re: [ppsp] Comment on base tracker protocol binary encoding

Martin Stiemerling <mls.ietf@gmail.com> Thu, 13 November 2014 02:27 UTC

Return-Path: <mls.ietf@gmail.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 8B0701A1AD9 for <ppsp@ietfa.amsl.com>; Wed, 12 Nov 2014 18:27:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, 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 6XIgIa45G3JN for <ppsp@ietfa.amsl.com>; Wed, 12 Nov 2014 18:27:10 -0800 (PST)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DCC461A1AD3 for <ppsp@ietf.org>; Wed, 12 Nov 2014 18:27:09 -0800 (PST)
Received: by mail-wg0-f47.google.com with SMTP id a1so15733719wgh.20 for <ppsp@ietf.org>; Wed, 12 Nov 2014 18:27:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=w+BrDQKqXnqGLEamf02E/sjJKp6SKrRMCc85QQBWv1U=; b=SEAYp0NA7R4yD3SjsOGZvLdI/dsKqIMlaMPNQzpLYIHAnM0C2qDoX136i+GMqhelHB 9EcM7zSbFDCCgpyFPucuzYDwntCvbiYsyCWlTqxeLB6i9nZEQ7cPvtyvOmoZ1/1aPMlV Rll9I/IUucmfcInNe4eWS3psTvw5ZcLMyJxfsy8G/93vnqPiQec8Gn/fjBkPla+ub7/P vwgZT3dWhpQk12smWv38H6ihQgN/IxBoFyeYXSDBu8bE99k2a2q0VSQU78eMMC0QC2pv 6a3DjSGeOoxQpx56Rmj8qbu5UGibz+WYHR3Dav2l8irl8tyvrx9IsgFJV2e9sB9yj1+T NzGQ==
X-Received: by 10.194.92.116 with SMTP id cl20mr13790982wjb.71.1415845628709; Wed, 12 Nov 2014 18:27:08 -0800 (PST)
Received: from dhcp-9bef.meeting.ietf.org (t2001067c03700152b5ba6174cf38422e.eduroam.v6.meeting.ietf.org. [2001:67c:370:152:b5ba:6174:cf38:422e]) by mx.google.com with ESMTPSA id cv7sm33637661wjc.3.2014.11.12.18.27.04 for <multiple recipients> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Nov 2014 18:27:05 -0800 (PST)
Message-ID: <546416F6.5000506@gmail.com>
Date: Wed, 12 Nov 2014 16:27:02 -1000
From: Martin Stiemerling <mls.ietf@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: "Prof. Rui Santos Cruz Eng." <rui.cruz@ieee.org>
References: <544E02A0.9060100@cs.vu.nl> <51E6A56BD6A85142B9D172C87FC3ABBB8624D461@nkgeml501-mbs.china.huawei.com> <544E35AF.3060906@cs.vu.nl> <74AA096A-8315-4348-88B2-BE6514379E45@ieee.org>
In-Reply-To: <74AA096A-8315-4348-88B2-BE6514379E45@ieee.org>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/ppsp/0LSl4uqKqJ12mu2S1Zie3h6eOlU
Cc: ppsp <ppsp@ietf.org>
Subject: Re: [ppsp] Comment on base tracker protocol binary 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:11 -0000

[writing as an individual, not as your Area Director]

Sorry for getting so late to this email, but:

Am 27.10.14 um 02:17 schrieb Prof. Rui Santos Cruz Eng.:
> The idea for the new specification of the protocol, was to avoid
> suggestions of encoding, leaving that to implementation.

No encoding, means no protocol, means no standard.

Get started on finding consensus on a protocol encoding right now. 
Otherwise, we can just abandon the tracker protocol draft.

   Martin

v2.23.0 | Report a Bug | By Email