[ppsp] [Technical Errata Reported] RFC7574 (4880)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 07 December 2016 03:04 UTC

Return-Path: <wwwrun@rfc-editor.org>
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 3115B12964C for <ppsp@ietfa.amsl.com>; Tue, 6 Dec 2016 19:04:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.098
X-Spam-Level:
X-Spam-Status: No, score=-107.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-2.896, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
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 oJQG9tLi7QE6 for <ppsp@ietfa.amsl.com>; Tue, 6 Dec 2016 19:04:22 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71B2E129629 for <ppsp@ietf.org>; Tue, 6 Dec 2016 19:04:22 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 59A6CB808B9; Tue, 6 Dec 2016 19:04:22 -0800 (PST)
To: arno@cs.vu.nl, r.petrocco@gmail.com, victor.grishchenko@gmail.com, spencerdawkins.ietf@gmail.com, ietf@kuehlewind.net, zongning@huawei.com, hishigh@sina.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20161207030422.59A6CB808B9@rfc-editor.org>
Date: Tue, 6 Dec 2016 19:04:22 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppsp/Cw6RLQfcaJQJ_h0ndnNsgousf9Y>
Cc: ppsp@ietf.org, shkim@etri.re.kr, rfc-editor@rfc-editor.org
Subject: [ppsp] [Technical Errata Reported] RFC7574 (4880)
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 07 Dec 2016 03:04:24 -0000

The following errata report has been submitted for RFC7574,
"Peer-to-Peer Streaming Peer Protocol (PPSPP)".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7574&eid=4880

--------------------------------------
Type: Technical
Reported by: Sung Hei Kim, Chang Kyu Lee <shkim@etri.re.kr>;

Section: 7.5

Original Text
-------------
   A peer MUST include the content integrity method used by a swarm.
   The code for this option is 3.  Defined values are listed in Table 4.

                   +--------+-------------------------+
                   | Method | Description             |
                   +--------+-------------------------+
                   | 0      | No integrity protection |
                   | 1      | Merkle Hash Tree        |
                   | 2      | Sign All                |
                   | 3      | Unified Merkle Tree     |
                   | 4-255  | Unassigned              |
                   +--------+-------------------------+

            Table 4: PPSPP Content Integrity Protection Methods

Corrected Text
--------------
   A peer MUST include the content integrity method used by a swarm.
   The code for this option is 3.  Defined values are listed in Table 4.

                   +--------+-------------------------+
                   | Method | Description             |
                   +--------+-------------------------+
                   | 0      | Unassigned              |
                   | 1      | Merkle Hash Tree        |
                   | 2      | Sign All                |
                   | 3      | Unified Merkle Tree     |
                   | 4-255  | Unassigned              |
                   +--------+-------------------------+

            Table 4: PPSPP Content Integrity Protection Methods

Notes
-----
As stated in the first sentence of chapter 7.5, “A peer MUST include the content integrity method used by a swarm.”, “No integrity protection” must not be one of the option for PPSPP content integrity protection method. Or, IETF 7574 must define PPSP-PP that does not use the integrity protection method.

The proposed is to remove option of “No integrity protection”  in Table 4.

Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party  
can log in to change the status and edit the report, if necessary. 

--------------------------------------
RFC7574 (draft-ietf-ppsp-peer-protocol-12)
--------------------------------------
Title               : Peer-to-Peer Streaming Peer Protocol (PPSPP)
Publication Date    : July 2015
Author(s)           : A. Bakker, R. Petrocco, V. Grishchenko
Category            : PROPOSED STANDARD
Source              : Peer to Peer Streaming Protocol
Area                : Transport
Stream              : IETF
Verifying Party     : IESG