Re: [ppsp] peer protocol in WG last call
Arno Bakker <arno@cs.vu.nl> Thu, 29 November 2012 12:35 UTC
Return-Path: <a.bakker@vu.nl>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20D0A21F89F2 for <ppsp@ietfa.amsl.com>; Thu, 29 Nov 2012 04:35:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.504
X-Spam-Level:
X-Spam-Status: No, score=-4.504 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gMF-1-EwWNZ4 for <ppsp@ietfa.amsl.com>; Thu, 29 Nov 2012 04:35:18 -0800 (PST)
Received: from mailin.vu.nl (mailin.vu.nl [130.37.164.16]) by ietfa.amsl.com (Postfix) with ESMTP id A8D4E21F8933 for <ppsp@ietf.org>; Thu, 29 Nov 2012 04:35:17 -0800 (PST)
Received: from PEXHB011A.vu.local (130.37.236.64) by mailin.vu.nl (130.37.164.16) with Microsoft SMTP Server (TLS) id 14.2.298.4; Thu, 29 Nov 2012 13:35:15 +0100
Received: from [130.161.211.249] (130.37.238.20) by mails.vu.nl (130.37.236.64) with Microsoft SMTP Server (TLS) id 14.2.298.4; Thu, 29 Nov 2012 13:35:15 +0100
Message-ID: <50B756A9.9080400@cs.vu.nl>
Date: Thu, 29 Nov 2012 13:35:53 +0100
From: Arno Bakker <arno@cs.vu.nl>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:11.0) Gecko/20120312 Thunderbird/11.0
MIME-Version: 1.0
To: Riccardo Bernardini <riccardo.bernardini@uniud.it>
References: <E6B2DF43-8D66-4092-8210-E86225FA251E@cisco.com> <F0DAB28A-870B-4E6B-AFB6-0D803164E7B4@cisco.com> <20121119114547.60502iibxkcnt0bf@webmail.uniud.it> <50ACCDF2.9070402@cs.vu.nl> <20121123181328.10352avqtdet10oo@webmail.uniud.it>
In-Reply-To: <20121123181328.10352avqtdet10oo@webmail.uniud.it>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [130.37.238.20]
Cc: ppsp@ietf.org
Subject: Re: [ppsp] peer protocol in WG last call
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: arno@cs.vu.nl
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, 29 Nov 2012 12:35:32 -0000
Hi Riccardo please see inline: On 23/11/2012 18:13, Riccardo Bernardini wrote: > > [Riccardo] > No specific protocol comes to my mind. I checked the RFC 6709 "Design > Considerations for Protocol Extensions" > (http://tools.ietf.org/html/rfc6709) for hints. In Section 4.1 there > is a list of possible solutions for protocol versioning. [...] > An alternative solution, where the option payload has a fixed length, > could be that A puts the numbers of the oldest and the newest > supported version and B picks one version in that interval. > I like the min/max versioning you propose here. I'll add a protocol option to hold the minimum version supported that is sent on the first HANDSHAKE in addition to the existing optional that will carry the max. The reply handshake will just have the existing version option that will contain the protocol selected by the receiver to use. If no common version is found, a closing HANDSHAKE is sent. I'll update the draft soon to accommodate your and Yunfei's suggestions. CU, Arno
- [ppsp] peer protocol in WG last call stefano previdi
- Re: [ppsp] peer protocol in WG last call Riccardo Bernardini
- Re: [ppsp] peer protocol in WG last call Arno Bakker
- Re: [ppsp] peer protocol in WG last call zhangyunfei
- Re: [ppsp] peer protocol in WG last call Riccardo Bernardini
- Re: [ppsp] peer protocol in WG last call Arno Bakker
- Re: [ppsp] peer protocol in WG last call zhangyunfei