IETF Logo Mail Archive

Re: [ppsp] FW: New Version Notification for draft-ietf-ppsp-reqs-04.txt

ZongNing <zongning@huawei.com> Thu, 29 September 2011 03:05 UTC

Return-Path: <zongning@huawei.com>
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 5CA211F0C3E for <ppsp@ietfa.amsl.com>; Wed, 28 Sep 2011 20:05:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.724
X-Spam-Level:
X-Spam-Status: No, score=-103.724 tagged_above=-999 required=5 tests=[AWL=2.648, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BxCNqBiIA3by for <ppsp@ietfa.amsl.com>; Wed, 28 Sep 2011 20:05:57 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id B8B391F0D3F for <ppsp@ietf.org>; Wed, 28 Sep 2011 20:05:57 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LS90087NKO4GD@szxga03-in.huawei.com> for ppsp@ietf.org; Thu, 29 Sep 2011 11:07:16 +0800 (CST)
Received: from szxrg02-dlp.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LS900JALKO492@szxga03-in.huawei.com> for ppsp@ietf.org; Thu, 29 Sep 2011 11:07:16 +0800 (CST)
Received: from szxeml203-edg.china.huawei.com ([172.24.2.119]) by szxrg02-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id ADZ16777; Thu, 29 Sep 2011 11:07:16 +0800
Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml203-edg.china.huawei.com (172.24.2.55) with Microsoft SMTP Server (TLS) id 14.1.270.1; Thu, 29 Sep 2011 11:06:42 +0800
Received: from SZXEML504-MBS.china.huawei.com ([169.254.8.252]) by szxeml410-hub.china.huawei.com ([10.82.67.137]) with mapi id 14.01.0270.001; Thu, 29 Sep 2011 11:06:41 +0800
Date: Thu, 29 Sep 2011 03:06:40 +0000
From: ZongNing <zongning@huawei.com>
In-reply-to: <4E83DC40.3060300@mti-systems.com>
X-Originating-IP: [10.138.41.128]
To: Wesley Eddy <wes@mti-systems.com>
Message-id: <B0D29E0424F2DE47A0B36779EC666779533D47@szxeml504-mbs.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset="us-ascii"
Content-language: zh-CN
Content-transfer-encoding: 7bit
Accept-Language: en-US, zh-CN
Thread-topic: [ppsp] FW: New Version Notification for draft-ietf-ppsp-reqs-04.txt
Thread-index: AQHMfk35WEs8oss1tUiXDRPbHvxJ3pVjohUA//9/cwCAAIdZwA==
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
X-CFilter-Loop: Reflected
References: <B0D29E0424F2DE47A0B36779EC666779532696@szxeml504-mbs.china.huawei.com> <4E79930E.5020509@cs.vu.nl> <B0D29E0424F2DE47A0B36779EC666779533C74@szxeml504-mbs.china.huawei.com> <4E83D533.5050007@mti-systems.com> <B0D29E0424F2DE47A0B36779EC666779533CC6@szxeml504-mbs.china.huawei.com> <4E83DC40.3060300@mti-systems.com>
Cc: "ppsp@ietf.org" <ppsp@ietf.org>
Subject: Re: [ppsp] FW: New Version Notification for draft-ietf-ppsp-reqs-04.txt
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
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, 29 Sep 2011 03:05:58 -0000

See inline.

-----Original Message-----
From: Wesley Eddy [mailto:wes@mti-systems.com] 
Sent: Thursday, September 29, 2011 10:47 AM
To: ZongNing
Cc: ppsp@ietf.org
Subject: Re: [ppsp] FW: New Version Notification for draft-ietf-ppsp-reqs-04.txt

On 9/28/2011 10:33 PM, ZongNing wrote:
> Hi, Wesley,
>
> Just to be clear, you agree with Arno or me? It seems to me that you actually agree with me.
>
> Here is Arno's opinion:
> " I think we need to make the requirements for simple trackers and for smart trackers more explicit."
>
> Here is my opinion:
> " Since there is no such definition like "simple tracker" and "smart tracker" in industry, I prefer NOT to define these terms in PPSP WG. For a requirement draft, we can just use the words - "MUST", "SHOULD", "MAY" etc to differentiate which are necessary (for basic inter-op) and which are preferred."


I think the options are to either:

- explicitly define simple versus smart trackers (as Arno suggested)

or

- think about dropping the "smart" terminology in the one place it
occurs (this may be what you're suggesting, with properties for smart
trackers as SHOULDs, but I wasn't sure that was exactly what you meant
or not)

[ZN]: I mean dropping the "smart" term and using the SHOULDs.
I am not in favor of defining smart tracker by ourselves in requirement spec, as I haven't seen clear demarcation of simple tracker and smart tracker in industry (on the contrary, we do see clear role of peer and tracker in existing P2P applications). Please correct me, if anybody does see clear definition of smart tracker. Thanks.

BR,
Ning Zong

-- 
Wes Eddy
MTI Systems

v2.23.0 | Report a Bug | By Email