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

RFC Errata System <rfc-editor@rfc-editor.org> Fri, 01 July 2016 02:13 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 6CFA412D0D3 for <ppsp@ietfa.amsl.com>; Thu, 30 Jun 2016 19:13:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.048
X-Spam-Level:
X-Spam-Status: No, score=-104.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, 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 fvxSZU0IdB8q for <ppsp@ietfa.amsl.com>; Thu, 30 Jun 2016 19:13:00 -0700 (PDT)
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 C157212D0D9 for <ppsp@ietf.org>; Thu, 30 Jun 2016 19:13:00 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6F4C9B81048; Thu, 30 Jun 2016 19:13:00 -0700 (PDT)
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: <20160701021300.6F4C9B81048@rfc-editor.org>
Date: Thu, 30 Jun 2016 19:13:00 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ppsp/LkNcwGwbWLyVNZWHdgGbjI9pOuA>
Cc: ppsp@ietf.org, shkim@etri.re.kr, rfc-editor@rfc-editor.org
Subject: [ppsp] [Technical Errata Reported] RFC7574 (4724)
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: Fri, 01 Jul 2016 02:13:02 -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=4724

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

Section: 1.3

Original Text
-------------
swarm ID
Unique identifier for a swarm of peers, in PPSPP a sequence of
bytes. For video on demand with content integrity protection
enabled, the identifier is the so-called root hash of a Merkle
hash tree over the content. For live streaming, the swarm ID is
a public key.

Corrected Text
--------------
swarm ID
Unique identifier for a swarm of peers, in PPSPP a sequence of
bytes. For video on demand, the identifier is the so-called root hash
of a Merkle hash tree over the content. For live streaming, the 
swarm ID is a public key.

Notes
-----
According to chapter 5 and chapter 6.1, it seems that it is not mandatory to use content integrity protection scheme.
The definition of swarm ID in the original text does not define how the ID is used in environment with the content integrity protection disabled.
It is possible to add new description on how swarm ID is defined in the content integrity protection scheme is disabled. 
Or, it is possible to remove the parts regarding content integrity protection.

We propose to remove "with content integrity protection enabled" part.

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 (IESG)
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