Re: [Gen-art] Gen-ART review of draft-ietf-ppsp-base-tracker-protocol-10

"Huangyihong (Rachel)" <rachel.huang@huawei.com> Thu, 22 October 2015 07:46 UTC

Return-Path: <rachel.huang@huawei.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B30391B2AEF; Thu, 22 Oct 2015 00:46:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 URDlX2jyg1cN; Thu, 22 Oct 2015 00:46:22 -0700 (PDT)
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 089C81B2AD9; Thu, 22 Oct 2015 00:46:20 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml406-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CCW50239; Thu, 22 Oct 2015 07:46:19 +0000 (GMT)
Received: from NKGEML402-HUB.china.huawei.com (10.98.56.33) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 22 Oct 2015 08:46:18 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.75]) by nkgeml402-hub.china.huawei.com ([10.98.56.33]) with mapi id 14.03.0235.001; Thu, 22 Oct 2015 15:46:11 +0800
From: "Huangyihong (Rachel)" <rachel.huang@huawei.com>
To: "Vijay K. Gurbani" <vkg@bell-labs.com>, "draft-ietf-ppsp-base-tracker-protocol@tools.ietf.org" <draft-ietf-ppsp-base-tracker-protocol@tools.ietf.org>
Thread-Topic: Gen-ART review of draft-ietf-ppsp-base-tracker-protocol-10
Thread-Index: AQHRB3hlmatfku85fEqLfpzRVOxWEJ53JTvg
Date: Thu, 22 Oct 2015 07:46:11 +0000
Message-ID: <51E6A56BD6A85142B9D172C87FC3ABBB864448CF@nkgeml501-mbs.china.huawei.com>
References: <561FF20B.1030302@bell-labs.com>
In-Reply-To: <561FF20B.1030302@bell-labs.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.136.79.189]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/gen-art/i9yPlHc1Auh5DoUR7AuotVc4GNI>
Cc: General Area Review Team <gen-art@ietf.org>, "draft-ietf-ppsp-base-tracker-protocol.chairs@ietf.org" <draft-ietf-ppsp-base-tracker-protocol.chairs@ietf.org>, "draft-ietf-ppsp-base-tracker-protocol.ad@ietf.org" <draft-ietf-ppsp-base-tracker-protocol.ad@ietf.org>
Subject: Re: [Gen-art] Gen-ART review of draft-ietf-ppsp-base-tracker-protocol-10
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2015 07:46:24 -0000

Hi Vijay,

Thank you for the review. Please see our replies inline starting with [Rachel]. 

BR,
Rachel

> 
> Document: draft-ietf-ppsp-base-tracker-protocol-10
> Reviewer: Vijay K. Gurbani
> Review Date: Oct-15-2015
> IETF LC End Date: Not known
> IESG Telechat date: Oct-15-2015
> 
> This document is ready as a Proposed Standard, however, it does have some
> minor comments and nits that I detail below.
> 
> Major: 0
> Minor: 3
> Nits:  9
> 
> Minor:
> - Generally speaking, I think one more round of edits for grammar and
>    clarity may not be a bad thing.

[Rachel]: Will do.

> 
> - S2, "The PPSP Tracker Protocol architecture is intended to be
>    compatible with the web infrastructure."  What is the "web
>    infrastructure"?  How is it defined?  What does it mean to be
>    compatible with it?  Perhaps you meant that the PPSP TP is a request-
>    response protocol, which characterizes many "web protocols"?

[Rachel]: Right. Will fix it.

> 
> - S3.2.5, Table 4: "available_bandwidth  | Upstream Bandwidth
>    available" is this provisioned upload bandwidth or instantaneous
>    upload bandwidth?

[Rachel]: It's available instantaneous upload bandwidth. Will add some clarifications.

> 
> Nits:
> 
> - General comment: too much use of gratuitous capitalization (Request
>    message, Tracker, Peer etc.)

[Rachel]: Will fix it in the next version.

> 
> - S1.1, CHUNK is better defined as "An uniformly sized atomic subset of
>   the resource that constitutes the basic unit of data organized in P2P
>   ..."

[Rachel]: As for the terminologies. I think it's better to reference RFC6972. So maybe just delete those already defined in [RFC6972] and keep those new ones.

> 
> - S1.1, For uniformity when defining terms, you may want to think of
>   starting the definition of live streaming as "LIVE STREAMING: Refers to
>   ..."

[Rachel]: Ok.

> 
> - S1.1: The taxonomy of a peer into a leecher or a seeder appears to be
>    absolute.  In real swarms (BitTorrent), a peer trades chunks with
>    other peers, so it is a leecher but also a provider for certain
>    chunks.  This eventuality is not considered here.
> 
> - S1.2.1, what is the implication of the prefix "[Peer Protocol]" in the
>    numbered steps shown?  Is it a reference (using syntax like we use for
>    references), or is it implying that the protocol used by a peer in
>    these steps is the peer protocol?  If so, why not put the RFC/I-D
>    number of the peer protocol there?

[Rachel]: Sorry, it should be [RFC7574].

> 
> - S1.2.2, s/Once CONNECTed/Once connected/
> 
> - S2.2, what is an "action signal"?  Perhaps easier to simply say that
>    "This Request message is used when ..."  Same with "information
>    signal".
> 
> - S2.3.1, s/register on a tracker/register with a tracker/

[Rachel]: Accepted. Will fix them in the next version.

> 
> - S3.1, "turning the definitions for JSON objects extensible."  I cannot
>    quite parse that.  Sorry.

[Rachel]: This sentence should be deleted.

> 
> Thanks,
> 
> - vijay
> --
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq