[ppsp] 2 Comments on PPSP-TP

김성혜 <shkim@etri.re.kr> Thu, 01 October 2015 09:19 UTC

Return-Path: <shkim@etri.re.kr>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 73E691A0242 for <ppsp@ietfa.amsl.com>; Thu, 1 Oct 2015 02:19:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.711
X-Spam-Status: No, score=-99.711 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id lLNIOFO_fbLj for <ppsp@ietfa.amsl.com>; Thu, 1 Oct 2015 02:19:37 -0700 (PDT)
Received: from smtpeg.etri.re.kr (smtpeg2.etri.re.kr []) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20A4A1A0235 for <ppsp@ietf.org>; Thu, 1 Oct 2015 02:19:37 -0700 (PDT)
Received: from SMTP2.etri.info ( by SMTPEG2.etri.info ( with Microsoft SMTP Server (TLS) id 14.1.355.2; Thu, 1 Oct 2015 18:19:35 +0900
Received: from SMTP1.etri.info ([]) by SMTP2.etri.info ([]) with mapi id 14.01.0355.002; Thu, 1 Oct 2015 18:19:34 +0900
From: 김성혜 <shkim@etri.re.kr>
To: "ppsp@ietf.org" <ppsp@ietf.org>
Thread-Topic: [ppsp] 2 Comments on PPSP-TP
Thread-Index: AdD8KkkgkURYs+n7QCyZgwK71ZxdEw==
Date: Thu, 01 Oct 2015 09:19:34 +0000
Message-ID: <609FE8B8E7BD1248A27BD3B8BC699ABD1D7768E0@SMTP1.etri.info>
Accept-Language: ko-KR, en-US
Content-Language: ko-KR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_609FE8B8E7BD1248A27BD3B8BC699ABD1D7768E0SMTP1etriinfo_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/ppsp/l0J6kR7oa43sNEFOjFaRZJlmqus>
Subject: [ppsp] 2 Comments on PPSP-TP
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: <https://mailarchive.ietf.org/arch/browse/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, 01 Oct 2015 09:19:39 -0000

Dear All,

We have been observing the PPSP-TP draft for implementation.
I know that PPSP-TP is already submitted to IESG for publication.
However, we would like to make two comments on this draft.
(Is it too late? :) )

In clause 3.1,
"An array is indicated by two numbers in angle brackets, <min..max>, where "min"
indicates the minimal number of values and "max" the maximum. “

According to clause 3.3.3,
ppsp_tp_request_connect object is defines as follows;

     Object {
             [ppsp_tp_peer_num_t      peer_num;]
             [ppsp_tp_peer_addr_t     peer_addr<1..*>;]
             ppsp_tp_swarm_action_t   swarm_action<1..*>;
     } ppsp_tp_request_connect;

However, the example in clause is not in accordance with the definition of JSON notation in RFC7159.

The swarm_action is defined as an array.
But, the example shown in clause 4.1.1. which as 2 swarm_action objects are in different style (format) as the array defined in RFC7159.
==> Please see the example in clause 13 of RFC7159 which shows an exmple of JSON array containing two objects.

Clause should be modified as follows.

             "Swarm_action": {
                 "swarm_id":       "1111",
                 "action":         "JOIN",
                 "peer_mode":      "SEED"
             "Swarm_action": {
                 "swarm_id":       "2222",
                 "action":         "JOIN",
                 "peer_mode":      "SEED"

----------------Proposed modification--------------------------
        "Swarm_action": [{
                 "swarm_id":       "1111",
                 "action":         "JOIN",
                 "peer_mode":      "SEED"
                 "swarm_id":       "2222",
                 "action":         "JOIN",
                 "peer_mode":      "SEED"

The example for peer_addr is also defined in the same manner.
Needs to check rest of examples in the draft for similar changes.

Second comment is,
I've heard that JSON is case sensitive.

The ppsp_tp_request_connect object defines swarm_action which use lower-case 's'.
However, in the example, it use "Swarm_action" with upper-case 'S'.
I think swarm_action (or Swarm_action) should be aligned.

Hope all works well.